Settling a group trip: many bills, many payers, fewest transfers

The dinner method works because there is exactly one creditor. Everyone pays that person and the loop closes. Add a second payer and the structure changes: now some people owe money to one person and are owed money by another, and if you settle receipt by receipt, every receipt generates its own set of transfers. Eleven receipts across six people can easily produce thirty small payments, most of which cancel each other out.

They cancel because money is fungible. If Ah Boon owes Siti RM80 and Siti owes Ah Boon RM50, there is no reason for two transfers to happen. One transfer of RM30 leaves everyone in exactly the same position. Scale that observation across the whole group and you get netting.

1. Work out each bill on its own terms. Each receipt is split among the people who were actually there, with that receipt's own service charge and tax applied proportionally — see the SST and service charge guide. Tax is a per-bill matter and must be settled before anything is merged; a Thai receipt and a Malaysian one do not share a tax rule.

2. Reduce everyone to a single number. For each person: everything they paid out, minus everything they consumed. Positive means the group owes them; negative means they owe the group. These numbers always sum to zero, which is a useful check — if they do not, a bill has been entered twice or a participant is missing.

3. Match the biggest debtor to the biggest creditor, repeatedly. Kumar owes 225, so he pays Ah Boon 225. Mei Ling owes 180; Ah Boon has 85 left to receive, so Mei Ling pays Ah Boon 85 and then Siti 95. Everyone is square in three transfers instead of the eight or nine you would get settling receipt by receipt.

With n people you never need more than n−1 transfers, and usually fewer. That is the whole payoff.

Netting optimises for the fewest payments, and it buys that by breaking the link between a debt and the meal it came from. Kumar pays Ah Boon RM225 without ever having eaten a RM225 meal that Ah Boon paid for — the figure is an aggregate, and if he wants to check it he has to trust the whole chain rather than one receipt.

For groups who settle regularly, that is fine. For a one-off trip with people who do not know each other well, pair-by-pair debts are often the better social choice: more transfers, but every line is hand-verifiable, and "I owe exactly the people who fed me" needs no explanation. BillSplitor offers both views for this reason — the netted plan and the pairwise breakdown are the same data, presented at different resolutions.

The temptation on a foreign trip is to convert each receipt with whatever rate your banking app showed that afternoon. Do not. Different rates on different receipts mean the individual shares no longer add up to what anyone actually paid, and the discrepancy lands on whoever is doing the arithmetic.

Pick one rate per currency for the whole trip, agree it out loud, and apply it everywhere. It will not exactly match anyone's card statement — nobody's does, once the bank spread and the foreign transaction fee are in — but it is transparent and it is the same for everyone, which is what matters. The alternative, if the group would rather not pick a rate at all, is to settle each currency as its own pool: THB debts settle in THB, MYR in MYR, and nothing is ever converted.

Whichever you choose, keep the tax per bill. Converting a Thai receipt to ringgit and then applying Malaysian SST to it is a mistake that is surprisingly easy to make in a spreadsheet.

Trips settle in dribs and drabs. Someone hands over RM100 at the airport, someone else transfers half now and half after payday, and the van driver got cash from whoever had it. Each of those is a real movement of money and each one changes the balances — a repayment simply shrinks the payer's debt and the recipient's credit, then the plan is recomputed.

The thing to avoid is settling money outside the record and remembering it later. If Mei Ling gives Ah Boon RM100 at the airport and it is never logged, the plan will still ask her for the full RM180, and one of two things happens: she pays twice, or she disputes it and somebody has to reconstruct four days of receipts from a group chat. Log it when it happens, not when it is queried.

• Agree the rate and who is fronting what before anyone spends anything.
• Photograph every receipt the moment it is settled — including the ones that feel too small to matter. Small receipts are the ones that go missing, and twenty of them is not small.
• Mark who was actually present for each bill. Not everyone joins every meal.
• Log cash handovers the same day, in the same place as the receipts.
• Settle once, at the end, from the netted plan — not nightly, which recreates the receipt-by-receipt problem you were avoiding.

Upgrade mode on the home page creates a bill set: a workspace that holds any number of receipts, each with its own payer, its own currency and its own tax lines, behind a single link you share once. Everyone claims across all of the bills in one pass rather than answering eleven separate messages.

The set computes each bill's shares with that bill's own tax rules, converts at the rate you set, nets the balances and shows both the minimum-transfer plan and the pairwise breakdown. Repayments can be logged at any point and the plan updates. There is more on the mechanics in how it works, and the FAQ covers the practical questions.