Five friends, one Airbnb in Lisbon, three credit cards, and at the end of the week somebody is mentally tallying who paid for the cab from the airport. Travel expenses break friendships not because the numbers are big, but because the process is bad. People feel watched, or unheard, or quietly resentful, and nobody wants to be the person sending the spreadsheet.

The fix is boring: agree on the rules before the trip, log everything in one place, settle once. This guide walks through how to do exactly that — what to decide upfront, which split modes actually work, and how to close the books without anyone feeling like the bookkeeper.

Agree on the rules before anyone books a flight

Money fights on trips are almost always rules fights in disguise. Two people had different mental models of what "we'll split it" meant, and now they're arguing about a 14-euro lunch. Pre-trip, pin down four things in a group chat:

1. What gets split, and what doesn't. Lodging, transport between cities, group meals, group activities — yes. Souvenirs, drinks ordered after one person went to bed, the upgrade somebody took on the rental car — no. Write it down. The default rule "everything we do together gets split" sounds fair until somebody buys a 90-euro hat.

2. The split mode you'll default to. Equal split is the lowest-friction option and fine for short trips with similar appetites. Percent splits are useful when income differs widely and the group has agreed (explicitly) that the higher-earning friends pay more. Exact-amount splits — "I had the steak, you had the salad" — are honest but exhausting if you do them at every meal. Pick one default, allow exceptions per expense.

3. Currency and conversion. If you're crossing borders, agree on a single base currency for the final settlement. Lock the conversion approach early: most groups use the rate on the day of the expense, not the day of the settlement. The free Frankfurter API (powered by the European Central Bank reference rates) is the standard most apps use.

4. Who fronts what. One person fronting the entire trip is convenient and a trap — they end up out three thousand euros for two weeks while the bank's reward points pile up unevenly. Rotate the fronting role, or at least have two or three people split the heavy charges (Airbnb, train tickets).

These four rules fit on one screen of a group chat. The argument you avoid is worth the awkward thirty seconds it takes to write them.

Log expenses where everyone can see them

The single biggest predictor of post-trip drama is whether expenses were logged in real time or reconstructed from memory two weeks later. Reconstruction is where lies live — not because anyone is dishonest, but because nobody remembers exactly what the taxi from the marina cost, and the receipt is gone, and the higher number wins by default.

Three options, ranked by how they actually behave on a trip:

A shared spreadsheet. Free, flexible, terrible on mobile. Two people will edit the same cell on a bumpy bus, and one edit will silently win. Fine for two people, breaks past four.
A dedicated splitting app. Splitwise was the default for a decade, with credible alternatives now including Settle Up, Tricount, and our own NomadCrew which adds a multi-currency settlement engine built for trips. For a fuller comparison, see Splitwise alternatives in 2026.
A group budget board with split logic. This is what trip-mode tools do: one shared log of expenses, every entry tagged with who paid and how it's split, the math compiled at the end. The difference from a generic splitter is that you also see the running total — useful when somebody asks "are we still on budget?".

Whichever you pick, the rule is: log it before the next meal. Memory is the enemy. A photo of the receipt or a one-line entry takes seven seconds; the argument it prevents takes thirty minutes.

Pick the right split mode for each expense

Not every cost wants the same logic, and forcing equal split on everything is how resentment builds. A working mental model:

| Expense type | Default split | Notes | | ------------------- | ------------------------- | ------------------------------------------------------------------------------ | | Lodging | Equal per night per head | Adjust if one person took the master bedroom | | Group meals | Equal | Unless someone's not drinking, then exact-amount on the alcohol line | | Taxis between sites | Equal among riders only | The two people who walked don't pay for the cab the four drinkers took home | | Activities | Per participant | Skip-the-line tickets for three doesn't get split with the two who slept in | | Groceries | Equal | If somebody has a dietary restriction that bumps the bill, ask first | | Souvenirs | Personal, never split | Even when bought together |

The pattern: default to equal for the convenient case, but use exact or per-participant the moment somebody opts out. Apps that support all three modes (equal, percent, exact) cover this without ceremony. Apps that only do equal force you to either fudge it or run a side-channel reconciliation, which is where bad blood starts.

