How to Organise an Internal Response When a Bank Requests Supporting Documents for a Cross-Border Payment

When your bank asks for additional documents to support a payment, the real problem is often not whether a contract exists. It is that the contract, invoice, import records, internal approvals and payment instructions sit with different people. The most effective response is not to send a batch of scattered files immediately. Start by aligning the transaction facts, document versions and response narrative internally.

A common misunderstanding is that a bank document request is merely an administrative step, and that sending any contract or short explanation will be enough. In practice, banks may review the payment purpose, counterparty, flow of funds, delivery of goods or services, payment amount and account details together. If names, amounts, dates, currencies or paying entities do not match across the documents, this may lead to further questions and delay the payment process.

This article addresses how to organise an internal response. It does not replace a bank's, lawyer's, tax adviser's or licensed professional's assessment of a specific transaction.

Start by identifying what the bank is actually asking

Do not treat a document request simply as a request for more attachments. Break down the bank's questions and identify which part of the transaction background it is examining.

Common areas of focus include:

• Why the payment is being made: for goods, services, an intra-group arrangement, equipment leasing or another business expense;
• Who is supplying the goods or services, and whether the payer, contracting party, invoicing party and beneficiary are the same entity;
• How the payment amount was determined and whether it corresponds with the contract, purchase order, invoice, payment request or instalment arrangement;
• Whether goods have been imported, are in transit or have not yet been delivered; and whether services have a defined scope, delivery records or acceptance evidence;
• Whether an intra-group payment has a clear commercial purpose, explanation of the related-party relationship and internal approval records;
• Whether this is an initial payment, final payment, advance payment, top-up payment or recurring settlement.

Keep the bank's original questions and number them one by one. Your internal response should be organised around those questions, rather than around the way each department normally stores its files.

Appoint one transaction-document coordinator

A common failure point in cross-border payment document requests is that finance responds to the bank, procurement holds the contract, logistics has the bill of lading, the business team understands the actual delivery, and group headquarters holds the background for a related-party arrangement. Yet no one checks whether these pieces form one complete and consistent account of the transaction.

You can appoint one coordinator to collect documents, maintain version control, track gaps and manage the external response. This person does not need to make independent decisions on bank requirements. Their role is to ensure that every submitted document helps answer three basic questions: why is the payment being made, who is being paid, and what business activity does it relate to?

Responsibilities can be allocated internally as follows:

Task	Suggested internal owner	Output
Receive and break down the bank's questions	Finance or treasury team	List of requested items and response deadline arrangement
Explain the commercial background	Business owner or procurement lead	Transaction summary, business purpose and delivery status
Provide contract and order versions	Procurement, legal or contract management personnel	Executed contract, purchase order and addenda
Provide evidence of goods or service performance	Logistics, project or business team	Shipping, delivery, acceptance or service records
Reconcile amounts and payment arrangements	Finance and treasury team	Payment request, invoice and outstanding balance explanation
Final review before submission	Appointed coordinator and management	Document index, explanation of differences and response email

The coordinator's work is not limited to chasing documents. More importantly, the coordinator should identify situations where the files appear complete but do not tell a consistent story.

Build a minimum document pack by payment type

Different payment types require different explanations. Do not use one template for every payment, and do not submit a large volume of documents that have no connection to the transaction simply to appear comprehensive.

Payments for imported goods

For import payments, the commercial contract, purchasing arrangement, goods information and logistics status usually need to connect clearly. Before submitting documents, check whether the goods description, quantity, pricing terms, supplier name, importing entity and paying entity are consistent.

Documents that may be prioritised include:

• Executed purchase contracts, purchase orders and addenda;
• Supplier invoices or payment notices;
• Packing lists, shipping documents or records showing the status of the goods;
• If the goods have entered Sri Lanka, relevant import declaration, customs clearance or release documents;
• An explanation of the payment stage, such as an advance payment, payment on arrival or final payment;
• Where contract, invoice and payment amounts differ, an explanation of the reason and supporting basis for the difference.

If you have appointed a customs broker for the import process, the connection between records before and after payment becomes particularly important. You may also refer to the published article, “After Appointing a Customs Broker for Imports: How to Check Declarations, Duties and Release Status,” to avoid a disconnect between import records and the payment explanation.

Payments for overseas services

