Most Indian schools collect fees in five or six instalments per year, across cash, cheque, UPI and bank transfer, with concessions for siblings, RTE students and staff children. Spreadsheets buckle under that complexity by November — which is exactly when fee management software becomes a survival tool, not a luxury.

But the market is crowded, and most marketing pages list the same generic features. This guide focuses on what actually matters once your accountant starts using the system every day.

FIFO payment allocation. When a parent pays ₹15,000 against a ₹20,000 outstanding balance spread across April, May and June fee heads, the system must allocate to the oldest dues first — automatically. Without FIFO, you end up with the strange situation where a student is "paid" for June but owes April, and the next reminder is wrong.

Per-month, per-head concessions with reasons. A blanket "10% off" discount field is not enough. Real schools give a fee waiver for tuition only (not transport), or a one-time concession for a specific month, or a sibling discount that varies by class. The system needs to record each concession with the head, the month, the amount, and a reason — so audits, parent queries and reversals are all defensible.

Instant digital receipts. Every payment must produce a unique, sequentially numbered receipt with the school logo, the parent name, the head-wise breakdown, mode of payment, collector name and a verification QR code. WhatsApp delivery within 30 seconds of payment dramatically reduces "did you receive my fee?" calls.

Cash ledger by collector. Most fee fraud happens at the cash desk. A daily per-collector cash ledger with opening balance, all collections, all handovers and a closing balance — with a mandatory daily handover step — turns this from a trust problem into an operational one.

GST and GSTR-ready exports. Schools registered under GST need to file GSTR-1 monthly and GSTR-9 annually. The fee software must tag GST-applicable items (transport, books, uniforms) separately from exempt items (tuition for K-12), and produce a GSTR-ready export.

Automated reminders that actually work. Scheduled SMS and WhatsApp reminders for upcoming dues, overdue dues, and partial payments — with templated personalisation (parent name, student name, class, amount, due date). Manual reminder workflows fail because no one has time to send 800 messages on the 5th of every month.

CA audit pack export. When the auditor arrives, you should be able to produce a complete audit pack — every fee receipt by date with the collector name, every concession with reason, every refund with approver — in a single click. Schools that cannot do this lose two working weeks every March.

Real-time dashboard for the principal. Today's collection, this month's collection vs target, top defaulters, collector-wise totals. Without this, the principal flies blind for 25 days a month and discovers shortfalls only at the bank reconciliation.

White-label parent portal. Parents should see their child's ledger, download past receipts, and pay outstanding dues from a school-branded portal — not a generic vendor portal. This single feature drives the most parent-trust improvement of anything on this list.

Putting it together. A school with 800 students, six fee heads and five instalments has roughly 24,000 fee transactions a year. Choose a system that handles all ten capabilities above, runs them on Indian-region servers, and is built specifically for K-12 schools — not adapted from a generic accounting tool.