🏢 B2B payments around the world

Credit transfers, the default B2B rail

A business-to-business (B2B) payment settles a debt arising from a commercial relationship between two legal entities. Its economics are the reverse of retail's on all three parameters: low volumes, high amounts, and a known counterparty under contract. The supplier is not trying to convert a shopping cart; it is collecting a receivable that already exists, within a period set by contract or by law. Neither cards nor wallets carry these flows. The dominant rail is the credit transfer.

Two families of rails coexist in almost every market. Deferred batch systems, inherited from clearing houses, aggregate thousands of instructions over a set period and then settle them on a net basis. This family includes the ACH Network in the US, Bacs in the UK, CNAPS / BEPS in China, and NACH in India. Single-payment settlement, gross or instant, processes each instruction individually: Fedwire Funds Service, CHAPS, T2, and the BOJ-NET Funds Transfer System. Deferred batch is cheap per transaction, and its settlement schedule is known in advance. Single-payment settlement executes immediately and becomes irrevocable. A well-run accounts payable function uses both families and splits its flows between them: batch for recurring payments, single-payment settlement for urgent or high-value instructions.

The average ticket is the mean amount per transaction on a given rail: total value divided by the number of payments. It separates business use from person-to-person use. An instant rail with an average payment above $100,000 has a treasury profile. In Canada, Interac e-Transfer passed 1.4 billion transactions worth C$554 billion over 12 months in 2024, more than 20% of them involving a business (Interac Corp., 2024 annual review). Some schemes keep the two customer bases apart. Denmark created Leverandørservice as the strictly B2B counterpart to its consumer direct debit. SEPA made the same choice with the SEPA Direct Debit B2B rulebook, separate from Core.

Limits, windows, and finality: what breaks a supplier payment

Three constraints determine the fate of a supplier payment. The first is the per-transaction amount limit set by the scheme. The second is the time window during which the rail accepts instructions. The third is finality, and misunderstanding it costs you after settlement, not before. The unit price of a transfer matters little next to these three parameters, since an instruction costs anywhere from a few cents to a few euros. Document all three before integrating the rail, never after the first incident.

• Who pays the charges: a SHA or BEN instruction delivers less than the invoice amount and automatically turns the receipt into unapplied cash.
• Local calendar: a national holiday shuts the domestic rail while the cross-border rail stays open, and vice versa.
• Payee verification: Verification of Payee, mandated by Regulation (EU) 2024/886, and Pay.UK's Confirmation of Payee in the UK check the name before execution. An out-of-date supplier master file now generates alerts, not transfers.
• Business alias addressing: PayNow uses the UEN in Singapore, DuitNow the company registration number in Malaysia, and PromptPay the tax ID in Thailand. IBAN is not the universal model.

Statutory payment terms compared

The payment period is the number of days between delivery or invoice date and actual payment. In most developed markets, it is not just a matter of contract: the law regulates it and penalizes overruns. The penalty varies far more than the period itself, from automatic interest in Europe to loss of tax deductibility in India and public disclosure in Australia and the UK. A 60-day clause negotiated in a country with a 45-day statutory cap therefore gives the buyer no cash advantage; it exposes the buyer to the local penalty.

Payment terms must be configured by counterparty country, not by a group-wide master file: the applicable rule and the penalty change from one market to the next. A single master file reproduces the same clause everywhere. A central procurement team that applies its standard terms in 15 countries breaks the law in at least three of them. The check belongs at supplier setup, when the country is known and the clause can still be changed. By payment time, the breach has already happened.

Commercial cards and virtual cards

A commercial card is a payment card issued in a company's name for expenses incurred on its behalf. In B2B, it covers purchases outside the PO process, travel expenses, and online marketing spend. Increasingly, it also pays supplier invoices through single-use numbers. Its form has changed in recent years, as the plastic card gives way to a number generated on demand. Commercial cards are now mostly virtual.

• Purchasing card: low-value purchases outside the PO process, with a line-item statement and Level 3 data.
• Travel and entertainment card: employee expenses, with liability on the company or the cardholder depending on the contract.
• Lodged card: a single number held on file by a travel agency or supplier, never issued to an individual cardholder.
• Single-use virtual card: a number generated per invoice or purchase order, with amount, currency, allowed MCC, and validity window locked at issuance.
• Fuel and fleet card: acceptance restricted by MCC, with reporting of volumes and vehicle registrations.

Factoring, reverse factoring, and transferable receivables

Trade credit is the financing a supplier provides its customer by agreeing to be paid after delivery. A 60-day payment term is thus a 60-day loan, with the supplier as lender. In many economies, outstanding trade credit exceeds bank lending to SMEs. Several refinancing techniques have grown up around it, and their names depend on whose viewpoint you take. Factoring is the supplier's view, reverse factoring the buyer's, and dynamic discounting is the case with no third-party funder.

