Multi-currency accounts for SaaS companies
A multi-currency account lets a SaaS company hold USD, EUR and GBP revenue, pay costs from matching balances and convert only the surplus. Worked FX example.
By Valeria VahorovskaUpdated 29 September 2026
A multi-currency account lets a SaaS company receive, hold and pay out USD, EUR and GBP without converting on arrival. Each currency gets its own balance and local receiving details. Costs are paid from the matching balance, and only the net surplus is converted, deliberately. That removes the double FX hit of converting revenue in and costs back out.
For the definition itself, see multi-currency account in the glossary. This guide is about how a software company should use one.
The quiet FX tax hits every SaaS company and dev shop with international customers. A US customer pays $30,000 and it auto-converts on arrival. Three weeks later you owe US contractors $11,000, converted back. That is two spreads on money that never needed to change currency. Paying the contractor bench is the payout half of this problem; this is the holding half.
Why SaaS companies lose money on FX
SaaS companies lose on FX because the exchange rate, not the fee, is most of the cost of moving money across borders, and auto-conversion pays it twice. The fee line on a statement hides the larger cost.
In its 2025 progress report on cross-border payments, the Financial Stability Board found business-to-business cross-border payments cost 1.6% on average, and that FX made up 87.1% of that cost. Conversion on the receiving side adds more. Where the receiving provider converts the currency, the same report found average FX margins of 0.7% to 1.1% on top.
Auto-conversion on arrival is exactly that receiving-side conversion. Every customer payment takes the morning’s rate, and every cost paid back out in the original currency takes another.
The matching principle: each currency as its own P&L
Matched flows, meaning dollar costs paid from dollar revenue, carry zero FX cost. Only each currency’s net surplus or deficit ever needs converting, and that is a fraction of gross flow.
| Currency | Money in | Money out |
|---|---|---|
| USD | US customer subscriptions, retainers, milestone payments | US contractors, US SaaS tools, cloud bills |
| EUR | EU customers | The Lisbon and Warsaw bench, EU vendors |
| GBP | UK customers | Payroll, office, UK suppliers |
The structure that enables it is a balance per currency: nested wallets under one relationship, not three bank accounts in three countries.
Two disciplines make it work:
- Bill customers in their currency, into local details. A US customer paying by domestic ACH to a US account number pays faster and cheaper than one wiring internationally. Local receiving details per market is the feature to insist on.
- Convert on purpose, not by default. Hold the month’s surplus and convert it in one sized move. Skip converting entirely the week before the bench payout draws that balance down anyway.
Worked example: converting every payment vs matching balances
Matching balances cut the converted volume in this example by more than two-thirds. The saving comes from converting net positions instead of gross flows, not from a better rate.
Say a software company with GBP as its home currency bills in USD and EUR. Its monthly flows, in USD equivalents:
| Currency | In | Out | Net |
|---|---|---|---|
| USD | $30,000 | $11,000 | +$19,000 |
| EUR | $12,000 | $14,000 | −$2,000 |
Converting every payment on arrival, and back again to pay costs, puts $67,000 a month through FX: $41,000 of USD and $26,000 of EUR. Matching balances converts only the net positions: the $19,000 USD surplus and a $2,000 EUR top-up. Applying the FSB’s 1.6% business-to-business average to both:
| Approach | Converted per month | Cost at 1.6% | Per year |
|---|---|---|---|
| Convert every payment | $67,000 | $1,072 | $12,864 |
| Match balances, convert the net | $21,000 | $336 | $4,032 |
The rate is the same in both rows. Only the volume changes, and the gap grows with every currency and customer you add.
Multi-currency account vs foreign bank accounts vs virtual IBANs
A multi-currency account gives you one relationship with a balance per currency. The older alternative, a bank account in each country, delivers the same local details at the cost of three onboardings, three logins and three reconciliations.
A virtual IBAN is a third, narrower thing. It is a receiving identifier that routes payments into an underlying account and holds no balance of its own. It solves collection and matching, not holding. For a SaaS company, the useful combination is a balance per currency with local receiving details in front of each.
What to check before opening a multi-currency account
Check four things: where the money sits, which local receiving details you get, the real FX spread, and whether balances post to your accounting. A fifth, concentration, matters once revenue flows through the account.
| Check | Ask | Red flag |
|---|---|---|
| Where the money sits | Safeguarded or deposit-insured, at which institution, under which regulator | No named institution. Ask where your money sits. |
| Local receiving details | ACH routing and account number, a EUR IBAN, a UK sort code | One IBAN sold as multi-currency. See what a virtual IBAN is. |
| FX price | The spread against the mid-market rate at the same moment | Only the fee line is quoted |
| Accounting | Do balances and conversions post to Xero or QuickBooks? | Three more tabs in the Friday matching ritual |
| Concentration | Does payroll depend on this one account? | No fallback. Apply the two-account rule. |
Multi-currency balances at a fintech are typically e-money: safeguarded rather than deposit-insured. Safeguarding at a regulated EMI is a real protection; a slick multi-currency interface over an unregulated wrapper is not. Evaluating Mercury on multi-currency applies this checklist to one provider.
How Fynex runs it
Fynex treats multi-currency as the default shape of a modern software business, not an add-on. Invoicing bills each customer in their currency and lands the money in the matching wallet. Payouts pay each contractor from the matching balance over their local rail.
The cash view shows every balance, every currency’s forecast and your net FX exposure in one position. “Should we convert the EUR surplus this week?” becomes a decision with numbers attached. Conversions run by rule or approval, and every movement reconciles to your accounting behind the flow. Fynex is an FCA-authorised e-money institution with client funds safeguarded by default, so the balances doing this work sit somewhere built for holding them.
Related: SEPA vs SWIFT covers which rail the money takes between balances.
Three currencies used to mean three banks, three spreads and a spreadsheet nobody trusted. It should mean one position, matched flows, and the spread paid once, on the money that genuinely needed to move.