Multi-currency group expenses - the complete guide
Splitting expenses across currencies without surprises. Bank rate vs market rate, snapshotting at write-time, group currency vs expense currency, and a worked four-person settlement.
Last reviewed May 2, 2026 by The EvenRound team
The currency problem in groups
Currency is the silent multiplier on group friction. A single-currency group has one source of confusion: who paid for what. A multi-currency group has three. There's the original currency the expense was paid in. There's the currency every member thinks in (which may differ for every person on the trip). And there's the currency the eventual settlement happens in. Reconciling all three is where most apps fall apart.
A concrete case: four friends are in Tokyo. The American paid ¥18,000 for the apartment one night. The German paid €240 for a dinner because the restaurant only took Visa-credit and her debit card hadn't worked. The Brit paid £80 for a temple tour. Three days in, nobody knows what anyone owes anyone else. The natural conversation is "let's convert to USD", but whose USD rate? Today's? The day each expense happened? The day they're settling?
The answer that minimises drift is to record every expense in the currency it was actually paid in. Don't mentally convert. Don't round. The ¥18,000 stays as ¥18,000 forever. The conversion to a common currency happens once, later, at settlement, using a rate that was snapshotted the day the expense happened.
This guide is about the design choices that make multi- currency groups stable: which rate to use, when to snapshot it, and how to think about FX fees that the group ledger can't see.
Bank rate vs market rate
There are two relevant FX rates and most people conflate them.
The market rate(also called the mid-market rate) is the midpoint of what banks pay each other to swap currencies. It's the number Google shows. It's the rate Wise advertises. It's the honest reference price.
The bank rate is what your specific bank or card actually charged you. It includes a spread (banks buy at one price and sell at another, pocketing the difference) plus often an explicit FX fee on top, which varies by card issuer. Total cost is usually 1-3% above market for a decent travel card and 5-7% for a bad one.
This matters because the bank rate is invisible to the group ledger. The app sees that you paid ¥18,000. It doesn't know your card billed €115 or €112 or €118 for that. We unpack the difference in detail in bank rate vs market rate.
The principle: a group ledger should always use the market rate for its math. The bank rate is between you and your card. Trying to reconcile the two inside the group is the road to nobody settling up.
Snapshotting rates at write-time vs at-settlement
Once you've picked the market rate, the next question is which day's market rate. There are two design choices, and we made a deliberate call.
Snapshot at settlementmeans the app re-fetches today's rate every time someone opens the balances view. The advantage is that the displayed numbers always match today's reality. The catastrophic disadvantage is that balances drift, daily, for reasons unrelated to the trip - a weekend of yen weakness can change the math on an expense from three weeks ago. People log in, see different numbers than yesterday, lose confidence, and the group never settles.
Snapshot at write-timemeans we capture the market rate the moment the expense is logged and freeze it. The yen-yen ledger entry never changes. The ¥18,000 is forever ¥18,000-as-€114.36-on-Tokyo-day-2. The trade-off is small: the displayed equivalent doesn't match today's rate. The benefit is huge: the ledger is stable, the math is reproducible, and the group settles based on a snapshot they all agreed to at the time.
We chose write-time snapshotting. The math is't perfect - somebody's card got a different rate from ours, plus or minus a percent - but it's stable, and stability is what prevents groups from never settling. More in how FX rates affect settlements and live exchange rates for group trips.
Group currency vs expense currency - design philosophy
Two distinct concepts, and confusing them is where most multi-currency tools fail.
The expense currency is the currency the expense was actually paid in. ¥ for the apartment. € for dinner. £ for the temple tour. This is a fact about the world and it never changes.
The group currencyis the display currency for balances and the settlement currency by default. It's a presentation choice. A group of mostly Europeans on a trip to Tokyo might pick EUR as the group currency, but a USD-based traveller can still settle their share in dollars at the end. Changing the group currency shouldn't - and doesn't - change any expense.
This separation is what lets a four-currency trip collapse to one settlement number per person at the end. The expense list reads honestly: ¥18,000 paid by Sarah, €240 paid by Anna, £80 paid by James. The balances tab reads cleanly: in EUR (or whatever group currency), here's what each person owes. We dive into the rationale in splitting expenses across multiple currencies.
Worked example - four people, three currencies, five expenses
Sarah (USA), Anna (Germany), James (UK), and Pri (also USA) take a five-day trip to Tokyo. The group currency is EUR. Five expenses. All split equally across all four members.
- Day 1 - Sarah pays ¥40,000 for the Airbnb. Snapshotted at €254.00.
- Day 2 - Anna pays €240 for dinner. (Paid in EUR natively, no conversion.)
- Day 2 - James pays £80 for the temple tour. Snapshotted at €94.40.
- Day 3 - Pri pays ¥12,000 for groceries. Snapshotted at €76.20.
- Day 4 - Sarah pays ¥30,000 for the bullet train. Snapshotted at €190.50.
Total in group currency: €855.10. Each person's share at equal split: €213.78.
Sarah paid €254.00 + €190.50 = €444.50 → owed €230.72 back.
Anna paid €240 → owed €26.22 back.
James paid €94.40 → owes €119.38.
Pri paid €76.20 → owes €137.58.
The greedy settlement algorithm matches biggest debtor to biggest creditor. James → Sarah €119.38, Pri → Sarah €111.34, Pri → Anna €26.22 wraps the remainder. Three transfers settle the group. Sarah, who had been carrying more than half the cost, gets her real money back.
Notice that nobody argued about FX rates during the trip. The snapshots happened automatically, the balance was always visible in EUR, and everyone settled in their preferred currency at the end.
Forex fees on payments
The group ledger doesn't see card-level FX fees. If Sarah's card charged her 2.5% on the ¥40,000 expense, the ledger still records the market-rate equivalent. The delta between "market rate at write-time" and "what the card actually billed" is on Sarah's side, not the group's.
This is right and wrong at the same time. It's right because trying to reconcile FX fees across four card issuers in a group ledger is a recipe for nobody settling. It's wrong because the person who paid in the foreign currency genuinely ate a cost the others didn't.
The pragmatic fix: pick one person to pay for everything abroad if possible (the one with the best travel card), and cycle who that is from trip to trip. Everyone else reimburses in the home currency, where there's no FX. We unpack the trade-offs in forex fees on group trips and when to pay in local currency vs home currency.
Tools we recommend (the honest read)
Multi-currency is the area where most expense splitters fall flat, including some popular ones. The honest comparison:
EvenRoundhandles multi-currency on the free tier. Snapshot at write-time, separate group currency from expense currency, settle in any member's preferred currency. AI receipt scanning preserves the expense currency from the receipt itself. Designed for this from day one.
Splitwise supports multi-currency but the conversion is paywalled - currency conversion is a Pro feature. On the free tier, multi-currency groups are awkward enough that most users either upgrade or fall back to a single-currency group, both of which are trade-offs. See the side-by-side in EvenRound vs Splitwise.
Tricounthandles multi-currency on the free tier and is the European default for travel groups. Worth a look if you don't need recurring expenses or a longer-term roommate ledger. Compared in EvenRound vs Tricount.
Most spreadsheets are honestly hopeless here. Doing multi-currency in Sheets means hardcoding rates, reconciling them weekly, and chasing the cell-by-cell math. We compared the trade-offs in spreadsheet vs app and the answer for multi-currency is unambiguous.
Round-up: best expense splitter for travel. Companion pillar: group travel expenses.
Frequently asked
Travel multi-currency without doing the maths
Create a group with the currency of your choice, log expenses in whatever currency they actually happen in, and settle cleanly at the end. Multi-currency on the free tier.