Split the Bill / Group Settlement
Add everyone in the group and what was paid for what — get each person's net balance and the fewest possible payments to settle up, not a suggestion to have everyone pay everyone back.
1. Who's splitting?
2. Expenses
{{ error }}
Who owes whom
- {{ name }} {{ amt > 0.005 ? 'is owed ' + fmt(amt) : (amt < -0.005 ? 'owes ' + fmt(-amt) : 'settled up') }}
Settle up in {{ result.transactionCount }} transaction{{ result.transactionCount === 1 ? '' : 's' }}
Nobody owes anybody anything.
- {{ t.from }} → {{ t.to }} {{ fmt(t.amount) }}
Total expenses: {{ fmt(result.totalExpenses) }}. Money that actually needs to change hands: {{ fmt(result.totalSettled) }} — always less than the total, since paying for your own share never needs to be transferred. At most {{ result.maxTransactions }} transactions are ever needed for {{ participants.length }} people.
Add at least two people and one expense to see who owes whom.
Every calculation runs in your browser. Nothing you enter is uploaded to a server, and nothing is stored — reload the page and the trip is gone.
Why this isn't "everyone pays everyone back"
Naively, every person who's owed money collects separately from every person who owes — up to n×(n−1) possible transfers for a group of n. This tool instead nets everyone to one balance each (positive if owed, negative if owing), then repeatedly settles the largest creditor against the largest debtor for the smaller of the two amounts. Every step fully clears at least one person, so a group of n people never needs more than n−1 transactions to settle completely.
Money is tracked internally in whole paise, not floating-point rupees, so splitting an odd amount across several people — ₹100 across 3 people, for instance — never loses or duplicates a paisa; the leftover paisa is assigned deterministically rather than dropped.
When custom shares are worth using over an equal split
An equal split is right when everyone genuinely shared something the same way — a taxi, a shared starter. It's wrong the moment it isn't — someone ordered the expensive dish, someone skipped a round. Custom shares handle that exactly, and this tool checks the amounts you enter for each person add up to the expense's total before accepting them, rather than silently rescaling a total that doesn't quite add up.
Frequently asked questions
Why isn't this just "everyone pays everyone back"?
That naive approach can need up to n×(n−1) separate transfers for a group of n people. This tool nets everyone to a single balance first, then settles the largest creditor against the largest debtor repeatedly — never more than n−1 transactions for n people, and often far fewer.
Can I split an expense unevenly?
Yes — turn on "Split unevenly" for an expense and enter an exact amount per person. It must add up to the total expense amount exactly, or the tool rejects it rather than silently rescaling your numbers.
What happens to leftover paise when splitting evenly?
They're assigned deterministically to keep the total exact to the paisa — never dropped, never duplicated, and never left to floating-point rounding to sort out on its own across many small expenses.
Is my trip saved anywhere?
No. Everything lives only in this browser tab — reload the page and it's gone. Copy the summary before you navigate away if you want to keep it.
Someone shows "settled up" with a balance that isn't exactly zero — is that a bug?
No — amounts within half a paisa of zero are treated as settled, which absorbs harmless rounding rather than showing a person as owing a fraction of a paisa.