Bank inquiries about invoices how to prepare documents the way banks want

Nikita Veremeev

24.03.2026 | 6 min read

Updated: 24.03.2026

I have been leading COREDO since 2016. During this time the COREDO team has registered hundreds of companies in the EU, Singapore, the UK, Cyprus and Dubai, helped clients obtain crypto, payment, forex and banking licenses, and built AML and KYC practices for businesses that operate international transfers. And the larger the operations and the wider the geography, the more often owners and CFOs face banking requests for invoices and payment documentation.

I often hear the same question: how can you minimize bank requests for documents and speed up payment processing?

Answer lies not only in the relationship with a particular bank, but in the quality of the initial documentation, the transparency of the supply chain and the maturity of your compliance processes. In this article I’ll show how we structure our work to reduce bank rejections on international transfers, and I’ll provide templates, checklists and case studies that have worked for our clients.

Why do banks ask for invoices and documents?

Illustration for the section “Why banks ask for invoices and documents” in the article “Bank requests on invoices — how to prepare documents ‘as banks want’”

The bank bears regulatory AML obligations/CFT and sanctions compliance. Regulatory standards of the FATF, EU AML directives (AMLD) and local rules require banks to check transactions not formally, but substantively. Hence KYC for corporate payments, CDD/EDD, sanctions checks, transaction monitoring and the obligation to file a suspicious activity report (SAR) when there are doubts.

In international transfers the bank analyses the payment through the prism of TBML (trade‑based money laundering), assesses whether the price is inflated, whether there are non‑standard delivery routes, how the invoice is prepared and whether it complies with SWIFT/ISO 20022 requirements for details. Partner correspondent banks and payment corridors add their own filters, and the requirements of correspondent banking relationships are often stricter than the policy of your remitting bank.

Sanctions lists and sanctions compliance operate in real time. The bank screens the counterparty against sanctions lists, checks the beneficial owner (UBO) using public and commercial registers, and matches the declared activity to the transaction. Any gap in the logic of the deal prompts a bank review of payment documents.

KYC/CDD/EDD, UBO and residency

Illustration for the section «KYC/CDD/EDD, UBO and residency» in the article «Bank requests on invoices - how to prepare documents «as banks want»»

The client’s profile determines the depth of the check. Standard CDD includes identification of the legal entity, verification of the UBO, the director and controllers. EDD, enhanced Due Diligence, is triggered in cases of increased risk: complex ownership chains, offshore jurisdictions, sensitive product groups, new markets, large prepayments.

COREDO’s practice confirms: if you prepare a package of documents in advance for an AML check, you cut up to 70% of subsequent requests. The package includes corporate registration, articles of association and proof of tax residency, an extract from the beneficial owners register, supply agreements, commercial invoices, specifications, as well as your company’s AML policy and KYC/EDD processes for counterparties.

For international transfers, the bank often requests confirmations of the source of funds (source of funds) and the origin of goods (chain of supply). The response to a query about the origin of funds and goods should link the figures in the invoice with incoming cash flows and logistical documents.

Banks’ requirements for invoices and ISO 20022

Illustration for the section «Banks' requirements for invoices and ISO 20022» in the article «Bank queries on invoices - how to prepare documents ‘the way banks want’»

Formal requirements for the invoice for the bank are the foundation. An invoice loses trust if it lacks mandatory fields, or if the format or signatures raise doubts. In practice, banks look at:

Mandatory invoice fields for banks: number and date, seller/buyer (full legal names), addresses, registration numbers, tax identifiers, IBAN and BIC, currency and payment terms, Incoterms and place of delivery, description of goods/services, units of measure, quantity, unit price and total amount, references to contract/PO, UTR/UETR if necessary.
Compliance of the invoice with SWIFT/ISO 20022 requirements: synchronization of currency codes, correct address fields for MT103/ISO pacs.008, correct payment purpose (remittance information), matching names and addresses with the KYC profile.
Requirements for signatures and electronic signatures on invoices: a recognised electronic signature and eIDAS‑compatible e‑archiving for e‑invoicing, or a handwritten signature of an authorised person and a stamp (if applicable under the jurisdiction).
Requirements for invoice format (PDF, XML, Peppol): for e‑invoicing in the EU, Peppol BIS/UBL; for documentary checks: an immutable PDF/A, no low‑quality scans; XML structures welcome ERP integration and OCR.

