In this article
The invoice arrives. The amount is clear, the due date is firm, and the payment instructions are precise. The only problem: the currency named on that invoice is not the one sitting in the payer's account. This is not an edge case. It is one of the most routine friction points in international commerce, and the mechanics for resolving it are more layered — and more consequential — than most finance teams appreciate until they are standing in front of a wire that needs to go out today.
This article walks through the complete landscape of options: what each path actually involves, where the costs hide, what the risks are at each stage, and how modern onchain payment infrastructure changes the settlement picture for deals involving multiple parties. Settlement agents, brokers, closing attorneys, title officers, and OTC desks will find the mechanics described here map directly to the workflows they manage every day.
Why the currency mismatch is the rule, not the exception
Global sourcing may provide exciting and profitable opportunities for a business, but paying invoices in a foreign currency is an important process to get right. Exchange rate fluctuations can affect margins, so it is worth taking a closer look at how to pay international invoices in a way that protects the business from unnecessary risk.
The modern business relationship does not always land inside a single currency zone. A US-based importer buying manufactured goods priced in euros, an Australian property developer settling a EUR-denominated architectural contract, a logistics firm paying a carrier whose invoices are in Singapore dollars — in each case, the buyer holds one currency and the invoice demands another. Unlike domestic payments, international transactions often require currency conversion. This exposes a business to foreign exchange risk, where exchange rate fluctuations can increase costs between the time an invoice is issued and when the payment is processed. In other words, what was budgeted for may not be what is actually paid in the end.
The problem compounds when a deal involves several parties simultaneously — a seller, a broker, a title company, a lender, and a sub-agent, for instance — all expecting payment at or near the same moment. A single currency mismatch upstream can create a cascade of delays downstream. Understanding the options in sequence is the first step toward making a good decision under time pressure.
Option 1: Spot FX conversion through a bank or specialist provider
The most direct path is a spot conversion: the payer instructs their bank or a specialist FX provider to convert the amount held in the domestic currency into the invoice currency at the current market rate, then transmit the converted funds to the payee. The mechanics sound simple. The actual cost structure rarely is.
Several parties are involved in business FX payments. The payer provides payment instructions and funds, while the bank or FX provider handles the currency conversion and routes the payment. Correspondent banks often act as intermediaries to move the money internationally before the recipient's bank credits the funds to their account.
Exchange rates come from the interbank market, where major banks trade currencies. The rate the payer gets includes a markup above this wholesale rate. This markup varies by provider and transaction size, and better rates are generally available for larger transactions. Additional fees for the transfer itself — cross-border fees, wire fees, or processing charges — can significantly affect the total cost.
The timing issue is equally important to understand. When making a cross-border payment, funds are not wired until they have been converted from the payer's currency to the payee's currency. The financial institution may delay withdrawing funds from the payer's account until the conversion is complete, which could take up to two business days.
The correspondent chain problem. If the sending bank does not have a direct relationship with the recipient's bank, the payment gets routed through intermediary banks — also called correspondent banks — that serve as connectors between the two systems. Each correspondent bank along the chain takes its own fee, often undisclosed upfront or at all.
There is no single network that processes payments worldwide, and global flows depend on interconnected payment networks. Most transactions rely on a patchwork of domestic systems connected through correspondent banking. The payment bounces through this chain of intermediaries — each one processing the transfer and sending it to the next stop until it reaches the final destination. For example, a USD payment sent from Germany to Japan might pass through banks in Europe and the United States first, depending on which institutions have existing relationships.
The practical consequence: the payee may receive less than the invoice amount because fees were deducted at each intermediate hop. For a settlement professional trying to reconcile a closing, a payment that arrives short of the exact invoice figure creates real operational complexity.
Scenario — the short-pay closing. An Australian property developer (AUD ledger) owes $120,000 USD (approximately AUD 186,000 at a representative rate) to a US-based sub-contractor. The developer instructs their bank to convert and wire. The bank quotes a rate with a 1.8% spread embedded, then the correspondent chain deducts a further $45 in fees at two hops. The sub-contractor receives $117,795 — $2,205 short. The closing agent now has to reconcile a discrepancy, request a top-up wire, and hold the closing until cleared. Each of those steps costs time and professional attention that was not in the original deal structure.
Option 2: A multi-currency account with pre-positioned funds
If the main bank does not allow holding multiple currencies, opening a separate business account in the payment currency lets the company hold foreign currency balances instead of being forced to convert funds upon each payment, which avoids unnecessary conversion fees.
Multi-currency accounts allow a business to hold funds in different currencies to avoid converting, eliminating FX risk altogether on a transactional basis. The FX decision has simply been moved upstream: the business converts at a time of its choosing, holds the balance, and then pays invoices from that balance without any in-payment conversion.
This works well for businesses with recurring payables in a known foreign currency. A US firm that consistently pays EUR-denominated software licenses, for example, can maintain a EUR-denominated account, buy euros when the rate is favorable, and pay each invoice as it arrives with no per-invoice FX event. The account does not eliminate currency risk entirely — the euro balance still has a USD cost basis that was locked in at conversion — but it removes the pressure of converting at a deadline-driven moment.
The limitation: this approach requires working capital to be pre-positioned in a foreign denomination. For smaller firms, tying up capital in a multi-currency account may not be practical. And for a one-off deal — a single property acquisition, a one-time equipment purchase — setting up a dedicated currency account is often not worth the administrative overhead.
Option 3: Forward contracts to lock the rate ahead of settlement
A forward contract locks in a rate of exchange today in anticipation of a future payable or receivable amount. The business agrees today to buy the invoice currency at a fixed rate, for delivery on the date the payment is due. Whatever happens to the market rate between now and then is irrelevant — the conversion rate is already fixed.
The main advantage of forward contracts is that they eliminate the downside risk exposure through a fixed future rate. They provide a degree of certainty, allowing businesses to protect their budgets from fluctuations in currency prices and lock in favorable rates ahead of time. However, there is no opportunity to benefit from favorable movements in exchange rates.
A forward transaction is any foreign exchange deal where settlement takes place on a future date, typically from a few days to six months ahead; however, under agreement, these contracts can be negotiated for up to and beyond a twelve-month period.
The mechanics have a few details worth understanding precisely. Unlike FX options, forward contracts do not carry an explicit upfront premium. The cost is embedded in the forward rate itself. In some cases, especially for longer-dated forwards or in volatile conditions, a margin deposit as a performance guarantee may be required. This deposit is returned at settlement.
Aligning the hedge to the actual payment date. The FX hedging window is the period the forward contract needs to cover. Aligning it with the actual cash outflow, rather than the invoice date or the approval date, helps ensure the hedge matures when the payment is due. If an invoice is received on 1 August with 60-day payment terms, the maturity date of the forward contract should match the settlement date of 30 September, not 1 August. A forward that matures three days before the payment settles leaves the business exposed for those three days, and on tight margins there may be no buffer to absorb that.
Scenario — the forward on a construction progress payment. A US general contractor has a EUR 450,000 (approximately USD 540,000 at a representative rate; approximately AUD 837,000) payment due to a German engineering firm in 90 days. The US company buys a forward contract for EUR 450,000 at today's quoted forward rate. Ninety days later, regardless of whether the euro strengthened or weakened, the contractor knows exactly what the payment will cost in dollars. The engineering firm receives precisely EUR 450,000 — not a euro more, not a euro less.
Forwards are less useful when the payment amount is highly uncertain — such as when hedging the wrong amount creates a different kind of risk — or when retaining upside if rates move favorably is a priority. In those cases, an FX option may be a better fit.
Currency forwards must be carried to settlement; closing them before the agreed date will incur a cost. If the underlying deal falls through and the payment no longer needs to be made, the forward contract still has to be unwound, and the cost of doing so depends on how the market has moved in the interim.
Option 4: Negotiating invoice currency with the payee
Before engaging the FX market at all, it is worth asking whether the invoice currency itself is negotiable. To make paying an international invoice easier, the supplier can be asked whether they would accept payment in the payer's local currency. For instance, many companies in China are open to being paid in local currency. If they agree, the payer can skip the hassle of converting money to their currency, saving on conversion fees and avoiding the stress of fluctuating exchange rates.
This transfers the FX risk to the payee. When paying in the payer's own currency, the payee often builds in a margin to cover their own conversion risk. In this scenario, the payer's business may lose control over the effective exchange rate, and suppliers may build in a spread that boosts their profits at the payer's expense. The question is which party is better positioned to absorb or hedge the currency risk — and at what cost to each.
For deals where the payee is a large organization with a treasury function and established FX hedging, they may be perfectly willing to invoice in the payer's currency. For smaller suppliers or those in emerging markets, absorbing FX risk is genuinely burdensome, and the resulting price premium may be more expensive than the payer simply handling the conversion themselves.
Option 5: Stablecoin rails — the dollar-denominated bridge
The four options above all operate within the traditional banking infrastructure. A fifth path has matured considerably in the last two years and deserves a direct, practical look: settling the invoice using a dollar-pegged stablecoin.
B2B stablecoin payments are commercial transactions between businesses settled in dollar-pegged tokens, typically USDC or USDT, on public blockchains rather than through bank wires, ACH, or SWIFT. The economic case is straightforward: settlement compresses from days to seconds, fees fall to single-digit cents on most chains, and the dollar balance becomes programmable — a payment can carry conditions and chain into longer treasury workflows.
The structural shift. A SWIFT MT103 wire still works the way it did in 1977: an instruction passes through a sender bank, one or more correspondent banks, and a beneficiary bank. Each hop carries fees and a settlement window. A stablecoin transfer replaces those intermediaries with a single onchain transaction and one or two off-ramp steps.
A traditional cross-border payment passes through two to four correspondent banks, each adding time, cost, and an FX cut. A stablecoin payment is one on-chain transfer, with a regulated on-ramp converting fiat to stablecoin at the start and an off-ramp converting back to local currency at the end.
How the flow works in practice. A B2B stablecoin settlement typically runs through five steps.
- Invoice issuance with payment instructionsThe supplier issues an invoice that names a stablecoin and a wallet address.
- Buyer-side on-ramp or wallet debitThe buyer either holds that stablecoin already in a treasury wallet or instructs an on-ramp partner to convert their local currency into the stablecoin.
- Onchain transferThe transfer posts onchain.
- Supplier-side receipt or off-rampThe supplier receives the token at their wallet or has a network's off-ramp partner credit local fiat — VND, BRL, MXN, NGN — to the supplier's bank account.
- ReconciliationBoth sides then reconcile against the invoice using the onchain transaction hash as the canonical reference.
The finality dimension. The transfer is final once confirmed onchain, settles in seconds to minutes depending on the chain, and produces a permanent transaction record that finance teams can reconcile against an invoice or general-ledger entry. Unlike a wire that can be recalled or returned through various bank channels, an onchain payment that has reached finality is not reversible. This is a feature in settlement contexts where certainty of payment is the primary objective — both parties know immediately whether the payment has landed.
For invoices denominated in a foreign currency the payer does not hold, the stablecoin path resolves the currency problem at the on-ramp stage. The payer converts their domestic currency (USD, AUD, EUR, or another) into the stablecoin at a single, transparent conversion point, then transmits the stablecoin. The payee receives a dollar-denominated asset — USDC, for instance — worth exactly the invoice face value. A $50,000 invoice paid in USDC delivers exactly $50,000 of value. There is no currency risk, no conversion spread, and no need for hedging. The supplier receives a dollar-denominated asset that they can hold, off-ramp to their bank account, or spend with other stablecoin-accepting counterparties.
USD-pegged stablecoins protect businesses from local currency depreciation. In corridors like Turkey→UAE or Argentina→US, FX volatility erodes supplier payment value between invoice date and settlement. Holding value in USDC eliminates this exposure — the supplier receives USD-equivalent value regardless of local currency movement.
Regulatory context. The GENIUS Act, signed in July 2025, gave the US its first federal framework for stablecoin issuers. The EU's MiCA regulation is fully applicable. The compliance perimeter around stablecoin B2B payments is not lighter than traditional payments — it is simply differently located, concentrated at the on-ramp and off-ramp stages where regulated entities handle the fiat-to-token and token-to-fiat conversion, rather than distributed across a chain of correspondent banks.
When the deal has multiple parties: the routing problem
The options above describe how a payer resolves a currency mismatch for a single payee. Real deals are rarely that clean. A commercial real estate closing, a cross-border asset sale, a multi-party equipment transaction — in each of these, the incoming payment from the buyer needs to be distributed simultaneously to several parties: the seller, the broker on each side, the title company, the lender, a sub-agent. Each party may have its own account, its own preferred currency, its own bank.
Under traditional wire infrastructure, this plays out in sequence. The closing agent receives the aggregate funds, then initiates individual outgoing wires — one to the seller, one to each broker, one to the title company — each with its own processing time, its own correspondent chain, its own potential for a short-pay or a delay. The deal has technically "closed" before any party has received their funds. Settlement risk sits in the gap between the closing moment and the moment every party confirms receipt.
This is precisely the workflow that onchain payment routing is designed to solve.
How Shaka.deal handles the routing. Shaka.deal is a B2B onchain payment router on Ethereum. It routes the total amount of a deal and distributes it simultaneously to every party at preset shares, in one transaction, with finality. The routing contract is non-custodial: it routes, it never holds funds. A single incoming payment arrives, and every designated wallet address receives its share in the same block. The settlement agent, closing attorney, or escrow officer defines the split in advance — the precise percentage or amount allocated to each party — and the router executes that distribution exactly as specified.
For a multi-party international deal, this collapses the sequential wire cascade into a single event. There is no "first in, first out" ordering, no partial distribution risk, no moment where funds are sitting undistributed waiting for the next outgoing wire to clear. Every party is paid at the same instant.
Scenario — an international commercial closing with four parties. A buyer in Australia is acquiring a US-based logistics business from a seller. The deal is denominated in USD. The payment needs to be split among the seller, the buyer's broker, the seller's broker, and the title company. Total deal consideration: $2,400,000 USD (approximately AUD 3,720,000).
Under the traditional model, the buyer converts AUD to USD, wires the full amount to the closing agent, who then initiates four separate outgoing wires. Each wire has its own processing window. If one wire fails or is short-paid, the others have already gone out and the closing agent is left managing an asymmetric reconciliation.
Under an onchain routing model with shaka.deal, the deal structure is configured in advance, with a preset share for each of the four parties.
| Party | Preset share | Amount (USD) |
|---|---|---|
| Seller | 91.5% | $2,196,000 |
| Buyer's broker | 3% | $72,000 |
| Seller's broker | 3% | $72,000 |
| Title company | 2.5% | $60,000 |
| Total | 100% | $2,400,000 |
The buyer converts AUD to USD stablecoin at the on-ramp stage, and the stablecoin payment routes through shaka.deal in a single transaction. All four wallets receive their precise allocation simultaneously, with a single transaction hash serving as the reconciliation record for every party. Settlement is immediate and certain. The closing attorney confirms distribution without managing four separate wire receipts.
The preset shares mean the distribution logic was agreed by all parties before funds moved — the same role a closing statement plays in traditional settlement, but executed by the routing contract rather than by sequential manual wire issuance.
Choosing the right path: a practical decision matrix
No single method is universally correct. The right choice depends on the specific shape of the deal.
Use a spot conversion when: the payment is needed immediately, there is no time to set up a forward contract, and the FX exposure on the specific transaction is small enough that a market-rate conversion is acceptable. Spot contracts allow a business to buy currency at today's rate for immediate settlement — ideal for one-off or urgent payments, or when rates are currently favorable.
Use a forward contract when: the payment date is known in advance, the invoice amount is fixed, and the FX exposure is large enough that a rate move between now and payment date would materially affect the business. A forward contract is an agreement to lock in today's exchange rate for a payment to be made in the future. This gives cost certainty and shields the business from currency market swings. Forwards work best with predictable cash flows. The higher the market volatility, the more valuable forward protection becomes.
Use a multi-currency account when: the business has recurring payables in the same foreign currency, has working capital available to pre-position in that currency, and wants to decouple the FX decision from the payment-execution moment entirely.
Negotiate invoice currency when: the relationship with the payee is strong enough to support the conversation, the payee has the institutional capacity to absorb or hedge currency risk on their end, and both parties would genuinely benefit from eliminating a conversion at the payer's level.
Use stablecoin rails when: settlement speed is a priority, the correspondent chain is long or expensive, the deal involves multiple payees who need to be paid simultaneously, or the payer wants a permanent, immutable record of the exact payment structure. The case for a stablecoin is strongest when multiple advantages appear together. Blockchains don't close for weekends or holidays — a fact that matters for time-sensitive treasury, market, supplier, and payout workflows.
For deals involving multiple parties and a structured payout — the scenario most relevant to settlement professionals — the stablecoin-plus-routing approach is not merely a technology preference. It is a structural improvement in the certainty and speed of settlement. The split is encoded before funds move. The distribution is simultaneous. The record is final.
Working with OTC desks for large conversions
When a conversion involves a significant sum — often in the six or seven figures — the execution mechanics change. B2B clients now expect tighter spreads, reliable execution, broader asset coverage, transparent settlement workflows, and the ability to trade without taking unnecessary operational risk. Demand for OTC execution is expanding beyond traditional crypto-native trading firms. Brokers, payment providers, fintech companies, banks, stablecoin businesses, family offices, and institutional desks are all looking for ways to serve clients who need efficient access to liquidity.
An OTC desk provides bilateral pricing for a single large conversion rather than exposing that conversion to the market order book. For large tickets — £250,000 and above — settlement runs through an OTC desk with bilateral pricing rather than an exchange order book. The conversion happens at an agreed price, the counterparties settle, and the converted funds move to the designated accounts. For a business converting, say, $1,500,000 AUD (approximately $970,000 USD) ahead of a USD-denominated closing, working through an OTC desk rather than retail FX channels typically means tighter pricing on the conversion itself.
Payments to suppliers in a foreign currency should not be confused with foreign exchange trading and hedging. More experienced treasury practitioners may choose to employ FX risk management instruments such as forwards, swaps, and options. These treasury teams typically work closely with specialists on their bank's FX desk to tailor appropriate solutions for their business.
Once the converted funds are in the appropriate stablecoin or fiat form, the routing layer takes over. The OTC desk handles the currency conversion; shaka.deal handles the distribution. The two functions are complementary, not competing.
Reconciliation: the often-overlooked back end
Every method of paying a foreign-currency invoice creates a reconciliation obligation. The settlement agent, closing attorney, or accounts payable team needs to match the payment that went out against the invoice that came in — and in a multi-currency context, that match involves both the amount and the exchange rate used.
Under correspondent banking, the payment confirmation from the sending bank often does not reflect what the payee actually received after intermediate deductions. The reconciliation requires collecting confirmations from both ends and resolving any gap. Depending on the route, costs can include a transfer fee, exchange-rate markup, correspondent-bank charge, recipient-bank charge, card-funding fee, or a fee for amending, investigating, or returning a payment. If the recipient needs an exact amount, it is worth asking whether intermediary fees could be deducted along the way — a question that matters most on routes involving several banks.
Under onchain routing, the transaction hash is a single reference that both the payer and all payees can independently verify. The amount sent equals the amount received (less the transparent on-chain fee, which on most EVM-compatible chains is a fraction of a cent per transaction at current gas prices). There is no version of events where the confirmation on one side does not match the receipt on the other.
For settlement professionals who spend meaningful time chasing wire confirmations and resolving partial-receipt discrepancies, this is not a theoretical benefit. It is a direct reduction in back-office labor on every deal where it applies.
Putting it together: the professional's checklist
For any deal involving a foreign-currency invoice, the following questions should be answered before funds move:
1. What is the exact amount, in what currency, and to how many parties? A single payee changes the options; multiple payees change the architecture.
2. When is the payment due? Same-day needs eliminate forward contracts and reduce optionality. Payments with known future dates benefit from rate-locking strategies.
3. What is the FX exposure on this specific conversion? A helpful way to think about the cost of remaining exposed to currency movements: a 3% move in EUR/USD on a $2 million payable represents a $60,000 swing. Even on smaller deals, the math is worth running.
4. What is the payer's institutional capacity? A firm with an established treasury function and banking relationships has different tools available than a smaller business making its first international payment.
5. Does the deal structure require simultaneous, certain distribution to multiple parties? If yes, sequential wire issuance is the wrong architecture. Onchain routing through shaka.deal is purpose-built for exactly this scenario.
6. What is the reconciliation requirement? Who needs to confirm receipt, by when, and in what form? The answer should drive the choice of payment rail, not the other way around.
The bottom line
Paying an invoice denominated in a currency you do not hold is not one problem — it is a cluster of decisions that compound on each other. The currency conversion decision is separate from the routing decision, which is separate from the timing decision, which is separate from the reconciliation requirement. Professionals who manage these deals for a living — closing attorneys, settlement agents, escrow officers, brokers — understand that every one of those decisions has a counterpart risk if it is made without full information.
The traditional toolset — spot FX, forwards, multi-currency accounts, correspondent wires — remains the right answer in many contexts, and working closely with banking relationships and FX specialists is the correct approach for sophisticated or complex conversions. But the traditional toolset has a structural weakness in multi-party deals: it is sequential where the deal requires simultaneous, and it is opaque where the deal requires a clear record.
Onchain payment routing, with shaka.deal at the distribution layer, addresses that specific weakness. The currency conversion still happens through the appropriate channel — a regulated on-ramp, an OTC desk, a treasury account. What changes is what happens immediately after: a single transaction routes the full deal amount to every party at once, at the exact preset shares, with a permanent and immediately verifiable record. Split. Instant. Certain. That is not a replacement for the professionals who structure and manage these deals — it is the infrastructure that lets them do their work with the finality that complex cross-border transactions deserve.
