It is the second week of the month, the actuals have closed, and the calendar shows a two-hour block labelled “Monthly Review.” Half the room has not read the pack. The CFO is asking questions that the commentary does not answer. The business unit heads are defending their numbers rather than discussing them. And somewhere in the middle of it all, a perfectly accurate variance report is failing the business that paid for it.

The report is not wrong. The numbers are correct, the comparisons are clean, and every adverse variance has an explanation attached. But explanations are not the same as insights, and insights are not the same as decisions. A variance analysis that tells you what happened without telling you what it means or what follows from it has done half the job at best.

The month-end actuals review is the most regular opportunity the finance function has to shape how a business thinks about its own performance. Most finance teams use it to report on the past. The ones that earn a seat at the strategic table use it to define the conversation about the future.

Why Most Variance Analysis Stops Too Early

The standard variance analysis answers one question: why did actuals differ from budget? That is a necessary question. It is not a sufficient one.

Consider a simple example. Revenue comes in ₹15L below budget for the month. The variance commentary reads: “Revenue was below budget by ₹15L due to lower volumes in the enterprise segment, partially offset by stronger-than-expected performance in SMB.” That is an accurate description of what happened. It tells us nothing about whether the enterprise volume shortfall is a one-month blip or a structural signal, nothing about whether the SMB outperformance is repeatable, and nothing about what the finance team recommends doing next.

The CFO reading that commentary has more data than before and the same number of decisions to make. That is not a useful outcome.

The gap is between explainable variance and actionable variance. Explainable variance closes the loop on history. Actionable variance opens a conversation about the future. Both require the same underlying analysis. Only one requires you to think harder about what the numbers are actually saying.

The Three Layers of a Complete Variance Analysis

A complete variance analysis moves through three distinct layers. Most teams stop at the first. The useful ones do not.

Layer 1: What happened. The quantification and attribution of the variance. How much? Against which baseline? Broken into which components? This is the price-volume-mix bridge, the waterfall chart, the budget-versus-actuals table. It is necessary, precise, and entirely backward-looking. This layer answers: where did the number land and why did it move from where we expected it to be?

Layer 2: Why it happened. The root cause behind the attribution. Volume was down in Enterprise: was that a market-wide contraction, a competitive loss, a delivery issue, or a one-time calendar effect? This layer requires conversation with the business, not just the spreadsheet. It is where the Finance BP earns their credibility because it demands an understanding of the business that a pure accounting function does not have.

Layer 3: What it means. The forward implication. If the Enterprise volume shortfall is structural, what does that do to the full-year forecast? If the SMB outperformance is repeatable, should the budget be revised upward? What decision does this variance analysis prompt, and by whom, and by when? This layer is where variance analysis becomes planning, and it is where most finance teams stop short.

The CFO does not need a report that tells them what happened. They were in the business when it was happening. What they need is a finance team that has processed that information into a point of view about what it means for the decisions they are facing right now.

Building the Price-Volume-Mix Bridge

The price-volume-mix (PVM) analysis is the most powerful tool for Layer 1, and the most commonly misunderstood. I covered the Price and Volume mechanics in detail in Mastering the Revenue Bridge and the Mix component in The Margin Illusion. The full PVM framework including the plug trap is in Price-Volume-Mix Analysis: The FP&A Tool Most Teams Get Wrong. Here I want to focus on how the bridge fits into a complete variance analysis process.

For a revenue variance, the bridge decomposes the total movement into three components:

Price variance: how much was driven by a change in what you charged.

\[\text{Price Variance} = (\text{Actual Price} - \text{Budget Price}) \times \text{Actual Volume}\]

Volume variance: how much was driven by a change in how many you sold.

\[\text{Volume Variance} = (\text{Actual Volume} - \text{Budget Volume}) \times \text{Budget Price}\]

Mix variance: how much was driven by selling a different proportion of high-value versus low-value segments. When you sell more of a lower-ACV segment and less of a higher-ACV segment, total revenue can miss budget even if volume beats. The Mix Variance article covers this in full with SaaS segment numbers.

The same PVM logic applies to an EBITDA variance bridge, moving from budget EBITDA to actual EBITDA through price, volume, mix, cost, and one-off items. One important caveat: if your business operates under Ind AS 116, EBITDA is already distorted by the reclassification of lease expenses into depreciation and interest. A bridge that does not account for this will attribute an accounting-driven EBITDA improvement to operational performance. I covered this trap in The Hidden Debt: Is Your Balance Sheet Ready for Ind AS 116?.

Writing CFO Commentary That Prompts a Decision

The bridge does the analytical work. The commentary does the communication work. They are equally important and rarely given equal attention.

Good CFO variance commentary has a tight structure: one paragraph, three sentences, one decision prompt.

