How to Calculate the Time and Cost of Manual School Fee Reconciliation

Because families pay in many different ways, and the bank record doesn't always say who paid for what. A reference may be missing or mistyped. One payment may cover several children, or someone other than the account holder may pay. Each of those needs a person to work out where the money belongs.

None of this reflects a lack of care. Parent payment matching is detailed work, and a finance team that does it accurately is doing it well. The effort comes from the variety of the payments, not from any weakness in the process.

The framework has five steps. You need three inputs, plus a cost per hour:

1. Count the payments per period: the number of payments to be reconciled in a typical month.
2. Find the exception rate: the share of payments that don't match cleanly and need investigation.
3. Time a clean match: the average minutes to check a payment that matches without trouble.
4. Time an exception: the average minutes to investigate, correct and record one.
5. Convert to hours and cost: add the minutes, divide by 60, then multiply by the loaded hourly cost.

As a formula: monthly hours = ((payments x (1 - exception rate) x minutes per clean match) + (payments x exception rate x minutes per exception)) divided by 60. Monthly cost is monthly hours multiplied by the loaded hourly cost, and annual cost is that figure multiplied by 12.

The numbers below are illustrative only. They show how the formula works and are not a benchmark, an industry figure or a promised saving. Replace them with your own.

In this example, exceptions are 10% of payments but nearly half of the time (2,400 of 5,100 minutes). That is the useful insight: the effort is concentrated in a small number of awkward payments.

The same formula also works for what-if questions. If the exception rate in the example were 5% instead of 10%, the time would be 2,850 minutes for clean matches and 1,200 for exceptions, or 67.5 hours a month, which is 17.5 hours less. That shows where the time sits. It is not a prediction of what any tool or process change will save.

Counting exceptions by type is more useful than counting them in total, because each type has a different fix. These are the most common sources:

1. Count payments for the last three months: to find a typical monthly volume.
2. Log exceptions by type for a sample period: a few weeks is enough to see the pattern.
3. Time a sample of clean matches and exceptions: even rough timings are better than guesses.
4. Include the related tasks: chasing families, correcting records, and preparing reports.
5. Agree the loaded hourly cost with your finance lead: including salary and related costs.
6. Repeat each quarter: so you can see whether anything is changing.

Start with the biggest exception type. If most of the rework comes from missing references, the fix may be a clearer payment reference and better communication to families. If it comes from split payments, it may be a billing structure question. The calculation tells you where to look, and the answer to what to change comes from the type of exception.

Imagine most payments matching automatically because the reference travels with the invoice, so the team only sees the awkward few. The month-end conversation starts with a short list of exceptions instead of a day of checking, and the same formula shows the time falling over the following quarters.

That's the thinking behind TENOR, Feoda's fee billing, payments and receivables product built on Oracle NetSuite, which is designed to connect billing and payment matching in one workflow. If you would like to see how your current process compares, start with the calculation above, and then assess where your own time is going.