Cross-border supplier payments: how banks and credit unions can pay their business clients' suppliers abroad
Cross-border supplier payments fail on deductions, delays and missing remittance data. The messages, the controls and the client experience that fix them.
- Cross-border supplier payments are judged by the supplier, not the payer. The supplier wants the full invoice amount, on the promised day, with enough reference data to close the invoice without a phone call.
- In ISO 20022 terms the payment is a pain.001 from the business client, a pacs.008 customer credit transfer between institutions, pacs.002 status reports and a camt.054 credit notification. The charge bearer and the remittance block decide most supplier complaints.
- The controls that matter run before release: KYB on the paying business, supplier due diligence, beneficiary account verification, payee change checks, sanctions screening including ownership, duplicate invoice detection and Travel Rule data.
- Show the business client one quote: the rate, every fee, the amount the supplier receives and how long the quote holds. A deduction the client did not see is the most common reason a supplier relationship sours.
- Stablecoin settlement shortens the leg between institutions to minutes on any day and makes the amount certain, but it is final. The controls have to clear first, and the messages, not the ledger, carry the parties.
A business that imports goods pays its suppliers abroad every month, often on fixed terms written into a contract. For its bank or credit union, those cross-border supplier payments are a steady and sticky line of business. For the business itself they are a recurring source of friction: the supplier reports a short payment, the funds arrive a day after the due date, or the invoice number never made it through, and the accounts receivable team on the other side cannot match the money.
This article is written for the payments, treasury and compliance teams at credit unions, regional banks and licensed money service businesses that want to offer supplier payments to their business clients, or to fix the service they already run. It sets out what the supplier actually needs, how the payment maps to ISO 20022 messages, which controls have to clear before release, how to present price to the client, and what changes when the settlement leg runs on regulated stablecoins.
What are cross-border supplier payments, and why do business clients find them painful?
A supplier payment is a business to business credit transfer that settles a commercial invoice. It differs from a personal remittance in three ways that shape the whole service. The amounts are larger and repeat on a schedule. The payee is a business with its own bank, its own receivables process and often its own currency. And the payment is evidence in a trade relationship, so a short or late payment has consequences beyond the transfer itself.
The complaints are consistent across institutions. The supplier receives less than the invoice because an intermediary deducted a fee along the correspondent chain. The arrival date is unknown until it happens. The reference data is cut short, so the supplier cannot apply the cash. The exchange rate is visible only after the fact. Each of these is a design choice somewhere in the payment, and each can be fixed by an institution that controls the flow end to end.
Speed expectations are rising as well. Per the Financial Stability Board's 2021 G20 roadmap targets, 75 percent of cross-border wholesale payments should be credited within one hour of initiation by the end of 2027. Business clients read about faster payments and ask why their supplier still waits two days.
What does a supplier payment look like as ISO 20022 messages?
The message chain is short and it repays reading once, because most supplier complaints trace back to a single field in it.
- The business client instructs its institution with a pain.001 customer credit transfer initiation, either from its own enterprise system or through the institution's portal, and receives a pain.002 status report in reply.
- The institution sends a pacs.008 customer credit transfer toward the supplier's bank, carrying the debtor, the creditor, both agents, the amount, the charge bearer, the purpose and the remittance information.
- Where institutions must move cover funds between themselves, a pacs.009 financial institution credit transfer carries that interbank leg under the same UETR.
- Each agent reports progress with a pacs.002 status report, so the client can be told the payment was accepted, settled or rejected rather than left to guess.
- The supplier's bank credits the account and the supplier receives a camt.054 credit notification or sees the entry on its camt.053 statement, ideally with the invoice reference intact.
Two fields cause most of the trouble. The charge bearer says who pays the fees: DEBT means the payer pays all charges, SHAR splits them, and CRED lets them come out of the amount sent, which matches OUR, SHA and BEN in the older MT 103. A supplier owed a fixed invoice should be paid with DEBT, priced into the client's quote, so nothing is deducted on the way. The second field is remittance information. A single unstructured line is easy to truncate. A structured remittance block carrying the invoice number, date and amount, or a separate remt.001 remittance advice for a payment that covers many invoices, lets the supplier apply the cash automatically. A purpose code that says the payment settles goods or services helps both screening and the supplier's own records.
Which controls must clear before a supplier is paid?
Supplier payments carry a particular risk profile. The payer is a known business client, but the payee is a third party the institution has never onboarded, and fraudsters know that accounts payable teams pay on instruction. The controls below are the ones an examiner will expect to see, in the order they usually run.
- KYB on the paying business, including beneficial owners and the nature of its trade, so the institution knows which suppliers and countries are normal for this client.
- Supplier due diligence proportionate to risk: the legal name, the country, the registration number or legal entity identifier where one exists, and a structured address.
- Beneficiary account verification before the first payment, so funds are not sent to an account that does not belong to the named supplier.
- Payee change controls. A request to change a supplier's bank details is the classic business email compromise, so it needs out of band confirmation with a known contact and a cooling off period.
- Sanctions screening of the supplier, its bank and its country, including ownership and control analysis rather than a name match alone.
- Duplicate detection on invoice number, amount and supplier, because a supplier paid twice rarely sends the money back quickly.
- Trade consistency checks for trade based money laundering: does the amount, the goods and the route make sense for this client.
- Travel Rule data under IVMS101 where the settlement leg moves virtual assets, so originator and beneficiary information travels with the transfer.
None of this is new, but the order matters more as settlement gets faster. Every one of these checks is cheaper before release than after it. A cancellation request sent as a camt.056 once the supplier has been credited usually ends in a rejection, and a recovery depends on the supplier's goodwill.
A supplier judges the payment, not the payer. The full amount, on the promised day, with the invoice reference intact, is the whole product.
How should FX and fees be shown to the business client?
As one quote, before the client approves. The quote should show the exchange rate, every fee the client will pay, the exact amount the supplier will receive in its own currency and the time for which the quote holds. If the institution cannot state the amount the supplier receives, it does not yet control the payment end to end.
Two practices reduce disputes. First, lock the rate at approval and settle against the locked rate, so a market move during the day does not change what the supplier receives. Second, keep the client's view and the supplier's view consistent: the amount on the quote, the amount on the pacs.008 and the amount on the supplier's credit notification should all reconcile without a footnote. Recurring supplier payments benefit from saved templates that re-price at each run rather than reusing an old rate.
What changes when the settlement leg runs on stablecoins?
The leg between institutions changes shape. Instead of a chain of correspondent accounts, value moves as a regulated stablecoin such as USDC on a public blockchain, and a payout partner in the supplier's country delivers local currency into the supplier's account. The transfer settles in minutes, on weekends and holidays as well as business days, and there is no intermediary in the middle to deduct a fee. The amount the supplier receives can be fixed at the quote.
Three things follow. Finality is immediate, so the controls above have to clear before the transfer is signed, not while it is in flight. The ledger carries an amount, a hash and a timestamp but no names, so the pacs.008, the pacs.009 and the Travel Rule payload remain the record of who paid whom. And reconciliation should key on the UETR, linking the client's instruction, the on-chain transaction and the supplier's credit in one trail. The last mile still runs on local clearing, so the payout partner's own controls and cut-offs belong in the institution's third party risk review.
How should a bank or credit union start offering supplier payments?
Start narrow and measure. Pick one corridor where several business clients already pay suppliers, and one payout partner in that country. Onboard the clients' most frequent suppliers first, verify their accounts once, and save them as templates. Then run the corridor for a quarter and track four numbers: time from approval to supplier credit, the share of payments that arrived short, the share that needed an investigation, and the share that the supplier applied without contacting anyone. Those numbers are the business case for the next corridor, and they are the evidence a risk committee will ask for.
Where StableNet fits
StableNet, built by SpendTheBits, is a cross-border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs. Settlement is in regulated stablecoins and completes in minutes with on-chain auditability. Every payment is ISO 20022 native, with a pacs.008 customer credit transfer, a pacs.009 interbank leg, pacs.002 status reports, pacs.004 returns and a head.001 envelope, tracked end to end by one UETR. KYB and KYC onboarding, KYT, sanctions and PEP screening and Travel Rule data under IVMS101 sit in the same path and write to a tamper-evident audit trail, so the controls a supplier payment needs run before release and leave the evidence behind.
- Credit union international payments: serving business members without a correspondent relationship
- Last mile fiat delivery: what happens after the stablecoin leg settles and the beneficiary wants local currency
- Beneficiary account verification: how to stop a cross-border payout reaching the wrong account
See it on your corridors
Book a working session and we’ll map StableNet’s compliance and settlement to one of your live payment flows.