Budget vs Actual Variance
The measured difference between what a company planned to spend or earn and what actually happened, expressed in dollars and percentages to surface operational deviations. The useful output is not the number but the attribution: how much of the gap is volume, how much is price or rate, and how much is timing that reverses next period.
The CFO wants an explanation for the $380K favorable variance in Q3 SG&A. Finance knows two things: hiring was slower than planned, and one vendor contract slipped. The variance report shows the number but not the reason, so someone writes the explanation as a separate document every quarter. Budget vs actual variance analysis compares what a business planned to spend or earn in a period with what actually happened, then explains the differences in terms that matter for business decisions. The variance, the difference between budget and actual, is where the analysis starts, not where it ends. A $380K favorable SG&A variance tells you the result. It doesn't tell you whether it reflects a permanent change in the cost structure, a timing difference that will reverse next quarter, or investments the business needed and didn't make. Which of those is true changes the operational and financial response entirely. Budget vs actual analysis is one of the most common exercises in FP&A and one of the most often done poorly, because the number is easy to calculate and the explanation is hard to produce consistently.
How budget vs actual variance analysis works
The analysis starts with the variance calculation: actual minus budget for revenue items (favorable if actual exceeds budget), and budget minus actual for expense items (favorable if actual is below budget). The total variance on any line can then be broken into components. Volume variance is the portion caused by doing more or less activity than planned: selling more units, hiring more people, processing more transactions. Price variance is the portion caused by rates or costs differing from plan: a higher average selling price, lower vendor rates, wage increases not in the budget. Timing variance captures activity that was planned but landed in a different period, such as a contract signed in October that was budgeted for September, or a hire who started in Q4 instead of Q3. The breakdown matters because each type calls for a different response. Volume variance on revenue says something about demand or sales execution. Price variance on expenses says something about vendor negotiation or inflation. Timing variance is usually neutral if it reverses as planned, but it becomes a problem when it is recurring slippage that permanently reduces capacity or investment. The analysis also needs a materiality view. Not every line deserves the same depth, and the best variance reports focus explanations on the variances that are largest in absolute dollars, most likely to recur, or most relevant to current strategic priorities.
Volume vs price vs timing variance
Splitting variance into volume, price, and timing is the standard framework, but applying it takes data the general ledger alone often can't supply. Volume variance on revenue needs unit or transaction data. Price variance on expenses needs invoice-level detail. Timing variance needs the original budget phasing compared with actual timing, which only works if the budget was phased correctly in the first place. If you build a single-number annual budget with no monthly phasing, you can't do meaningful timing analysis: everything looks like a permanent variance even when it isn't. How often you run the analysis also changes its value. Quarterly variance analysis is retrospective; it explains what happened after the fact and rarely changes behavior in the quarter being analyzed. Monthly analysis is still mostly retrospective but close enough to allow corrective action. Weekly analysis, usually applied to revenue and cash rather than the full P&L, looks forward and allows course correction within the period. Weekly analysis is only worth the effort for metrics where a week's difference affects a decision the business can actually make.
How FP&A tools surface variance analysis, drill-down depth
FP&A and forecasting platforms handle variance reporting in two ways: automated variance calculations with drill-down to the underlying transactions, and structured commentary workflows where finance partners attach explanations to specific variances. Drill-down is simple; any tool connected to the ERP can show variance by account, cost center, vendor, or transaction. Commentary is where platforms differ. Some require commentary in a structured template tied to specific variance thresholds. Others are freeform. The strongest setups tie commentary directly to the management report so the explanation sits next to the number in the board pack instead of in a separate document. Before evaluating any FP&A tool for variance reporting, ask specifically about the commentary workflow: how commentary is entered, who owns it, how it flows into the final report, and what happens to it for trend analysis across periods.
Variance analysis process questions worth asking
- Is our budget phased monthly, and does the phasing reflect when activity was actually expected to happen, or was it spread evenly across quarters?
- Do we decompose variances into volume, price, and timing components, or do we only report the total variance?
- At what threshold do we require written explanations for variances, and is that threshold applied consistently across all functions?
- How long after the close does variance analysis typically take to complete, and what is the constraint?
- Is variance commentary attached to the variance data in a system, or produced as a separate document that lives outside the financial model?
- Do business unit leaders understand the difference between favorable and unfavorable variances that are structural versus those that are temporary?
Where variance analysis goes wrong
The most common failure in variance analysis is timing: analyzing variances after the quarter closes instead of during it. By the time a Q3 variance analysis is finished in late October, the Q4 plan is already the current forecast and the Q3 explanation has little operational use. Teams that get value from variance analysis use it to monitor during the period, not to report after it. The second failure is treating every variance as equally important regardless of size or driver. Writing a detailed explanation for every line with any variance, immaterial ones included, pulls attention away from the variances that matter. Good variance reports apply a materiality filter and put analytical depth into variances that are large, recurring, or strategically significant. There is also a behavioral risk in how variances are communicated. If favorable variances are celebrated regardless of cause, managers will time spending to produce them instead of investing where the business needs it. Analysis that separates favorable timing variances from real efficiency gains avoids rewarding the wrong behavior.
Comparing planning platforms
Planning platforms separate on who can maintain the model after go-live, which is a staffing question as much as a software one. Once budget vs actual variance is settled as a requirement, read the Forecasting Software category guide for how the market splits, then weigh the Anaplan profile against the Pigment profile on that requirement rather than on the feature list. Our Anaplan pricing breakdown records what the vendor publishes and what is quote-based. The Anaplan against Pigment comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the forecasting ROI calculator so the business case is written down before a vendor writes it for you.
Budget vs Actual Variance questions
How is budget vs actual variance different from forecast variance?
Budget vs actual variance compares results with the original approved plan for the period. Forecast variance compares results with the most recent forecast, which may have been updated after the budget was set. Both are useful, but they answer different questions. Budget variance tells you how well the original assumptions held. Forecast variance tells you how well the latest predictions held. An organization that keeps updating its forecast as new information comes in will usually show smaller forecast variances and larger budget variances, which is expected and healthy.
Should unfavorable variances always be investigated?
Not necessarily. Materiality and context matter more than the direction of the variance. A small unfavorable variance on an immaterial line may not be worth investigating. A large favorable variance caused by skipping a planned investment is more concerning than a moderate unfavorable variance from a one-time expense. Decide what to investigate based on the size of the variance, whether it is likely to recur, and whether it says something important about business performance or planning accuracy.
How should variance explanations be structured for a board audience?
Board-level variance explanations should lead with the bottom-line impact, name the top two or three drivers in plain language, separate timing variances (expected to reverse) from permanent ones, and connect the variance to any implications for the full-year outlook. Skip the line-by-line recitation. Board members need to understand what happened and what it means, not reconstruct the analysis themselves.
Related terms
Capital Expenditure (CapEx), Cash Flow Forecasting, and Driver-Based Planning come up in the same workflow as budget vs actual variance, and the rest of the planning platforms cluster is indexed in the finance operations glossary.