Splitting a group dinner bill in a spreadsheet took me 20 minutes. Now it's a paste.
Last summer I organized a ten-person trip. The group tab was one card, but people paid for different meals, some covered the Airbnb, one person bought all the groceries. At the end I opened a spreadsheet and spent twenty
Last summer I organized a ten-person trip. The group tab was one card, but people paid for different meals, some covered the Airbnb, one person bought all the groceries. At the end I opened a spreadsheet and spent twenty minutes building a balance table β and then had to defend every number to people who were sure they'd paid more.
ExpenseSplit is the thing I wish I'd had. You list the shared costs and who paid what, plus how the split should work, and it returns each person's balance: what they owe or are owed. No spreadsheet, no defending formulas.
The arithmetic is simple and that's the trap
On paper it's subtraction and division. In practice the hard parts are uneven shares β someone only ate half the group dinner β and multiple payers covering different things. A spreadsheet handles this, but only after you build the model correctly once, and only if everyone trusts your model.
The tool's job is to remove the model-building step and the trust gap. It computes per-person balances and gives you a copyable summary you can paste into the group chat. The math is boring on purpose; the value is that it's transparent and fast.
What "uneven shares" means in practice
Most splits aren't equal. A couple shares one room cost. Three people skip the excursion. I built it to accept shares per person per expense rather than forcing a single equal split, because the equal split is the rare case, not the default.
When I tested it on the trip data afterward, it reproduced my hand-built numbers exactly β which was the point. I wanted a second computation I didn't have to defend, because the first one was mine and therefore suspect to everyone else.
Where it fits
ExpenseSplit is a paste-first tool: you enter the costs and payers, you get balances. No account, no syncing everyone into an app they'll never open. For a one-off trip or a roommate month, that's the right weight.
The honest limit: it's a calculator, not a bookkeeping system. It doesn't track who's paid you back over time or handle recurring shared bills with interest. If you need persistent multi-month tracking, a spreadsheet or a dedicated split app still wins. This is for the moment after the bill arrives and before the argument starts.
What I'd hand-check anyway
Even with the balances computed, I still confirm the input once. A typo in who paid β entering the wrong name for a fifty-dollar dinner β produces a clean, confident, wrong answer, and no tool flags that. The computation is only as trustworthy as the list you typed. I also keep ExpenseSplit for the one-off case; for a household running shared costs every month, a persistent tracker saves more friction over time. The right tool depends on whether the split is a moment or a habit, and most trips are moments.
FAQ
How does ExpenseSplit handle uneven splits?
You can assign shares per person per expense, so someone who ate half the dinner carries half the cost. It's not locked to an equal split across everyone.
Does it need everyone to install an app?
No. You enter the costs and payers yourself and get a copyable summary to share. No one else needs an account.
What does the output look like?
A per-person balance table: what each person paid, what they owe, and the net they should send or receive, ready to paste into a chat.
Is this a replacement for long-term shared-expense tracking?
No. It computes a one-time settlement. It doesn't persist balances across months or track repayments over time.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.