If you run finance for a mid-market company in Southeast Asia or LATAM, cross-border payments are probably costing you more than you think. Not just in fees, but in time, predictability, and supplier trust. We've tracked hundreds of international wire transactions at JuniGo, and the pattern is consistent: businesses using traditional bank wires pay 3 to 5 percentage points above mid-market rate and wait an average of two to four business days per transaction. For a company sending USD 50,000 monthly to suppliers, that's USD 1,500 to USD 2,500 in unnecessary FX costs every single month.
This guide covers the full picture: how cross-border B2B payments work mechanically, where costs actually come from, how to evaluate settlement options, and what to look for in a payment platform.
How an International B2B Payment Actually Moves
When your Singapore company pays an Indian supplier in INR, the payment does not travel directly. It moves through a correspondent banking chain. Your bank sends the payment to its correspondent bank in a hub market (often the US or UK), which then routes it to a local Indian bank, which finally credits the supplier's account. Each step introduces a fee and a time delay.
SWIFT handles the messaging layer, telling each bank what to do and where to send funds next. But SWIFT itself does not hold money. Banks do. And each bank in the chain may deduct a correspondent fee, typically USD 10 to USD 20, from the payment principal. This is why a supplier sometimes receives USD 850 when you sent USD 900. The shortfall is not a mistake. It's expected behavior in a correspondent banking chain.
Local payment rails work differently. A fintech with direct bank accounts in both Singapore and India can receive SGD from your account and simultaneously release INR from its Indian account to your supplier. No SWIFT chain. No correspondent deductions. Settlement happens within hours because it's two domestic transfers, not one international chain.
Where the Real Costs Hide
Most businesses think of cross-border payment costs as the wire transfer fee: SGD 25 or USD 35 on the bank statement. That fee is real. But it's typically the smallest component of the total cost.
The larger cost is the FX spread. Banks typically apply a 2.5% to 4% markup above the interbank mid-market rate. On a USD 50,000 payment, that's USD 1,250 to USD 2,000 in currency conversion cost that appears nowhere on your statement as a line item. You only see it if you compare the rate you received to the rate on Reuters or XE at the same moment. Most finance teams never make that comparison.
There's also the correspondent deduction problem. If you send USD 50,000 and the supplier receives USD 49,740, you have a reconciliation mismatch. The shortfall appears as a discrepancy in your ERP unless you manually adjust. Over 20 transactions a month, that's 20 manual adjustments.
Practical note: Ask your bank to show you the mid-market rate and their applied rate side by side before confirming your next wire. Most will not volunteer this. When you ask directly, the gap becomes visible.
Settlement Options: A Comparison
| Method | Typical FX Spread | Settlement Time | Correspondent Fees | Best For |
|---|---|---|---|---|
| Bank SWIFT wire | 2.5-4% | 2-4 business days | USD 15-45 per transaction | One-off large payments, bank-required corridors |
| Fintech local rails | 0.4-0.8% | Same day to next business day | None (fixed in markup) | High-frequency corridors with local bank coverage |
| SWIFT GPI | 2-3.5% | Same day (tracking included) | USD 15-35 | Bank clients needing speed with existing bank relationship |
| Stablecoin-assisted bridge | 0.2-0.6% | Minutes to 2 hours | Near zero | High-cost corridors where local rails are thin |
What to Look for in a Cross-Border Payment Platform
The category has grown. There are dozens of platforms positioned for international business payments. Here's what actually separates adequate from excellent, based on what finance teams tell us they care about after switching.
All-in cost disclosure before confirmation. Not "fee-free" marketing. The mid-market rate, the applied rate, the spread percentage, and the total cost in source currency as a single line before you click confirm. Any platform that won't show you that upfront is hiding cost somewhere.
Recipient-gets-exactly-what-you-sent guarantee. This one is harder than it sounds. It requires the payment provider to absorb correspondent deductions rather than pass them to the recipient. Not all platforms do this. Ask directly: does the recipient receive exactly the quoted amount?
Beneficiary verification before payment execution. Wrong account number returns generate USD 25 to USD 85 in return wire fees plus 3 to 7 days of delay. A platform that validates IBAN, IFSC, CLABE, and local account formats before executing saves real money and time.
ERP integration that actually works. Most finance teams run NetSuite, QuickBooks, or Xero. Payment reconciliation should push automatically: source amount, destination amount, applied rate, transaction ID, cost center code. Manual journal entry for every cross-border payment is a hidden time tax.
Evaluating Corridors Specifically
Not all corridors are equal. Singapore to India is well-served by local rail infrastructure. Singapore to Nigeria involves much higher SWIFT fees and more correspondent hops. Singapore to Mexico has improving local rail options but remains costlier than most Asia corridors.
When evaluating a payment platform for your specific corridors, ask for the current markup rate and average settlement time for each corridor you use. Some platforms show corridor-specific data in their dashboard before you commit to a payment. That's a meaningful differentiator. You should know what the last 30-day average rate was for your specific currency pair before locking a payment.
In our experience, finance teams often don't realize their most expensive corridor until they run corridor-specific cost analysis. One pattern we see repeatedly: a company's Philippines supplier payments cost 3 percentage points more than India payments despite similar transaction sizes, because they were on a SWIFT-only path for one corridor while using local rails for the other.
Building a Cross-Border Payment Policy
Finance teams that manage cross-border payments well don't leave decisions to individual bank relationships. They build a policy: approved corridors, approved platforms per corridor, maximum FX spread tolerance (typically 0.5 to 1% above mid-market for regular suppliers), payment frequency (weekly batch preferred over daily one-off), and ERP reconciliation requirements.
The batch payment approach deserves emphasis. Running 20 supplier payments as a single CSV upload versus 20 individual wire approvals saves 3 to 5 hours of finance team time per run. At consistent FX rates locked for the batch window. With a single reconciliation file instead of 20 separate confirmations.
Start with your top 3 corridors by payment volume. Audit the last 3 months of actual exchange rates received versus mid-market on those dates. Calculate the real spread. That number is the business case for evaluating alternatives.
