Split by who actually turned up, not who said yes
Ten said yes, seven came, one never replied and played anyway. Why attendance — not the RSVP list — should decide the split, and how to run it that way.
4 min readUpdated 4 September 2026
Every regular game has this argument once. The turf was booked for ten, seven came, and the bill does not care. Do the three no-shows pay? Does the one who turned up without replying pay the same as everyone else? Whoever paid the venue is now running a small court case in a group chat.
The reason it turns into an argument is that most groups only ever record one list — the RSVP list — and then have to argue about how it differs from reality. Keeping two lists removes the argument, because everyone can see both.
Three different facts, three different lists
| The list | What it answers | What it decides |
|---|---|---|
| The roster | Who is in this group at all | Who gets notified about a session |
| The RSVP | Who intends to come | Whether the game happens |
| The attendance | Who actually played | Who is in the split |
NikiPri keeps them separate on purpose, and only the third one touches money. A person who said IN and did not come is not in the split. A person who never replied and turned up is.
How it works in practice
Collect RSVPs before the game
IN, OUT or MAYBE, with a live count against the number of players you said you need. This is the list that decides whether there is a game at all.
Mark attendance after it
A team admin opens "Mark who played". Everyone who said IN is already ticked — because that is right most of the time — and the job is correcting the handful who differ.
Add the expense
Its participants default to exactly the people marked as played. Nobody types a list of names, and nobody can quietly leave themselves out.
Correct it if you got it wrong
Change who played and an equal split recalculates. Custom splits and expenses that already have a payment against them are deliberately left alone — and the app tells you which ones it skipped.
But the no-shows cost us money
Sometimes they genuinely did. A ground booked for ten and paid for whether or not ten arrive is a fixed cost, and the seven who came end up covering the three who did not. That is a real grievance, and "attendance decides the split" does not answer it by itself.
What the app gives you is the ability to be explicit rather than passive-aggressive. Two workable approaches:
- Split the whole bill among the people who played, and say so up front. Simple, and the cost of a no-show is shared by everyone who came. Most casual groups land here.
- Include the no-shows in the split for that session, using exact amounts or shares. Defensible when the booking was made on the strength of their yes — but agree the rule before the game, not after the bill.
Why the split is not just "total ÷ people"
Because the total rarely divides cleanly. ₹1,000 between three is ₹333.33 each, which is ₹999.99 — and a rupee that vanishes every week is how a ledger stops being trusted. Splits are computed in paise and the remainder is distributed, so the parts always add back up to exactly what was paid.
The same figures you see while adding the expense are the ones stored. There is no "approximately" step between the preview and the record.
Common questions
Can a player mark their own attendance?
No — a team admin does it. Attendance decides money, so it is not something each person edits for themselves. Anyone can see the result, which is the check that keeps it honest.
Someone played but I forgot to add them. Can I fix it later?
Yes. Edit who played and the equal split recalculates around the new list. If the expense has a custom split or somebody has already paid against it, it is left as-is and you are told, so you can decide what to do rather than having the numbers change under you.
What about someone who came late or played half the game?
Use a shares split — two shares for a full game, one for half — or exact amounts if you want to be precise. Both are a couple of taps on the same expense.
Does a cancelled game wipe the expenses?
No. Cancelling a session keeps the RSVPs and any expenses booked against it, because calling off a match does not un-spend the deposit you already paid. The expenses are shown to you when you cancel so nothing is forgotten.