Budget Versus Actual Variance Analysis

A monthly budget versus actual cycle that budget holders trust and act on: clean mapping and thresholds, named owners, explanations with causes, review meetings, action logs and the analysis skills behind them.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Budget Versus Actual Variance Analysis, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help your team organise its work. It is not financial, investment, tax, accounting or legal advice, and it does not recommend any product, investment or deal. Rules differ between countries, so check decisions that matter with qualified, licensed advisers in the countries concerned. Investing can lose money, and raising or managing other people's money is regulated in most countries.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧾 Finance & Accounting

Budget Versus Actual Variance Analysis

Comparing actual results to budget and forecast each month, explaining the variances and turning them into actions for budget holders.

  1. Variance review scope across company, division and cost centre
  2. Budget and actuals reconciled on one account mapping
  3. Favourable and adverse sign convention
  4. Variance investigation thresholds by line
  5. Variance explanation owner for each line
  6. Variance report layout with month, year-to-date and full-year columns
  7. Comparator choice between budget, forecast and prior year
  8. Variance reason codes
  9. Twelve-month variance history baseline
  10. Variance cycle deadlines after the close
  11. Pre-issue miscoding and accrual sweep
  12. Monthly variance report run and ledger tie-out
  13. Budget holder explanation requests and chasers
  14. Headcount and payroll variance check
  15. One-page variance summary for leadership
  16. Monthly variance review meeting
  17. Variance action log follow-through
  18. Timing variance reversal tracker
  19. Weekly watch on high-risk spend lines
  20. Quarterly full-year outturn variance review
  21. Annual threshold and reason code refresh
  22. Price, volume and mix variance on revenue
  23. Flexed budget for activity-driven costs
  24. Timing versus permanent variance judgement
  25. Writing variance explanations with cause, permanence and action
  26. Monthly operating profit variance waterfall
  27. Rate and efficiency variances for labour costs
  28. Variance reporting tool decision
  29. Automated variance extract from ledger and budget
  30. Self-service variance view for budget holders
  31. Committed spend reported beside actuals
  32. Permanent variances handed to the reforecast
  33. Rephasing the budget when timing was wrong
  34. Variance explanation quality audit
  35. First variance cycle on the new process
  36. Half-year variance review with leadership
  37. Board or audit committee variance briefing
  38. Year-end budget outturn retrospective
  39. Variance lessons handed to next year's budget
  40. First quarter as a budget holder explaining variances
  41. Defending a large overspend to leadership
  42. New FP&A analyst inheriting the variance process
  43. Splitting variance work across a small finance team
  44. Divisional variance roll-up for an enterprise group
  45. Variance control during a spending freeze
  46. Planning and operational variance split
  47. Constant currency variance restatement
  48. Control limits for noisy variance lines
  49. Earned value variances on major projects
  50. Standard cost variances in manufacturing

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Variance review scope across company, division and cost centre

Ask who needs to see variances at which level before building anything: the leadership team usually wants a dozen lines at company level, while a department manager needs every account in their own cost centre. Writing down the levels, the lines and the audience for each stops one giant report from trying to serve everybody and pleasing nobody.

First tasks

  • List every level at which budgets are currently set, from company to project
  • Name the readers at each level and the lines they own
  • Count the lines each reader would have to explain in a typical month
  • Agree the one-page scope note with the finance lead

Budget and actuals reconciled on one account mapping

Variances are only meaningful when budget and actuals sit on exactly the same accounts, cost centres and periods, and in many businesses they do not: the budget was built on summary lines, renamed accounts or last year's structure. Reconciling the loaded budget back to the approved total and mapping every budget line to a ledger account removes the false variances that otherwise waste the first meeting.

First tasks

  • Export the loaded budget and total it against the approved budget
  • Map every budget line to a ledger account and cost centre
  • List ledger accounts with actuals but no budget and decide where each belongs
  • Check the monthly phasing in the system matches the approved phasing

Favourable and adverse sign convention

Half the arguments in a variance meeting come from people reading a minus sign differently: is a negative cost variance good or bad? Choosing one convention, labelling every variance favourable or adverse in words, and using the same colours throughout the report means nobody has to stop and work out which way round a number runs.

First tasks

  • Write the sign convention for revenue, costs and profit in two sentences
  • Add a favourable or adverse label beside every variance figure
  • Pick colours for the labels and check they read in greyscale
  • Print the convention in the footer of every report page

Make it yours.

Install Budget Versus Actual Variance Analysis, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.