This free budget variance review checklist is the monthly budget-versus-actual review for finance teams, FP&A, controllers and the budget holders who own each cost centre. One run is one month’s review for one entity, started once the month-end close is signed off. It confirms the actuals are final, pulls the report by cost centre or department and account for the month and the year to date, and agrees it to the trial balance. Every line over your threshold, set as an amount and a percentage on the first task, goes to its budget holder with a deadline. The explanations are classified as timing, volume, price or rate, one-off, error or permanent change. Mispostings are corrected through a journal, and a variance that will continue adds a reforecast for the rest of the year. Finance writes the commentary and a variance report, the finance lead reviews it, management signs it off, and the agreed actions are tracked to next month’s review. Answers along the way add a forecast comparison, a chase and an escalation for missing explanations, a leadership decision on a large variance and the quarter-end pages.
The Annual Budget Planning Checklist sets the budget once a year. The Monthly Management Reporting Pack Checklist reports the month to leadership. Between them sits the monthly budget variance review: the budget-versus-actual report taken line by line, every line over the threshold explained by the person who owns it, mispostings corrected and the forecast changed where a variance will not reverse.
This checklist is that review, for the person preparing it, the budget holders, the finance lead and whoever signs it off. It starts once the Month-End Finance & Accounting Close Checklist is signed off, and its commentary and forecast change are what the management pack reports. If you run both, this review replaces the pack’s own variance queries and commentary collection: mark those pack tasks not applicable and take this review’s commentary, forecast change and decisions into the pack once the finance lead has reviewed them. If you do not produce a full management pack, this review’s variance report is the monthly report to leadership.
Covers: budget against actual by cost centre and account, the threshold, budget holder explanations, mispostings, the forecast decision, commentary, sign-off and the action log.
When: every month, once the books are closed.
Output: an explained variance log, a signed-off variance report and a list of actions with owners.
Covers: assumptions, department submissions, challenge sessions and the approval chain that produce the budget.
Use it: to set the budget this review measures against. Annual Budget Planning Checklist.
Covers: KPIs, the results against budget, forecast and prior year, cash, the board pack and distribution.
Use it: to report the month to leadership, with this review’s commentary in it. Monthly Management Reporting Pack Checklist.
Eight phases take one month’s review from the closed books to the actions agreed for next month. The first task sets the threshold and the people, and later answers add only what this month needs: a comparison with the latest forecast, a chase and an escalation for missing explanations, a correcting journal, the reforecast, a leadership decision on a large variance and the quarter-end pages. Management sign-off is the gate: nothing is shared until it is done.
The person preparing the review starts the run once the month’s close is signed off. The answers on the first task assign every task, set each due date in business days from the day the books were closed and add the steps this month needs.
Pull one report for the entity from the locked ledger, by cost centre or department and by account, for the month and the year to date. Prove it is complete before anyone looks at a variance.
Apply the threshold from the first task to every line, for the month and the year to date. A line over it goes in the variance log with its budget holder. Look at the transactions behind it first, so budget holders are not asked about a posting finance can put right.
Each budget holder gets their own flagged lines and a deadline. Missing explanations add a chase and an escalation. An explanation that shows an error or misposting adds the correction tasks in Phase 5.
Correct what was posted wrongly, then decide whether the forecast changes. Timing differences move between months and one-offs pass; a permanent variance adds the reforecast tasks. The approved budget stays as it is.
Turn the explanations into commentary and a short variance report. In a quarter-end month two more tasks add the quarter and year-to-date review and the pages for the board pack.
The finance lead reviews the log and the commentary. A variance large enough to need a decision, such as a spending freeze or a budget reallocation, goes to leadership before sign-off. Management sign-off is the gate: nothing is shared until it is done.
Share the signed-off variance report, give each budget holder their results and actions, and track every action to next month’s review, where the first phase checks them again.
Each flagged line gets one type on the classification task. The type decides the question for the budget holder and what happens to the forecast.
| Kind of variance | What it usually looks like | What to ask the budget holder | What it means for the forecast |
|---|---|---|---|
| Timing | Spend or income in a different month from the budget’s phasing: an invoice early or late, a project start moved | When will it reverse, and in which month? | None for the full year if it reverses; check the phasing of the next months |
| Volume | More or fewer units, hours, customers or people than the budget assumed | What drove the volume, and will it continue? | Changes the forecast if the new level continues |
| Price or rate | The same volume at a different price, pay rate, exchange rate or supplier cost | Is the new price fixed for the rest of the year? | Changes the forecast from the month the new price applies |
| One-off | A cost or income that will not repeat, such as a settlement or a recruitment fee | Will it really not repeat, and was it approved? | No change to later months; the year to date carries it |
| Error or misposting | A cost in the wrong cost centre, account or month, or a duplicate | Not a question for the budget holder: finance corrects it through a journal | None; run the report again after the journal |
| Permanent change | A decision or event that changes the run rate, such as a new contract, a lost customer or a new hire | What changed, and from when? | Reforecast the rest of the year |
Phase 3 tests every line in both views, because each one catches what the other misses.
| What you see | What it often means | What to do |
|---|---|---|
| Over the threshold in the month, not in the year to date | Often timing: the month is catching up with an earlier one, or running ahead of a later one | Confirm when it reverses, and say so in the commentary |
| Over the threshold in the year to date, not in the month | A small overspend or underspend that repeats every month | Ask whether it will continue; it may need a reforecast |
| Over the threshold in both | A larger change, or a one-off in this month | Explain it in full and decide on the forecast |
| Under the threshold in both, but the same direction every month | Drift that the threshold does not catch yet | Mention it in the commentary and watch next month |
These are working rules, not a standard. Your own finance policy decides the threshold, the types you use and who signs off.
A monthly recurring schedule starts the review for each entity. Enter the day the books were closed and every task gets a due date from it, counted in business days. Each month’s review sits on the Reports Grid with its answers, so one that is still open stands out.
Management sign-off is a gate: the variance report cannot be marked shared, and the actions cannot be logged, until it is done. A large variance goes to leadership for a decision first, so the sign-off happens with the decision recorded. See how approval steps work.
Each budget holder is assigned the explanation task, with its due date, and overdue alerts go to every assignee. A missing explanation adds a chase and then an escalation to the finance lead. Analytics shows completion rates and overdue and late work by person and by step, month after month.
CheckFlow does not hold your budget or calculate variances; your accounting system, spreadsheet or planning tool does that. CheckFlow runs the process around the report: who flags each line, who explains it, what was corrected, what changed in the forecast, who signed off and which actions are still open.
Close the month first with the Month-End Finance & Accounting Close Checklist and the Balance Sheet Reconciliation Checklist, so the actuals are final. Correct mispostings through the Journal Entry Review & Approval Checklist, carry the cash effect of a reforecast into the Weekly Cash Flow Forecast Checklist, and report the month to leadership with the Monthly Management Reporting Pack Checklist. The budget itself is set with the Annual Budget Planning Checklist.
Month-End Finance & Accounting Close Checklist
Annual Budget Planning Checklist
Monthly Management Reporting Pack Checklist
Weekly Cash Flow Forecast Checklist
Journal Entry Review & Approval Checklist
Describe the process in a sentence and the AI checklist generator drafts the phases and tasks for you.
A budget variance review is the monthly check of actual results against the budget, line by line, once the books are closed. Finance pulls the budget-versus-actual report by cost centre and account, flags every line over an agreed threshold and asks the budget holder who owns it to explain it. The explanations are classified, errors are corrected, the forecast is changed where a variance will continue, and the review is signed off with a list of actions. A favourable variance is better than budget (lower cost or higher income); an adverse one is worse.
Monthly suits most businesses, once the month-end close is signed off, so the figures being explained are final. Starting before the close means explaining numbers that are still moving. In a quarter-end month this checklist adds a quarter and year-to-date review and the pages for the board pack. Run it on a recurring schedule so it starts every month without anyone remembering to.
There is no standard figure. Each business sets its own in its finance policy, usually as an amount and a percentage of the line’s budget, and applies the same threshold every month. Using the amount alone flags every large line, even when the change is small in proportion; using the percentage alone flags small lines that hardly matter. This checklist asks for both on the first task and lets you choose whether a line is flagged when it is over either one or both.
Most variances fall into six types: timing (spend in a different month from the budget’s phasing), volume (more or less activity than planned), price or rate (the same activity at a different cost), one-off items, errors or mispostings, and permanent changes such as a new contract or a lost customer. The type matters because it decides what happens next: timing reverses, an error is corrected through a journal, and a permanent change goes into the forecast.
Both. A line can be over the threshold in the month and back on budget for the year, which usually means timing. Another can stay under the threshold every month while the year-to-date overspend keeps growing. This checklist tests every line in both views, and flags a line that is over the threshold in either.
When it will continue. Timing differences and one-off items leave the full-year forecast alone. A volume, price or permanent change that will carry on into later months goes into the forecast for the rest of the year, while the approved budget stays as it was, so you can still see the difference. Pass any change in the timing of cash to whoever runs the Weekly Cash Flow Forecast Checklist.
Chase once with a short new deadline, then escalate to the finance lead, who raises it with the budget holder or their manager. Mark the line unexplained in the variance log, so the review can be signed off without pretending it has an answer, and carry it into next month’s review. In this checklist, choosing “One or more explanations missing” adds the chase and the escalation tasks.
The Monthly Management Reporting Pack Checklist produces the whole pack leadership reads each month: KPIs, results against budget, forecast and prior year, cash and the board pages. The budget variance review is the work underneath its variance section, done with each budget holder: flagging their lines, getting the explanations, correcting mispostings, deciding on the forecast and tracking the actions. If you run both, run this review first and take its commentary and forecast change into the pack once the finance lead has reviewed them (Phase 7), so budget holders are asked once; the pack’s variance queries and commentary tasks can then be marked not applicable. Note anything that changes at sign-off in next month’s pack.
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request
