Splitting costs in multiple currencies without losing money

If any part of your trip happens in another currency, the money gets harder in a way that isn't obvious until it's already gone wrong. Not dramatically — just a few percent here and there, always flowing in the same direction.

Here's what actually goes wrong, and the protocol that prevents it.

The rate has to be frozen on the day#

This is the single most important rule, and most people don't discover it until they've been bitten.

Say you pay €80 for dinner in Lisbon on a Tuesday. Your group settles up in shekels three weeks later. There are two ways an app can handle this:

Convert at the current rate. Every time anyone opens the app, the €80 gets converted using today's rate. The amount your friends owe you drifts a little every day. The screenshot someone took last week no longer matches. If the currency moves 3% in three weeks — completely ordinary — the totals silently change by 3%.

Freeze the rate at the moment of the expense. The €80 is converted once, on Tuesday, at Tuesday's rate, and that conversion is stored with the expense forever. The number never changes again.

The second is correct, and it's correct for a reason that isn't really about maths: an expense is a historical event. It happened once, at one rate. A balance you agreed on last week should be the same balance today, or you'll spend the last morning of the trip arguing with a moving target.

If your tool recalculates old expenses at today's rate, the group is settling up against a number that changes while they look at it.

This is why Lumela stores the rate per expense and never revisits it. You can display totals in any currency you like — that's a view — but the underlying record is fixed.

Conversion fees are a hidden transfer between friends#

Here's the subtler problem.

Four people are in Portugal. Dana's card charges a 2.5% foreign transaction fee. Noam's card charges nothing. Both pay for group dinners.

If you record the face value of each bill — €80, €95 — the group splits those numbers evenly and everything looks fair. But Dana's bank charged her €82 for the €80 dinner and Noam's charged him €95 for the €95 one. Over a week of Dana paying for things, she's absorbed a couple of percent of the group's total spending, alone, invisibly.

Nobody is being unfair on purpose. The record just doesn't contain the information.

Two ways to handle it:

The simple way (recommended for short trips): agree in advance that whoever has the cheapest card pays for the big shared things. Then the fee is small and it's the same person absorbing it, deliberately.

The precise way: record what the payer's bank actually charged them, not the number on the menu. When Dana's statement says ₪310, log ₪310 — that's what she is genuinely out of pocket, and it's what the group should reimburse. This is the fairest option and it requires the payer to check their banking app, which realistically happens for large expenses and not for coffee.

Cash makes it worse before it makes it better#

The classic move: one person withdraws €400 at an ATM and becomes the group's bank for the week.

The trap is treating the withdrawal itself as a group expense. It isn't — it's a transfer between the withdrawer's own accounts. If you log "ATM €400" as a shared expense, you've charged everyone for money that hasn't been spent yet, and then you'll charge them again when it is.

The rule: cash withdrawals are not expenses. Only what the cash buys is an expense. The withdrawal fee — and only the fee — can reasonably be split, because it was a genuine cost of getting the group its cash.

If one person is holding group cash, log each thing it buys as an expense paid by them. Their balance will show a large amount owed to them, which is accurate: they're carrying the group's money.

Pick one settlement currency, before you leave#

Decide up front which currency the final settle-up happens in. Usually it's the one most of the group banks in.

This matters because the display currency and the settlement currency are different things. Everyone can view the balances in whatever they think in — that's just a rendering. But the transfers at the end need one agreed unit, or you'll get a second round of conversion arguments at the very moment everyone wants to go home.

Say it once, in the first planning conversation: "we're settling in shekels." Done.

Never become the group's exchange bureau#

There's always a version of this trip where one person, being helpful, offers to change money for everyone, or to take cash from people and pay for things on their card.

Don't. Not because anyone's dishonest, but because it converts a clean set of expenses into an unauditable pile of informal transactions, all of which route through one person who is now doing bookkeeping on holiday. The moment there's a discrepancy, they're the only one who could have caused it — which is an unpleasant position to be in even when you did nothing wrong.

Log expenses. Settle at the end. Let the banks do the currency.

The protocol, in full#

Before you leave

1. Agree the settlement currency.
2. Check who has a card with no foreign transaction fee — that person pays for the big shared things.
3. Agree that ATM withdrawals aren't group expenses, only what they buy.

During the trip

1. Log every expense in the currency it was actually paid in. Don't convert in your head.
2. For large expenses, log what your bank charged you, not the face value on the bill.
3. Never let one person become the informal exchange.

At the end

1. Read out the balances in the settlement currency.
2. Send the transfers before anyone leaves.

One thing to check in any app you use#

Ask it a single question: if the exchange rate changes tomorrow, does yesterday's expense change?

If the answer is yes, you'll be settling up against a moving number, and someone will eventually notice that what they owe isn't what they agreed to. If the answer is no, everything else is detail.