How debt simplification works, and when not to use it
Ten people owing ten people collapses into four payments. Here is the arithmetic, and the one case where you should switch it off.
In this guide
Debt simplification reduces a tangle of who-owes-whom to the smallest practical set of payments. It works by calculating each person’s net position — everything they paid minus everything they owe — and then matching the people in credit against the people in debit, rather than settling each expense separately. The totals are identical either way; only the number of transfers changes. In a group of five it typically drops from ten or more payments to three or four.
- Simplification never changes what anyone pays in total. It changes only who they hand it to.
- It works on net positions, so an expense you paid for and an expense you owe on cancel out before anyone transfers anything.
- The saving compounds with group size: the possible pairwise debts grow roughly with the square of the group, while the required transfers grow linearly.
- You may end up paying someone you never shared a specific expense with. That is the mechanism working, not a bug.
- Turn it off when the group needs to see exactly who owes what for which expense — reimbursements, disputes, or anything being audited.
After a week away with four other people, the raw picture is absurd. You covered the villa deposit, someone else covered the car, a third person paid for dinner twice, and by the end almost everyone owes almost everyone something. Settled literally, expense by expense, a five-person trip can generate more than a dozen small transfers — several of which cross in opposite directions on the same day.
Step one: net positions
The first move is to stop thinking about expenses and start thinking about people. For each person, add up everything they paid on the group’s behalf, subtract their fair share of the group’s total spending, and keep the difference. That single number is all that matters for settling.
| Person | Paid out | Fair share | Net position |
|---|---|---|---|
| A | $480.00 | $300.00 | Owed $180.00 |
| B | $345.00 | $300.00 | Owed $45.00 |
| C | $240.00 | $300.00 | Owes $60.00 |
| D | $225.00 | $300.00 | Owes $75.00 |
| E | $210.00 | $300.00 | Owes $90.00 |
The two columns of net positions must always match: $225.00 is owed to people, $225.00 is owed by people. If they do not balance, an expense has been recorded without a payer or without a split.
Notice what has already happened. Every expense in the trip — however many there were, whoever paid, however they were split — has collapsed into five numbers. C might have been part of eleven separate expenses; all that survives is that they are $60.00 short.
Step two: match debtors to creditors
Now match the two sides. The usual approach is greedy: take the largest debt and the largest credit, settle as much of both as possible in one payment, remove whoever is now at zero, and repeat. It terminates quickly and, in practice, produces very few payments.
Four payments, and every balance is zero. A receives $180.00 across three transfers; B receives $45.00; E makes two payments totalling $90.00. Nobody pays a cent more or less than their net position. And $225.00 is the least that could possibly move — you cannot settle a group without at least transferring what the debtors owe.
Why the saving grows with the group
In a group of five there are ten possible pairs, and a badly tangled trip can produce a debt in most of them. In a group of ten there are forty-five. The number of possible obligations grows roughly with the square of the group size, while the number of transfers needed to clear them grows in a straight line — at most one fewer than the number of people involved.
That is why simplification feels like a minor convenience for three people and an obvious necessity for twelve. It is also why it matters most on exactly the occasions when nobody has the patience for admin: the end of a group holiday, the last day of a festival house, a wedding weekend where four people paid for things on behalf of nine.
What it does and does not guarantee
- It guarantees the totals. Every person’s net position is settled exactly. Simplification is a routing decision, never a recalculation of who owes what.
- It guarantees termination. Each payment zeroes at least one person, so a group of *n* people always settles in at most *n* − 1 transfers.
- It does not guarantee the theoretical minimum. Finding the provably smallest set of transfers is a hard computational problem in general; the greedy approach gets you very close, very fast, and the difference is almost never more than a payment.
- It does not preserve the story. You may be asked to pay someone you never shared an expense with. The underlying record still shows every original expense — the payment list is a summary of the outcome, not a rewriting of the history.
- It does not fix bad data. If an expense was split wrongly, simplification will faithfully route the wrong amount to the wrong person.
Simplification changes who you pay. It never changes what you pay.
When to switch it off
- Someone is claiming the money back. An expense being reimbursed by an employer or a landlord needs a direct line from payer to payee. A simplified payment from a third party will not match the paperwork.
- A specific expense is disputed. While one line is being argued about, itemised debts keep the argument contained to that line instead of blocking the whole settle-up.
- One person does not trust the arrangement yet. A new member of the group sometimes needs to see the direct chain from what they owe to who they owe it to. Show them the itemised view once and the objection usually disappears.
- Subgroups should not be mixed. If two housemates keep a private balance separate from the wider house, simplification across the whole group will merge them. Use separate groups instead.
- A payment needs a reference. Where a transfer has to carry a reason — a shared invoice, a deposit return — the direct debt is the record. This matters more with multi-currency settlements, where a bank reference may be the only trace.
Using it in practice
Simplification is only as good as the record underneath it, and the record is only good if things were logged when they happened. A group that reconstructs a week of spending from memory on the final evening does not have a debt-simplification problem — it has a data problem, and no algorithm improves it.
Log each cost as it occurs, let the balances run for the whole trip, and simplify once at the end. That is the whole method, and it is why a group trip can settle in five minutes rather than five days.
Frequently asked questions
How does simplify debts work?
Does debt simplification change how much I owe?
Why am I paying someone I never shared an expense with?
How many payments does a group need to settle up?
When should you not simplify debts?
Jonas M.
Product contributor to Expenso’s splitting tools
Jonas works on the part of Expenso that decides who owes what. He writes about the mechanics of shared money — why simplified debts work, where splitting rules break down, and what actually changes when a bill repeats every month.