A debt instrument is a document that evidences the debt and gives a path to enforcement against the debtor. A transfer order does not. In Brazil, the boleto bancário, run by Nuclea on the Nova Plataforma de Cobrança, is still used in B2B because it is an enforceable instrument, unlike Pix. Japan went the other way and organized the phaseout of paper. Its 179 bill and check clearing houses closed on November 2, 2022, replaced by the Japanese Bankers Association's 電子交換所 (electronic clearing house), which itself is slated to close in April 2027 (Nikkei, 2025). In Thailand, PromptBiz, launched by National ITMX on August 29, 2023, with five pilot banks, carries electronic invoices, payments, and receipts together. The resulting transaction history serves as a basis for SME lending.

Matching payments to invoices

Cash application is the accounting step that matches an incoming payment to the invoice it pays and then clears the receivable. A B2B payment that is received but not applied leaves the invoice open on the customer account and creates unapplied cash. The supplier then chases a customer who has already paid, blocks a delivery because the credit limit looks maxed out, or books a provision against a receivable that no longer exists. The real cost of B2B payments is measured by the auto-match rate and the number of full-time equivalents assigned to collections. Bank fees matter less.

• Bulk payment: one transfer for 17 invoices, with no remittance advice attached or sent separately.
• Unilateral deductions: late-payment penalties, credit notes, and retentions applied without any details.
• Early payment discount: the amount received matches no invoice to the cent, and no matching algorithm can guess it.
• Correspondent fees: under a SHA or BEN instruction, the payee receives less than the invoiced amount.
• FX difference: the invoice is in a foreign currency, and the payment is converted at a rate the supplier did not know when invoicing.
• Re-keyed reference: a number truncated, transposed, or replaced by the payer's name in a free-text field.

--- CASE 1: unstructured remittance -----------------------------
Amount received .. : EUR 47,812.35
Narrative ........ : "PAYMENT INVOICES JULY XYZ CO"
Consequence ...... : no automatic matching possible.
                     The accountant opens the customer account,
                     looks for a combination of invoices totaling
                     47,812.35, and fails: EUR 213.80 is missing,
                     withheld for a credit note never communicated.

--- CASE 2: structured remittance -------------------------------
Amount received .. : EUR 47,812.35
Invoice 1 ........ : INV-2026-004417  amount due 21,340.00
Invoice 2 ........ : INV-2026-004498  amount due 26,686.15
Credit note ...... : CN-2026-000212   amount       -213.80
Creditor reference : RF18 5390 0754 7034      (ISO 11649 standard)
Consequence ...... : automatic matching of all three lines,
                     zero difference, no human intervention.

ISO 20022 and structured data

ISO 20022 is an international standard for financial messaging, built on a common data dictionary and XML syntax. It has replaced the proprietary formats of the main interbank settlement systems. For B2B payments, the standard carries typed invoice data, where legacy formats offered only a free-text field. The benefit is in cash application: software reads an amount due from a field designed for it, instead of parsing it out of a sentence. Payment speed, by contrast, depends on the rail, not on the message format.

<RmtInf>
  <Strd>
    <RfrdDocInf>
      <Tp><CdOrPrtry><Cd>CINV</Cd></CdOrPrtry></Tp>   <!-- commercial invoice -->
      <Nb>INV-2026-004417</Nb>                         <!-- invoice number -->
      <RltdDt>2026-06-30</RltdDt>                      <!-- invoice date -->
    </RfrdDocInf>
    <RfrdDocAmt>
      <DuePyblAmt Ccy="EUR">21340.00</DuePyblAmt>      <!-- amount due -->
      <CdtNoteAmt Ccy="EUR">213.80</CdtNoteAmt>        <!-- credit note deducted -->
    </RfrdDocAmt>
    <CdtrRefInf>
      <Tp><CdOrPrtry><Cd>SCOR</Cd></CdOrPrtry></Tp>    <!-- structured reference -->
      <Ref>RF18539007547034</Ref>                      <!-- ISO 11649, check digits 18 -->
    </CdtrRefInf>
  </Strd>
</RmtInf>

Running B2B collections, market by market

A B2B collection architecture is the set of arrangements a supplier puts in place to get its invoices paid, from choosing the rail to refinancing the receivable. None of them carries over unchanged from one continent to another: the rail, the addressing, and the legal instrument all change. The decision sequence, however, is the same everywhere. It starts with the rail, chosen based on its limit and operating hours, then moves to locking in the invoice reference. Next comes setting payment terms under local law, then refinancing the receivable.

• Map each corridor's rail, per-transaction limit, cutoff time, and applicable holiday calendar.
• Require your bank to pass on every RmtInf block in full, including multiple occurrences and CTX addenda, and write it into the account agreement.
• Check that the ERP issues a unique reference per invoice, verifiable with check digits, and that it comes back unchanged in the camt.053.
• Specify in the contract who pays the charges: a SHA instruction on a correspondent corridor turns every receipt into a discrepancy to resolve.
• Configure payment terms by counterparty country, and check the gap between the negotiated clause and the local statutory cap.
• Keep payee name data up to date: EU Verification of Payee and UK Confirmation of Payee now block on stale records.
• Treat any reverse factoring program as a disclosure item under IAS 7 and IFRS 7, not just a treasury tool.
• Plan the fix for party addresses on CBPR+ corridors: the November 14, 2026, deadline was postponed by Swift on August 27, 2026, and a new timetable is due by December 2026.