I will note SEPA separately. Specifics of preparing invoices for SEPA payments include an IBAN in EU/EEA format, a correct BIC for cross‑border, indicating the payment purpose up to 140 characters and the absence of references to sanctioned terms. Incorrect details affect the return of the payment: an error in the IBAN or BIC immediately leads to a reject or a return with a fee and delay.

How to prepare an invoice for the bank

Illustration for the section «How to prepare an invoice for the bank» in the article «Bank requests for invoices — how to prepare documents “as banks want”»

Proper preparation of a commercial invoice for export: not about a “pretty template”, but about a precise connection to the contract and logistics. I recommend:

Include Incoterms (version and term), the point of risk transfer and the place of delivery. This reduces the risk of banks questioning proof of delivery.
Justify the currency and exchange operations in the invoice: state the contract currency, the rate (if you fix it), the conversion terms, to explain potential discrepancies in amounts during clearing.
Provide a reasonable justification for the price: references to the price list, quotations, links to the specification, and discounts. This speeds up the verification of goods value during bank checks and reduces TBML risk.
For shipments from warehouses in the EU, explicitly indicate the warehouse, batch number, item movement in the ERP, and the contact of the responsible 3PL. Banks increasingly request proof of the supply chain, and the storage location is part of that evidence.
For exports to Asia — state HS codes, product description in English, the contact of the customs broker and the expected route; these are best practices for preparing invoices for exports to Asia.

Our experience at COREDO has shown that linking the invoice to the Purchase Order and Spec ID, as well as to the payment’s UETR, increases clearing speed and reduces manual checks. Banks’ fraud-screening algorithms “read” invoices via OCR: clear tables, absence of handwritten corrections, and a standardized structure reduce false positives in AML monitoring.

What documents are required for a large payment?

Illustration for the section «What documents are required for a large payment» in the article «Bank requests on invoices — how to prepare documents “as banks want”»

The list varies, but there is a recurring core. The COREDO team regularly prepares such packages:

Supply agreement/commercial contract, specifications, invoice and proforma invoice.
Proof of shipment: bill of lading (B/L), air waybill (AWB), CMR, packing list, insurance policy.
Evidence of performance: acts, acceptance confirmations, confirmation letters from the counterparty, photos/certificates of quality.
Payment evidence: proof of payment: SWIFT MT103, UETR, sometimes CIN/ARN in acquiring, bank statements.
Documents to confirm the value of the goods: price lists, commercial offers, quotas, exchange/index quotations, an independent appraiser’s report for specific goods.
Corporate package: legal entity registration, articles of association, UBO register, tax residency confirmations, licenses (e.g., VASP, EMI/PI, forex), AML/KYC policy.
For advances: explanation of the prepayment model, guarantee instruments (SBLC/bank guarantee), escrow conditions. Banks’ requirements for advance payments under a contract are stricter; the bank expects strengthened security measures.

Bank document verification

The compliance department conducts banking according to AML‑Alert rules and internal scorings. AML risk scoring algorithms take into account country risk, industry risk, account behavior, as well as the results of sanctions checks in real time. If risk is elevated: EDD is triggered and additional documents are requested.

OCR and automatic invoice validation compare the invoice‑matching fields with the payment order and the client’s profile. Address mismatches, name discrepancies, odd descriptions or non‑standard formats trigger a manual review. counterparty checks by the bank for invoices include corporate registries, media screening and PEP – Politically Exposed Persons screening.

In trade finance the bank assesses compliance of the documentary terms of the letter of credit/guarantee, and also reconciles routes, dates and amounts. To facilitate payment verification in trade finance, it is important to synchronize the invoice, transport documents and the letter of credit terms before issuance.

How to respond to a bank inquiry about a payment

The speed and accuracy of the response determine how long clearing will take. The solution developed at COREDO is to create an SLA with the bank for handling documentary queries and an internal regulation specifying who prepares the substantive response and within what timeframes. Below are practical elements.