For service fee payments, the challenge is usually not producing an invoice. It is explaining what the service actually is, who performed it, what work output it brought to the Sri Lankan entity, and how the amount for this payment was calculated.

It is useful to organise service documents in three layers: agreement, performance and settlement.

• Agreement: service agreement, scope of work, quotation or project plan;
• Performance: project documents, work output, meeting records, progress reports, delivery confirmation or internal records showing use of the service;
• Settlement: service provider invoice, payment request, fee calculation explanation and internal approval records.

A common misunderstanding is that an invoice from group headquarters or another related party is enough to make payment directly. In practice, the related-party relationship does not replace an explanation of the transaction background. You still need clear records of the services, the benefiting entity, the pricing or allocation basis, and the relevant internal approvals.

Intra-group payments

Intra-group payments may involve management services, shared services, technical support, lending arrangements, fund transfers or other internal transactions. The required explanation and key documents vary by payment type. It is therefore not advisable to use “group charges” as the only payment purpose.

Confirm internally what the payment is defined as within the group; what commercial role the Sri Lankan entity performs; whether the payment is supported by a contract, board or management approval, internal policy or settlement basis; and whether the payment amount can be traced to a calculation schedule, invoice or settlement notice.

If the nature of the payment has not been clarified, discuss it with your appointed legal, tax and banking advisers before submitting the payment instruction. Do not describe different types of funding arrangements as one payment purpose merely to speed up processing. This can make later explanations, reconciliations and ongoing compliance management more difficult.

Complete a five-point consistency check before submission

Once the documents are collected, review at least the following five areas:

1. Entity consistency: Is the relationship between the contracting party, invoicing party, beneficiary and payer clear? If they differ, is there documentation that explains the arrangement?
2. Amount consistency: Can the contract amount, invoice amount, amounts already paid and the current payment request be reconciled? If there is a difference, does the explanation cover exchange rates, instalments, discounts, freight or other adjustment factors?
3. Business consistency: Do the contract description, invoice description, payment purpose and actual goods or services use the same terminology?
4. Timing consistency: Can the contract date, service period, invoice date, shipment or delivery date and payment stage be explained as a coherent sequence?
5. Version consistency: Are you submitting the final executed documents or draft versions? If there are addenda, amended orders or corrected invoices, is it clear which document is currently effective?

This check helps prevent a common problem: the business team submits an older contract, finance makes payment based on a revised quotation, and the supplier invoice uses a different service description. Each document may appear reasonable on its own, but together they can be difficult to explain.

Send a one-page transaction summary with the documents

In addition to the attachments, prepare a concise one-page transaction summary to help the bank understand how the documents relate to each other. It does not need to be a legal opinion, and it should not include unconfirmed regulatory conclusions.

The summary can include:

• The nature of the transaction and payment;
• The payer, beneficiary and their relationship;
• The contract or order name, signing date and core business content;
• The payment amount, currency and payment stage;
• A list of documents provided;
• A brief explanation of any differences in names, amounts or entities;
• An internal business contact who can clarify operational matters.

Avoid two approaches when responding. The first is sending an email that only says “please see attached,” leaving the bank to piece together the transaction background. The second is removing important differences to make the situation look simpler. The first often creates more back-and-forth. The second may cause a larger issue if further documents are requested later.

Turn each document request into a lasting process

After completing a document request, record the questions raised by the bank, the final document list used and the internal time spent. Then create a basic transaction file for each recurring cross-border payment type and archive it by transaction number or supplier number.

For recurring import purchases, technical service fees or intra-group settlements, you can set pre-payment checks in advance: whether the contract has been signed, whether the invoice has been received, who holds delivery evidence, who confirms the payment purpose, and who will coordinate any bank document request. This will not guarantee that the bank will not ask further questions. It can, however, reduce last-minute document searches, version confusion and repeated internal confirmations.

Whether a payment is processed, and the pace of processing, remains subject to the bank's review of the specific transaction and supporting documents. Your internal goal should be simpler: when the bank asks a question, you can provide a clear response based on one consistent set of facts, one document index and one accountable coordinator.

This content is provided for general information only and does not constitute legal, tax or immigration advice. Specific requirements should be confirmed based on the latest guidance from the relevant Sri Lankan authorities and appointed licensed professionals.