How to manage school fees: a practical guide for the fee office

A fee structure answers four questions: which class, which academic session, which fee heads — tuition, admission, examination, transport and so on — and on what schedule. Tie each structure to a class and a session. When fees are revised for next year you create a new structure, and last year's invoices and receipts stay exactly as they were.

Installments belong to the structure rather than being arranged on the side. Common patterns are annual, half-yearly, quarterly and monthly, with one-time heads such as the admission fee charged once. Set the due date for each installment, and decide whether a late fee applies after it.

An invoice states what a family owes for an installment; a receipt records what they paid against it. Keeping both, rather than writing receipts against a mental list of dues, is what turns outstanding balances into a report instead of a reconciliation.

It also handles part payments cleanly. An invoice can be partly paid, fully paid or overdue, and its balance is always the invoice total less the payments and concessions recorded against it.

Schools reduce fees for many reasons — siblings, children of staff, merit, need, sports quotas, and admissions under the Right to Education Act among them. The mistake is to record the reduction by lowering the invoice. Six months later nobody can say why one student pays less than another, and an auditor or trustee who asks gets a shrug.

Record each reduction as a concession against the invoice, with its category, the amount and who approved it. The original fee, the concession and the reason all survive, and a report of concessions by category becomes possible.

Receipt numbers should run in a single unbroken sequence. A gap is the first thing an auditor asks about, because a gap is also what a deleted receipt looks like. Two rules follow from that:

• Never delete a receipt. Cancel it with a reason, so that the number stays accounted for.
• Never let two counters issue the same number. In software this needs a sequence that is locked while each number is allocated — spreadsheets, and some systems, get this wrong when two cashiers work at once.

AcadiFlow's fee module allocates receipt and invoice numbers from a locked counter for exactly this reason.

Collecting online through a payment gateway saves families a trip and the office a queue, but it brings one subtle trap. A parent can pay and then close the browser before being sent back to the school's site. If the system records payments only on that return, the money reaches the bank and the fee stays unpaid on the ledger.

The reliable approach is to record the payment from the gateway's server-to-server notification (a webhook), verify its signature, and ignore duplicates. Gateways retry notifications, and a retried notification must never credit the same fee twice.

Decide in advance who bears the gateway's transaction charge. Some schools absorb it; others pass a convenience fee on to parents. Either way, say so clearly before the parent pays.

• Record every counter payment against an invoice, with its mode — cash, cheque, demand draft, UPI or bank transfer.
• Treat a cheque as pending until it clears. If it bounces, reverse the payment and reopen the invoice rather than deleting anything.
• Close each day with a collection report by mode, and reconcile it against the cash in hand and the bank deposit slip.

Start from an overdue list by class, showing each family's outstanding amount and oldest unpaid installment. Remind before the due date, again when it passes, and then talk to the family. Reminders through the parent portal and email are cheaper and less confrontational than phone calls, and they leave a record.

Late fees should follow a published rule — a flat amount, or an amount per day after a grace period — applied the same way to everyone. A late fee the office waives case by case should be recorded as a concession like any other.

Refunds arise when a student leaves mid-session, when a fee is paid twice, or when a concession is approved after payment. Treat them as a workflow — requested, approved, processed — rather than a cash payout, so that every refund has an approver and a trail back to the original payment.

• Day-end collection by payment mode.
• Outstanding dues by class, with the oldest unpaid installment.
• Concessions granted, by category and by approver.
• Collection against billing for the session, month by month.
• Cheques pending clearance, and cheques returned.