How to keep track of group expenses

Not “is the total right?” but “can this be explained?”. A balance nobody can trace back to specific expenses is not trusted, and an untrusted balance does not get settled — people quietly dispute it by simply not paying.

Three questions any expense record should answer without anyone's memory:

1. What was this expense, and how much was it?
2. Who paid it?
3. Which people did it apply to?

Informal systems answer the first, sometimes the second, and almost never the third — which is the one that determines the numbers.

The window in which an expense is recorded accurately is about thirty seconds wide. During it, the exact amount is on a screen in front of you, you know who it was for, and you remember why.

Afterwards, all three degrade. The amount becomes “about £40”, the people become “I think everyone”, and the reason vanishes. Recording later is not the same activity as recording — it is reconstruction, and it is reliably wrong at the edges.

Make it everyone's job

A single designated bookkeeper is a bottleneck who was not present for most of the spending. Whoever pays should record — it is the only arrangement where the person with the information is the person entering it.

Records split across a chat thread, a note on someone's phone, a spreadsheet and two people's memories cannot be reconciled, because no single view contains everything. Worse, each source feels authoritative to whoever maintains it.

• One group per real-world context. The flat is one group; the holiday those same people took is another.
• Everything for that context goes in that group, including costs paid before it started.
• If something does not belong in the shared ledger, it belongs in a personal record — not in a second unofficial list.

Splitting a context across two groups because one seemed to be “for the big things” guarantees a set of expenses that never get reconciled with the others.

Ordinary expenses need no explanation. The unusual ones need a sentence, and it is always the unusual ones that get questioned later.

1. Splitting everything across the whole group by default, including the things only two people shared. This is the single most common source of wrong balances.
2. Forgetting the costs paid before the group was created — deposits, tickets, bookings. Someone is usually hundreds down before anyone starts tracking.
3. Recording a settlement that has not actually happened yet. A balance cleared on a promise is worse than an open balance, because it is now invisible.
4. Letting one person's expenses accumulate unrecorded until the end. They will not remember them all; nobody does.
5. Never settling. Balances that only grow stop feeling like real money, and the record becomes decorative.

• Review monthly. A quick scan catches a missing expense while somebody can still remember it.
• Settle on a schedule. Monthly for a household, at the end for a trip. Regular settling keeps the numbers small and the conversation routine.
• Fix errors in place. Edit the expense rather than adding a compensating one — a corrective expense that exists to cancel a mistake makes the ledger unreadable a year later.
• Keep the record after settling. A settled group is the history of what something cost, which is genuinely useful next time. Export it to CSV if it matters.

Every member can add expenses from their own device, so capture at the point of payment is possible for whoever paid. Each expense records the payer and the people who shared it as structured fields rather than as a description. Balances are calculated, not maintained. An activity feed shows what changed and who changed it, settlements can be voided or edited with the history annotated rather than rewritten, and any ledger exports to CSV.

See group expenses for the mechanics, or how it works for the arithmetic.