A Canadian company invoices an American client in US dollars. The money arrives, is converted to Canadian dollars, and sits in the operating account. Nine days later the same company pays a US supplier — and buys US dollars back. The pair was crossed twice, both times at a rate somebody else chose, on money that never needed to leave the currency it started in.
That round trip is the cost a multi-currency account removes. It is not the cost most comparisons look at.
The short version
- A multi-currency account moves the moment of conversion from the payment rail to a point you choose — that single property is where the rest of the benefit comes from.
- The cost it removes is the round trip: a currency arrives, converts, and is bought back days later to pay a supplier in that same currency.
- That cost scales with the number of invoices rather than their value, and it never appears as a line item — it is priced into a rate.
- Netting only works when flows run both ways. For one-directional flows the account changes when conversions happen, not how many.
What a multi-currency account actually changes
The feature is usually described as holding money in several currencies, which sounds like a convenience and prices like one. The operational change is narrower and more useful: it moves the moment of conversion from the payment rail to a point you choose.
Without it, every incoming payment in a foreign currency converts on arrival, and every outgoing one converts on release. The rail decides when, because the account can only hold one currency. With a multi-currency account, an incoming US dollar payment stays in US dollars until you have a reason to change that — and if the reason never comes, the conversion never happens.
Everything else that gets attributed to multi-currency infrastructure follows from that one property.
The conversion you pay for twice
Most businesses with cross-border flows have receivables and payables in the same currency. They rarely appear on the same screen: one lives in sales, the other in procurement, and the account between them holds a single currency.
The result is the round trip from the opening paragraph. US dollars arrive and convert to Canadian dollars. Canadian dollars convert back to US dollars to pay a supplier. Each crossing carries a spread, and the two crossings cancel each other out in every respect except cost.
Put illustrative numbers on it. A company that receives USD 200,000 across twenty invoices in a quarter and pays out USD 150,000 across twelve crosses the pair thirty-two times, while the flows themselves only require converting the USD 50,000 surplus — once. The other thirty-one crossings exist because the account could not hold the currency in between. The figures here are an illustration, not a benchmark; the shape is what carries over.
What makes this expensive is not the size of the spread but the count. The cost scales with the number of invoices, not with their value, so it grows exactly as the business grows — and it never appears as a line item. It is priced into a rate, and a rate does not arrive with an invoice.
A multi-currency account lets those flows net against each other: money received in a currency pays obligations in the same currency, and only the genuine surplus gets converted.
The gap between the invoice and the settlement
The second effect is about timing, and it decides margins more often than the spread does.
When you invoice in a currency you do not hold, the rate that matters is the one on the day the money lands — which is neither the day you quoted nor a day you control. A thirty-day term is thirty days of exposure on a price you already committed to. Published references like the Bank of Canada daily exchange rates or the ECB euro reference rates make the movement easy to see after the fact; they do nothing about who carries it.
Holding the currency moves that decision. The receivable arrives and stays in its own currency, and the conversion becomes a separate action, taken when the rate, the cash requirement, or the netting position justifies it. The exposure does not disappear — it stops being decided by the calendar of someone else’s payment run.
Three capabilities behind one phrase
“Supports CAD, USD and EUR” can mean three different things, and a provider may have one of them without the others.
| Capability | What it means | What it needs |
|---|---|---|
| Receive | The currency can arrive and stay in that currency | An account that holds the balance, and a way for the sender to reach it |
| Hold | The balance sits in the currency until you decide | No forced conversion on credit |
| Pay out | Money leaves in that currency, on that currency’s rail | Access to the rail that carries it — Swift, SEPA, ACH, a domestic Canadian rail |
The third is where most of the difference lives. Receiving euros and holding them is of limited use if paying them out means converting to another currency first and sending a wire. That is the same question as which rail carries which transaction, asked from the account side: a currency you can hold but not pay out of is a currency you are storing, not operating in.
Where holding currency does not help
Netting only works when the flows run both ways. A company that receives US dollars and never pays them out has nothing to net — for it, the account changes the timing of the conversion but not the number of them. That is still worth something, and it is a smaller something than the round-trip case.
Two other situations where the account is not the answer. If a supplier can only be reached by a rail your provider does not have, holding their currency does not create access — it just parks the money closer to the problem. And if your margins are thin enough that a fraction of a percent decides them, the conversation is about where the rate comes from and how it is quoted, not about how many balances an account can carry. Holding a currency is not a hedge.
What to look at in your own flows
Take one quarter and put receipts and payments side by side by currency rather than by counterparty. Two numbers come out of it: how much of each currency you received and paid in the same period, and how many separate conversions those flows produced. The first is what netting could have covered. The second, multiplied by your spread, is what the round trips cost.
If the two numbers are close to each other, the account structure is the cheapest fix available — cheaper than renegotiating rates, because it removes conversions instead of repricing them. If the flows are one-directional, the answer is elsewhere: in how conversion is quoted rather than in where the balance sits.
Common questions
Is a multi-currency account the same as a foreign currency account at a bank?
Only if all three capabilities are there. Receiving a currency and holding it is the easy part; paying out of it, on the rail that currency travels, is where accounts differ. An account that receives euros and holds them but has to convert before it can send them gives you storage rather than an operating currency.
Does holding a currency protect me from exchange-rate movement?
No. A multi-currency account is not a hedge. It removes conversions that cancelled each other out and moves the remaining ones to a moment you choose, but whatever you do eventually convert is exposed exactly as it was before. Hedging is a separate instrument with its own cost, and the two questions are worth keeping apart.
Is this only worth it above a certain volume?
The count matters more than the volume. Each crossing carries its own spread, so the cost of the round trips grows with the number of invoices rather than with their value: a business with many small cross-border invoices can be paying more in avoidable conversions than one with a handful of large ones. Count the conversions before assuming you are too small for this to matter.
What if I only receive a currency and never pay it out?
There is nothing to net, and the account changes the timing of the conversions rather than the number of them. That is still worth something — the rate is taken when you decide rather than when the payment lands. But for a one-directional flow the more useful question is how the rate is quoted and what sits between it and the reference rate.
Which currency should I invoice in?
Whichever currency you also have obligations in, when the client accepts it — that is what creates the overlap netting can cover. When the client insists on their own currency, the choice is really about who carries the movement between the invoice and the payment, and that belongs in the price rather than in the payment terms.
In short
A multi-currency account is not a way to keep money in three places. It removes conversions that cancel each other out, and it moves the remaining ones to a moment you choose instead of a moment the rail chooses. The size of that saving depends on how symmetric your flows are, which is a question your own quarter can answer.
Open a multi-currency business account with Montowire. We hold CAD, USD and EUR in one operating environment and pay out on the rail each currency travels — Swift under our own BIC, indirect SEPA, ACH, and Interac for domestic Canadian transactions through a Canadian payment provider. We are registered with FINTRAC as a money services business, registration M23481791, and with the Bank of Canada as a payment service provider under the Retail Payment Activities Act. Neither registration is a license, and we are not a bank in any jurisdiction.
