How to settle group expenses in the fewest possible payments
Short answer
Calculate each person’s net position — what they paid out minus what they owed — then match the biggest debtor to the biggest creditor and pay the smaller of the two amounts. Repeat until everyone is at zero. A group of n people can always settle in at most n−1 payments, and usually fewer, instead of the up to n×(n−1)÷2 individual debts that exist on paper. Six people with fifteen possible debts typically settle in three or four transfers.
Key points
- Only net positions matter. Who paid whom for what is irrelevant at settle-up time.
- Largest debtor pays largest creditor, the smaller of the two amounts. Repeat.
- n people always settle in n−1 payments or fewer.
- The net positions must sum to zero — if they do not, an expense is missing.
- Do not simplify when it means paying someone you have no relationship with.
Why the obvious approach creates so many payments
If you settle expense by expense, every expense creates a debt from each participant to whoever paid. Six people across a weekend generate dozens of tiny debts pointing in every direction — and many of them cancel out. If A owes B £40 and B owes C £40, then A can pay C £40 directly and both original debts vanish. Debt simplification is just this observation, applied systematically.
The method, by hand
- 1
Work out what each person paid
Total everything each person put on their card or paid in cash for the group.
- 2
Work out what each person owed
Their share of every expense they were part of — not necessarily an equal share of everything.
- 3
Subtract to get each net position
Paid minus owed. Positive means the group owes them; negative means they owe the group. Check the positives and negatives cancel to zero — if they do not, an expense is missing or double-counted.
- 4
Match the largest debtor to the largest creditor
The person most in the red pays the person most in the black, the smaller of the two amounts. One of them lands exactly on zero and drops out.
- 5
Repeat until everyone is at zero
Each round removes at least one person, so a group of n always finishes within n−1 payments.
A worked example
Six friends, a weekend away, £1,320 spent in total — £220 each.
| Person | Paid | Owed | Net |
|---|---|---|---|
| Anya | £640 (the house) | £220 | +£420 |
| Ben | £310 (groceries, fuel) | £220 | +£90 |
| Chi | £240 (dinner) | £220 | +£20 |
| Dev | £90 (breakfast) | £220 | −£130 |
| Eli | £40 (coffees) | £220 | −£180 |
| Fay | £0 | £220 | −£220 |
The positives total £530 and the negatives total −£530. They cancel, so the ledger is complete.
| Round | Payment | Result |
|---|---|---|
| 1 | Fay → Anya, £220 | Fay is settled. Anya still owed £200. |
| 2 | Eli → Anya, £180 | Eli is settled. Anya still owed £20. |
| 3 | Dev → Anya, £20 | Anya is settled. Dev still owes £110. |
| 4 | Dev → Ben, £90 | Ben is settled. Dev still owes £20. |
| 5 | Dev → Chi, £20 | Everyone at zero. |
Five payments instead of the fifteen debts that existed on paper. Nobody pays anyone twice except Dev, who was the most tangled position to unwind.
The maths, briefly
A group of n people has up to n×(n−1)÷2 possible debt relationships — 15 for six people, 45 for ten. Simplification always finishes in at most n−1 payments, because every round zeroes out at least one person. That is a reduction from quadratic to linear, and it is why the benefit grows sharply with group size: ten people go from up to 45 debts to at most 9 payments.
When not to simplify
- When it routes money between people who barely know each other. Fay paying Anya £220 is fine if they are friends. If Fay is someone’s new partner and Anya is a colleague, sending a stranger £220 feels wrong even when it is arithmetically correct.
- When someone wants to see the direct relationship. "I owe you for the dinner you paid for" is socially legible. "I owe someone I did not eat with £180" is not, and some people dislike it enough to be worth accommodating.
- When the group is still spending. Simplify at the end, not mid-trip. Simplifying twice creates payments that themselves need reconciling.
- When one payment would exceed a transfer limit. Splitting one large payment into two is a practical constraint that beats mathematical elegance.
Getting the net positions right
Almost every settlement that goes wrong goes wrong before the simplification — in the ledger, not the algorithm. Three checks:
- 01Do the nets sum to zero? If not, an expense is missing, duplicated, or has the wrong payer. Fix it before matching anyone.
- 02Did every expense have the right participants? Four of six went to the aquarium. If that was logged as a six-way expense, two people are being charged for a day out they did not have.
- 03Are mid-trip repayments recorded as payments, not expenses? If Dev handed Anya £50 in cash on day two and it was logged as an expense, it gets split six ways and the ledger is wrong in two directions at once.
Work out the shares first
Trip cost split calculator
Split flights, hotels, food, and taxis across everyone on the trip.
Everyone pays the same.
Enter a total trip cost to see the split.
- Person 1$0.00
- Person 2$0.00
- Person 3$0.00
- Person 4$0.00
- Total trip cost
- $0.00
- Total
- $0.00
A trip is dozens of expenses, not one.
FamZam logs each one as you go in any currency, converts it in real time, and works out the fewest payments needed to settle up at the end.
Frequently asked questions
How do you settle group expenses with the fewest payments?
Work out each person’s net position — total paid minus total owed — then have the largest debtor pay the largest creditor the smaller of the two amounts. Repeat until everyone reaches zero. A group of n people always settles in at most n−1 payments, and usually fewer.
What is debt simplification?
It is the practice of cancelling out circular debts so money moves in as few transfers as possible. If A owes B and B owes C the same amount, A pays C directly and both original debts disappear. Bill splitting apps apply this automatically across a whole group.
How many payments does a group of six need to settle up?
At most five, and often three or four, compared with the fifteen possible debt relationships that exist between six people. Each round of matching zeroes out at least one person, so the maximum is always one fewer than the number of people.
Why do my net positions not add up to zero?
Something is wrong with the ledger, not the maths. The usual causes are a missing expense, an expense entered twice, the wrong person recorded as payer, or a mid-trip repayment logged as an expense rather than a payment. Find it before settling — the algorithm cannot fix a wrong input.
Is debt simplification always a good idea?
Not always. It can route a large payment between two people who barely know each other, which feels wrong even when it is arithmetically correct. Some people also prefer the direct relationship of paying back whoever actually covered them. Both are reasonable grounds to settle the longer way.