Why Actuals Never Match Budget: A Field Guide to Variance Analysis
Every company builds a careful annual budget, and then the year happens and it never matches. Variance analysis is how finance teams explain the gap fast, correctly, and in language an executive can actually use.
The Budget Is a Guess, Treat It Like One
Every company builds an annual budget, usually finished sometime between October and December for the following calendar year, based on assumptions about growth, pricing, costs, and headcount that were the best available information at the time. Then the year happens, and it never matches. A customer that was supposed to renew churns instead. A raw material that was budgeted at last year's price jumps 15 percent because of a supply shock. A product launch that was supposed to ship in March ships in June. None of this means the budget was badly built. It means a budget is a forecast made under uncertainty, locked in months before the period it covers even begins, and reality does not hold still that long. The job of variance analysis is not to prove the budget was right or wrong. It is to explain, clearly and quickly, why the actual result differs from the plan, so decision makers know whether to worry, adjust, or ignore the gap.
Three Kinds of Variance
Nearly every variance an FP&A analyst investigates falls into one of three buckets, and separating them correctly is one of the most useful habits in the job. Timing variance happens when spend or revenue simply lands in a different month or quarter than budgeted, but nets out over the full year. A marketing campaign budgeted for September that actually runs in October looks like a bad September and a great October, when nothing has actually changed about the underlying plan. Rate variance happens when the price per unit changes, a vendor raises the cost per part, a new hire's salary comes in above the budgeted band, or a lease renews at a higher rate per square foot. Volume variance happens when the company simply does more or less of something than planned, sells more units, ships more packages, hires more people. A retailer that sells 20 percent more units than budgeted in December will spend more on shipping than budgeted, and that is not bad news, it is a direct, healthy consequence of stronger sales. Mixing volume variance up with rate variance, treating higher shipping spend as a cost control failure when it is actually just more orders going out the door, is one of the most common mistakes new FP&A hires make.
Favorable Is Not Always Good
Budgets get evaluated in two directions, favorable, meaning the result was better than plan, and unfavorable, meaning worse than plan. It is tempting to treat every favorable variance as a win and move on, but the most useful variance analysis digs into favorable numbers just as hard as unfavorable ones. A department that comes in 20 percent under its spending budget might look disciplined, or it might mean a hiring plan slipped and the team is now understaffed heading into a busy season, a problem that will show up as a much worse variance three months later. Revenue that beats budget because of one enormous one time order from a single customer is a very different story from revenue that beats budget because the core business accelerated broadly, even though both show up as the same green number on a summary page. Good variance analysis asks why for every large gap, in both directions, not just the ones that look bad.
A favorable variance that nobody investigates is just an unfavorable variance with better timing. The habit of asking why for good news, not just bad news, is what separates variance analysis that actually protects a business from variance analysis that only reacts to it.
A Worked Example
Imagine a regional coffee chain, Overlook Roasters, budgeted 2 million dollars in revenue and 1.5 million dollars in cost of goods sold for the quarter, implying a 25 percent gross margin. Actual results came in at 2.3 million dollars of revenue and 1.85 million dollars of cost of goods sold.
| Metric | Budget | Actual | Variance |
|---|---|---|---|
| Revenue | 2,000,000 | 2,300,000 | up 300,000 (15%) |
| Cost of goods sold | 1,500,000 | 1,850,000 | up 350,000 (23%) |
| Gross margin | 25.0% | 19.6% | down 5.4 pts |
The revenue beat looks great on its own. But margin fell more than five points, so an analyst has to dig in. Suppose the investigation finds unit volume rose in line with the revenue beat, meaning cost of goods sold should have risen roughly 15 percent too, to about 1.725 million dollars, not 1.85 million. The extra 125,000 dollars is a rate variance, bean prices rose faster than budgeted because of a weather related coffee futures spike that quarter. Now the story is precise. The business grew faster than expected, which is good, and input costs rose faster than budgeted, which is a real margin problem worth flagging to leadership, not just a footnote.
How to Present a Variance Without Getting Grilled
The fastest way to lose credibility in a business review is to show a variance number with no explanation and get asked why on the spot. Strong FP&A analysts pre empt the question. The convention most finance teams use is a bridge, a short walk from budget to actual that names each driver and its dollar or percentage impact, ordered from largest to smallest, so the biggest story comes first. Vague language, spend was higher than expected, gets replaced with specific language, freight costs rose because a key lane moved from ocean to air shipping to hit a launch date, which cost 40,000 dollars more but avoided missing the date entirely. The second version answers the question before anyone has to ask it, which is exactly the reputation a good FP&A analyst wants to build inside a company.
The Bottom Line
A budget is a snapshot of assumptions made months in advance, and reality never fully agrees with it. The skill is not predicting the future perfectly, it is explaining the gap fast, correctly, and in one sentence a busy executive can actually use.