Who owes who: settling up after a trip without a spreadsheet

Every group trip ends with the same five minutes. Somebody says "so… should we sort out the money?" and the room goes quiet in a very specific way.

This is a short guide to making those five minutes painless — and to understanding why the numbers your app shows you sometimes feel wrong even when they're right.

Two ways to answer "who owes who"#

Say three people go away for a weekend.

• Amit pays ₪900 for the cabin.
• Bar pays ₪300 for groceries.
• Carmel pays ₪150 for gas.

Total: ₪1,350, so ₪450 each.

The pairwise answer looks at each relationship separately. Bar owes Amit ₪150 net; Carmel owes Amit ₪150 net; Bar and Carmel are square with each other on gas and groceries. Two transfers, both to Amit, both explainable in one sentence.

The simplified answer treats the whole thing as a graph and finds the minimum number of transfers that settles everyone. In a three-person case it often looks identical. In a ten-person case it does not: it will happily tell you to send ₪380 to someone you never shared a single expense with, because it netted your debt to Dana against Dana's debt to them.

Both are arithmetically correct. Only one survives contact with a tired group in a car park.

Why "optimal" feels wrong#

The simplified answer optimises for a metric nobody actually cares about: number of bank transfers. Sending two transfers instead of three costs you approximately eleven seconds.

What it costs in exchange is traceability. When Yael asks "why do I owe Tom ₪380? I didn't buy anything with Tom", the honest answer is "because the algorithm routed your debt through two other people." That's a fine answer for an engineer and a terrible one for a friend.

The purpose of the settle-up isn't to minimise transfers. It's to end the trip with nobody privately thinking they got the worse end of it.

Pairwise balances lose the elegance and win the argument. That's why Lumela shows pairwise and lets you open any pair to see both directions itemised — every expense that added to what you owe them, and every one that added to what they owe you.

The four-minute settle-up script#

Do this on the last morning, in person, before anyone drives off. It works because it's public and finite.

1. Get the list up on one screen. Not a spreadsheet on a laptop — a phone that gets passed around. If your tool can't produce a per-person balance in one tap, that's the tool's fault, not yours.

2. Read it out loud. "Yuval, you're owed 340. Dana, you owe 180. Noam, you owe 160." Saying numbers out loud does something a screen doesn't: it invites correction while everyone is still in the room.

3. Handle objections immediately. Someone will say "wait, was I in on the boat trip?" Open the expense, look at who's included, fix it, and let the totals recalculate. This is the whole reason to keep receipts and per-expense participant lists — so a question takes fifteen seconds instead of becoming a topic.

4. Send the transfers before you leave. Not "I'll do it tonight." Tonight has a way of becoming next Thursday, and next Thursday has a way of becoming an awkward reminder message. Everyone has their banking app open right there. Do it in the room.

Things that make the last morning worse#

Rolling reimbursements during the trip. Ten small transfers throughout the week feel responsible and make the final total impossible to verify. Log everything, settle once.

A tracker only one person can see. If the balances live in one person's notes app, that person becomes both accountant and defendant. Shared visibility from day one means the numbers were agreed continuously rather than presented at the end.

Currencies that moved. If your tool converts at today's rate rather than the rate on the day of the expense, the totals shift under everyone's feet. Anything you screenshotted last Tuesday no longer matches. Freeze the rate per expense — more on that here.

Guests who don't exist in the system. If someone joined for two nights and your tracker can't represent them, their share silently lands on whoever paid. Add them as a guest rather than "sorting it out separately", because "separately" means "never".

What about the person who paid for everything?#

Most groups have one. They booked the place months ago, put the deposit on their card, and have been ₪2,000 out of pocket for six weeks.

Two things help:

1. Log the big-ticket items when they're paid, not when the trip starts. A booking made in March is a March expense. Everyone sees the number early and nobody is surprised at the end.
2. Let them ask for a partial early. There's nothing wrong with "the cabin's paid, can everyone send their 400 now?" It's much less awkward in March than a full settle-up in August, and it stops one person financing the group for a quarter.

When someone doesn't pay#

It happens. Usually not maliciously — someone forgets, then feels bad, then avoids the topic, then it's been a month.

The fix is boring: a shared record that everyone can see removes the need to chase. Nobody has to be the person who sends the message, because the balance is just there, visible, quietly unresolved. In practice most people close it within a day of noticing.

If it goes on longer than that, one direct message, once, without commentary: "hey — think the ₪160 from the cabin is still open?" And then let it go. No trip is worth the friendship, and a group that keeps a running score is going to stop travelling together anyway.

The one-line version#

Show people numbers they can trace, out loud, in a room, once, before anyone drives home.