Four Controls That Stop School Fees Going Missing

Almost every school that loses money to its own fee process loses it the same way. Not to theft. To a single unchecked entry.

Somebody takes ₦180,000 at the desk on the first Monday of term, writes it in the book, and does not get to the summary sheet because there are fourteen parents waiting behind. Six weeks later a parent produces a receipt for a payment the school cannot find. Now the school is choosing between accusing a paying customer of lying and writing off the amount. It usually writes it off, and it usually does not record that it did.

The frustrating part is that the controls that prevent this are not complicated and do not require an accountant. They require that no single person be the only pair of eyes on a transaction.

1. The person who receives money should not be the last person to confirm it

This is the oldest rule in bookkeeping and the one small schools break most often, usually without noticing, because the bursar is trusted and competent and there is nobody else free.

Trust is not the point. A second review catches honest mistakes far more often than dishonest ones: the payment entered against the wrong sibling, the ₦50,000 typed as ₦500,000, the transfer credited twice because the parent sent the receipt on WhatsApp and then again by email.

What this looks like in practice is a verification step: money is recorded when it arrives, so the parent gets their receipt immediately, but the entry is flagged as unverified until somebody else has checked it against the bank statement or the POS printout. In 1410SMS this is the verification queue on the Payments tab. Verifying never moves a balance. It records who checked the entry and when, which is exactly what you want in February when you are trying to reconstruct October.

Do this weekly. A queue reviewed once a term is a filing cabinet.

2. Never delete a wrong entry. Reverse it

When a payment is recorded in error, the instinct is to delete the row and re-enter it correctly. Resist it. A deleted row leaves no trace that it existed, which means the one thing you cannot later reconstruct is what actually happened.

The correct move is to void the entry with a stated reason, which reverses the payment, restores the invoice balance and leaves both the original and the reversal visible. Six months later the record still says: this was recorded, this is who reversed it, this is why.

Two things worth being clear about, because they get conflated:

• Voiding is not a refund. No money moves. It is the correction of a mistaken entry, usually a duplicate or a payment recorded against the wrong child.
• Voiding is not rejection. Rejecting is a review verdict and leaves the balance alone. Voiding actually reopens the invoice for payment.

Most voids are internal corrections that the parent never needs to hear about, which is why notifying them should be a decision you make per void rather than something that happens automatically. Occasionally it does need telling, and then you want the option.

3. Treat the parent as your auditor

This one costs nothing and is the most effective control on the list.

Every parent who receives a receipt the moment they pay, and who can look up their own outstanding balance without phoning the office, is checking your books for you. They have a strong incentive to notice a payment that never landed, and they will tell you within days rather than at the end of term.

Schools that send receipts on request, or at the end of the week, or only when a parent asks twice, lose that entirely. The error is still there. It just gets found in November.

The practical version: receipts go out automatically on every payment, invoices carry your bank details so nobody is guessing where to send money, and the parent portal shows a live balance rather than a figure someone typed into a message. If you want one change from this article, make it this one.

4. Separate the roles, even when you cannot separate the people

Here is the part most advice on this subject skips.

Textbook segregation of duties assumes you have enough staff to give receipting, reconciliation and approval to three different people. A school with two administrators and a head does not have that, and telling them to hire is not useful advice.

What you can do is stop everyone signing in as the same account. If your bursar, your receptionist and your head teacher all use one shared admin login, you have no record of who did anything, and every control above collapses to nothing. Separate accounts with separate permissions cost nothing and give you an audit trail with real names on it.

Then split the sensitive permissions, even across only two people. Recording a payment and voiding a receipt do not have to sit with the same person. Neither do voiding and verifying. In a two-person office you will not achieve full separation, and you should not pretend otherwise, but moving the void permission to the head teacher alone is a meaningful control that takes about a minute to configure.

What to do this term

If you are starting from a notebook and a shared login, do not attempt all four at once. In order of value for effort:

1. Give every member of staff their own account. One afternoon, no cost, and it makes everything else possible.
2. Turn on automatic receipts to parents. Immediate effect, no process change for your staff.
3. Move the void permission away from whoever records payments day to day.
4. Start reviewing the verification queue on a fixed day each week. Friday afternoon works well because the week's bank statement is available.

None of this makes fraud impossible. It is not meant to. It means that a mistake surfaces in days rather than months, while it is still small enough to fix and while everyone still remembers what happened.

The Fee Management docs cover how each of these works in 1410SMS, and Roles & Permissions covers splitting the sensitive ones.