What school fee software gets wrong about Indian fee structures

A school fee is a stack of heads — tuition, admission, transport by distance slab, examination, laboratory, sometimes a one-time development charge — and each behaves differently. Some are annual, some per term, some only apply in the entry year, some depend on whether the pupil takes the bus.

Generic billing software models one amount and a due date. Fee software has to model the stack, because concessions apply to particular heads and not others. A staff-child waiver might cover tuition but not transport. A sibling concession might be a percentage of tuition only. If the system stores a single total, every one of those becomes a manual adjustment somebody has to remember and justify.

Ask a vendor to enter your actual fee structure during the demo, not a sample one. Ten minutes of that tells you more than the rest of the meeting.

Every school has them and no two schools have the same rules. Sibling discounts, staff children, merit scholarships, government reimbursement categories, hardship waivers decided case by case by the trustee.

Three questions separate systems that handle this from ones that do not. Can a concession apply to specific heads rather than the whole bill? Is there a record of who approved it and when? And does the receipt show the concession, or does it silently show a smaller number?

That last one matters more than it sounds. A receipt that shows the full fee, the concession and the net amount is a document that defends itself. A receipt showing only a reduced total invites the question, next year, of why this pupil paid less.

A great deal of Indian school fee collection is partial and in cash. A parent pays what they can this month and the rest after a harvest, a salary, a wedding. This is normal, not an edge case, and software built around online payment of a full invoice handles it badly.

What you need: a bill that can carry a running balance, receipts for each part payment against the same bill, and a clear outstanding figure per pupil that a clerk can read at the counter without arithmetic. Plus a cash-collection screen that works on the office computer, because that is where most of the money is actually taken.

Online payment matters too, and increasingly so — but a system that treats cash as an afterthought will be fought by the office from day one.

Automated reminders are the feature most likely to embarrass you. Getting the rules wrong means a parent who paid yesterday receives a demand today, or a family receives six messages in one afternoon because six heads fell due together.

Check three things. Does a reminder read the current balance at the moment it sends, or a figure calculated when it was queued? Is there a cap on how many messages one family can receive in a day? And can a family be excluded — the hardship case the trustee is personally handling should not be receiving automated demands.

Years later, nothing you built matters as much as whether you can reproduce a receipt. A parent disputes a payment, an auditor samples a term, a pupil transfers and needs a clearance certificate.

So: are receipts numbered in an unbroken sequence? Can you reprint one identically? If a payment is reversed, does the reversal appear as its own entry rather than the original quietly changing? A fee ledger that can be edited without trace is not a ledger.

For parents who read Urdu, Marathi or Hindi more comfortably than English, the receipt should be in that language — which is a typography problem more than a translation one, covered separately in our guide on Urdu-medium schools.

Fee structures are held as heads with their own periods and rules, and concessions carry the approving user on the record rather than appearing as an unexplained smaller number. Part payments run against a single bill with a live outstanding balance, and there is a cash-collection screen built for the office counter rather than only an online payment link.

Online payment is designed to run through the school's own payment account, so collections reach the school directly. Worth knowing precisely: if a school has not configured its own gateway credentials, collection falls back to a shared account, so configuring your own is part of setup rather than an optional extra. Gateway fees are the gateway's, on whichever account the money lands in.

On reminders, the honest state of things: each bill carries a minimum gap before it can be chased again, so no single invoice gets a daily demand. But the throttle is per bill, not per family — a family with several heads falling due together can still receive several messages in a day. That is the exact failure this guide told you to ask about, and the answer for us today is that the per-family cap is not built yet. Ask the same question of anyone else you shortlist; most will not have it either.