Every institute accounts office has the same Monday morning ritual: a cash box count, a gateway settlement report and a bank statement, compared by hand against a receipt book. When the three disagree, the difference is rarely fraud. It is usually a receipt that never made it into the register, a gateway fee netted off a settlement, or a concession agreed in a corridor and never written down.
The fix is not a better spreadsheet. It is deciding, once, that every payment — whatever the channel — posts to the same ledger with the same numbering, and then designing the counter workflow around that decision.
The three places money actually enters
- At the counter: cash, cheque, demand draft and the occasional card swipe on a bank terminal.
- On the gateway: UPI, cards and net banking, which arrive as a settlement file a day or two later.
- In the bank: NEFT or IMPS transfers that carry a student name in the narration, if you are lucky.
Most institutes reconcile only the first channel in detail, treat the second as a monthly total and hope the third sorts itself out. That is where the drift begins, because outstanding dues are then calculated from an incomplete picture.
Where reconciliation quietly breaks
- Receipts issued by hand and posted to the register a week later, with numbers that no longer match the sequence.
- Gateway deductions — MDR, GST on fees — recorded as a shortfall against the student rather than as a separate line.
- Partial payments posted against the wrong fee head, so the tuition balance looks cleared while the term charge is not.
- Concessions agreed verbally, then applied as a discount at the counter instead of a recorded adjustment.
- Refunds issued without an approval step, leaving a receipt that cannot be reversed cleanly.
If the ledger and the receipt book can disagree, they eventually will. The only durable fix is a single sequence that both of them reference.
What a ledger that reconciles by design looks like
- One fee-head taxonomy per institution: tuition, term charges, hostel, one-time deposits, each with its own plan and due dates.
- Institution-level receipt numbering that covers counter and online payments alike, so the sequence never forks.
- Gateway payments confirmed by a signed server-to-server webhook, not by the browser redirect a parent sees.
- Idempotency on gateway events, so a retried payment or a refreshed page cannot produce two receipts.
- Concessions and adjustments recorded as entries with an approver, not as a smaller amount typed at the counter.
- A daily collection report split by payment method, plus ageing buckets for what is still outstanding.
The point of the last two is not reporting for its own sake. Ageing that is computed from an incomplete ledger produces the wrong follow-up list, and the office spends the month chasing families who have already paid.
A one-week starting point
Pick one institution. List its fee heads and due dates, then map every existing receipt to a head. Next, switch one channel — usually the gateway — so that it posts automatically and issues numbered receipts. Run a full week where the counter also posts through the same system, and compare the daily collection against the cash box and the settlement file each evening. If those three agree for five working days, the ledger is trustworthy and the rest of the group can follow.
Month end stops being an investigation and becomes a printout. That is the whole test: if closing the month needs a reconciliation meeting, the process is still manual somewhere in the middle.
Acadelogy team · 18 Nov 2026