How to answer a bank’s payment inquiry: briefly state the context of the transaction, attach a structured package, highlight the invoice’s compliance with the contract and logistics, provide a link to UETR/MT103.
Sample response to a bank’s invoice query: “We confirm that the payment under contract No.… dated … in favor of … corresponds to commercial invoice No.… dated … for the amount of … in the currency …. Delivery terms – Incoterms 2020, DAP, … address. Shipment is confirmed by AWB No.… dated … (copy attached). The price corresponds to specification No.… and the price list dated … (attached). The supplier company is identified, UBO: … (register attached), VASP license No.… (attached).”
Template for a bank response to invoice documents: 1) brief description of the transaction; 2) list of attachments; 3) reconciliation of amounts and dates; 4) explanation of currency and conversion; 5) contact of the responsible person.
How to conduct internal preparation for bank documentary requests: set up a checklist by transaction type, RPA to assemble the package from ERP/DMS, allocate an SLA window (e.g., T+1 business day) and response time KPIs.

In cases of requests about the origin of funds and goods, attach a scheme of cash flows and the logistics chain. If the matter concerns proof of payment, take into account banks’ proof-of-payment requirements: it is best to provide MT103 with a full set of fields and UETR, and for SEPA: confirmation with the End-to-End ID.

Reduce bank inquiries and speed up clearing

This combines processes, automation and team training. I will highlight six practices that COREDO’s approach leads to.

The practice of e‑invoicing and bank requirements: migration to Peppol BIS/UBL or compatible XML, issuance of immutable PDF/A and storage via e‑archiving. This strengthens trust and speeds up OCR validation.
Integration of ERP/CRM with invoice and payment preparation systems: synchronization of IBAN/BIC fields, Incoterms, HS codes, addresses. Invoice matching and reconciliation close gaps in amounts and dates.
Implementing RPA for handling bank inquiries: bots assemble the document package, pull MT103/UETR, collect transport waybills, and preserve an audit trail for internal control.
Solutions for automatic document verification (KYC SaaS) and reducing false positives: integrating sanctions checks on the client side, preliminary PEP screenings and counterparty scoring algorithms.
Corporate compliance policies and internal control: SLA and KPI processes for the compliance department, internal audit on handling bank inquiries, regular training of finance/compliance personnel.
ROI metrics from compliance automation: how to measure the economic effect of reducing bank inquiries — look at average TAT for response, share of payments without inquiries, clearing time, cost of manual processing, reputational risks and frozen liquidity.

When a CFO sees that the impact of correct invoice preparation on clearing speed is measured in hours rather than days, they can easily justify investments in RPA and KYC SaaS. It’s not just “paper for the sake of paper”, it’s working capital and the reliability of payment corridors.

Regional and product nuances

EU and SEPA: IBAN, BIC, account detail requirements, e‑invoicing and eIDAS. Banks pay attention to tax residency, economic substance and UBO registers. Particulars of invoice checks in supply chain finance channels: mandatory compliance with limits and factoring rules.
United Kingdom: focus on sanctions screening and SARs, strong EDD practice. ISO 20022 is being implemented; banks expect clean remittance data and reconciled addresses.
Singapore and Hong Kong: attention to TBML in trade routes and high‑risk goods, they prefer clear Incoterms and shipment confirmations.
Dubai/UAE: focus on source of funds, licenses and economic substance compliance; long supply chains raise additional questions.
Trade finance and factoring/invoice financing: requirements for proof of delivery and price are stricter than for a simple TT. Configure templates for letter of credit/guarantee in advance and link each field to the supporting document.

Banks’ requirements for foreign exchange operations and rate control have tightened: record FX logic in the invoice and contract, especially for SWIFT transfers in USD via US correspondent banks, where compliance filters are particularly strict.

Registration and licenses for banks

Registering a legal entity in the EU or Asia for banking purposes: it’s not just a registered address. The bank assesses economic presence: office, employees, directors, contracts and accounts, as well as whether the activity complies with licenses. The COREDO team has implemented projects where clients required EMI/PI licenses for payment services, VASP licenses for crypto services, forex registration and even Banking licenses in certain jurisdictions.

Banks’ requirements for beneficial owner (UBO) verification have become stricter: open registers, notarizations, apostilles, eIDAS signatures and video KYC. We build AML procedures for companies taking regulatory expectations into account and prepare policy documents so the bank can see the maturity of internal controls.

Documents are stored using electronic document storage and issuance tools compatible with e-archiving. This is important during audits, M&A and when preparing for requests related to large transactions, when historical invoices, tax confirmations for bank checks and proof of contract execution are requested simultaneously.

COREDO cases: what worked

