Education

School Fee Collection in Pakistan - Vouchers, Bank Challans and Arrears

How fee collection actually breaks in Pakistani schools: vouchers that ignore concessions, challans the bank cannot reconcile, and defaulter lists that are out of date before they are printed. What to fix, and how automated fee generation handles it.

Ask any school administrator in Pakistan what takes the most time in the first week of a term, and the answer is not teaching. It is fees. Vouchers have to go out, the bank statement has to be matched against them, concessions have to be remembered, and somebody has to work out who has not paid.

Most schools do this in a spreadsheet next to a register. It works until it doesn't - and it usually stops working in one of five specific places.

1. Concessions that live in someone's memory

Nearly every school gives concessions: staff children, siblings, hardship cases, a discount the principal agreed two years ago. In a spreadsheet these are applied by hand each month, which means they are applied inconsistently, and when the person who knew about them leaves, the knowledge leaves too.

The fix is to attach the concession to the student record, not to the monthly working file, and to record who approved it. Then a voucher generated in March is the same as one generated in September, and a query about why a family pays less has an answer.

2. Fee heads that get totalled into one number

Tuition, transport, laboratory, library, examination and annual charges are different things. Transport in particular varies by route, not by class. When they are collapsed into a single "fee" column, three things become impossible: telling a parent what they are paying for, working out whether the transport operation covers its costs, and refunding one component without unpicking the whole voucher.

Keep the heads separate on the voucher. It is more work once and less work every month afterwards.

3. Challans the bank cannot reconcile

This is the one that quietly costs the most. If the challan format does not match what the bank returns, reconciliation becomes a manual comparison of two lists - and manual comparison produces both duplicates and missed payments. A parent who paid gets a defaulter notice; a parent who did not gets missed.

A challan format matched to the school's actual bank, with the returned statement reconciled automatically, removes an entire category of angry phone calls.

4. Defaulter lists that are already stale

A defaulter list exported on Monday and chased on Thursday will name families who paid on Tuesday. Nothing damages a school's relationship with parents faster.

The list has to be generated from the current ledger at the moment it is printed, not from last week's export.

5. Reminders nobody reads

Letters sent home in school bags do not arrive. SMS gets ignored. In Pakistan, WhatsApp is where parents actually read messages - so that is where a fee reminder belongs, sent from a template rather than typed out for each family.

What automated fee generation looks like

Automating this is not about removing judgement. Concessions, arrears rules and late fees stay the school's decision. What automation removes is the re-application of those decisions every single month.

In practice, that means fee vouchers generated with concessions and sibling discounts already applied - siblings linked so the family discount is automatic rather than remembered - and fee heads kept separate on the printed voucher, in the school's own format.

It means fee heads and instalments configurable per class, per campus or per student, because a school with three branches does not charge one rate. It means arrears, late fees and staff-child rates applied by the school's own rules, and concessions recorded against whoever approved them, so corrections are attributable to a named user.

And it means the boring parts stop being manual: challan formats matched to the bank, returned statements reconciled automatically, defaulter lists drawn from the live ledger, and templated fee reminders going out over WhatsApp.

This is what MjFour School Management is built to do. Plans start at PKR 1,000 a month for up to 200 students on one branch, with setup, training and support included - the full write-up is here.

What to check before you buy anything

Whatever system you look at - ours or anyone else's - these are the questions worth asking, because they are where implementations fail:

  • Can it print a voucher in the format we already use, or must we retrain parents and the bank?
  • Does it match our bank's challan format, and reconcile the statement the bank returns?
  • Can concessions be recorded against the person who approved them?
  • Are fee heads separate, and can transport be charged by route?
  • Is the defaulter list generated live, or exported and then chased?
  • Can it handle more than one campus without a second login?

If a vendor cannot demonstrate the first three with your own paperwork, the rest of the demo does not matter.

Disclosure. MjFour and Graduate.pk are run by the same team. The problems described above are the ones schools actually report; the product is ours, and you should weigh it accordingly.

Also on Graduate.pk: university fee structures for what higher education costs in Pakistan, and degree programmes by field and level.