How to Respond to Additional Information Requests When Opening a Business Account

When a bank or EMI comes back with additional questions after an application has been submitted, start by identifying what it needs to verify. Compare the request with the original company profile, select the relevant supporting evidence, and explain how each document answers the question. Address missing information and changes explicitly, then check the response as one complete package before sending it.

A request for additional information is not always a request for more documents. It may be an attempt to close a specific information or verification gap.

For a corporate service provider, onboarding consultant or internal team managing client applications, the challenge is to make the case understandable to someone encountering the business for the first time. The reviewer may know banking requirements well without knowing the client's industry, terminology or commercial arrangements.

Treat the exchange as a practical effort to establish whether the provider can serve the company. Help the reviewer understand the facts and the evidence needed for a decision. Additional verification is not, by itself, evidence of a poor application or an impending rejection.

Four principles should guide the response:

• Explain what may not be obvious. Translate specialist terms and connect trading names, services and legal entities.
• Link each answer to evidence. Identify the relevant document, page or clause and state what it confirms.
• Make differences visible. Explain changes, discrepancies and unavailable documents instead of leaving the reviewer to infer their meaning.
• Invite a precise follow-up. Ask whether the response addresses the requested point and what else is needed, including the required format.

The workflow is straightforward:

For preparation before submission, see our corporate bank account opening documents guide. The process below starts when the provider returns with follow-up questions.

Understand what the request is asking you to clarify

A bank asking for additional information may need a fuller explanation, documentary support, or clarification of information that appears inconsistent. A request for information (RFI) can concern one statement or several connected parts of the case.

Read the exact wording before requesting more material from the client. Identify the fact being checked and whether the request specifies a document, an explanation, or both. Use this table to locate the relevant part of the case.

These are possible forms of evidence, not a universal submission checklist. Follow the provider's conditions on document type, date, signatures, certification and format.

If the request is ambiguous, clarify its scope. A question about “funding”, for example, may need clarification about which funds or period it concerns. A narrowly framed clarification is more useful than sending a broad collection of unrelated documents.

Break the request into answerable questions

One paragraph can contain several KYC follow-up questions. A request about expected payments may ask for amounts, frequency, countries and counterparties. Answering only the amounts leaves the other points open.

Turn the request into a working list, preserving its original order. For each question, record:

• the fact or verification point being addressed;
• the relevant information and evidence already submitted;
• any additional answer or document needed from the client;
• the person responsible and the response deadline, if one is given.

Separate information that exists but needs explaining from information that genuinely needs to be obtained. This helps avoid asking the client for documents the team already holds.

Where several people contribute, assign one person to assemble the final response. That person should check that the answers use the same company details, figures and assumptions throughout.

Check the answer against the original application

Compare the proposed response with the version actually submitted. A team's current understanding of the client may contain updates that the reviewer has not seen.

Check the business description, website, turnover, geography, transaction profile, ownership structure and source of funds. Compare like with like: the same period, currency, entity and type of figure. Keep actual results distinct from forecasts.

If something has changed, explain what changed and when. If the original application was wrong, correct it explicitly. Consistency means presenting an accurate, coherent account, including any necessary corrections.

Connect the website and the legal entity

A practical point to check is whether the website can be linked to the applicant. A site may use a brand while contracts, invoices and the application use the registered company name.

Check the footer, contact page or legal information page for an accessible explanation of that relationship. If the site belongs to another group entity, state that accurately. The reviewer should not have to infer which company provides the services or enters into contracts.

A submitted website should clearly describe the business and its services. Depending on the provider's requirements, evidence of domain ownership may also be requested if the website's connection to the applicant cannot be verified. [1]

Reconcile service descriptions and amounts

An invoice may name one technical stage of a service described more broadly in the application. Explain how the stage relates to the declared activity and the relevant agreement, order or statement of work.

Check the calculation too. If a contract records EUR 10,000 but an invoice shows EUR 9,000, identify the reason. If a signed variation records a 10% discount, reference it and show the calculation. If no such record exists, do not describe the adjustment as documented.

These are fictional illustrations. In a real case, the explanation must match the actual records. A covering letter cannot replace a missing agreement about material commercial terms.

Choose evidence that supports the specific answer

Once the verification point is clear, select evidence that supports the answer. A bank asking for additional documents may need a particular form of proof; it may also need help finding information within documents already provided.

For every attachment, ask: what does this establish, and where can the reviewer see it?

Together, these records can explain a transaction, but the relevant combination depends on the actual request.

There is no universal “strongest evidence package”. Depending on the provider, acceptable evidence may include an invoice with a matching bank statement or a signed customer contract, subject to requirements such as document date and signature. Confirm which option addresses the request; there is no need to treat every possible form of evidence as a required attachment. [2]

