Yes! You can use AI to fill out RL360 Withdrawal Request

Joint policies or trusts require signatures from all individual owners, trustees, or authorized signatories. This is often missed when one person fills out the form on behalf of others, leading to immediate rejection of the request. To avoid this, ensure all required parties have signed the declaration section before submission, either with a wet signature or an approved digital signature. Tools like Instafill.ai can help manage the signing process by routing the form to all required signatories.

Users frequently make typos when entering long account numbers, IBANs, or SWIFT codes, or they provide a SWIFT code that isn't 8 or 11 characters long. These errors result in payment failure and significant delays as the funds are returned and the request must be re-processed. Double-check all banking information against a statement, paying close attention to the specific requirements for SWIFT codes (international) versus Sort Codes (UK). AI-powered form fillers can validate formats for IBANs and SWIFT codes to prevent such errors.

The form requires a copy of a bank statement if the payment is going to a new account, and may also require certified proof of identity and address. Applicants often forget to attach these documents, assuming the form itself is sufficient, which halts the process until the documents are received. To prevent delays, use the checklist on page 2 to confirm all necessary documents, like a recent bank statement or certified ID, are included with your submission.

Many people are unsure of their Tax Identification Number (TIN) or incorrectly answer the 'Specified US Person' question. This information is critical for international financial reporting (FATCA/CRS) and errors or omissions will cause the request to be flagged for follow-up, delaying the withdrawal. Before filling the form, locate your TIN (e.g., National Insurance Number, Social Security Number) and carefully read the definition of a 'Specified US Person' to ensure you answer accurately.

The form specifies a limited list of acceptable digital signature providers (e.g., DocuSign, AdobeSign) and requires the inclusion of the corresponding audit report. Users may use an unapproved service, paste a scanned image of their signature, or forget to include the audit trail, all of which invalidate the submission. Always use one of the approved digital signature platforms and ensure you download and attach the full audit report along with the signed form to prove its integrity.

Applicants sometimes create confusion by selecting 'One-off' withdrawal but also filling in details for regular withdrawals, or by entering both a fixed amount and a percentage. This ambiguity forces the processing team to seek clarification, causing delays. Carefully decide on your withdrawal type and complete only the relevant fields—either the 'One-off' amount or the details for 'Regular withdrawals' (frequency, dates, and either a fixed amount or a percentage, but not both).

Policyholders wishing to cash in their entire policy sometimes mistakenly use this withdrawal form. The form explicitly states it is not for full surrenders and that a separate 'Surrender Request' form is required. Using the wrong form leads to an automatic rejection and the need to start the entire process over with the correct paperwork, wasting valuable time. Always read the 'WHO IS THIS FORM FOR?' section first to confirm it matches your intention.

The form requires a clear explanation if the policyholder's country of residence is different from the country where the beneficiary bank account is held. This is an anti-money laundering (AML) check that is frequently overlooked by applicants. Failure to provide a reason will trigger a compliance review and delay the payment. If your bank is in a different country than your residence, provide a simple, clear reason in the 'Country connection' section, such as 'I maintain a bank account in my country of citizenship'.

The instructions clearly state to 'Please complete in BLOCK capitals throughout' and use a 'dd/mm/yyyy' date format, but these are easily missed. While it may not always cause a rejection, non-standard formatting can slow down data entry and processing. Taking a moment to follow these simple rules ensures clarity and helps expedite the request. Since the original is a non-fillable PDF, using a tool like Instafill.ai can convert it to a fillable version and help enforce formatting rules automatically.

A simple typographical error in the policy number is one of the most common and critical mistakes. Since the policy number is the primary identifier for the account, even a single wrong digit will prevent the system from locating the policy, causing the request to be rejected outright. Carefully copy the policy number from your official policy documents and double-check it before submitting the form. AI-powered tools like Instafill.ai can securely store and accurately autofill this number to prevent manual entry errors.