Here's a situation every friend group eventually produces: you owe Alex $30 from dinner, Alex owes Sam $30 from the taxi, and Sam owes you $30 from the tickets. Three debts, three awkward reminders, three bank transfers waiting to happen.
Or: zero transfers, because the loop cancels itself. Nobody needs to send anything — each person is owed exactly as much as they owe. Recognizing and collapsing these loops is called debt simplification, and it's one of the quietly great ideas in shared-expense tracking. Here's how it works, when it applies, and what it does and doesn't change.
The core idea: net position is what matters
Every debt in a friend group is an edge in a little graph: an arrow from the person who owes to the person who's owed. What each person actually cares about, though, isn't the arrows — it's their net position: everything owed to them minus everything they owe.
Debt simplification is the observation that many different sets of arrows produce the same net positions, and some sets need far fewer payments than others. If a rearrangement leaves everyone's net position untouched, it is financially identical — and everyone should prefer the version with fewer, smaller transfers.
The perfect circle above is the cleanest case: you → Alex → Sam → you, all $30. Everyone's net position is zero, so the debts can simply be cancelled. No money moves at all.
A worked example with leftovers
Loops are rarely perfect. Say:
You owe Alex $50
Alex owes Sam $30
Sam owes you $20
Net positions: you owe $30 net ($50 out, $20 in), Alex is owed $20 net ($50 in, $30 out), Sam is owed $10 net ($30 in, $20 out).
There's a $20 circle hiding in those three debts (the largest amount that traverses the full loop). Cancel it, and the remainder is:
You owe Alex $30
Alex owes Sam $10
Sam and you: square
Same net positions, but three payments became two, and $100 of gross debt became $40. Nobody gained or lost a cent — the bookkeeping just stopped exaggerating how entangled everyone is.
Why bother, if the money is the same?
Because gross debt has real costs even when net debt is small:
Every open balance is a small social liability. It's a reminder that might need sending, an ask that might feel awkward, a thing to remember. Three debts of $30 weigh more on a friendship than their $0 net suggests.
More transfers, more friction. Each settlement is a payment app round-trip and a "did you get it?" — pure overhead when a rearrangement could have avoided it.
Inflated balances misrepresent relationships. If the ledger says you owe Alex $50 while Sam owes you $20 within the same loop, you look more indebted than you functionally are.
Simplification makes the ledger tell the most economical version of the truth.
What simplification is not
Worth being precise, because the term can sound like financial engineering:
It's not debt forgiveness. Nothing is waived; every net position is preserved exactly.
It's not pooling. Your debts remain yours, person to person. Simplification only cancels amounts that traverse an actual loop back to you.
It moves no money. It's a bookkeeping event — the recognition that certain obligations already offset.
One design consequence: since no money moves, a good tracker should record simplification as an entry, not perform it silently. When HiBill simplifies a circle of debts, it writes a system entry into each affected timeline — "this is one step of a debt simplification, a circle of debts that cancelled out; no money changed hands" — so months later you can still see exactly why a balance jumped from $50 to $30. A balance that changes without a visible cause is how trust in a ledger dies, even when the change was correct.
HiBill also keeps simplification explicit rather than automatic: if a loop exists among your balances, you can trigger the cancellation; if none exists, it tells you there's nothing to simplify. Some group-pot apps instead restructure everyone's debts continuously and invisibly, which minimizes transfer count but means the balance you see may connect you to expenses you never shared. Between friends, your balance changed because your own debts formed a circle is easy to accept; your balance changed because the algorithm rerouted the group is not.
When it applies (and when it can't help)
Simplification needs a loop, and loops need at least three people with debts pointing in a circle. It can't do anything for:
Two-person balances. Debts between you and one friend already net automatically — every decent tracker offsets your $40 against their $15 into one $25 balance. That's netting, the two-person special case; simplification proper is the multi-person version.
One-directional chains. If you owe Alex and Alex owes Sam but Sam owes nobody, there's no circle. (Money could skip the middle hop — you pay Sam directly — but that changes who owes whom, which is a different, consent-requiring operation.)
Loops arise naturally wherever the same people share expenses with rotating payers — flatmates, trip groups, regular dinner crews. If that's your situation, circles are quietly accumulating in your balances right now.
The takeaway
Debt simplification is netting, extended around a circle: find debts that chase each other in a loop, cancel the common amount, leave every net position intact. Fewer transfers, smaller balances, same truth. The best implementations do it transparently — visibly, per-person, as a recorded event — so the ledger gets simpler without getting mysterious. If your friend group's debts feel more tangled than they should, the tangle may already be a circle waiting to disappear.