Try it now, capture a real invoice
Free plan · No credit card · Your data stays yours
Budget variance analysis is the process of comparing actual financial results to the budgeted amounts, measuring the gap, and explaining why it happened so you can act on it. A variance is the difference between what you planned to spend or earn and what actually occurred. The analysis turns that raw number into a decision: keep going, investigate, or correct. Controllers run it every month as part of the close so leadership sees where the business is on plan and where it is drifting.
The budget variance formula
The formula is simple:
Variance = Actual - Budget
To express it as a percentage, which makes small and large line items comparable:
Variance % = (Actual - Budget) / Budget x 100
A department budgeted $50,000 for software and spent $58,000. The variance is $8,000, or 16 percent over budget. On its own that number means little. The analysis is deciding whether 16 percent is a timing difference, a price increase, or a control problem worth stopping.
Favorable versus unfavorable variance
Direction matters more than sign. A variance is favorable when it helps profit and unfavorable when it hurts it, and that depends on whether the line is revenue or cost.
| Line type | Actual above budget | Actual below budget |
|---|---|---|
| Revenue | Favorable | Unfavorable |
| Expense | Unfavorable | Favorable |
Spending $8,000 more than budgeted is an unfavorable expense variance. Earning $8,000 more than budgeted is a favorable revenue variance. A favorable cost variance is not automatically good news either: coming in far under a maintenance budget can mean deferred work that returns as a larger bill later.
How to do budget variance analysis, step by step
1. Pull actuals against budget by line
Start with a clean comparison of actual to budget for every GL account or department, for the month and year to date. The year-to-date view catches drift that a single month hides.
2. Calculate the dollar and percent variance
Compute both. The dollar figure tells you materiality; the percentage tells you severity. A 40 percent variance on a $500 line is noise. A 4 percent variance on a $2 million line is real money.
3. Apply a threshold
You cannot investigate every line, so set a rule: flag any variance over, say, $5,000 and 10 percent. Everything above the threshold gets explained; everything below is left alone. This keeps the analysis focused on what changes a decision.
4. Find the root cause
For each flagged item, sort the cause into one of a few buckets: volume (you did more or less activity than planned), price or rate (a vendor raised prices), timing (an expense landed in a different month than budgeted), or a one-off event. The bucket points to the fix.
5. Report and act
Write a short, plain explanation next to each material variance and a recommended action. Leadership does not need the whole schedule; they need the five lines that moved and why.
What causes budget variances
Most variances trace back to a handful of drivers. Volume changes, when sales or production run above or below plan, flow through to variable costs. Price changes on the input side, a supplier increasing rates, drive spending variances even when volume is flat. Timing differences, an annual insurance premium hitting in March instead of the budgeted January, create a variance that reverses later. And forecasting error, an unrealistic budget in the first place, shows up as a variance that repeats every month. Accurate accounts payable forecasting reduces the timing surprises that clutter a variance report.
Where accounts payable feeds the analysis
A large share of the expense side of any budget flows through accounts payable, so the quality of your variance analysis depends on the quality of your AP data. Two things matter. First, expenses have to hit the right GL account and the right period. An invoice coded to the wrong account or accrued in the wrong month creates a variance that is really a coding error, not a business event. Second, you need the detail behind each number. When a line is over budget, the fast answer comes from drilling into the underlying invoices, which vendor, which amounts, which dates. Clean GL coding and complete invoice records turn a three-day variance investigation into a three-minute one.
This is where automating invoice capture and coding pays off for the controller. When every invoice is captured, coded consistently, and accrued in the right period automatically, the actuals in your variance report are trustworthy on day one of the close. Our accounts payable software keeps that data clean, and once the numbers are reliable you can push them straight into board-ready financial statements without re-keying anything.
Budget variance analysis example
A mid-market services firm budgets $120,000 in monthly contractor costs. April actuals come in at $138,000, an unfavorable variance of $18,000, or 15 percent. The controller drills into AP and finds two causes: $12,000 is a March invoice that arrived and was booked in April, a timing difference that will reverse, and $6,000 is a genuine rate increase on a key contractor. The report says exactly that: $12,000 timing, self-correcting, and $6,000 price, permanent, renegotiate at renewal. Leadership now knows only $6,000 of the $18,000 is a real, ongoing problem. That is the entire point of the exercise.
Common mistakes to avoid
Do not analyze every line; thresholds exist so you spend attention where it matters. Do not treat all favorable variances as wins; under-spending on required work is often a deferred cost. Do not stop at the number; a variance report without causes is just arithmetic. And do not ignore timing; a large share of monthly variances are period differences that reverse, and calling them out prevents a false alarm.
Frequently asked questions
What is a good budget variance percentage?
Most finance teams treat variances within 5 to 10 percent of budget as normal and focus on anything larger. The right threshold depends on the size and volatility of the line, but a common rule is to investigate variances that exceed both a dollar floor and a percentage, for example over $5,000 and over 10 percent.
What is the difference between a static and flexible budget variance?
A static budget variance compares actuals to the original fixed budget. A flexible budget variance compares actuals to a budget recalculated at the actual activity level, which strips out the effect of doing more or less volume than planned. The flexible version isolates price and efficiency differences from pure volume effects.
How often should you run budget variance analysis?
Monthly, as part of the close, is standard so problems surface while there is still time to act. High-spend or fast-moving areas may warrant a weekly look. The cadence should match how quickly you can actually change the outcome.