The admin calendar a school office actually runs — structure freeze, term billing, concessions, reminders, dues and year-end reconciliation — and the two steps worth automating before any of the others.
Checklist5 min readSchool administrators, principals and accounts staff
The whole thing is on this page. No email, no download, no wait.
School fee-cycle checklist
Four Avance — https://fouravance.com/resources/school-fee-cycle-checklist — updated 2026-08-31
A school's finance year is not a spreadsheet, it is a cycle: the same eight things happen in the same order every year, each one depends on the one before it, and the whole thing is held together by two or three people in the office who know where everything is. This checklist writes that cycle down, so it survives one of them being on leave.
The cycle, in the order it actually happens
Phase
What the office is doing
What breaks without a system
Admissions and re-admission
New admissions, promotions, transfers in and out, section allotment.
The fee list is built from last year's roll, so a student who left is still billed and a new one is missed.
Fee structure freeze
Heads of fee agreed class by class, concessions and transport slabs approved.
Two versions of the fee structure circulate; parents quote the one they were told first.
Term one billing
Demand raised, notices issued, collection begins.
Demand is never totalled, so nobody knows what was supposed to come in.
Concessions and scholarships
Staff wards, siblings, merit and need-based reductions applied.
A concession granted verbally is invisible to accounts, and the ledger stops reconciling from that day.
Reminders and follow-up
Due date passes; reminders go out; the office starts calling.
The same family gets three reminders in one evening, one per child.
Terms two and three
The same billing run repeats, now with arrears carried forward.
Arrears and current dues get mixed, and a part payment lands against the wrong term.
Exam eligibility and dues clearance
Dues checked before hall tickets or results are released.
The list is prepared by hand, at speed, from a ledger that is out of date.
Year-end reconciliation and transfer certificates
Demand versus collection closed off, refunds settled, TCs issued.
The gap between demand and collection cannot be explained line by line.
Before the year starts: freeze the fee structure
List every head of fee separately — tuition, admission, exam, lab, library, transport, uniform, activity — even where you present a single figure to parents. A combined figure cannot be refunded or waived in part.
Fix the amount class by class and write down the approval date. Mid-year changes should be rare enough to be an event.
Put the concession rules in writing before the first parent asks: staff wards, siblings, merit, and hardship. Include who approves each, and the maximum.
Transport by route and stage, not per student. Then a route change is one edit, not forty.
Mark which heads are optional, and how a parent opts out of them.
Decide the late-fee rule and, more importantly, who is allowed to waive it. That authority is where fee ledgers go to die.
Write the refund rule for a mid-year withdrawal now, calmly, rather than in the meeting where it is being demanded.
Billing and receipts
One receipt series, sequential, no reuse, no gaps you cannot explain.
One receipt per payment received, not one per term. A parent who pays in three instalments gets three receipts.
Decide how a part payment is allocated — oldest dues first is the usual rule — and apply it the same way every time.
Record the payment mode on the receipt: cash, UPI, bank transfer, cheque. At year end this is what makes the bank reconciliation possible.
Close the day: total collected, split by mode, counted and signed. Every day, including the quiet ones.
Decide who may cancel a receipt, and make sure a cancellation leaves a visible trace rather than removing the number from the series.
Reminders that work, and do not make you the villain
Use a ladder, not a blast: a notice a week before the due date, one on the due date, one a week after, then a phone call from a person.
One message per family, not per student. Three children means one message listing three names.
Never name a child in a group. Fee matters go to the parent's number, individually, always.
Keep a record of what was sent, to whom and when, so that a disputed "we were never told" has an answer.
Give every reminder a way to pay in it. A reminder that requires a trip to the office is a reminder to come next week.
Stop reminders the moment payment lands. Nothing damages trust faster than a demand for money already paid.
What to automate first
Do not automate the whole cycle at once. Two steps carry most of the pain and almost none of the risk, and they are the two to do first.
First: receipts and numbering. It is the highest-volume task in the office, it is mechanical, and getting the series right is the foundation everything else reports on.
Second: the dues list. One reliable, current list of who owes what, by class, that anybody in the office can pull without asking the one person who knows the ledger.
Then: reminders, once the dues list is trusted. Automating reminders on top of an unreliable list means automating the wrong messages, faster.
Leave for later: concession logic, transport slab billing and exam-eligibility gating. Each has enough local exceptions that you want a year of clean data before you encode the rules.
Year end: the reconciliation nobody schedules
Total demand raised, total collected, total outstanding — per class, and then totalled. These three numbers should be producible on any given Monday, not assembled in March.
Total concessions granted, by category, with the approval against each.
Refunds issued and to whom.
Advance collections that belong to next year, kept separate from this year's collection.
Dues cleared against every transfer certificate issued, with the date.
An archive of the year's receipts that will still open in five years.
A one-page handover note for whoever runs the cycle next year. This is the document that makes the whole checklist worth doing.
Thirty-five questions to ask any software vendor before you sign — data residency, exit and export, the pricing traps, invoice compliance, and who actually answers at 9pm. Written to be useful even if you buy from someone else.
Owners, operations leads and finance managers evaluating a vendor
Display name, business profile, opt-in, template categories and the 24-hour window — plus the things that quietly get a number restricted. The platform rules are cited from Meta's own documentation with the date we checked them.
Owners, and whoever actually holds the business number
Read
Checklist
Got stuck on one of these?
Send us the questions you could not answer. We will tell you which ones software actually solves, which are process problems no product will touch, and where our own answer would be a bad fit for you.