A variance is a prompt for investigation, not an explanation. Spending above budget could reflect higher activity, a price increase, a timing difference or an error in the original plan. Begin by defining what the budget assumed and whether actual figures use the same scope and accounting basis. Without that alignment, the comparison can direct attention towards the wrong problem or reward an apparent saving.

Keep the approved budget version and its key assumptions. Map actual accounts to the same categories and reporting periods. Identify missing invoices and estimated accruals before interpreting a difference as operational performance. Where departments use different coding, reconcile the mapping first. Changing classifications after results are known can make a variance disappear without changing the underlying business outcome or improving anyone's understanding of it.

Separate volume, price, mix and timing where those distinctions help. A sales increase may come from more units or from a shift to expensive products with weaker margins. A lower wage bill may reflect vacancies rather than improved productivity. Ask the people responsible for the activity to explain the drivers, supported by records, and distinguish recurring changes from events unlikely to repeat in subsequent periods.

For a hypothetical catering company, ingredient spending exceeds the original budget because additional events were sold. Comparing the actual cost with a budget adjusted for genuine activity helps separate growth from waste or price changes. The revised comparison still needs care: management should not retrospectively alter the standard merely to remove an unfavourable result. Keep the original assumptions visible alongside the operational explanation.

Connect each material variance to a decision. Management may need to review prices, procurement, staffing or the sales forecast. Assign an owner and define what evidence will show whether the action worked. Avoid filling the report with comments such as higher than expected that repeat the numbers without explaining them. Smaller differences can be monitored together when investigation would cost more than the insight offers.

Update the forecast to reflect new information while preserving the original budget as the decision baseline. The two documents serve different purposes. A budget comparison review can improve the mapping, assumptions and commentary, helping the team use deviations as evidence for action rather than as a monthly exercise in defending figures that have already happened and cannot be changed.

Sources