Finance Index
How do international vendor payments work, and who carries the FX risk?
Reference guide to international payments FX basics, including payment timing, method choices, control points, reconciliation, and vendor communication.
International vendor payments move via SWIFT wires through correspondent banks or via local in-country rails (SEPA, BACS, EFT). You can pay in the vendor's local currency (you carry the FX conversion) or in USD (the vendor's bank converts, often at a worse rate, and the vendor effectively carries it). Local-currency on local rails is usually cheaper and more reliable than a USD SWIFT wire.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| How do international vendor payments | International vendor payments move via SWIFT wires through correspondent banks or via local in-country rails (SEPA, BACS, EFT). | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | Pay in local currency and you lock the conversion on your side - the vendor receives the exact agreed amount, and you bear the rate. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Where do providers hide margin | In the spread - the difference between the wholesale interbank rate and the rate you're quoted. | Keeps vendor records and payment decisions reliable. |
| Iban | IBAN identifies the account in most of Europe and many other countries; SWIFT/BIC identifies the bank for cross-border routing; the UK uses sort codes, the US uses ABA routing numbers. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | The provider quotes a rate (interbank rate plus a spread), you accept it within a validity window, and the payment executes at that locked rate; the executed rate should post to your ERP so the GL matches what the bank actually charged. | Reduces payment errors, timing issues, and reconciliation cleanup. |
Who carries the FX when I pay in usd vs local currency?
Pay in local currency and you lock the conversion on your side - the vendor receives the exact agreed amount, and you bear the rate. Pay in USD and the vendor's bank converts on arrival at a rate you don't control, often deducting fees, so the vendor receives an uncertain amount. For predictable vendor relationships, paying in local currency on a local rail is the cleaner choice.
Where do providers hide margin in the FX rate?
In the spread - the difference between the wholesale interbank rate and the rate you're quoted. A "no-fee" international payment often carries a wide spread that costs more than an explicit fee would. Always compare the all-in rate (spread included) against the mid-market rate, and ask whether the quoted rate is executable and how long it holds.
What are iban, swift/bic, sort codes, and routing numbers - what does each country require?
IBAN identifies the account in most of Europe and many other countries; SWIFT/BIC identifies the bank for cross-border routing; the UK uses sort codes, the US uses ABA routing numbers - each destination country requires a specific field set, which is why country drives the required data.
How do FX rates get applied to AP payments?
The provider quotes a rate (interbank rate plus a spread), you accept it within a validity window, and the payment executes at that locked rate; the executed rate should post to your ERP so the GL matches what the bank actually charged.
What is swift gpi and can it tell me where a payment is stuck?
SWIFT gpi adds end-to-end tracking (a UETR reference) to cross-border wires so banks can see status and fees at each hop; ask your bank for the UETR to trace a payment through correspondent banks.
Our international payment has been "in transit" for a week - how do I trace it?
Get the UETR/gpi reference from your bank, have them trace it through the correspondent chain, and check for a compliance hold or missing field at an intermediary - most week-long delays are a screening review or a data gap, not a lost payment.
What are our / ben / sha fee instructions and which should AP default to?
OUR = sender pays all fees (vendor receives the full amount); BEN = beneficiary pays all fees; SHA = shared. Default to OUR when the vendor must receive the exact invoice amount; SHA is common but leads to short-payment disputes.
The vendor in germany received €180 less than invoiced - correspondent fees or FX spread, and how do I make them whole?
Likely intermediary/beneficiary fees under SHA/BEN; book the shortfall, send a top-up for the difference, and switch to OUR instructions or a local-currency local rail so the vendor receives the full amount next time.
Bank wires vs fintech FX providers for international AP - cost and control compared?
Bank wires are familiar and offer finality but often carry wide spreads and correspondent fees; fintech FX providers and integrated AP payment platforms typically offer tighter rates, local rails, and better tracking - evaluate the all-in rate and whether the payment stays connected to your AP workflow.
What is a local-currency local-rail payment (sepa, bacs, eft) and why is it cheaper than swift?
A payment sent on the destination country's domestic network rather than through correspondent banking - it avoids intermediary fees and typically settles faster and cheaper, which is why paying EUR via SEPA beats a USD SWIFT wire to Europe.
What is FX rate locking and how long do quotes hold?
Locking fixes the executable rate against your payment so the rate you approve is the rate that settles; live quotes hold only briefly (seconds to minutes), so you must accept within the countdown or request a new quote - an estimated rate is not a locked rate.
How should we account for FX gain/loss between invoice date and payment date?
Record the liability at the invoice-date rate and the payment at the settlement rate; the difference posts to a realized FX gain/loss account. Mechanics vary by ERP and require multi-currency setup - having the executed rate post automatically removes the manual month-end rate override.
What is a purpose-of-payment code and why do some countries reject payments without one?
A regulatory code describing why funds are being sent, required by certain countries' central banks for cross-border compliance; omit it for those destinations and the payment rejects - collect it as part of country-specific setup.
Should international payments run through a separate approval workflow with FX-specific review?
Yes - they add currency, rate, and destination risk and are harder to recover, so a dedicated FX approval step (reviewing the rate and fee treatment) separate from payment approval is justified, especially where treasury owns FX policy.
How do I validate international bank details before paying?
Use IBAN checksum validation, confirm the BIC against a directory, apply confirmation-of-payee equivalents where the destination supports them, and collect country-specific fields up front - validating before execution prevents the failed-payment-minus-fees cycle.
Stampli perspective
Stampli handles cross-border payments inside the AP workflow in local currency or USD: it shows an estimated rate while you prepare the payment, requests a live executable quote with a short validity window before execution, can route an FX-specific approval separate from payment approval, and records the executed rate against the payment for ERP reconciliation. Stampli is not an FX broker - the provider sets the rate; Stampli surfaces, locks, and records it.