Ask a school accountant where the week goes around an installment due date, and the answer is rarely "collecting fees." It's everything around collecting fees:
- Sending reminders, one class at a time
- Answering "how much do I owe?" on the phone
- Writing receipts for cash and cheques
- Matching bank credits to students, because the parent's name on the transfer isn't the child's
- Rebuilding the defaulter list, which was out of date the moment it was printed
- Explaining to the principal why the collection number in the accounts office doesn't match the one in the register
Almost all of that is automatable. The part that isn't — deciding what to do about a family that genuinely can't pay — is the part that deserves the accountant's time.
Start with the structure, not the reminders
Automation only works if the rules are written down. Before any reminder goes out, the system needs to know:
- Fee heads: tuition, hostel, transport, admission, exam and anything else you charge, each separately.
- Installment plans: how many, when each falls due, and whether different classes or boarders follow different plans.
- Concessions and waivers: sibling, staff-ward, merit, need-based — each with a rule and a record of who approved it.
- Late fines: whether you charge them, from which day, and who can waive them.
In most schools, at least one of these lives only in someone's head. That's fine until they go on leave during fee week. Writing them into the system is the unglamorous first step, and it pays for itself the first time a parent asks why their concession wasn't applied.
Reminders: a schedule, not a scramble
Once the structure is in place, reminders become a schedule the system runs on its own. A pattern that works well:
| When | What | Tone |
|---|---|---|
| 7 days before the due date | Amount due, due date, a payment link | Informational |
| On the due date | Same, plus a line on late fines if they apply | Neutral |
| 7 days after | Balance outstanding, payment link, a contact person | Firm, polite |
| 15 to 30 days after | A personal call from the office, not another message | Human |
Two rules make this work. First, every reminder carries the exact amount and a way to pay right now. A reminder that says "please clear your dues" generates a phone call. A reminder with ₹18,450 and a payment link generates a payment. Second, reminders stop the moment the fee is paid. Nothing erodes trust faster than a "your fee is overdue" message to a parent who paid yesterday.
Payments that reconcile themselves
The biggest time sink isn't reminding. It's matching.
When a parent pays by bank transfer, the office sees a credit with the parent's name, a reference that may or may not mention the child, and an amount that may or may not match any single installment. Someone has to work out which student it belongs to. Multiply that by a few hundred families.
Payment links fix this at the source. Each link is generated for a specific student and installment, so when the parent pays, the system already knows exactly what the payment is for. On the system we run for Chaitanya's Academy, a payment posts against the right installment automatically, through a verified notification from the payment gateway; the receipt goes out instantly; and the ledger, the receipt and the bank settlement stay in agreement without anyone reconciling by hand. It's one of the moments in an ordinary Tuesday on a school ERP.
Cash and cheques still exist, and they should go into the same ledger through the same screen, with a receipt from the same series. A school that keeps a separate receipt book "for cash" has two ledgers, and two ledgers eventually disagree.
Knowing who's behind, while it still matters
A defaulter list printed at the end of the month is a history lesson. What the office needs is a live view:
- Dues by class and section, so class teachers can mention it gently at the right moment
- Ageing — who is 7 days late, who is 30, who is 90 — because each group needs a different conversation
- Collection against the due date, so the principal can see whether a new reminder schedule is actually working
This is also where fee data meets the rest of the school. A student who is both behind on fees and absent more than usual is a family worth calling for reasons that have nothing to do with money.
What should stay human
Automating reminders is easy. Automating consequences is where schools get into trouble.
- Hardship is a conversation, not a rule. A family that has always paid on time and is suddenly 45 days behind needs a call from a person, and perhaps a revised plan. No system should decide that.
- Don't automate penalties that affect the child. Withholding a report card or blocking an exam hall ticket may be school policy, but it should be a decision a named person takes, case by case. We make the same argument about AI in AI for Schools: let the system prepare, let people decide.
- Never shame. Defaulter lists on notice boards, names read out in class, or reminders posted to a class WhatsApp group are hurtful, and they put a child's financial information in front of other parents. Under the DPDP Act, that is also a data protection problem. Reminders go to the guardian, privately, every time.
A useful test from our guide on deciding what to automate: automate anything high-volume and consistent, and put a human checkpoint in front of anything where one mistake costs more than a month of automation saves. Reminders pass the first test. Consequences fail the second.
If you're moving to a new system
Fee automation is only as good as the balances it starts with. If you're migrating from registers or an older system, reconcile every student's billed, paid and due amounts before go-live, and time the switch away from an installment date. Our migration checklist covers the full process.
What changes when it works
The accountant stops spending fee week on the phone and at the bank statement, and starts spending it on the forty families who actually need a conversation. Parents pay faster, because paying is one tap from the message that reminded them. And the principal's collection number is the same number the accounts office sees, every morning, without anyone assembling it.
Want to know how much of your fee week is avoidable? Our free audit maps your current fee process end to end. Book 30 minutes, or see how fees, payments and reconciliation work in our school ERP.