The math behind "who owes who" — and why most apps get it wrong
When a group splits several expenses, the naive way to settle up means way more payments than necessary. Here's how SplitHonest fixes that.
The problem with splitting expense-by-expense
Say four friends — Alex, Sam, Jordan, and Taylor — share a weekend. Alex pays for dinner, Sam pays for the Airbnb, Jordan pays for gas, and Taylor pays for groceries. If you settle each expense on its own, you can end up with 8, 10, even 12 individual payments criss-crossing the group — Alex owes Sam for the Airbnb, Sam owes Jordan for gas, Jordan owes Taylor for groceries, and so on. Most of those payments are redundant: if Alex owes Sam $20 and Sam owes Alex $15 from a different expense, that's really just Alex owing Sam $5 — not two separate payments.
What SplitHonest actually does
Instead of tracking payments expense-by-expense, SplitHonest calculates each person's overall balance across every expense in the group, then works out the smallest possible number of payments needed to settle everyone up completely. In the example above, what could have been 8+ individual transfers usually collapses down to 2 or 3 — often just "Taylor pays Sam $34, Jordan pays Alex $12," and everyone's even.
Settling expense-by-expense
8 payments
Simplified by SplitHonest
2 payments, same result
Why this matters
Fewer payments means less awkwardness, less back-and-forth in the group chat, and less chance someone forgets to pay their $4 share of something from three weeks ago. It's also just the mathematically correct way to settle a shared ledger — not a nice-to-have, the right answer.
Try it yourself
Every group in SplitHonest shows this automatically — add your expenses, and the settle-up screen tells you exactly who should pay who, and how much, with the fewest possible transactions.