Every board cycle, the finance lead has the same job: explain to the board why the actuals don't match the budget. The reason could be anything, from lagging programme spend, to a grant landing late, to a cost slipping from one quarter into the next.
But the meeting itself is rarely the hard part. Most finance leads can talk a board through a set of numbers. The hard part is getting numbers you'd be willing to stand behind when a trustee starts asking questions.
What the board actually needs to know
Boiled down, it's all about variance reporting. This is the gap between what you planned to spend and receive and what actually happened. This needs to be explained well enough that the board can govern on it. But charities or public bodies have an extra layer to deal with, because the money isn't in one pot.
Under the Charities SORP, restricted and unrestricted funds are reported separately, and in practice each fund or programme is tracked against its own budget. This means a variance isn't a single number but a set of them, and 'broadly on plan overall' can hide a restricted fund that's badly off track.
The question behind each line is whether the difference is due to timing that will wash out, or a real change the board needs to act upon.
Most of the work is upstream
Answering this question credibly depends almost entirely on the data underneath, and that's where most of the effort actually goes. In this sense, a variance explanation is only as good as the coding beneath it.
For example, if a cost was tagged to the wrong programme, you get a phantom variance in two places at once: a false overspend where the cost landed, and a false underspend where it should have gone.
When transaction records are manual and scattered across spreadsheets, card receipts, and invoices sitting in an inbox, most of the reporting cycle gets spent assembling and coding that data rather than thinking about what it means. When that happens, the narrative tends to end up being written in the last few hours, on top of numbers you haven't had time to trust.
The high cost of shaky data
Messy upstream data is costly because it's slow and the numbers are fragile. When a board member picks a line and asks why it's moved, a shaky answer is the worst answer because it erodes trust.
It's these crucial moments that make or break the relationship between the board and the finance team. A sole finance lead who spends most of the cycle reconciling rarely has time left to spot the variance that actually matters before the big meeting.
Fixing bad data at the source
Most of the fix for this type of situation actually sits upstream in the inputs, rather than the report itself. In this sense, the credibility of a variance report is decided long before you open the template, and it comes down to how spend was recorded throughout the period.
To rectify this, code transactions to the right fund and programme as they happen, not in a year-end scramble. Keep receipts and approvals attached to the spend they belong to so you're not reconstructing from memory.
You should also be reconciling as you go, so the ledger is close to correct at any point in the period, rather than only after a cleanup. Once you've done this, the report becomes close to a byproduct of clean books, and you can start dedicating more time to explaining the numbers.
Where a tool like Moss fits in
Moss doesn't produce the variance report or generate your SORP accounts. The reporting layer stays in your accounting system, where it belongs.
Where it does help is upstream of reporting. Expense management and accounts payable capture and code spend as it happens, with receipts attached, and sync two-way with the accounting system, so the transaction data behind the report is clean, coded and audit-ready by the time you come to explain it.
In this sense, it shortens the reconciliation that sits behind the report. It doesn't touch the report itself.
Where credibility is really decided
While the report your board sees is the last and most visible slice of the work you've done, its credibility was actually decided months before. It depends on how cleanly the underlying spend was captured and coded.
Get that right and you immediately give yourself an easier time in the variance meeting. Instead of defending numbers you assembled at speed, you're explaining a picture you already trust.
