How schools manage tuition and fees — the process, not the software
This is a process article rather than a product one. The mechanics of collecting school fees are broadly the same everywhere; what differs is how many of the decisions a school has actually written down.
The five decisions behind a fee structure
1. What is a fee head, and what is an add-on
Tuition, admission, examination, laboratory, transport, hostel, activity. The distinction that matters is which apply to everyone in a class and which depend on a service the family opted into. Mixing them produces a structure nobody can explain to a parent.
2. What the cycle is
Monthly, termly, or annually with instalments. Cash flow argues for monthly; administrative load argues for termly. Whichever you choose, the cycle should be the same across a level — per-family cycles are where reconciliation starts to fail.
3. Who the payer is
Obvious until a family separates, a grandparent pays, or an employer sponsors. Record the payer on the family, not on the student, and allow it to differ from the primary contact.
4. What happens to a mid-year joiner or leaver
Pro-rata by month, by term, or not at all? Decide before the first one arrives, because the answer you give the first family becomes the precedent.
5. What the late rule is
A flat late fee, a percentage, or a grace period. Write it down. A late fee applied inconsistently is worse than none at all.
Concessions should be rules, not favours
Every school has sibling discounts, staff-child concessions and scholarships. Almost every school administers at least some of them as a verbal arrangement one person remembers.
That fails in three predictable ways: the person leaves; two families in the same situation are charged differently; and the concession outlives the reason for it, because nobody recorded an end date.
A concession should carry a basis, a value, a start date, an end date and an approver. Applied automatically from the household or the staff record, it produces the same answer for everyone, and it expires when it should.
Collection: the reconciliation step
Most schools collect through several channels at once — counter, bank challan, and increasingly an online payment. The technical part is easy. The part that causes disputes is reconciliation: matching a payment to the challan it was meant for.
The failure is always the same. A family pays at the bank, the bank file arrives, one line does not match a challan because of a typed reference, it sits unmatched, a reminder goes out, and a parent who paid on time receives a demand. You have lost more goodwill than the amount was worth.
Two rules prevent almost all of it:
- Never absorb an unmatched line silently. It should stay visible until a person resolves it.
- Never send a reminder from a balance that has unreconciled payments against it.
Following up without doing damage
Age the outstanding balances — current, 30 days, 60, 90 — and treat each bucket differently. A family one cycle behind usually needs a reminder. A family three cycles behind usually needs a conversation, and often an instalment arrangement, and sometimes a concession that should have been granted a year ago.
Withholding results or portal access is where schools should be most careful. It is a real lever and occasionally a necessary one, but it affects a child rather than the payer. If your school does it, make it an explicit written policy approved by the head, applied uniformly, with a documented exception route — not a default setting somebody enabled.
What good looks like
- A parent can see exactly what they owe and why, without asking.
- Two families in the same situation are charged the same, without anyone checking.
- A payment is matched within a day, and an unmatched one is visible.
- No reminder ever goes to a family who has paid.
- The fee ledger and the school accounts agree without a monthly reconciliation exercise.
CampusFlo covers this in its fees and billing module, including concessions as dated rules, bank-file reconciliation, ageing and online payment.