مواد پر جائیں
School operations3 min read

How to digitise school fee collection without losing a term to it

A practical sequence for moving fee collection off spreadsheets — what to change first, what to leave alone, and the reconciliation step almost everyone skips.

Most schools that come to us have already tried to digitise fees once. It usually failed for the same reason: they started with the software instead of the ledger.

Here is the order that actually works.

Start by writing down your fee policy

Not the software requirements — the policy. Every head, every concession, every exception you grant in practice but have never formally documented. The sibling discount. The staff-child rate. The family the principal quietly agreed to let pay in three instalments.

This document is the hardest part of the whole project, and it has nothing to do with technology. Schools that produce it in week one finish the rollout in a month. Schools that skip it spend the next term discovering their own rules one angry parent at a time.

Reconcile before you migrate, not after

The single most common failure: importing student and fee data into a new system, going live, and only then discovering the imported arrears total doesn't match the old register.

Do it the other way round. Import into a staging environment. Print the outstanding-dues total. Put it next to the number your accounts office believes is correct. They will not match on the first attempt — they never do. Find out why before the system becomes the source of truth.

The gaps are usually mundane: a concession applied in one register and not the other, a payment recorded against the wrong sibling, a reversal that was never posted. Every one of them is cheap to fix now and expensive to fix later.

Change the challan last

There is a strong temptation to redesign the fee challan at the same time. Resist it for one cycle.

Parents recognise the current challan. Your bank recognises the current challan. Changing the system and the document in the same month means that when something goes wrong, you cannot tell which change caused it. Run one cycle on the new system with the old challan format, confirm the numbers, then redesign.

Automate the follow-up before the payment

Counter-intuitively, the feature that moves collection rate most is not online payment — it is the reminder.

In our experience the pattern is consistent: a reminder three days before the due date and a second on the due date moves on-time collection substantially, and it does so in week one, before anyone has changed how they pay. Online payment channels matter, but they take longer to shift behaviour, particularly where parents are used to paying at a bank counter.

Start with the reminder. It is the cheapest thing on the list and the fastest to show a result.

What to expect

A single-campus school with clean records should be running a full fee cycle on a new system inside six weeks. Multi-campus groups take longer, mostly because reconciliation has to happen per branch and the branches rarely agree with each other.

The work is not really software work. It is bookkeeping work with software attached — and the schools that understand that up front are the ones it goes well for.

Have a question we haven't answered?

Ask us directly. We usually reply the same day, and the good questions become articles.