Explain the relevance of evidence already submitted

If the necessary document is already in the case, point to its exact location and explain why it addresses the question. Resubmit it where requested or useful, while making clear whether it is unchanged or updated.

If a document supports only part of the answer, state that limit. A counterparty's registry entry helps identify the company; it does not establish that the applicant has a commercial relationship with it. A project screenshot may illustrate work in progress without establishing its price, acceptance or payment.

Where requested material contains confidential client information, identify the restriction and discuss an acceptable form of evidence. An authorised extract, agreed redactions or acceptance records may be options, depending on the circumstances. Check both what may be disclosed and what the provider will accept; an NDA does not automatically resolve either question.

Explain missing documents directly

Address every requested document, including those the client cannot provide. Explain whether it has not yet been created, does not apply to the company, or is unavailable for another reason. Identify the relevant alternative and ask whether the provider can accept it.

Newly incorporated and pre-trading companies

A company without invoices, turnover or transaction history should state its actual stage of development. A signed customer agreement can show a concrete commercial commitment even though no work has yet been completed or paid for.

The customer's legal name, registry reference and website can make the counterparty easier to identify. Explain why those materials are included and what the agreement itself establishes.

If no signed agreement exists, ask which alternatives the provider accepts. A business plan, investor pitch or letter of intent serves a different evidential purpose from a completed transaction. For some newly incorporated businesses, a business plan or investor pitch may be accepted, subject to the provider's eligibility and document requirements. Confirm this for the specific onboarding route. [3]

If a document is expected later, give a realistic availability date where known. Keep historical figures, contractual commitments and projections clearly distinguished.

Documents with different names across jurisdictions

An apparently missing document may be a terminology issue. A bank's checklist can use names familiar in its own jurisdiction while the applicant holds differently structured local records.

Explain the document's official title and function, then map the requested information to its actual sections. If one document addresses two requested points, show both connections explicitly and ask whether it satisfies the requirement.

UK guidance distinguishes a Memorandum of Association, recording the initial subscribers' agreement to form the company, from Articles of Association, setting out rules for running it. [4] Singapore's newer framework uses a Constitution: ACRA describes the reform as merging the memorandum and articles, and its current forms page identifies the old M&AA sample as applicable to incorporations before 3 January 2016. [5]

If a Singapore company receives a request for “Memorandum and Articles”, explain the constitutional document applicable to that company and identify the relevant provisions. This does not establish that it replaces separately requested incorporation or ownership evidence.

A similar issue arises with activity codes. Compare the definitions and classification versions, not just the numbers:

Sources: Statistics Singapore and Companies House. [6][7]

For a company developing business software, UK code 62012 may help explain the scope of its Singapore activity. This is an illustrative comparison, not an official one-to-one equivalence. State the company's actual registered code and describe its operations in plain language; explain any overlap or differences relevant to the question.

Make the response easy to review

Follow the order of the incoming request. Make each answer understandable without requiring the reviewer to reconstruct it from several attachments.

A useful response structure is:

Question: Repeat or accurately summarise the requested point.

Answer: Give the direct answer, followed by necessary context.

Supporting evidence: Name the file and relevant page or clause, and explain what it confirms.

Change or gap, if relevant: Explain a correction, update, unavailable document or proposed alternative.

For the software example above, the response might read:

This is fictional response wording, to be adapted to the actual request and evidence.

Keep explanations proportionate. A straightforward point may need two sentences; a complex ownership chain or payment arrangement may need more. Use filenames that identify the entity, document and relevant date or reference.

Submit through the provider's specified channel. Where possible, send a coordinated package. If some items remain outstanding, identify them and follow the provider's instructions for supplying them separately. If the stated deadline cannot be met, raise this before it passes and request an extension.

Review the package as a whole before sending

KYC additional information requests can involve several contributors and overlapping documents. Individually correct answers may still conflict when assembled into one response.

Read the final package against both the request and the original submission. Check that:

This final check addresses avoidable reasons for another follow-up request: partial answers, unexplained attachments, conflicting figures, incomplete ownership chains and evidence whose relevance remains unclear. It cannot eliminate requests arising from the provider's own review requirements.

After submission, retain the exact response and attachments in the case record. Log what was sent, when, which company-profile facts were updated and what remains outstanding. Preserve the original submission so future reviewers and colleagues can follow the changes.

The working sequence should remain traceable:

A clear response lets the reviewer understand the company's activity, see what supports each answer and identify anything still unresolved. It also gives the team a reliable record for the next stage of the case.

About the author

Alexander Blinov is the founder of OnboardOS. His experience spans corporate legal services, KYC/AML and onboarding international companies with banks and EMIs. He is developing OnboardOS to help corporate service providers gather client information, identify evidence gaps and prepare coherent account-opening submissions.