What to carry into the next finance meeting

  • Separate confident matches from items that genuinely need a person.
  • Preserve the original payment evidence instead of replacing it with a spreadsheet row.
  • Treat unresolved money as a visible work queue with an owner and next action.
01

The hard part is not receiving money

Most schools can see that money arrived. The difficult work begins when a bank narration, mobile-money reference, receipt book, and learner account do not use the same language.

A bursar may spend the morning moving between a bank portal, an exported statement, a messaging thread, and a spreadsheet that only one person fully understands. The final total can be correct while the path to it remains fragile.

02

Start with one evidence trail

A useful reconciliation process keeps the source transaction, the proposed learner or invoice match, the reason for that proposal, and the final approval together. Someone reviewing the entry later should not have to reconstruct the story from memory.

This is also where automation should be modest. A system may suggest a match when the amount, reference, payer, and timing align. It should not silently turn uncertainty into certainty.

  • Received: the payment exists, but has not yet been classified.
  • Suggested: the system has a likely match and can explain why.
  • Needs review: evidence conflicts, is incomplete, or could apply to more than one account.
  • Posted: an authorized person approved the accounting effect.
03

Design the exception queue before the happy path

The cleanest screens are not always the most useful ones. A finance team needs to know which payments are unresolved, how long they have been waiting, who is looking at them, and what evidence would settle them.

Good exception handling reduces interruption. Instead of asking the whole office whether anyone recognizes a payment, the record can carry a focused request: confirm the learner, request a remittance note, split the amount, or return it for correction.

04

Close with an explanation, not only a total

At day-end or month-end, the useful output is more than “bank equals ledger.” The team should be able to explain what matched automatically, what required judgment, what remains unresolved, and whether any amount is old enough to need escalation.

That explanation gives school leaders a clearer view without pulling the bursar away from the work to build another report.

A note on scope

This article describes working principles, not legal, tax, or accounting advice. Schools should apply their own policies and professional guidance.
Sources

Further reading and review basis

Written by Schoolbooks editorial team · Reviewed by Schoolbooks product and finance review · Updated 2026-08-15