Virtual CFO Services
Budget vs Actual Analysis: How to Track Variance and Explain It to Your Board
Lekha Editorial Team
CA-reviewed · Published
Budget vs actual analysis is the most basic financial control discipline — comparing what you planned to what actually happened. Done well, it's an early warning system for emerging problems and an accountability mechanism for management. Done poorly (or not at all), it means the annual budget is a document that's opened twice: when it's created and when it's compared to actual results at year end.
Setting Up the Variance Analysis
The variance analysis compares actual monthly results to the budget for the same month (and cumulatively for the year-to-date).
The standard report: a table with columns for Actual (this month), Budget (this month), Variance (₹ difference), Variance (% difference), Actual (YTD), Budget (YTD), Variance (YTD ₹), Variance (YTD %).
Rows: Revenue (total, and by segment if meaningful), each major cost category (salaries, rent, marketing, software, professional fees, etc.), Gross Profit, EBITDA, and Cash.
Materiality threshold: only explain variances above a defined threshold. Common thresholds: variances above 10% of budget AND above ₹1 lakh in absolute value. This filters out rounding differences and small items while highlighting meaningful deviations.
Monthly cadence: the variance report should be produced within 5 business days of month end — before the management review meeting (and well before the board meeting). If you're producing the variance report 3 weeks after month end, the information is stale and the opportunity to course-correct has narrowed.
Root Cause Analysis: Beyond the Numbers
The numbers tell you what happened; root cause analysis tells you why. The board needs the why to make decisions about whether to respond and how.
Revenue variance framework: Volume variance: did we have more or fewer customers / transactions than planned? Price variance: did we charge more or less per unit than planned? Mix variance: did we sell more of the higher-margin or lower-margin products than planned?
For a SaaS company with ₹5 lakh revenue shortfall: 'Revenue was ₹20 lakh vs ₹25 lakh budget. The shortfall was entirely volume-driven — we acquired 8 new customers vs the planned 12. ARPU was ₹2,500/month vs the plan of ₹2,500/month (no price variance). The 4 customer gap was because 2 deals slipped from October to November (both now signed) and 2 deals were lost to a competitor.'
Cost variance framework: Headcount variance: are actual salaries different from planned because of timing of hires, below-plan hiring, or above-plan compensation? Activity variance: did spending on a category (e.g., marketing) happen at a different rate than planned because of timing or a strategic decision? Efficiency variance: did you spend more or less per unit of activity than planned?
Presenting Variances to the Board
The board has limited time and should not be reading through every variance. Present variances in order of materiality, with clear language about cause and forward implication.
Format that works: three columns — Item, Amount/%, Explanation.
Revenue — ₹5 lakh unfavourable (20% miss): 4 new customers vs 12 planned. 2 deals signed in October, after month end. 2 lost to competitor (see strategy section for response).
Marketing — ₹3 lakh favourable (25% underspend): planned Q4 campaign deferred to Q1 following decision to change creative agency. New budget impact in Q1.
Salaries — ₹2 lakh favourable (8% underspend): 2 planned Q3 hires (CTO and Senior Engineer) not started until Q4. Full-year impact visible in H2 budget revision.
Board members want three things from variance analysis: to understand what happened, to understand the management team's awareness of the situation, and to know if any board action is required. Format the presentation to answer all three in the shortest possible time.
Key takeaway
Budget vs actual analysis is the most basic CFO discipline, and it's often the most neglected. A monthly variance report produced within 5 days of month close, with clear root cause explanations, is worth more to a startup's financial management than most expensive tools or processes. Do the simple things consistently.
Frequently asked questions
How often should the budget be revised during the year?
Most companies do one formal budget revision mid-year (typically after Q1 or Q2 actuals) when there's enough data to update the assumptions. A company that materially outperforms or underperforms budget in the first half needs a revised H2 plan — otherwise, you're tracking variance against a number that everyone knows is wrong. Some companies do quarterly reforecasts. Avoid too-frequent revisions (monthly) because they reduce accountability — if the budget is always being revised, there's no fixed target to be held to.
Is it better to have a conservative or ambitious budget?
Neither extreme is ideal. A consistently conservative budget (always easily beaten) fails to challenge the team and doesn't create urgency for performance. A consistently ambitious budget (always missed by 30%) trains the organisation to ignore budget targets as meaningless. The target: a budget where actual performance falls within 10–15% of plan 75–80% of the time. Some months will be above (good news) and some below (requiring explanation) — that's the right range of variance that makes budget tracking a useful discipline.
Should the board-facing budget variance report show absolute numbers or percentages?
Both, always. Absolute numbers (₹5 lakh variance) give the board a sense of scale. Percentages (20% miss) give the board a sense of significance relative to the budget. A ₹5 lakh miss on a ₹25 lakh plan is 20% — significant. A ₹5 lakh miss on a ₹2 crore plan is 2.5% — within normal noise. Without both numbers, the board member has to calculate the percentage themselves — avoidable friction.
How should a startup handle a budget that was set unrealistically high?
Acknowledge it explicitly in the board reporting. 'The revenue budget for H1 was set at ₹3 crore based on assumptions that have proved too optimistic for the current market environment. Actuals were ₹2.1 crore. We are revising the H2 plan to reflect the corrected acquisition assumptions.' Continuing to report against an impossible budget without acknowledging the unrealism is a governance failure. Boards prefer a frank mid-year budget revision over monthly 30% misses with optimistic explanations.
What is a rolling forecast and how is it different from an annual budget?
A rolling forecast is updated continuously — typically monthly or quarterly — to always show the next 12 months of expected performance. Unlike an annual budget (which is fixed at year start and compared against throughout the year), a rolling forecast is always current. The combination of both is most powerful: the annual budget provides the accountability benchmark; the rolling forecast provides the latest best estimate of where you're going. Rolling forecasts are particularly useful for companies with highly uncertain revenue trajectories where a fixed annual budget is stale within 2–3 months.