Budget vs actual variance analysis: the monthly method

Quick answer. Budget vs actual variance analysis means comparing each month's actual accounting figures with the locked budget, computing the variance in value and percentage, breaking it down (volume, price, cost), identifying its cause and owner, then deciding corrective actions and updating the reforecast.

Your annual budget is approved, the file is filed away, and nobody reopens it before year-end close. This is the most common pattern we see in SMEs, and it is exactly where the value of financial steering is lost. A budget is only useful when compared, month after month, with what actually happened. This page deals solely with variance tracking: if you are looking to build your annual budget, the construction process is covered separately.

Budget vs actual variance analysis is not a cosmetic reporting exercise. It is the tool that turns a forecast into a decision: hire or wait, chase a supplier, freeze an investment, revise a price. What it requires is a stable, readable, action-oriented monthly method.

A variance, by definition, is the difference between actuals and budget. It is favourable when it improves profit and unfavourable when it erodes it. This simple definition hides a reading difficulty: the direction of a variance depends on the nature of the line, revenue or cost. It is this grammar that the monthly method is designed to discipline.

A budget reviewed once a year only provides reassurance at the start of the period. A variance spotted in March can still be corrected in March; spotted in December, it can no longer be corrected.

Monthly tracking shortens the loop between event and decision. The earlier a variance is detected, the wider the room for manoeuvre.

A monthly cadence also enforces close discipline. To compare, you need clean actuals every month, hence accounting kept up to date, which benefits the whole management process.

There is a threshold effect on team confidence. When tracking is annual, every variance discovered late looks like a bad surprise and feeds distrust. When it is monthly, the variance becomes ordinary management information, discussed calmly, without drama.

Our reading. Across the SMEs we support, the companies that track their variances every month are not those with the most accurate budget. They are the ones that react fastest. Initial accuracy matters less than the review cadence.

The annual budget must be broken down by month. An annual envelope mechanically divided by twelve does not reflect the real seasonality of the business.

Once monthly, the budget becomes a locked reference. All comparisons during the year point to this version, not to a file reworked along the way.

Mixing the initial budget and revised forecasts in the same table is the most common mistake. You then no longer know what you are comparing against.

Monthly breakdown is not just a matter of allocation. It forces you to make explicit assumptions that stayed vague in the annual envelope: which month the sales campaign starts, when the activity peak falls, in which period hires arrive. Set down in black and white, these assumptions also become control points throughout the year.

Actuals must come from the accounting records, once the month is closed, not from bank extracts or side spreadsheets.

The account groupings of the actuals must be strictly identical to those of the budget. A budgeted line with no accounting mirror makes the variance unreadable.

Expense accruals are decisive. Actuals that ignore invoices not yet received or prepaid expenses show an artificial favourable variance that will reverse the following month.

Speed of close drives the usefulness of the analysis. Actuals available on the 5th of the following month leave three weeks to decide; the same actuals delivered on the 25th only serve to record. Shortening the monthly close is therefore a steering investment in its own right, not a mere accounting comfort.

A Pennylane dashboard fed directly by the period's entries limits re-keying and speeds up the availability of actuals at the start of the month.

For each line, the variance in value is the difference actual minus budget. The percentage variance relates this difference to the budget.

The direction of the variance depends on the nature of the line. A variance is favourable if it improves profit, unfavourable if it erodes it.

This point regularly reverses readings: on a revenue line, actuals above budget are favourable; on a cost line, actuals above budget are unfavourable.

The two measures complement each other. Value tells you what the variance weighs in euros on profit; percentage tells you whether it is a trend drift. A variance of small value but high percentage often signals a line that is slipping and deserves watching, even if its amount stays modest for now.

Here is a purely illustrative numerical example, with no regulatory value:

An overall variance does not say what to correct. Breaking it down points to action.

On revenue, the variance splits into a volume effect (quantities sold) and a price effect (the unit price applied). Revenue lagging because volumes are down does not call for the same response as revenue lagging because prices were pushed down.

On a variable cost, the same logic separates the quantity effect from the unit-cost effect. Consuming more material is not the same as paying more for the material.

The breakdown sometimes reveals variances that offset each other. Revenue in line with budget can hide a sharply rising volume and sharply falling prices, two opposite management signals that an overall variance would leave entirely invisible. This is where the breakdown stops being a technical exercise and becomes a commercial decision tool.

Trade-off. Should every variance be broken down? No. The volume-price-cost breakdown takes management time. We reserve it for structural lines (revenue, main purchases, payroll) and leave minor lines to the simple value variance, as long as they stay below the materiality threshold.

A variance commented on without an identified cause is merely an observation. The method requires linking every significant variance to a factual explanation.

The materiality threshold prevents the analysis from drowning. You only comment on variances above a threshold defined in advance, in value or percentage.

Each significant variance is assigned to an operational owner, not just to the finance function. It is this ownership that makes action possible.

The cause must be factual, not a comfort justification. Saying a line overran because activity was strong is an empty phrase; saying an exceptional order triggered an unbudgeted material purchase is a cause, because it tells you whether the variance will recur. The quality of the analysis is decided precisely at this level of precision.

The underestimated risk. The most dangerous variance is not the biggest one, it is the small recurring unfavourable variance. A modest monthly overrun on a cost line, repeated twelve times, often weighs more than a spectacular one-off slip, and it slips below the materiality threshold if that threshold is poorly calibrated.

The analysis does not end with a table, but with a decision. Each significant variance must lead to a dated and, where possible, quantified action.

The reforecast, or revised forecast, updates year-end in the light of observed variances. It absorbs lasting variances without touching the reference budget.

Distinguishing cyclical from structural variances is essential here. A billing delay recoverable next month does not flow into the reforecast; a structural loss of a client does.

The reforecast also brings consistency. Kept each month, it avoids the tunnel effect of a company discovering at year-end a result far removed from its budget without ever having adjusted its trajectory. The revised forecast acts as an interim compass, halfway between the locked budget and the final close.

In practice. Each month we formalise a three-column table: observed variance, documented cause, action and owner. This document fits on one page, can be reviewed in a fifteen-minute meeting, and serves as the thread from one month to the next. Setting up this routine often falls within a mission to set up management control in an SME.

A few methodological principles avoid the most common pitfalls of variance tracking.

• Never change the reference budget during the period: the measurement loses its anchor.
• Compare identical scopes: a chart-of-accounts change mid-year distorts every variance.
• Accrue expenses before concluding: unaccrued actuals lie about the direction of the variance.
• Set the materiality threshold in advance, not afterwards, to avoid commenting only on what suits you.
• Keep a written record of causes: the history of variances is more instructive than any isolated variance.

Variance analysis is an internal management method. It creates no reporting obligation and replaces no tax computation. For tracking tailored to your activity and presentable to your financiers, support through an outsourced CFO for startups and SMEs or building a forecast balance sheet consistent with your reporting are often the right footholds.