Learn · International payments
Cross-border business payments: a practical pre-flight checklist
Use this cross-border payment checklist to verify beneficiary details, bank codes, purpose data, fees, approvals, fraud controls, and remittance references.
On this page
In short
What should a business check before making a cross-border payment?
Verify the commercial obligation, beneficiary identity, exact account name and number, destination-specific bank identifier, payment currency and purpose, any intermediary instruction, charge allocation, and the recipient’s expected net amount. Confirm bank-detail changes independently, screen the transaction under your compliance process, preserve approvals, and send a complete invoice reference. The correct data set depends on the corridor and rail, so obtain the beneficiary’s official instructions and validate them with the sending institution before release.
The pre-flight checklist
Complete these eight gates before release
1. Establish the obligation
Match the beneficiary legal name, invoice number, purchase order or contract, goods or services, amount, currency, due date, and entity that owes the money. Resolve duplicates, credit notes, and disputed quantities before creating the payment.
2. Collect instructions from an authoritative channel
Use a signed contract, verified vendor portal, bank letter, or previously validated master record. Treat emailed changes as unverified until confirmed through a trusted phone number or contact path that did not come from the change message.
3. Validate the destination identifiers
Check whether the corridor requires an IBAN, account number, SWIFT/BIC, national clearing code, branch code, or combination. Validate structure and bank identity, then confirm the account belongs to the intended beneficiary through your approved process.
4. Confirm currency and conversion
Make the instruction match the invoice currency unless an authorized amendment says otherwise. Record who converts, the executable rate, explicit fees, expected deductions, and the beneficiary’s expected net amount.
5. Supply regulatory and purpose data
Ask the sending bank or provider what beneficiary address, originator data, payment purpose, purpose code, tax documentation, or supporting invoice the specific route requires. Do not guess a code from a generic description.
6. Apply fraud and compliance controls
Independently verify changed instructions, screen under the company’s risk-based sanctions and financial-crime process, investigate name or country alerts, and keep maker-checker or dual approval for material payments.
7. Review execution details
Confirm rail, intermediary instruction if needed, charge code, cutoff, value date, holiday impact, provider limit, available balance, approval deadline, tracking method, and what happens if the payment is rejected or returned.
8. Make reconciliation possible
Include the invoice or customer reference in the structured remittance field, retain the confirmation and trace identifier, notify the beneficiary securely, and assign an owner to investigate a short, late, or unapplied receipt.
Know which identifier answers which question
| Identifier | What it identifies | Pre-flight use |
|---|---|---|
| SWIFT/BIC | A business party, commonly the beneficiary bank | Check bank identity, country, location or optional branch element, and route requirements |
| IBAN | A bank account under a country’s registered ISO 13616 format | Check country-specific length and structure; use only where the destination issues IBANs |
| IFSC | An Indian beneficiary bank branch for routes such as RTGS | Confirm the beneficiary bank branch with the recipient and sending institution |
| ABA/RTN | A US bank routing identifier for applicable domestic instructions | Do not substitute it for the destination’s international or local requirement |
| Local clearing code | A bank or branch within a national system | Use the destination’s requested format, such as BSB, sort code, CLABE, or another supported code |
| Account number | The beneficiary account within its banking system | Match it exactly with the beneficiary name and required bank identifiers |
SWIFT says a BIC uses an eight-character core under ISO 9362: a four-character business-party prefix, two-letter country code, and two-character party suffix. An optional three-character branch identifier can supplement it. SWIFT also warns that some BICs are non-connected reference identifiers with no right to exchange messages on the SWIFT network. That is one reason a code-format match alone is not proof that a proposed route will execute.
ISO appointed SWIFT as the registration authority for ISO 13616 national IBAN formats. The registry describes each participating country’s structure, and the registration procedure allows a maximum IBAN length of 34 characters. Use the country’s registered pattern as a structural check, but obtain the actual IBAN from the account holder or its bank. Never construct a live beneficiary IBAN from examples.
For an Indian domestic RTGS instruction, the Reserve Bank of India says the remitter should have the beneficiary name, account number and type, plus the beneficiary bank branch name and IFSC. A cross-border provider may request additional international information. Therefore, validate the IFSC for the exact branch and ask the sending institution which fields its international-to-India route needs.
Intermediary banks and charge instructions
An intermediary bank is not universally required as a field. Wells Fargo’s wire FAQ says SWIFT/BIC routing generally routes wires without intermediary details, while some cases require them. If the beneficiary’s bank supplies an intermediary instruction, preserve its bank name, BIC or clearing data, account-for-credit details, and currency exactly as provided. If your form has an intermediary field but the beneficiary instructions do not, ask the bank rather than filling it by inference.
Who bears transaction charges?
| Feature | Charge instructionSWIFT definition | Operational checkBefore release |
|---|---|---|
| OUR | Payer bears all transaction charges | Ask whether the beneficiary amount is guaranteed in this corridor |
| BEN | Payee bears all transaction charges | Warn that deductions may create an invoice shortfall |
| SHA | Charges are shared between sender and receiver | Agree how each side records fees and short receipts |
The allocation code does not establish the amount of every charge. Confirm how the sending bank implements it for the selected route.
Purpose-of-payment codes are corridor data, not memo text
The BIS Innovation Hub explains that AML/CFT and foreign-exchange rules in participating countries may require senders to declare the purpose of a cross-border payment, and that countries typically use different purpose-code lists. Missing required purpose data can stop or delay processing, so “professional services,” “invoice payment,” and “salary” cannot safely be converted into one universal code.
The most common causes of a bounce, hold, or delay
| Failure point | What to check before sending |
|---|---|
| Wrong beneficiary or account | Match legal name, account, invoice, approved master record, and independent confirmation |
| Wrong or missing bank code | Use the code type required by the destination and validate the exact branch or institution |
| IBAN copied with an error | Normalize spaces as the form requires, validate country length and checksum, and recheck against bank-issued instructions |
| Currency/account mismatch | Confirm the beneficiary account accepts the instructed currency and who converts |
| Missing purpose data | Obtain the corridor’s current purpose-code requirement from the executing institution |
| Compliance alert | Provide accurate party, address, purpose, and invoice data; escalate matches under the risk-based program |
| Missing intermediary instruction | Ask whether the corridor routes from the beneficiary BIC or needs a supplied correspondent |
| Unusable remittance reference | Put the agreed invoice identifier in the structured field and avoid ambiguous free text |
| Cutoff or holiday miss | Confirm submission cutoff, processing calendar, value date, and approval completion time |
SWIFT’s correspondent-banking analysis links manual intervention and delay to sanctions hits, returns, missing information, time-zone issues, and closed settlement systems. The practical response is not to promise a universal delivery time. Record the provider’s route-specific estimate, send before its stated cutoff, and retain enough data to trace the payment if it stops.
Do a total-cost and control sanity check
- Source-account debit and currency.
- Sending fee and any account-tier condition.
- Executable FX rate compared at the same time with an independent reference.
- Expected intermediary and receiving-bank deductions.
- Beneficiary net amount and who cures a short receipt.
- Expected delivery date, cutoff, holidays, return and repair handling.
- Internal approval, fraud verification, compliance review, and supporting records.
- Remittance quality and the staff work required to reconcile the payment.
If two quotes use different currencies or rate timestamps, they are not comparable. Normalize them to the same source amount or beneficiary amount, use a same-time reference rate, add explicit charges, and write down the expected net receipt. The FCA’s payment-pricing review specifically cautions against presentations that foreground low or zero fees while obscuring exchange-rate costs.
Fraud and sanctions checks belong before approval
For organizations within its scope, OFAC encourages a risk-based sanctions compliance program built around management commitment, risk assessment, internal controls, testing and auditing, and training. The framework says risk assessment may account for customers, counterparties, products, services, supply chains, intermediaries, transactions, and geographies. A checklist should route possible matches to qualified review rather than asking an AP operator to guess.
Frequently asked questions
Frequently asked questions
Do I need both an IBAN and a SWIFT/BIC?
Often for an IBAN-country wire, but the sending institution decides the required combination. The IBAN identifies the account under a national format; the BIC identifies a business party such as the bank. Ask for the beneficiary’s bank-issued instructions.
Does every country use IBAN?
No. SWIFT’s registry covers national formats registered under ISO 13616. Other destinations use local account and clearing identifiers, so never manufacture an IBAN for a country whose banks do not issue one.
Is a valid SWIFT code proof that the beneficiary account is genuine?
No. A structurally valid BIC can identify an institution or other business party, but it does not prove the named beneficiary owns the supplied account or that the proposed route is authorized.
When is an intermediary bank required?
Only when the chosen banks, currency, or corridor require one. Some routes can use the beneficiary bank’s BIC; others need explicit correspondent details. Follow bank-issued instructions and ask the sending institution when the field is unclear.
What is a purpose-of-payment code?
It is structured data describing the economic nature of a payment for processing or regulatory use. Lists differ by jurisdiction and direction, so select the current code through the executing bank or provider rather than reusing one by analogy.
How should I verify a vendor’s bank-detail change?
Use a trusted contact method independent of the change message, confirm the legal beneficiary and complete bank instruction, document who verified it, and retain dual approval. Do not use the phone number supplied only in the suspicious email.
What reference should go on the payment?
Use the invoice number or other identifier the beneficiary has agreed to reconcile, placed in the provider’s structured remittance field when available. Keep the transfer confirmation and trace reference separately for investigations.
Sources
External links open in a new tab.
- Business Identifier Code — SWIFT
- IBAN Registration Procedures — SWIFT
- IBAN Registration Procedures and data fields — SWIFT
- Wells Fargo Business Online Wires — Wells Fargo
- Digital Wires FAQs — Wells Fargo
- RTGS frequently asked questions — Reserve Bank of India
- Purpose codes for foreign-exchange transactions — Reserve Bank of India
- Project Nexus: Enabling instant cross-border payments — BIS Innovation Hub
- The Future of Correspondent Banking: Cross Border Payments — SWIFT Institute
- Commercial Invoice — US International Trade Administration
- A Framework for OFAC Compliance Commitments — US Office of Foreign Assets Control
- Business Email Compromise — Federal Bureau of Investigation
- International payment pricing transparency — UK Financial Conduct Authority
Written by
Glide Research
Payments research
Glide Research maps payment rails, FX corridors, and banking access so travellers, freelancers, and treasury teams can move money without legacy wire tax.
- Published
- Last reviewed
Glide · Borderless banking
Moving money across borders?
Hold crypto and 80+ currencies in one account, convert close to the mid-market rate, and pay out on local rails instead of paying the wire tax. Solo, or with multisig for teams.
- Currencies
- 80+
- Spend anywhere
- Visa card
- Registered with
- FINTRAC · Canada