You built a budget in December. It felt thorough — you thought about seasonality, padded a few line items, ran it past your accountant. Then March happened. Payroll came in higher than planned, a big customer paid net-60 instead of net-30, and marketing spend that was supposed to be $4,000 turned into $9,000 because a campaign "just needed a bit more" to hit its numbers.
If you never go back and compare what actually happened to what you planned, none of that is a lesson — it's just noise that repeats itself every quarter. Budget vs. actual (BvA) variance analysis is the discipline of closing that loop: taking the budget you committed to and the real numbers your books produced, lining them up side by side, and asking why they don't match.
Done well, it's one of the highest-leverage habits a small business owner can build. Done sloppily — or not at all — a budget is just a document you made once and never looked at again.
What Variance Analysis Actually Is
At its core, budget vs. actual analysis is simple arithmetic:
Variance = Actual − Budget
For revenue lines, a positive variance (actual exceeds budget) is favorable. For expense lines, a positive variance (you spent more than planned) is unfavorable. It's easy to get this backwards, so a useful mental shortcut: favorable always means "better for profit than you expected," whether that's more revenue or less cost.
| Line item | Budget | Actual | Variance | Favorable / Unfavorable |
|---|---|---|---|---|
| Revenue | $120,000 | $109,000 | -$11,000 | Unfavorable |
| Cost of goods sold | $48,000 | $43,000 | -$5,000 | Favorable |
| Payroll | $35,000 | $39,500 | +$4,500 | Unfavorable |
| Marketing | $4,000 | $9,000 | +$5,000 | Unfavorable |
| Net income | $18,000 | $6,800 | -$11,200 | Unfavorable |
That table alone tells you more than a P&L in isolation ever could. Revenue missed by 9% — is that a demand problem or a timing problem? Payroll ran hot — planned headcount, overtime, or a new hire that wasn't in the plan? Marketing doubled — was that a deliberate decision mid-quarter, or scope creep nobody flagged?
The Two Traps That Make Variance Analysis Useless
Trap 1: Only looking at dollar variances. A $5,000 miss on a $10,000 budget line is a crisis. A $5,000 miss on a $500,000 revenue line might be rounding error. Always look at variance as both a dollar amount and a percentage — percentage tells you the magnitude, dollars tell you whether it's worth anyone's time to investigate.
Trap 2: Treating every variance as a problem. Variances aren't inherently good or bad — they're information. A big favorable revenue variance sounds like good news, until you realize it came from pulling forward next quarter's orders, which means next quarter's budget is now unrealistic. The point of the exercise isn't to hit every line exactly on budget; it's to understand why the number moved and decide whether that reason should change your plan going forward.
A Repeatable Monthly Process
The businesses that get value from budget vs. actual analysis don't do it as a one-off panic exercise before a bank meeting — they run it on a fixed monthly cadence, using the same five steps every time:
- Close the books first. Variance analysis is only as good as the actuals feeding it. Run it before your bank reconciliation is done and you're comparing a plan to guesses.
- Pull budget and actual side by side, at the same level of detail — comparing a summarized budget to a granular actual (or vice versa) makes real variances invisible.
- Calculate variance in both dollars and percentage for every line, then sort by dollar impact to find what actually matters.
- Flag the lines that cross a threshold — a common rule of thumb is anything over 10% and over a fixed dollar amount (say, $1,000–$2,000 for a small business), so a rounding difference on a tiny line doesn't eat your review time.
- Write down the "why," not just the "what." A spreadsheet that says "Marketing: +$5,000 unfavorable" is not an explanation. "Marketing: +$5,000 — approved a mid-month ad spend increase to chase a Q2 lead-gen target" is a decision you can defend, learn from, and either repeat or avoid.
That fifth step is the one most businesses skip, and it's the one that actually makes the habit valuable. The number tells you that something happened. Only a human explanation tells you whether it should happen again.
Recurring Variances Are the Real Signal
A single month's variance might be noise — a late invoice, a one-time repair bill, a customer who paid early. What deserves real attention is a variance that shows up the same direction, multiple months in a row. That's not bad luck; it's a sign the original budget assumption was wrong.
If payroll runs 8% over budget every single month, the problem isn't March — it's that the budget was built on a headcount or overtime assumption that never matched reality. The fix isn't to keep "explaining" the same variance quarter after quarter; it's to reforecast the line so the budget reflects what's actually happening, and use the freed-up analysis time to look for the next real anomaly instead of the same old one.
Make It a Conversation, Not Just a Report
If you have managers or department heads, the monthly variance review works best as a short, structured conversation rather than an email with a spreadsheet attached. A few questions turn a numbers exercise into a planning tool:
- What drove this variance — something we controlled, or something that happened to us?
- If we could redo last month, what would we do differently?
- Does this change what we should expect for next month, or was it a one-time event?
Keeping the review to the handful of line items that crossed your threshold (not all 40 rows of the P&L) keeps these conversations short enough to actually happen every month instead of getting skipped when things get busy.
Why This Depends on Clean Books
None of this works if your actuals are unreliable. If transactions are miscategorized, if you're not closing the books consistently, or if you're pulling "actuals" from a bank balance instead of an accrual-based P&L, your variance analysis will chase phantom problems and miss real ones.
This is where the mechanics of your bookkeeping system matter as much as the budgeting spreadsheet. Plain-text, version-controlled accounting makes it straightforward to pull a clean, consistent P&L for any period and diff it against a prior plan — the same rigor you'd expect from comparing two versions of a code file, applied to your finances.
Keep Your Numbers Ready for the Comparison That Matters
A budget is only useful if you actually check it against what happened — and that check is only useful if your books are accurate enough to trust. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data, so pulling a reliable actual-vs-budget comparison is a query, not a reconstruction project. Get started for free and see why developers and finance professionals are switching to plain-text accounting.