The standard budget-versus-actual table is a starting point, not an endpoint — if analysis stops at the table, it has not begun. IMA research confirms that fewer than 25 per cent of mid-sized companies decompose variances beyond the total-level comparison, leaving the vast majority stuck reporting what happened without explaining why or what to do about it. Three upgrades transform BvA from a report pack into a decision agenda: materiality thresholds that eliminate noise so not every variance competes for attention, flexible budgets that separate volume effects from operational performance (the single most impactful analytical upgrade), and narrative discipline requiring every material variance to carry a “why,” a “so what,” and a “now what.” The output should be a decision agenda, not a data appendix. If the CEO glances at the BvA report and moves on, the format has failed — the goal is discussion and action, not compliance.
Three days producing. Five minutes reading. The monthly plan vs actuals cycle in most mid-market finance teams follows this pattern with depressing regularity. The controller assembles the numbers, formats the table — plan, actual, variance, variance percentage — distributes it, and waits. The CEO scans the summary page, nods, and moves on. The board receives it as an appendix. Nobody asks a follow-up question. The report has been delivered. The analysis has not happened.
This is not a problem of effort. It is a problem of methodology. The standard BvA table answers a single question: “what happened?” It does not answer “why did it happen?” or “what should we do about it?” Those are the questions that matter. This article explains how to move beyond the table.
What Plan vs Actual Actually Means — and Where Most Teams Stop
Variance analysis in its simplest form compares budgeted or planned figures against actual results. The output is a variance (the arithmetic difference) and a variance percentage (the difference expressed as a proportion of plan). Every financial controller knows how to produce this table. The question is what happens after it exists.
There is a critical distinction between BvA reporting and BvA analysis:
| BvA Reporting | BvA Analysis | |
|---|---|---|
| Output | Table of numbers | Narrative with decisions |
| Question answered | What happened? | Why did it happen? What now? |
| Time allocation | 90% production, 10% review | 50% production, 50% interpretation |
| Audience response | Glance and file | Discuss and decide |
| Value created | Compliance | Insight |
Most mid-market finance teams are stuck firmly in the left column. IMA (Institute of Management Accountants) research confirms that fewer than 25% of mid-sized companies decompose variances beyond the total-level BvA comparison. The vast majority never move past the table.
The Cost of Table-Centric BvA
When BvA stops at the table, several things go wrong — quietly, cumulatively, and expensively.
The effort-to-impact ratio collapses
The finance team spends days closing the books, reconciling data, and formatting reports. The output reaches leadership in a form that invites scanning, not engagement. The problem is not the CEO’s attention span. It is the report’s decision-relevance. A wall of numbers without context or priority is genuinely difficult to act on.
Standardised excuses replace genuine analysis
When every variance receives the same weight and the same superficial explanation — “timing differences,” “one-off,” “phasing” — no real diagnosis occurs. These phrases are not explanations. They are placeholders that allow the cycle to close without understanding what happened or whether it will happen again.
Budget credibility erodes
If the budget was constructed poorly — on unrealistic assumptions, with inadequate operational input, or as a negotiated political number — then the entire BvA exercise becomes theatre. Comparing actuals to a flawed baseline produces variances that are artefacts of bad planning, not signals of operational performance. And when people recognise this, they stop trusting the process entirely.
Corrective actions never arrive
Ventana Research finds that companies with structured variance analysis are 2.4x more likely to meet or exceed their financial targets. The mechanism is straightforward: structured analysis identifies causes, causes inform actions, actions change outcomes. When BvA stops at the table, this chain never starts.
Six Principles for Moving Beyond the Table
1. Start with materiality thresholds
Not every variance deserves an explanation. Define materiality thresholds before the reporting cycle begins — both in absolute terms (e.g., variances above £50,000) and relative terms (e.g., variances above 10% of plan). Apply them consistently. This eliminates the noise that makes BvA reports exhausting to produce and tedious to read.
A controller who explains every £2,000 deviation is not being thorough. They are burying the £200,000 trend in a wall of immaterial detail.
2. Layer the analysis for different audiences
The CEO, the divisional manager, and the financial analyst need different views of the same reality:
| Audience | Needs | Format |
|---|---|---|
| Executive / Board | Top 5 material variances with cause and action | One-page summary with commentary |
| Divisional managers | Variances within their scope, decomposed by driver | Detailed tables with narrative per line |
| Financial analysts | Full detail, trends, decomposition | Drill-down workbooks with period-over-period data |
The answer to the CEO attention problem is not shorter reports. It is more decision-relevant reports — summary with drill-down capability, not compression that removes context.
3. Use flexible budgets to separate volume from efficiency
This is the single most impactful upgrade most mid-market finance teams can make to their BvA process.
A static budget assumes a fixed level of activity. When actual volume differs from plan, every cost line shows a variance — even if the business operated exactly as expected at the actual volume level. This produces volume variances that obscure operational performance.
A flexible budget adjusts the budget for actual volume, isolating the volume effect and revealing whether the business performed efficiently at the volume it actually achieved.
Example:
| Static Budget | Actual | Static Variance | Flex Budget (at actual volume) | Flex Variance | |
|---|---|---|---|---|---|
| Revenue | £1,000,000 | £920,000 | −£80,000 | £950,000 | −£30,000 |
| Variable costs | £600,000 | £580,000 | +£20,000 | £570,000 | −£10,000 |
| Contribution | £400,000 | £340,000 | −£60,000 | £380,000 | −£40,000 |
The static budget shows a £60,000 shortfall in contribution. The flexible budget reveals that £20,000 of this is a volume effect (selling less than planned) and £40,000 is an efficiency/price effect (performing worse than expected at the actual volume). These are fundamentally different problems requiring fundamentally different responses.
Aberdeen Group research shows that firms using flexible budgets report 35% improvement in forecast accuracy — because the baseline itself becomes more meaningful.
4. Add narrative discipline: why, so what, now what
Every material variance needs three statements:
- Why (cause): What happened operationally or commercially to produce this variance?
- So what (impact): What is the financial and strategic consequence if this continues?
- Now what (action): What specific corrective action is planned, or has a conscious decision been made to accept the variance?
This is where BvA shifts from data to analysis. Without these three statements, the variance is reported but not understood. The distinction matters because understanding is what generates action.
| Variance | Why | So What | Now What |
|---|---|---|---|
| Revenue −£80K | Key customer delayed Q1 order to Q2 due to their own cash flow constraints | £80K timing shift; expect recovery in Q2. No margin impact. | Monitor customer payment behaviour. No plan revision needed. |
| Materials +£45K | Spot purchasing at premium prices due to primary supplier stockout | Margin erosion of 1.2pp if sustained. Annualised risk: £180K | Procurement to qualify secondary supplier by end of Q2. |
| Labour +£30K | Overtime to meet delivery deadline on Project X | One-time cost, fully offset by project margin. | No action required. Document as project cost for future pricing. |
5. Track patterns across periods
A 2% variance in a single month is noise. A 2% variance in the same direction for six consecutive months is a trend — and likely a structural issue that the plan did not capture.
Cumulative and trend perspectives are essential. Each month should not be treated as an isolated event. The BvA report should show:
- Current month variance
- Year-to-date cumulative variance
- Rolling trend (direction and magnitude over the past 6–12 months)
- Comparison to the same period in the prior year
Pattern recognition is what converts monthly reporting into genuine performance monitoring.
6. Close the loop
Document what was decided and track whether corrective actions were carried out. If a March variance triggered a pricing review, the April report should note whether that review happened and what it found. Without this feedback loop, BvA is a series of disconnected observations rather than a continuous management process.
Common Pitfalls
Producing the table and calling it analysis. The table is data. Analysis is interpretation, causation, and recommendation. If the BvA output contains no narrative, no prioritisation, and no action items, it is a report, not an analysis.
Explaining every variance with equal weight. Materiality thresholds exist for a reason. Spending two paragraphs on a £3,000 variance while a £150,000 deviation gets one line is a failure of prioritisation, not thoroughness.
Comparing actuals to a static budget when volumes have changed. This is the most common methodological error in mid-market BvA. It produces volume variances that mask or distort operational performance. Flexible budgets address this directly.
Formatting over substance. Colour-coding, conditional formatting, and visual design are useful — but they do not replace analysis. A beautifully formatted table with no narrative is still just a table.
Treating BvA as a finance exercise rather than a management conversation. The output of BvA should be a decision agenda — a list of issues requiring management attention, each with a cause, an impact assessment, and a proposed response. If it remains an internal finance document, its value is limited to compliance.
Industry Considerations
Manufacturing: Standard cost variances — material price, material usage, labour rate, labour efficiency — are well established in manufacturing environments. The gap is typically not in producing these variances but in connecting them to management decisions and tracking corrective actions.
Services: Project-level BvA (budget vs actual hours, rate variances) is often tracked at individual project level but rarely aggregated into a portfolio view that reveals patterns across projects, clients, or service lines.
Retail and distribution: Markdown variances and promotional cost variances sit alongside standard BvA. These are frequently reported but rarely subjected to root cause analysis — the “why” behind markdown decisions is seldom traced back to demand planning accuracy.
Frequently Asked Questions
How is plan vs actual different from variance analysis? Plan vs actual is the comparison itself — the arithmetic of plan minus actual. Variance analysis is the broader discipline that includes decomposing that difference into its components (price, volume, mix), diagnosing causes, and deciding on responses. BvA is the input; variance analysis is the process.
What materiality threshold should we use? There is no universal answer. Common approaches include absolute thresholds (e.g., variances above £25,000 or £50,000), relative thresholds (e.g., above 5% or 10% of plan), or a combination. The threshold should reflect the organisation’s size, risk tolerance, and the cost of investigating vs the cost of ignoring. Start somewhere reasonable and adjust based on experience.
Can we improve BvA without changing our tools? Yes. The principles in this article — materiality thresholds, layered reporting, narrative discipline, flexible budgets, trend tracking, and loop closure — apply regardless of whether BvA is performed in a spreadsheet or a dedicated reporting environment. The methodology matters more than the medium.
How do flexible budgets relate to rolling forecasts? A flexible budget adjusts the original plan for actual volume. A rolling forecast replaces the static annual plan with a continuously updated projection. Both address the same underlying problem — the original plan becoming stale — but through different mechanisms. They are complementary, not substitutes.
Related Reading
- Variance Analysis — A Practical Guide — the structural foundation for BvA analysis
- Root Cause Analysis for Financial Variances — how to diagnose the “why” behind material variances
- Driver-Based Performance Analysis — connecting variances to operational and commercial causes
- Management Reporting Framework — structuring reports for decision-relevance
Sources
- IMA (Institute of Management Accountants), “Statements on Management Accounting: Variance Analysis,” imanet.org
- Ventana Research, “The Value of Structured Variance Analysis in Mid-Market Companies,” ventanaresearch.com
- Aberdeen Group, “Flexible Budgets and Forecast Accuracy in Mid-Market Finance,” aberdeen.com
Martin Duben is the founder of OneTribe Advisory, where he works with mid-market finance leaders on performance analysis, management reporting, and financial governance. He writes about the practices that separate reporting from analysis.