---
title: "Holding client revenue in three currencies without losing on FX"
description: "Multi-currency accounts for software companies: hold USD, EUR and GBP as they arrive, pay costs from matching balances, and convert deliberately — not per payment."
url: "/blog/multi-currency-accounts-software-companies/"
date: "2026-07-17"
author: "Valeria Vahorovska"
tags: ["Guides","Cash Flow"]
---

# Holding client revenue in three currencies without losing on FX

The way to hold client revenue in three currencies without bleeding on FX is to stop converting at the edges: let dollars arrive as dollars, pay dollar costs from the dollar balance, and convert only the genuine surplus — deliberately, in sized conversions you time, not per-payment ones the calendar forces. A software company that matches flows this way pays the spread once on its true net exposure instead of twice on every gross movement.

This is the quiet FX tax on [every dev shop and studio](/studios/) with international clients: the US client pays $30,000, it auto-converts on arrival; three weeks later you owe your US contractors $11,000, converted back. Two spreads, both on money that never needed to change denomination. Multiply by every month and every currency, and it's the same *"3% of my gross margin"* leak operators complain about — [we covered the payout half already](/blog/pay-your-contractor-bench/); this is the holding half.

## The matching principle

Think of each currency as its own small P&L:

- **USD in:** US client retainers, milestone payments. **USD out:** US contractors, US SaaS tools, cloud bills.
- **EUR in:** EU clients. **EUR out:** the Lisbon and Warsaw bench, EU vendors.
- **GBP in:** UK clients. **GBP out:** payroll, office, UK suppliers.

Matched flows — dollar costs paid from dollar revenue — carry **zero FX cost**. The only money that ever needs converting is each currency's net surplus or deficit, and that's a fraction of gross flow. The structure that enables it is simply [a balance per currency](/blog/how-nested-accounts-work/): nested wallets under one relationship, not three bank accounts in three countries.

Two disciplines make it work:

**Bill clients in their currency, into local details.** A US client paying a domestic ACH to a US account number pays faster and cheaper than one wiring internationally — and the FX decision becomes yours, not theirs. [Local receiving details per market](/docs/accepting-payments/what-is-a-virtual-iban-and-how-do-customers-pay-by-bank-transfer/) is the feature to insist on.

**Convert on purpose, not by default.** Auto-conversion on arrival is the expensive convenience: it takes the morning's rate on every payment. Holding and converting the monthly surplus in one sized move pays fewer spreads at better rates — and lets you skip converting entirely the week before the bench payout draws that balance down anyway.

## What to check before you park revenue anywhere

**Where the money actually sits.** 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 UI over an unregulated wrapper is not. [Ask where your money sits](/blog/where-your-money-sits/), in whose name, under which regulator.

**The spread, not the fee.** Providers advertise the fixed fee and earn on the rate. Price any provider by comparing their conversion against the mid-market rate at the same moment.

**The reconciliation story.** Three currency balances that don't flow into Xero are three more tabs in [the Friday matching ritual](/blog/reconcile-payments-to-xero/). Balances, invoices and payouts should book themselves.

**Concentration.** The account that holds your revenue shouldn't be the single point of failure for payroll. The [two-account posture](/blog/the-two-account-rule/) applies to multi-currency setups too: operating layer for flow, chartered bank for the vault.

## How Fynex runs it

Fynex treats multi-currency as the default shape of a modern software business, not an add-on. [Invoicing](/features/invoicing/) bills each client in their currency and lands the money in the matching wallet; [payouts](/features/payouts/) pay each contractor from the matching balance over their local rail; the [cash view](/features/cash/) shows every balance, every currency's forecast, and your net FX exposure in one position — so "should we convert the EUR surplus this week?" is a decision with numbers attached, not a guess. 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.

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 exactly once — on the money that genuinely needed to move.