Sentence 1: State the headline variance and attribute it to its primary driver. Quantify both. Sentence 2: Give the root cause and classify the variance as situational or structural. Sentence 3: State the forward implication and name the decision owner and timeline.

Here is what that pattern looks like using the April numbers from the ₹50 Cr ARR SaaS model:

April revenue was ₹7.7L below budget, driven by a two-deal Enterprise volume slip (₹20.0L adverse) partially offset by higher-than-budgeted Enterprise ACV (+₹4.8L) and an SMB volume beat (+₹15.0L) that came at a 50% price concession rate (₹7.5L adverse). The Enterprise shortfall is a pipeline timing issue, not a capacity problem: ACV on closed deals was 8% above plan and the two slipped deals are confirmed in the May pipeline. The SMB discounting rate of 50% against volume gain is above the acceptable threshold and requires the commercial leader to review mid-market pricing policy before Q1 close; unaddressed, it will compress SMB gross margin by approximately 36 basis points in FY27.

Three sentences. The first attributes and quantifies every component of the ₹7.7L miss. The second classifies each driver as situational or structural. The third names the decision, the owner, and the consequence of inaction. A CFO reading this has everything needed to make a call without asking a follow-up question.

The version most finance teams write reads: “Revenue was below budget by ₹7.7L due to lower enterprise closures and SMB discounting.” That sentence is accurate. It is not useful.

The Four Questions Every Commentary Must Answer

Before sending any variance commentary, I run it through four questions.

1. Situational or structural? A situational variance is a one-time event: a delayed deal, an unplanned cost, a calendar timing difference. A structural variance reflects a change in the underlying business: a shift in customer behaviour, a change in competitive dynamics, a cost base that has permanently moved. The CFO needs to know which one they are looking at because the response is entirely different.

2. What is the full-year implication? A ₹15L monthly miss is a different problem depending on whether it reverses in the next month or compounds over the remaining quarters. Commentary should always quantify the full-year impact of leaving the variance unaddressed, even if the answer is “minimal.”

3. Who owns the response? Every actionable variance has an owner. Revenue variance is owned by the commercial team. Cost variance is owned by the relevant function head. If the commentary does not name an owner and a timeline, it has not completed the loop from analysis to action.

4. Has the forecast been updated? If the variance has a full-year implication, the forecast should reflect it. A monthly actuals review that identifies a structural issue without updating the forward view has generated information without integrating it. The most useful finance teams treat the actuals close and the forecast update as one continuous process, not two sequential ones.

Putting It Together: The One-Page Actuals Summary

The most effective format for a monthly actuals review is a single page: the PVM bridge, a three-to-five-line brief summary, a table of key variances with root cause and owner, and the revised full-year forecast range. Everything else goes into an appendix that exists to answer questions, not to fill space.

The one-page constraint is not arbitrary. It forces the prioritisation that is the hardest and most valuable part of the Finance BP role. When you can only say five things, you have to decide which five things matter. That decision is where finance judgement lives. The teams that produce one-page summaries have done more analytical work than the teams that produce forty-slide decks. They have done the extra step of deciding what matters, which is precisely the step that compliance-oriented finance teams most often skip.

Three Habits That Make the Difference

The variance reviews that actually change decisions share three things in common.

They treat the variance analysis as a draft, not a deliverable. The numbers are draft one. The root cause investigation is draft two. The forward implication and decision prompts are the finished product. Most teams stop at draft one.

They have the business conversation before the pack is finalised. Root cause analysis done entirely within the finance team produces financially accurate but operationally incomplete explanations. The best teams talk to the business unit heads before the commentary is written, not after.

They review the forecast at the same time as the actuals. The actuals tell you where you were. The forecast tells you where you are going. Reviewing them together, and updating the forecast in light of the actuals, is what transforms the month-end process from a backward-looking exercise into a forward-looking one.

The Actuals Review Your CFO Actually Wants

The monthly actuals review does not have to be the meeting nobody looks forward to. When it is done well, it is one of the most valuable conversations a finance team facilitates: a structured discussion about what the numbers mean and what to do about them.

Getting there requires moving past Layer 1 and being willing to ask the harder questions. Not just what happened, but why. Not just why, but what it means. Not just what it means, but what we are going to do about it. That is the shift from financial reporting to finance business partnering, and it starts with the way you approach a variance bridge.

The driver-based budgeting article covers how the budget assumptions that feed your variance analysis are constructed in the first place. Understanding how the drivers were built makes it significantly easier to explain why they moved. And if you are thinking about which variances belong in a management dashboard versus a deep-dive pack, the finance dashboard article covers the metric selection question in detail.

I would love to hear how your team approaches the monthly actuals review: what works, what does not, and where the conversation tends to stall. Let’s connect.