Budgets · July 7, 2026

Budget vs actual: how to catch variance in real time

Budget vs actual analysis compares what you planned to spend against what you actually spent, line by line, and expresses the difference as a variance in dollars and percent. The formula is simple. The problem is timing: most teams run it weeks after the money left. Here is the method, a worked example, and how to move it to real time.

The variance formula

For a cost line, variance is usually written so that overspending shows as a positive number you need to explain:

Variance ($) = Actual spend − Budgeted spend
Variance (%) = Variance ($) ÷ Budgeted spend × 100

A cost line that comes in under budget is a favorable variance (you spent less than planned); over budget is an unfavorable variance. Be careful with the labels, though. A favorable variance on ads might mean the campaign never launched; a favorable variance on hiring means the roles are unfilled. Variance tells you where reality diverged from the plan. It does not tell you whether that divergence is good news. That still takes a human who knows the context.

A worked example

A 60-person software company, one month of operating spend, five categories:

Swipe the table sideways to compare all columns.

Notice how the total hides the story. A 9.6 percent overall miss sounds manageable; the 48.8 percent travel blowout inside it is the actual problem. Variance review always works at the category or team level first, and only then rolls up.

The usual causes behind an unfavorable variance

Before treating a variance as a discipline problem, check the boring explanations. In practice most unfavorable spend variances trace back to one of five causes:

• Timing. An annual renewal or a prepaid contract landed this month; the year is fine, the month looks terrible. Fix the budget phasing, not the spend.
• Unbudgeted but legitimate spend. The conference, the emergency hardware, the legal invoice. The process failure is that nobody raised it before the money moved.
• Price creep. The same vendors, the same usage, higher unit prices. Subscriptions are the classic case, and nobody notices because the merchant name never changes.
• Volume growth. Usage-based tools and headcount-linked costs rising faster than the plan assumed. This is a forecasting miss, not a spending one.
• Genuine overspend. Someone bought something they should not have, or more of it than agreed. The smallest bucket by count, and the one variance review exists to catch.

The reason to separate these is that each gets a different fix: rephase, pre-approve, renegotiate, reforecast, or have the awkward conversation. A variance number without a cause attached is a fact, not a finding.

Why month-end review is too late

The table above is honest and useful, and in most companies it arrives somewhere between the 10th and the 20th of the following month, after close. By then the travel overspend is seven weeks old at the far edge: the conference was booked, attended, and expensed before anyone with budget authority saw a number. Nothing in the review can change the outcome; it can only explain it. That is the structural weakness of month-end variance analysis: it is a post-mortem dressed up as a control.

A variance report explains the overspend. An alert prevents the next one.

Thresholds: warn at 80, act at 100

Real-time variance tracking replaces "how far over did we end up?" with "how close to the line are we right now?". The widely used convention is two thresholds per budget line:

• 80 percent of budget: a warning to the budget owner. There is still room to slow down, defer a purchase, or consciously accept the overage.
• 100 percent of budget: a breach notification to the budget owner and finance. Every subsequent charge in that category is a known exception, not a surprise.

Pace matters as much as level: 80 percent consumed on day 25 is fine, on day 9 it is not. Good real-time tracking reads the threshold against the day of the month, so a fast burn early in the period warns sooner.

How real-time tracking changes the cadence

Moving from monthly to continuous does not mean staring at dashboards all day. It means alerts carry the urgent work and the calendar carries the reflective work:

Swipe the table sideways to compare all columns.

The monthly meeting still exists, but its character changes: nothing in the variance table is news anymore, because every breach already triggered a conversation when it happened. The meeting becomes about fixing budgets, not discovering overspend.

Getting there with the accounts you already have

The ingredients are unglamorous: budgets defined per category and team, a live feed of card and account transactions, and real-time expense tracking that maps each charge to its budget line as it posts. That is precisely the layer spend management software built around alerts provides, without moving your banking or card program. If your card limits and your budgets should agree with each other, our corporate card policy template shows how to line the two up, and recurring charges, the quietest source of unfavorable variance, get their own treatment in our subscription audit walkthrough.