Which rail should treasury use for each payment, and when? SWIFT GPI launched in 2017, promising same-day use of funds in the receiving country across 40-plus corridors, plus end-to-end tracking and visibility into fees deducted along the route. By 2023, GPI covered most SWIFT cross-border payment volume. That reach still does not answer the practical question: when is SWIFT GPI preferable to a local rail, and when is a local rail better?
What SWIFT GPI changed
Before GPI, SWIFT payments were largely invisible while in transit. The originating bank sent the message, then requested a network trace if the payment failed to arrive within several days. That could take several more days, leaving payer and payee unable to locate the funds.
GPI made two specific changes. A GPI tracker reference, the UETR (Unique End-to-End Transaction Reference), travels through the correspondent chain and lets all parties see near-real-time status. GPI also added a confirmation-of-credit message, sent by the beneficiary bank when funds post to the account, rather than merely when the instruction arrives.
For treasury teams, especially on high-value B2B payments, these are meaningful gains because counterparties can receive settlement confirmation. Knowing a USD 500,000 supplier payment reached a Hong Kong counterparty within hours, instead of waiting for the supplier's email, removes friction from payment confirmation workflows.
GPI did not alter the correspondent banking structure. A UAE company's payment to a Japanese supplier may still pass through several correspondent banks, each able to deduct fees from the principal. GPI makes those deductions visible, which helps, but does not prevent them. Where several correspondents are involved, the combined fees can be substantial compared with the payment value.
SEPA: the EUR payments standard
Within the Single Euro Payments Area (SEPA), B2B treasury teams mainly use two instruments. SEPA Credit Transfer (SCT) settles on the next business day and has no payment ceiling. SEPA Instant Credit Transfer (SCT Inst) settles within 10 seconds, 365 days a year, with a current per-transfer limit of EUR 100,000, although the ceiling has risen over time and differs by bank participation.
For EUR-denominated suppliers in Germany, France, or the Netherlands, SEPA is usually preferable to SWIFT. Fees are flat and low, from a few cents to a few euros depending on the bank. There is no correspondent chain or principal deduction, settlement follows a known timeframe, and IBAN addressing standardizes beneficiary validation across 36 participating countries.
SEPA's limits are its EUR-only scope and participating-country boundary. A EUR payment to an Australian supplier still uses SWIFT, even when the payment is settled in EUR. Treasury teams paying in EUR and non-EUR within the same regions must therefore identify which payment leg qualifies for SEPA and which does not.
ACH: the US settlement network
The Automated Clearing House (ACH) network handles US domestic USD transfers through batch cycles. Under current NACHA rules, multiple settlement windows run during the business day. Same-Day ACH is available for credits and debits submitted before set morning and early-afternoon Eastern Time cutoffs.
Standard ACH settles on the next or second business day and supports payroll, recurring vendor payments, and supplier settlements where next-day timing works. Same-Day ACH settles that day when payments meet an available window. ACH suits USD payments to US suppliers or entities when settlement need not be faster than same-day.
ACH generally costs less than a wire, and at scale is much cheaper per transaction for recurring payments. Cross-border use requires the payee to hold a US bank account and routing number. A Dubai company paying a US software vendor can usually use it, but not for a US contractor whose only account is foreign.
Faster Payments: UK real-time rails
Faster Payments Service moves GBP between UK bank accounts in seconds, 24 hours a day, seven days a week. Its current per-payment limit is GBP 1 million, though banks may impose lower customer limits. There is no same-day cutoff, so a payment sent at 11 PM Sunday reaches the beneficiary within seconds.
For GBP payables to UK suppliers, Faster Payments is the preferred infrastructure. Near-instant settlement, non-banking-day availability, and its high limit cover most B2B cases. Participating UK accounts, now essentially all major UK banks, use sort codes and account numbers rather than IBANs.
For cross-border finance teams, the important detail is that Faster Payments covers only GBP transfers between UK accounts. A EUR payment from a SEPA account to a UK GBP account needs conversion, performed by the sending or receiving bank, not by Faster Payments. A fast rail does not remove the currency-conversion issue. Speed and currency are handled by separate infrastructure layers.
Selecting the right payment instrument
Regular international payables are best managed with a decision matrix, not one platform:
EUR payments to suppliers in SEPA-participating countries: Use SEPA Credit Transfer for standard timing or SCT Inst for same-day settlement. SWIFT only adds cost and complexity here.
USD payments to US-based suppliers: Use ACH for standard vendor payments. Choose Fedwire or SWIFT when same-day USD settlement exceeds ACH's Same-Day limits or the bank does not join ACH.
GBP payments to UK-based suppliers: Use Faster Payments below GBP 1 million. Use CHAPS, the UK's high-value same-day system, above that limit or when a specific same-day guarantee is required.
All other currency corridors: SWIFT GPI is generally the only international network available. Map the correspondent chain for each corridor and include correspondent fees in the payment cost model.
The treasury team's strategic choice
SWIFT GPI remains a sound option. For high-value transfers beyond regional rails, it provides more transparency than SWIFT previously offered. The error is using it for every international payment because it is familiar, instead of sending eligible EUR and GBP payments through faster, cheaper local networks.
We're not saying local rails are always the right choice. SWIFT GPI tracking helps with high-value transfers where settlement confirmation affects cash management. For Dubai to Singapore, its tracking, fee visibility, and speed make it reasonable. For a EUR payment to Berlin, SEPA is cheaper, faster, and suitable.
The practical lesson is to set a default network for every currency and destination corridor, rather than treating SWIFT as the universal fallback. Treasury teams that do so often move meaningful volume to regional rails, lowering cost and settlement time across much of their payables.
