// trip expense splitter
Split costs. Settle clean.
Log who paid for what on your trip or event - this works out exactly who owes who, then hands you a PDF for the group chat.
Name the trip or event
This shows up as the title of your settlement report.
A backup lets you move this trip to another device or browser, or keep an extra copy.
Used only for display in totals and the PDF - no conversion happens.
Who's splitting this?
Add everyone involved. You can remove someone from a specific expense later if they sat it out.
Log an expense
By default the cost splits equally among the people you check below - switch to custom if shares differ.
Logged expenses - tap "edit" to change one
Already settled directly?
If someone paid another person back in cash or by transfer outside any expense above, record it here so the final settlement accounts for it.
Settlement summary
Here's exactly who needs to pay who.
Who owes / is owed
Already settled directly
Settle up (minimum transactions)
How to split expenses after a trip (without the group chat math)
Anyone who's been on a group trip knows the pain that comes after it: a dozen forwarded screenshots, someone's "I think I paid for the cab too?", and a WhatsApp thread no one wants to scroll back through. This trip expense splitter does the math for you - log who paid for what, mark who actually took part in each expense, and get a clean, downloadable settlement that tells everyone exactly what they owe.
1. Name your trip or event
Start by giving your trip, party, or outing a name - "Goa Weekend," "Flatmates April," "Office Offsite." This becomes the title of your final report, so future-you can tell it apart from the next one.
2. Add everyone splitting the bill
Type in each person's name and add them one by one. You need at least two people for splitting to make sense, but there's no upper limit - this works just as well for a couple's weekend as it does for a 15-person bachelor party.
3. Log each expense as it happened
For every expense, enter what it was for, the amount, and who actually paid the bill at the counter. By default the cost splits evenly across everyone - but if someone skipped that activity, sat out the dinner, or wasn't around for the cab, just uncheck their name. They're left out of that one split entirely, while still being part of the trip overall. If the split isn't even - say one person's hotel room cost more, or someone only had a starter while everyone else had a full meal - switch to a custom amount or percentage split for that one expense instead.
4. Record anything already settled directly
If someone paid another person back in cash or by UPI/bank transfer mid-trip - outside of any group expense - log it as a direct payment. The final settlement subtracts it automatically, so the numbers reflect what's actually still owed, not just what the spreadsheet math says.
5. Review who owes who
Once every expense is in, the summary shows each person's net balance - how much they're owed or how much they owe - and then collapses it into the smallest possible number of payments needed to settle everyone up. No one has to make five small transfers when one would do.
6. Download the PDF, or copy it as text, and share it
Hit download for a clean settlement report with the trip name, full expense log, and final payments - or use "Copy as text" for a short plain-text version that pastes cleanly into WhatsApp or any other chat. Either way, drop it in the group chat and you're done - no spreadsheet required.
Why split expenses equally (and when not to)
Equal splitting works well for shared costs everyone benefits from the same way - meals, fuel, a shared cab, an Airbnb. It breaks down when costs are personal (someone's solo souvenir shopping shouldn't count), when someone genuinely didn't take part in something, or when shares are just different by design (a bigger room, a pricier dish). That's exactly why this tool supports three split modes per expense: equal by default, a custom exact amount per person, or a percentage - so you're never forced to pretend a split was even when it wasn't.