A payment run becomes expensive to examine when suppliers in three or four currencies are paid from one home currency account. Each payment triggers a conversion, yet the conversion cost is rarely shown separately from the payment in the reports finance teams review. For companies early in their international expansion, this may be adequate. As volumes rise and the currency mix becomes predictable, the single account model creates costs worth assessing structurally.
How single currency accounts handle cross border payments
In a conventional single currency setup, the company holds all funds in its home currency. When an international payment is sent, the bank converts that balance into the destination currency at its internal rate, starts the SWIFT transfer, and debits the account for the converted amount plus stated fees. Every payment in a non home currency therefore undergoes conversion when it is initiated.
This arrangement is suitable when cross currency payments are infrequent and volumes are modest. Its operational simplicity is real: one account, one reconciliation, and no separate currency balances to administer. Finance does not need to decide when to convert or how much to retain in each currency.
The cost builds in two places. One is the FX spread on each conversion. The other is conversion timing, since the rate is whatever prevails on the payment date, not one treasury selected earlier. For companies with substantial, predictable payables in one currency, converting immediately before each payment means taking that day's market rate instead of selecting a better window earlier in the cycle.
What changes with a multi currency account
A multi currency account keeps balances in two or more currencies under one account structure. Depending on the provider, it may use separate currency wallets with individual balances, or one account that supports holding and paying in several currencies without distinct sub accounts.
The operational difference is that a EUR payment can come directly from a EUR balance, rather than being converted from the home currency at payment time. Conversion into EUR happens separately, when the finance team selects the timing and rate. Building a destination currency balance and paying suppliers become separate decisions instead of one transaction.
For corridors with material volume, that separation creates two benefits. The first is rate selection: convert when conditions are favorable, rather than on the date a payment falls due. This is not currency speculation. It applies to FX the same purchasing discipline used for commodities, buying under favorable conditions instead of always paying the spot rate when demand arises.
The second is payment routing. In many corridors, funds from a local currency account can use local rails instead of SWIFT. A EUR payment funded from a EUR balance may use SEPA rather than an international wire, lowering cost and settlement time. This depends on the provider's network, not on holding EUR alone, although the two commonly coincide.
When pre funding makes sense
Pre funding is converting home currency into a destination currency before the payment date and holding it until needed. The tradeoff is between controlling FX costs and tying up capital in currency positions.
Pre funding is most useful when several conditions coincide. Payment volume in a currency must be high enough for conversion savings to exceed the cost of holding the balance early. Timing should also be predictable. If EUR supplier payments cluster in the third week of each month, converting and holding EUR the week before is straightforward. Finally, the company should not have substantial revenue in that currency naturally offsetting the payable exposure.
The case is weaker when payment volumes are small or unpredictable, available cash for pre funded balances is limited, or currency pair volatility is low enough to make timing gains negligible. A company with irregular EUR payables and a USD based cost base has limited option value from pre funding EUR. In that situation, the simpler single currency model may be the appropriate tradeoff.
Consider a Gulf services company paying software contractors in India, the Philippines, and Indonesia, with amounts clustering on one date each month. Payment values are reasonably predictable. USD/INR, USD/PHP, and USD/IDR have active spot markets with accessible rates. Converting and holding local balances one to two weeks before payment cycles provides useful timing flexibility without tying up substantial capital.
How to assess a multi currency account provider
Multi currency account products differ materially. The practical distinctions are network coverage, transparent fees, and the currency pairs supported at usable quality.
Network coverage means the currencies settled through genuine local rails rather than SWIFT. A provider with SEPA for EUR, Faster Payments for GBP, ACH for USD, and local rails in several other high volume markets may cover most needs of a growing global company. A provider advertising support for 50 currencies but settling most through correspondent SWIFT relationships with an added markup offers less than the headline suggests.
Transparent fees matter because multi currency pricing is often difficult to compare. Some providers charge a fixed payment fee and a stated percentage over mid market for FX, making costs auditable. Others hide margin in the rate without showing the mid market reference, recreating commercial banking's opacity. Ask directly what rate you receive against mid market for each regularly used currency. How directly the provider answers is informative.
The quality of currency support matters more than the list count. A provider settling INR payments through NEFT at competitive rates for a company paying ten Indian contractors each month is more useful than one listing 80 currencies but sending INR by SWIFT, with a wide spread and three day settlement.
Moving from single to multi currency in practice
The move need not be immediate or complete. Many companies open a multi currency account alongside existing banking, route their highest volume cross currency corridors through it, and keep other activity where it is. Finance can then compare actual payment costs before changing accounts payable workflows.
Measuring first turns the choice from a strategic preference into an observed cost question. If actual payments show that EUR transfers through a multi currency account with SEPA cost materially less per quarter than transfers through the primary bank, finance has a concrete basis for broader changes. The same evidence can support the operational case internally by showing the measured quarterly difference.
