Migration · 5 min read
Most schools start fee management in a spreadsheet: a column per month, a row per student, and a filter for "pending". It works — until it doesn't. The failure modes are always the same: a formula overwritten by hand, two people editing different copies, and no reliable audit trail when a receipt is questioned months later.
What changes when fees move into a system
A fee system replaces the spreadsheet's rows with three distinct things: fee heads (what is charged), invoices (what is owed), and receipts (what was paid). Because they are separate records, you can answer questions a spreadsheet can't: what was charged but never invoiced, what was invoiced but partially paid, and who received a discount and why.
The migration itself is usually less painful than feared. Students import in bulk, fee structures map cleanly to existing heads, and outstanding dues carry over as opening balances so no history is lost.
The checklist
Before you move, export your current fee data — every invoice, every payment, every opening balance. Confirm the mapping of old heads to new fee heads. Then do a trial import on a disposable batch, reconcile totals, and only then go live. Any system worth using will let you validate before committing.
After go-live, the habit that matters most is issuing receipts through the system — not recording them in a notebook first. The system becomes the source of truth only when the money hits it.