How to split group trip expenses

The group chat nobody wanted to open

What broke down on that trip was not honesty. It was bookkeeping. Nikhil had a phone gallery full of receipts in two currencies. He had a rough memory of who was present for which meal. He also felt several thousand rupees out of pocket, without being able to prove it. Meanwhile Divya had paid for the airport taxis and one dinner. She had no idea whether she was owed money or still needed to pay.

So the group did what most groups do: somebody guessed. A message went out saying "everyone send 8,500 and we’re done". It felt decisive. It was almost certainly wrong for at least three of the five. A round number sent to a group is not a settlement. It is a hope. It also leaves the two people who took part least paying for things they never touched.

The uncomfortable part is that this rarely produces an argument. It produces something worse: a small, lasting unfairness that nobody raises, because raising it would be awkward over an amount too small to be worth the friction. The fix is not more trust. It is writing two lists instead of one.

Payer and participant are two different roles

This difference matters more than anything else on the trip. Most spreadsheets never make it clear. The payer is the person whose money actually left an account: the card that was swiped, the UPI that went through, the cash handed over at the counter. The participant is the person who should bear the cost of that particular bill.

Those two roles overlap constantly and are not the same thing. On the scuba day, Nikhil was the payer for the entire booking, but only three of the five were participants. On the single-room night, the resort bill had one payer and one person who should bear the extra, even though everyone else was staying in the same hotel. Mixing the two is what produces the classic complaint, "but I paid for that!". That complaint is true. It still says nothing about what anyone owes.

Once each bill records both roles, the awkward conversations mostly stop being necessary. Nobody has to remember who was at breakfast, because breakfast has a list attached to it. Nikhil stops being the group treasurer arguing from memory. He becomes just another line in a ledger that happens to show him a long way ahead.

• Payer: the person whose account the money actually left, one per bill
• Participants: the people who should bear that bill, which may be one person or everyone
• A person can be a payer on some bills and only a participant on others
• Being a payer is not the same as spending more. It usually just means having the card that worked

Equal split is a method, not a rule

An equal split is the right tool when everyone genuinely used the same thing: the shared taxi, the group dinner where the plates were passed around, the room the whole group slept in. It is fast. It is easy to defend. On most trips it will cover most of the bills. Reaching for anything more complicated when equal will do is how people abandon the exercise halfway.

Custom shares exist for the bills where equal would be wrong. Someone upgraded to a single room. Two people skipped the scuba trip and spent the day at a café. One person joined three days into a six-day trip. One does not drink, and the bar tab was not small. A custom split is valid as long as the individual shares add up to the bill total. That is the only rule it has to meet.

What makes custom splits work socially is deciding them at the time, in front of everyone, rather than reconstructing them from memory two weeks later. Nobody objects to "the three of us are splitting the scuba" while standing at the dive shop. Everybody objects to being told in a group chat, after the fact, what they apparently agreed to.

Then there were two currencies

Half of this trip’s bills were in baht and half in rupees. The flights, the visa fees and the airport taxis were rupee expenses paid in India. The resort, the boat, the food and the endless 7-Eleven runs were baht expenses paid in Thailand, some on card and some in cash withdrawn at an ATM with a fee attached.

A shared ledger holding raw baht and raw rupees side by side cannot tell you who owes whom, because the numbers are not comparable. Adding 4,200 to 4,200 when one is baht and the other is rupees produces a figure that means nothing at all. It will not look obviously wrong on a screen. Every foreign bill needs an explicit rate applied to it before it joins the shared ledger.

The group agreed one rate for the whole trip, taken from the average of what their cards had actually charged. Using each transaction’s own rate is more precise, but on a week-long holiday the difference is usually small enough that agreement matters more than the last few rupees. What is not optional is writing the rate down.

What the settlement actually showed

Read the result one person at a time. Each line is share minus paid. A plus means they still owe. A minus means the group owes them. Nikhil was around ₹34,000 ahead, rather than the ₹42,500 the guessed round number would have handed him. That is because two bills he thought he had covered were paid by Divya.

The two friends who skipped scuba owed noticeably less than the flat figure. That was the entire point of the exercise. The totals across the group always sum to zero. If they do not, something is wrong in the data: a bill entered twice, a payer missing, a currency not converted, or a custom split whose shares do not add up to the bill.

The second useful thing is the number of transfers. Five people with five separate balances could produce a dozen small payments, most of which cancel each other out. Netting them down means the group can settle in a handful of transfers instead. Fewer UPI messages. Fewer things to chase. And a much better chance that everyone actually finishes paying.

Splits are promises. Payments are cash that moved

The evening the group settled, two people paid in full. One paid half and said the rest would come after his salary. One paid Nikhil in cash. Those are payments, and they belong in a different column from the split. A split records an obligation. A payment records money that actually changed hands. Keeping them separate lets a half-paid balance stay visible, instead of disappearing because someone meant to pay later.

This is also the honest answer to the most common question about tools like this one. Westro calculates shares, balances and settlements. It does not transfer money. Nobody’s bank account is touched. No payment is started. No request is sent on your behalf. The actual transfer still happens in UPI, in cash, or through your bank, exactly as it would have anyway.

This limit is useful to understand. It is not a flaw. What causes trip-money resentment is almost never the payment method. It is the confusion about what is owed. Remove the confusion and the transfers take about ninety seconds.

• Record the split when the bill happens, while participation is still fresh in everyone’s memory
• Record payments separately, including partial ones, so remaining balances stay honest
• Convert every foreign-currency bill with a stated rate before comparing shares
• Settle once, at the end, using the netted list rather than a dozen ad-hoc transfers

What changed on the next trip

Six months later the same group went to Coorg, and the difference was almost boring. Bills got logged the evening they happened, usually by whoever paid, sitting in the car or waiting for food. Custom splits were agreed out loud at the counter. On the drive home somebody opened the settlement, read out four transfers, and the money moved before anybody had unpacked.

Nikhil stopped being the group’s accidental banker. Not because he paid less, but because being ahead by ₹30,000 stopped feeling like a risk he was carrying alone. The method did not make the trip cheaper. It made the amounts knowable, which protects friendships.

Trip Manager holds the trip, the people, the bills and the payments in one place. Your bank and UPI statements stay the record of what actually moved. The five minutes of logging each evening is where the accuracy comes from.