A growing software business sells in the UK, the EU, and the US. Revenue arrives in GBP, EUR, and USD respectively. Costs are predominantly in GBP — payroll, office, the bulk of suppliers — but with meaningful USD obligations to cloud infrastructure providers and a handful of EUR contracts with European partners. The CFO has built the operating model around three currencies, each held in a separate bank account, each with its own statement, its own reconciliation, and its own FX exposure.
What this looks like in practice: a Wise Business account for the multi-currency receivable, a domestic GBP business account for operating cash, and a separate USD account that exists primarily to pay the AWS bill in the currency it's denominated in to avoid being converted twice. The treasury function involves moving value between the three accounts whenever the operating cash needs topping up, paying FX margin on each conversion, and tracking the net position across the three balances at any given moment.
This is not unusual. It is the default state for any business with more than one currency in the income or cost line. The complexity scales with the number of currencies.
Why multi-currency operations break down on traditional infrastructure
The traditional banking system treats each currency as a separate account with separate operations. A USD balance is held at a USD-clearing institution. A EUR balance is held at a EUR-clearing institution. To move from one to the other, the business has to either run a bank-to-bank transfer (which crosses correspondent rails and incurs a margin) or use an FX provider (which is faster but still applies a spread).
Three structural costs follow.
The first is FX margin on every conversion. Even competitive providers charge 0.3-0.7% on standard currency pairs, and more on minor pairs. A business that converts £50,000 monthly between currencies pays £150-350 per month in FX margin alone — money that disappears into the conversion infrastructure rather than landing on the balance sheet.
The second is timing inefficiency. The business has to convert at the moment cash is needed, not at the moment the rate is favourable. A CFO who notices a strong GBP-USD rate has limited ability to act on it because the conversion is operationally tied to the payment, not separable from it.
The third is reconciliation overhead. Three accounts, three statements, three sets of incoming and outgoing flows that have to be reconciled separately and then aggregated into a single management view. The finance team spends time on the structural complexity of the setup rather than on the substance of the business.
How a single wallet handles multiple currencies
A Spondula business wallet holds multiple token denominations in the same account: GBP-S, USD-S, EUR-S, AED-S, and any other supported token. There is no separate account per currency, no separate login, no separate balance to top up or move between. Revenue arrives in whatever token the customer paid in. Outflows go in whatever token the supplier or recipient is settling in. Conversions between tokens happen on the merchant's schedule, at the merchant's chosen rate moment, at the standard 0.2% spread.
The structural change is that the currency is a property of the balance, not a property of the account. The business has one balance — denominated in whatever mix of tokens reflects current operations — and converts between the components on demand. The conversion is operationally separable from the payment because the wallet holds both sides of any potential conversion at all times.
Join the conversation.
0 comments · Be respectful, be specific, be useful.
Be the first to comment.