Nonprofit budget vs actual dashboard

A nonprofit budget versus actual report has to satisfy two audiences with different questions. The board wants to know whether the organisation is on plan. Funders want to know whether their restricted money went where the grant agreement said it would. A dashboard that answers only the first will fail an audit; one that answers only the second is useless for running the organisation.

Variance is a question, not a verdict

The preview shows $62,000 under budget and labels it on track. That reading depends entirely on the time elapsed. At 58% of budget spent, the organisation is on plan only if roughly 58% of the year has passed — and it is July in a fiscal year that began in January, so 58% is almost exactly right.

Change either side and the same number means something different. Underspend in month eleven is not prudence, it is an execution problem and, for restricted funds, frequently a clawback. Read variance against elapsed time, always, and put both on the dashboard so nobody has to do the arithmetic in their head.

Read it by program, never in aggregate

The aggregate number is the least informative figure on the page. In the preview, the organisation is 58% through its budget overall, but Housing Aid is at 71% and Food Security at 54%. Those two programs are having entirely different years, and the aggregate says neither.

Program-level variance is also what most funders actually ask for. A grant agreement restricts money to a program, so the reporting unit is the program, and an organisation that can only produce an organisation-wide figure will be rebuilding it by hand every reporting cycle. That is a chart-of-accounts decision made at setup, not a reporting decision made later.

Restricted funds change the arithmetic

Unrestricted money is fungible: underspend in one area can fund another. Restricted money is not, and treating the two alike is the single most common reporting failure in a small nonprofit. Three rules follow.

• Track restricted and unrestricted separately at the ledger level, not with a spreadsheet overlay applied at reporting time. The overlay is where the error enters.
• Watch the grant calendar, not the fiscal calendar. Grant periods rarely align to your fiscal year, so a program can be on plan for the year and behind on a grant that ends in March.
• Treat unspent restricted funds as a liability, not a surplus. Money that may have to be returned is not money the organisation has, however it looks on a summary line.

The $890,000 remaining across three active grants in the preview is the figure a finance committee should be asked about first, because it is the one with an external deadline attached.

Administrative ratio, and what it does and does not prove

Admin and operations is 12.5% of the budget in the preview and running at 48% consumed. Funders and rating bodies look at the admin ratio, and the pressure to push it down is constant. It is worth being clear-eyed about it: an admin ratio below what the organisation genuinely needs is not efficiency, it is deferred cost, and it usually shows up as the finance function nobody funded.

What the dashboard should do is make the allocation defensible rather than minimal. If shared costs are allocated across programs on a documented basis, the ratio survives scrutiny. If they are allocated on a basis somebody invented at reporting time, it will not.

Cadence and the close

Monthly, as part of the close, with a formal review at each finance committee meeting. Quarterly is too slow for a variance to still be correctable — a program tracking 15 points behind at the end of Q2 can usually be brought back; the same gap discovered in Q3 usually cannot.

The prerequisite is a close that actually finishes. A budget versus actual report built on a ledger that is six weeks behind is a historical document, and every decision it informs is being made on the previous quarter's facts. Nonprofit and mission-driven bookkeeping covers the setup; the month-end close checklist covers the process.

Frequently asked questions