A school was matching payments to pupils by hand

Every week, somebody at the school sat down with a mobile-money statement and a fee register and worked through them line by line. Amount, phone number, a short reference somebody had typed on a phone. Match it to a pupil. Update the balance. Next.

That is the job. Nobody calls it a software problem. They call it admin, or they say the bursar is busy, or they hire a second person for the office.

What it costs when it goes wrong

A parent is told they still owe money they have already paid. They are certain, because the confirmation message is on their phone. The school is also certain, because it is not in the register.

So two people start looking for evidence: scrolling back through a statement, hunting for a reference, asking for a screenshot to be sent again. That afternoon costs both of them, and the parent leaves the conversation trusting the school slightly less whatever the outcome. Multiply it by a term.

What replaced it

Nothing clever. The platform does the same matching the bursar was doing, on every payment, immediately, and keeps hold of what it matched on.

Money arrives three ways: live as a parent pays, in a file when a statement is uploaded, entered by hand at the office. All three go through the same decision, so the record cannot depend on which door the money came in through. The same payment arriving twice is recorded once. Every record carries where it came from and what matched it to a pupil.

Which means when a parent disputes a balance, the answer is on the screen. Not in a drawer, not in somebody's memory, not in a statement nobody can find.