Finance can explain every number. Management still doesn’t know what to do.
The finance department has solved the mystery.
Revenue missed budget by $1.2 million, and after three days of analysis, two meetings, and a spreadsheet that now requires its own security clearance, the explanation is ready.
Sales were lower than expected.
Excellent detective work.
The CFO has questions.
“Why were sales lower?”
“Customer demand softened.”
“Why?”
“We’re investigating.”
“Didn’t we investigate that last month?”
“Yes.”
“And?”
“Demand was also soft.”
Welcome to the monthly variance review, where everyone learns that last month’s problem has successfully survived another month.
The numbers are accurate. The commentary is polished. The waterfall chart is beautiful.
Unfortunately, nobody has made a decision.
The Problem Isn’t the Variance. It’s What Happens Next.
Budget variance analysis is supposed to help management understand what changed and what to do about it.
Somewhere along the way, many finance departments became exceptionally good at the first part.
Revenue is below budget because volume declined. Payroll is above budget because overtime increased. Marketing is under budget because campaigns were delayed.
All perfectly reasonable explanations.
But they leave out the questions that matter.
Why did volume decline? What’s causing the overtime? Will delaying marketing affect future sales?
And perhaps most importantly, what happens financially if management does nothing?
That’s where variance analysis starts becoming useful.
The $300,000 Savings That Cost $900,000
Consider a hypothetical manufacturing company.
Its monthly financial report shows a $300,000 favorable labor variance.
Management is pleased. The operations department has apparently discovered the secret to controlling payroll.
Except there’s a problem.
The company achieved those savings by leaving several production positions vacant.
With fewer employees, production capacity fell. Orders were delayed, and some customers purchased elsewhere.
Finance investigates and discovers that the staffing shortage prevented the company from fulfilling $1.5 million in orders.
At a 60% contribution margin, those lost sales represent $900,000 in forgone contribution.
Here’s what the financial picture looks like:
| Financial impact | Amount |
|---|---|
| Labor expense savings | +$300,000 |
| Lost contribution from unfilled orders | −$900,000 |
| Net operating impact | −$600,000 |
Illustrative figures; assumes the lost orders would otherwise have been fulfilled and earned the stated contribution margin.
The department beat its labor budget by $300,000.
The business is potentially $600,000 worse off.
The expense variance is favorable. The economics are not.
And if finance only reports the labor savings, management might congratulate the person responsible.
Possibly with a bonus.
Stop Investigating the Biggest Number
Another common mistake is treating the largest variance as the most important one.
Imagine three issues appearing in the same monthly report:
- Insurance expense is $200,000 above budget because premiums increased.
- Customer churn has reduced monthly recurring revenue by $75,000.
- Maintenance expense is $150,000 below budget because critical work was postponed.
The insurance variance gets the most attention because it’s the largest unfavorable number.
But the premium may already be contractually fixed. Finance needs to update the forecast, and management can revisit coverage at renewal.
Meanwhile, the lost recurring revenue could represent $900,000 in annualized revenue exposure if those customers aren’t replaced.
And the deferred maintenance could create a much larger problem if equipment fails.
The biggest variance isn’t necessarily the biggest risk.
Financial materiality should consider what happens next, not simply what happened last month.
That’s a different way to prioritize the conversation.
Sometimes the Budget Is the Problem
There’s another possibility that finance teams are occasionally reluctant to discuss.
The budget was wrong.
A company builds its annual plan assuming 12% revenue growth. Three months later, market demand has weakened, competitors have reduced prices, and customers are delaying purchases.
The latest forecast suggests 4% growth.
Leadership doesn’t want to change the budget because the company is still committed to achieving 12%.
Fair enough. Keep the target.
But insisting that the forecast also show 12% doesn’t make the business more ambitious.
It makes the forecast less useful.
The budget records what management approved. The forecast reflects what the company currently expects. The target represents what leadership wants to achieve.
They serve different purposes.
When those numbers disagree, finance should explain the gap and identify the decisions needed to close it.
Forcing them to match is an excellent way to produce a reassuring spreadsheet.
It’s a less effective way to run a business.
What a Useful Variance Report Actually Looks Like
A good variance report should make it difficult for management to leave without understanding the financial consequences.
Instead of:
“Revenue unfavorable due to lower sales volume.”
Try:
“Revenue is $420,000 below plan because Product A orders declined 18%. Customer interviews indicate delivery delays are driving cancellations. Restoring production capacity could recover an estimated $250,000 in monthly sales, subject to demand confirmation. Operations is evaluating the required investment.”
Now there’s something to discuss.
Is the capacity investment justified? How quickly could sales recover? What happens if the company waits another quarter?
Finance doesn’t need to make every operating decision.
It should make the economics of those decisions visible.
And when management chooses not to act, the forecast should reflect that choice.
Doing nothing is still a decision. It just rarely comes with a slide explaining the cost.
The Question Every CFO Should Ask
At the end of the next budget variance review, ask one question:
“What decision are we making differently because of this analysis?”
If the answer is clear, the process is doing its job.
If nobody can answer, the company may have spent another month documenting problems it already knew existed.
The spreadsheet isn’t the problem.
It did exactly what everyone asked.
Perhaps it’s time to ask something better.