How to reduce the risk of a bank returning an international payment

Bank return of an international payment is a situation where funds leave the company’s account, reach an intermediate link, and after a few days are returned with a fee and no result. Reasons almost always lie not in a technical fault, but in documentary or compliance logic: the bank, currency control, or correspondent bank lacked information, something contradicts between documents, or the operation fell under a sanction filter. Most of these risks can be mitigated in advance.

1. Consistency of contract, invoice, and payment order

The most common reason for return is the discrepancy of details or amounts between documents. Party names, jurisdictions, settlement currencies, product or service descriptions in the contract, specification, and invoice must match. The payment amount must exactly correspond to the invoice or an explicitly specified part of the contract. If partial payments are provided for—each transaction must be linked to a specific stage or a specific invoice, not «the contract as a whole».

2. Payment purpose

A correct payment purpose contains: a reference to the contract (number and date), a reference to the invoice or specification, a brief description of the transaction subject, and if necessary—the indication of the UNK and the code of the type of currency operation. Formulations such as «payment under contract», «fund return», «by agreement of the parties» without specificity increase the probability of suspension and request from currency control. If the payment is an advance, it is better to specify this directly in the purpose.

3. Counterparty verification

Before sending the payment, it makes sense to independently run the counterparty through sanction lists and check the basic public information: registration country, registration or tax number, legal address, website, industry. Special attention—on the recipient bank: its jurisdiction, inclusion in sanction lists, risk of correspondent bank refusal. If neither the supplier nor its bank has a public business history, the paying bank will almost certainly ask for an explanation, and the correspondent bank may return the payment without explanation.

4. Product and service description

Vague formulations are a frequent cause of additional requests. «Equipment», «components», «services» without clarification practically always require clarification. Sufficient specificity must be in documents and in the payment purpose: type, purpose, application area. This is important for both currency control and sanction screening, which sometimes triggers on keywords and HS code.

5. Consistency of amounts and timelines

The payment must correspond to the timelines stated in the contract: if the payment is advance, the planned delivery date should not look «infinite»; if the payment is based on fact, ideally, it should be supported by transport documents. The amount should not be significantly higher than the invoice; «rounding up» and overpayments raise questions. If the transaction is multi-party or includes an agent, it is important for the documents to clearly indicate who pays for what.

6. Prepared-in-advance explanations

Good practice is to prepare the operation’s business purpose explanation together with the payment package itself, without waiting for the bank’s request. In the explanation, the company briefly describes its activities, the counterparty, the transaction subject, the economics, and the logic of the settlement chain. This removes most of the counter-questions and significantly shortens the compliance passage time.

7. Sanction and country risk

Even technically clean payment may be returned by the correspondent bank if the country, currency, bank, or product falls into a zone of heightened attention. Before sending, it is worth evaluating not only direct sanction restrictions, but also indirect ones: correspondent bank restrictions, specific financial groups’ policies, and existing industry restrictions. If the settlement route looks questionable, it is reasonable to pre-work an alternative scheme, currency, or bank.

Checklist before sending

• Party details in the contract, invoice, and payment order match.
• Payment currency and amount correspond to the invoice.
• Payment purpose contains references to the contract and invoice, and the transaction subject description.
• Counterparty and its bank have been checked against sanction lists.
• Product or service description is sufficiently specific.
• UNK and the code of the type of currency operation are specified if necessary.
• A short business purpose explanation is prepared in case of a request.

Each of these points individually does not guarantee instant passage, but their combination significantly reduces the probability of return. Payment return is almost always a symptom that compliance did not receive the full picture of the operation. Providing it to the bank before the request—the cheapest insurance.