Budget vs Actual Reports: How to Read Variance
The gap between budget and actual says little on its own. Sign rules, the percentage trap, price and volume splitting, and where Floemdata stands on budgets today.

At the monthly meeting a table appears: budget, actual, difference. The difference is coloured red or green, and the conversation stops there. But a variance is a result; the table does not answer why. A budget-versus-actual report is useful to the extent that it helps you read the gap correctly and reach the cause.
Write the sign rule first
Variance = actual − budget. For revenue a positive gap is good; for cost a positive gap is bad. With both in one report, colour coding gets muddled. The simple fix: add a favourable / unfavourable column to every row and tie the colour to that column, not to the sign.
The percentage trap
A small amount on a small budget line becomes a large percentage. Fictional example: an overspend of 1,000 on a cost budgeted at 2,000 is a 50% variance; the same 1,000 on sales budgeted at 400,000 is 0.25%. Show both amount and percentage, and define a materiality threshold (for example, highlight when both exceed a set level). Take the threshold from the size the decision-maker cares about, not from the data.
Price and volume: split the gap in two
Sales came in 8,000 above budget, but it is too early for good news. Fictional example: budget is 1,000 units × 100 = 100,000. Actual is 900 units × 120 = 108,000. The gap is +8,000, yet two separate movements sit inside it:
- Price effect = (actual price − budget price) × actual quantity = (120 − 100) × 900 = +18,000
- Volume effect (on revenue) = (actual quantity − budget quantity) × budget price = (900 − 1,000) × 100 = −10,000
The total is still +8,000: +18,000 − 10,000. The company sold less and covered it with price. A one-line difference would not show that. Adding product mix and cost effects widens the breakdown, but even a two-part split changes the question asked at the management meeting.
The budget is data too
- Freeze the version. The budget approved at the start of the year and a forecast revised mid-year are different versions; state which one you compare against.
- Match the dimensions. If the budget is by product group and actuals by product, comparison works only at the shared level.
- Phasing. Splitting an annual budget into twelve equal parts creates false variance in a seasonal business.
- Name the source. Does the actual figure come from a reconciled number? If not, part of the variance is a data difference.
Where Floemdata stands
Floemdata's warehouse processes actual sales, cost, stock and receivables data from SAP Business One. We did not find a table, connector or report in the code that takes in, stores or compares budget data with actuals, and the product documents contain no record that this is on the roadmap (not verified). The method in this article can be used today by keeping your budget in a separate table and tying it to the same dimensions as the actuals, but that is not something the product does.
To begin, pick the largest variance in your last quarterly report and split it into price and volume. Questions are welcome at info@floemdata.com or via Floemdata.