Case 1. Successful passage of a bank review during an export transaction from the Czech Republic to Southeast Asia. The client supplied industrial equipment on FCA terms. The bank requested proof of payment, confirmation of the price, the route, and the beneficiaries. We linked the invoice to the specification and the price list, provided a discount calculation, attached the CMR and the insurance policy, and supplied the MT103 and UETR. Additionally, we prepared a letter explaining the currency and exchange operations. The payment went through within 24 hours, and the bank lowered the client’s risk level in the client profile.

Case 2. A crypto service licensed in Estonia with payment infrastructure in the EU and the UK. The bank’s requests concerned KYC for corporate payments and AML checks of partner invoices. We implemented a KYC SaaS, standardized the invoice format (PDF/A + XML), defined an EDD policy for high-risk counterparties, and set up real-time sanctions screenings. The number of requests fell by 53%, and clearing time was reduced from 2.1 days to 10 hours.

Case 3. A group with offices in Slovakia and Singapore, exporting components to Asia. The goal was to speed up VAT refunds and reduce documentary queries on SEPA and SWIFT. We moved invoicing to Peppol, implemented OCR validation and RPA for package assembly, trained the finance/compliance team, and established an SLA with the bank for T+1 responses. The effect of correct invoice preparation on clearing speed became tangible: delays almost disappeared, and frozen liquidity decreased by 18%.

Checklists and templates

Checklist: mandatory details of a commercial invoice for European banks

Number, date, parties with addresses, registration and tax IDs.
IBAN, BIC, currency, payment term and conditions.
Description of goods/services, quantity, price, amount, ISO currency code.
Incoterms (version, term, place), HS codes for export.
Reference to contract/PO, Spec ID, responsible contact.
Signature/electronic signature, e-archiving.
Linkage to UETR/End-to-End ID if required.

Checklist: how to prepare a document package for AML checks

Company registration, articles of association, UBO register, tax residency.
Contract, invoices, specifications, price lists.
Proofs of delivery: B/L, AWB, CMR, packing list, insurance.
Evidence of price and market value, quotations.
Proof of payment: MT103, UETR, bank statements.
AML policies/KYC, CDD/EDD procedures, monitoring logs.

Template response to the bank regarding invoice documents

Introduction: payment identifier, amount, date, counterparty.
Transaction description: subject, Incoterms, timelines, delivery.
Documents attached: contract, invoice, transport documents, confirmations.
Justification of price and currency: links to price lists/quotations, exchange rate/FX terms.
Proofs of payment: MT103, UETR, statement.
Responsible contact and SLA for providing additional materials.

Turnkey COREDO support

I build the COREDO practice around predictability and transparency. For new markets the team handles registration and substance in the EU, the UK, Singapore or Dubai, and sets up banking relationships and documentation processes. During licensing (payment services, forex, VASP) we align regulator requirements with banks’ expectations so that after obtaining the license you don’t run into “unpreparedness” for KYC/AML monitoring.

The solution developed at COREDO for companies with recurring payments is a single playbook: invoice and contract templates, checklists for proof of delivery and proof of payment, bank response procedures, a document matrix by deal type, as well as compliance KPIs. We conduct an internal audit of bank query handling, set up SLA and KPI processes for the compliance department, train finance/compliance personnel and help measure the economic impact of reducing bank queries.

In sanction-risk situations we structure interaction with the bank: agreed contact points, clear escalation paths, scenarios for SAR situations and preventive counterparty checks. If you are preparing for a large deal or M&A, we assemble an electronic data room in advance: invoices, acceptance certificates, e-invoicing logs, licenses, tax confirmations and corporate documents, so that the bank and counterparties see that things are orderly and under control.

Invoice and compliance as an accelerator

Banks do not slow down business on purpose; they are fulfilling a regulatory mandate. When the invoice and the document package meet the bank’s requirements, SWIFT/ISO 20022 and the logic of the transaction, payments go through quickly and inquiries are minimized. When KYC/CDD/EDD and e‑invoicing processes are embedded into your operations, you control TBML risk, eliminate unnecessary “manual” checks and free up working capital.

The COREDO team has gone through dozens of different scenarios with clients – from SEPA payments for regular supplies to complex corridors involving multiple correspondent banks. I see how discipline in documentation and pre-established SLAs with the bank turn complex compliance into a competitive advantage. If you are planning expansion into the EU, the UK, Singapore or Dubai, want to obtain a financial license or build a mature AML function – engage onshore experts. This way you will avoid lengthy checks, preserve your reputation and gain predictability in international payments.