For couples splitting unevenly because of income, the 50/30/20 rule still works as a per-person guideline — but proportional contribution to shared expenses is a separate decision and should be agreed before the trip, not negotiated at the dinner table.

Settle once, in as few transfers as possible

The thing every group gets wrong on the last night: trying to settle expense-by-expense. Six people, forty expenses, everybody owes everybody a little — and now you're trying to Venmo your way through a matrix of 1.50-euro debts at 2am.

Don't do that. Settle once, with a debt-simplification algorithm.

A simple greedy algorithm reduces a tangled web of mutual debts down to the minimum number of transfers: usually one or two payments instead of fifteen. Most splitting apps do this for you under the hood — Splitwise calls it "Simplify Debts", NomadCrew's trip mode calls it the "settlement plan". The underlying math is straightforward: sort everyone by net balance (positive owed, negative owing), then have the largest debtor pay the largest creditor, repeat.

A few things to know about the algorithm:

It minimizes count of transfers, not always who pays whom. Sometimes Anna ends up paying Mark even though her actual ledger of expenses was with Carlos. Most people don't care; some do. If your group cares about "real" debt paths, run the actual ledger instead and accept more transfers.
It assumes everyone trusts everyone. If your group has trust issues, simplification is the wrong tool — settle pairwise.
It only works once everybody has logged everything. If someone is still entering expenses three days after the trip, the simplification will shift around. Set a deadline ("everything logged by Sunday night") and lock it.

After settlement, archive the trip and move on. Don't leave the group chat alive for the awkward "hey did the money come through" pings. A clean close is part of the deal.

Currency conversion: pin the rate, not the date you settle

Cross-border trips have one extra wrinkle: an expense paid in CHF on Tuesday and reimbursed in EUR on Sunday is two different numbers depending on which day's rate you use. The convention that prevents arguments:

Convert each expense at the rate on the day it was paid, store both amounts, and only convert again if the underlying source needs auditing.

This way, the person who paid 80 CHF on a strong-franc day doesn't lose 4% because the franc dipped before settlement. Apps that handle this correctly cache the historical rate per expense; apps that re-convert at settlement quietly redistribute the FX risk and somebody always notices. The European Central Bank's reference rates are the de facto standard and what Frankfurter (and NomadCrew) use under the hood.

For a deeper dive into running expenses in multiple currencies — especially when you live across them — see Multi-currency budgeting on the road.

A worked example

Five friends, four days in Lisbon, EUR base. Anna pays the Airbnb upfront (920 EUR). Mark and Carlos each pay for one group dinner (~85 EUR each). Lina buys the train tickets to Sintra for four (60 EUR — Eva slept in). Eva covers groceries twice (~40 EUR total).

Total: 1,190 EUR across five people, but Eva only joined four expenses out of five. Equal split on lodging and dinners and groceries = 218 EUR per person. Sintra is 15 EUR per Sintra-goer; Eva pays zero for that.

Net balances after the math:

Anna: paid 920, owes 218 → +702
Mark: paid 85, owes 233 → −148
Carlos: paid 85, owes 233 → −148
Lina: paid 60, owes 233 → −173
Eva: paid 40, owes 218 → −178 (no Sintra)

Greedy settlement: Eva pays Anna 178, Lina pays Anna 173, Carlos pays Anna 148, Mark pays Anna 203 (wait — that overshoots by 55, so Mark pays Anna 148, then Mark pays Lina nothing because Lina is already settled — let the app do this part). Four transfers, all into one account, done.

That's the entire trip closed in four taps on the last evening, instead of forty-five tiny Venmo notifications over the next two weeks.

Close the loop and try it on a real trip

The pattern is always the same: agree upfront, log in real time, split per-expense honestly, settle once with simplification. Apps don't fix bad rules; they enforce good ones if you set them.

If your next trip is in the next month, you don't need to read more — you need to set up the shared space and invite your group. NomadCrew's trip mode is built for exactly this: one shared board, multi-currency by default, three split modes, a settlement engine on the last day, and an export to CSV when you're done. Free to try, no card required.

For groups planning bigger trips with structured budgets, the group trip budget template walks through the eight line items every trip needs and how to pre-allocate them.