A Fee Collection Checklist for the New Academic Session

Fee collection problems almost never start in the month the fee is due. They start months earlier, in decisions about how the structure was set up, what was communicated, and what the office would do when someone paid late or paid the wrong amount. Fix those in April and September looks after itself.

This is the checklist we walk new schools through before their first collection cycle on Simption. It applies just as well if you run fees on a ledger.

Before the session opens

1. Write the fee structure down once, as a table. Class by class, head by head — tuition, transport, hostel, activity, exam, lab. Every later argument ("but last year it was…") is settled by pointing at this table. If the structure lives in three people's heads, no software will save it.
2. Decide the instalment calendar and publish it. Monthly, quarterly or term-wise, with exact due dates. Parents plan around dates they were told in advance; they resent dates they discover in a reminder.
3. Settle the late-fee rule — and whether you will actually apply it. A rule that is waived on request for anyone who asks is worse than no rule, because the parents who paid on time notice. Decide the amount, the grace period, and who is allowed to waive it (usually one person, in writing).
4. List every concession category. Sibling discount, staff ward, scholarship, management quota, RTE. Each one needs a name, a percentage or amount, and an approver. Concessions applied ad hoc at the counter are where fee accounts quietly go wrong.
5. Map optional heads to the students who actually opted in. Transport is the usual culprit: a student who left the bus route in January should not be billed for it in April. Do this reconciliation before the first demand goes out, not after the first complaint.
6. Carry forward last year's dues explicitly. Old balance should appear as its own line on the new demand, not be silently added to tuition. Parents will pay a clearly labelled arrear; they will dispute an unexplained larger number.

The first collection cycle

7. Send the demand before the due date, not on it. A reminder that arrives a week early reads as helpful. One that arrives on the day reads as a threat. Two messages — one early, one two days before — is a reasonable rhythm.
8. Offer at least one way to pay that doesn't involve the counter. UPI, a payment link on the receipt, or a bank transfer with the admission number as reference. Every payment that happens from a parent's phone is one fewer queue on the last date and one fewer cash-handling risk.
9. Issue the receipt at the moment of payment. Not at the end of the day, not "we'll send it". A receipt number generated immediately, printed or sent to the parent's phone, is what makes the ledger trustworthy. Late receipts are how duplicates and missing entries happen.
10. Handle partial payments deliberately. Decide in advance whether a partial payment is allowed, which head it settles first, and how the balance is shown. Leaving this to the person at the counter produces a different answer every day.

After the due date

11. Run one defaulter list, from one source. Class teachers asking students in front of the class, the office calling, and the principal sending a note — all from different lists — is how the same family gets three reminders in a day. One list, one owner, one follow-up schedule.
12. Reconcile bank against ledger weekly, not at year-end. Online payments that didn't get matched to a student, cheques that bounced, cash that was banked a day late — each is a ten-minute fix in the week it happens and a week-long audit if left until March.

Signs the setup is working

• The office can answer "what does this student owe, and why?" in under a minute, from one screen.
• No parent is surprised by the amount on a demand note.
• Receipts are never issued from a manual book because "the system was slow".
• The principal can see the day's collection without asking anyone.