How to split a bill over WhatsApp without the group chat argument

This is the step people skip and the one that costs the most. A receipt is thermal paper: it fades, it creases in a pocket, and it goes in the bin with the tissue. Photograph it while it is flat on the table and the light is still on it — the whole thing in one frame, including the totals at the bottom, which is the half people crop off.

If two people paid for different parts of the night, photograph both receipts. Do not try to reconstruct the second one from memory later; you will get the tax wrong and you will under-claim, because people always misremember in the direction that costs them nothing.

"Everyone owes RM38" invites an argument. "Here is the list, tap what you had" does not, because it moves the decision to the person who actually knows what they ate. It also makes the maths auditable: anyone who thinks their figure is wrong can look at the items behind it instead of arguing with a total.

The other reason to send items is speed. An equal split needs everyone to agree; an itemised split needs everyone to answer independently, and independent answers arrive in parallel instead of in a thread.

Whoever sends the link should claim their own items before sharing it. It sets the format, it proves the link works, and it removes the most common stall — a group where everyone is waiting to see how the first person does it.

It also catches scanning errors while you still remember the meal. If a line says "NASI GORENG KG" twice and there was only one, fix it now, not after four people have claimed around it.

One message, in the group where the meal was arranged, with a date attached: "claim by Sunday and I'll send the totals." A deadline is not bossy — it is the thing that converts an open-ended request into a task. Without one, the message competes with every other message in the chat and loses.

Resist sending it to people individually. You will lose track of who has it, and anyone who has already paid has no way to see that.

One reminder in the group at the deadline, naming what is still unclaimed rather than who is still missing. "Two satay and a bandung are unclaimed — if they were yours, tap them" gets a better response rate than tagging three people, and it keeps the tone off the person.

After that, close it. Assign the remaining items to whoever is willing to absorb them, send the final figures, and let it go. A split that stays open for three weeks costs more in goodwill than the unclaimed satay is worth.

Most unpaid shares are not refusals; they are friction. The person means to pay, opens their banking app, does not have your number to hand, and closes it again. Put the payment detail in the same place as the amount — a QR code they can screenshot, or a number they can copy — and the gap between "I should pay" and "paid" disappears.

Ask for the exact figure, not a rounded one. Rounding up looks generous when one person does it and looks like a fee when ten people do it to you.

1. The unclaimed shared dish. Nobody ordered the kangkung, so nobody claims it, so the payer eats it — literally and financially.
2. The second receipt. Drinks moved to another place and someone else paid. It never enters the split at all.
3. The person who left early. They paid "their share" in cash at the table before the tax was worked out, and it was short.
4. The rounding habit. Everyone rounds down to the nearest note. Ten people rounding down is not a rounding error.
5. The one who always forgets. Not malice — no record. Once the amount is out of the chat scrollback, it stops existing.

Four of the five are record-keeping problems, not honesty problems. That is the whole case for having the split live somewhere other than a chat thread.

The app is this loop with the record-keeping taken off you. Photograph the receipt on the home page, check the scanned items, claim yours, and share one link into the group. Everyone else opens it in their browser — no account, no install, no app store detour, which matters because the friction of "download this first" is exactly what kills a split.

Each person taps what they ate and gets an exact figure with the service charge and tax already worked in proportionally — see the guide on SST and service charge for why that proportional part matters. You get an email when the last person is done, with a breakdown of who owes what, and your payment QR sits on the same screen as their amount.

If the night involved several receipts or several people paying, that is a different shape of problem — see settling a group trip. Otherwise, how it works covers the rest.