How to split expenses when the trip crosses currencies

· 4 min read

Multi-currency splitting seems like it should be a solved problem, and it mostly is — except for one decision that groups get wrong, which then produces an argument at the end of the trip.

The decision is when you convert.

Convert when you spend, not when you settle

Say your group spends 400 dirhams on a dinner in Dubai. Someone logs "400 AED". Two weeks later you settle up, and now somebody has to turn that into rupees.

At which rate? The rate on the night? The rate today? The rate the card actually charged, which includes a markup nobody can find? The three answers differ by a few percent, and across a whole trip a few percent is real money — and more importantly it is arguable money, which is worse.

Converting at the moment of capture avoids all of it. The expense goes in at the rate that day, the rupee figure is fixed, and nobody relitigates it later. It also means your running total is meaningful while you are still travelling, which is when knowing what the trip is costing is actually useful.

This is what TripSynk does — a foreign-currency expense converts to rupees when you add it, and that figure is what the ledger carries.

The theoretical objection is that capture-time conversion is less "correct" than using the rate you were actually charged. That is true. It is also not worth the friction, because the alternative is a group of six trying to reconcile six different card statements with different markups.

The card fee problem

Here is the part that genuinely is uneven, and it is worth handling explicitly.

If Priya pays a 400 AED dinner on her Indian card, she is charged the conversion rate plus a foreign transaction fee — typically 2 to 3.5 percent, sometimes with GST on top. If Rahul pays the next one with a travel card at a better rate, he is charged less for an equivalent expense.

So the person with the worse card is quietly subsidising the group, every single time they pay.

Three reasonable approaches:

Ignore it. If everyone is paying roughly equally with similar cards, the differences wash out and it is not worth tracking. This is the right answer for most trips.

Nominate a payer. One person with the best card pays for as much as possible, everyone reimburses in rupees. Cleanest, and it also simplifies the ledger enormously — fewer people paying means fewer debts. The catch is that person is carrying a lot of the group's money, so settle promptly.

Log the fee. If one person is genuinely absorbing a lot of fees, add it as a small shared expense. Fair, and more effort than most groups will sustain.

The one thing not to do is leave it unspoken. The person paying the fees notices; they usually just do not say anything.

Cash changed at different rates

The other quiet unevenness. Someone changed money at the airport at a bad rate, someone else used an ATM at a good one, someone got a decent rate in the city.

The practical answer is to treat cash as its face value in the local currency and convert at the standard rate like any other expense, rather than at what each person personally paid. Trying to track individual exchange rates is a rabbit hole and produces almost no fairness for a great deal of admin.

If someone got badly stung at an airport counter, that is a personal loss, the same as losing a note. Absorbing it into the group ledger means everyone pays for one person's decision to change money at the worst possible place.

Practical rules

Log in the currency you actually paid. Not a mental conversion. Enter 400 AED, let the app do the rest. Mental conversions at dinner are where the errors come from.

Pick one settlement currency and stick to it. For an Indian group that is rupees. Everything converts to it once, and the settle-up is in rupees regardless of where the money was spent.

Screenshot the payment. In countries where UPI works — and that list now includes UAE, Singapore, France, Nepal, Sri Lanka and several others — the payment confirmation has the amount, the payee and the date, and TripSynk reads those directly.

Settle in rupees. Do not try to settle in the foreign currency. Everyone is home, everyone has a rupee account, and the point of the exercise is for the transfers to actually happen.

The summary

Convert at the point of spending, keep one settlement currency, and be honest about the card-fee unevenness rather than pretending it is not there.

The reason to fix the timing is not precision — it is that a number recorded once and never revisited is a number nobody argues about, and the goal of a trip ledger is to end the conversation rather than to be perfectly correct.

← All posts