Guide

How to explain a budget vs actual variance: a field guide for FP&A

A step-by-step method for finding why a number moved, tracing it to source, writing commentary that holds up, and presenting it to the board.

Eddie Ningombam Updated Nov 2026

The short answer. To explain a budget vs actual variance: confirm the number is real, break it into drivers (price, volume, mix, timing, one-time items, FX), trace each driver to the source transactions, classify it as timing, one-time or structural, and state what it means for the forecast and who owns it. Lead with the conclusion, focus on material items, and keep the evidence one click away.

Why explaining a variance takes so long

Finding a variance is easy. Every planning tool and dashboard will show you that software spend is 12% over budget. Explaining it is the hard part, because the answer is spread across systems: the ledger has the total, the AP system has the invoices, the contract has the renewal date, and the person who approved it has the context.

One finance lead we work with spent two to three hours explaining a single $10,000 gap. That is normal, not careless. Most of the time goes into verifying and tracing, not calculating. The method below is designed to shorten exactly that part.

The example used in this guide (illustrative)

A Series B SaaS company closes Q3 with operating expenses $87,000 (1.5%) over budget across five cost centers. The largest, CC001, is $27,000 over. We will explain that $27,000 step by step.

Step 1: Is the variance real?

Before explaining a variance, rule out the ones that are not there. A surprising share of variances are bookkeeping effects, not business events.

False varianceWhat happenedHow to check
CutoffAn invoice landed in the wrong periodCompare invoice dates with posting dates around period end
Accrual and reversalAn accrual was booked but its reversal was not, or the reverseLook for matching entries in the next period
MappingA cost was coded to the wrong account or cost centerCheck reclasses and new vendors without a default mapping
Budget phasingThe budget was spread evenly but the spend is lumpy by designCompare against the phasing assumption, not just the total
FXThe budget used one rate, actuals anotherRestate actuals at the budget rate to isolate the currency effect

In the example: no cutoff or mapping issues. The full $27,000 is real spend in the quarter.

Step 2: Which variances deserve an explanation?

Set a materiality threshold so the team spends time where it matters. A common approach combines a percentage and a dollar floor, for example "over 5% and over $15,000", so that a 40% swing on a tiny line and a 1% swing on a huge line are both handled sensibly. Pick thresholds with your CFO once and keep them stable, so the board sees a consistent standard.

Group everything under the threshold into "other" with a single line of commentary.

Step 3: Break the variance into drivers

Every variance is some combination of a small number of drivers. Naming them is what turns "we were over" into an explanation.

DriverQuestion it answersExample
Price or rateDid we pay more per unit?Vendor price increase, higher contractor rate
VolumeDid we buy or sell more units?More seats, more usage, more hires
MixDid the blend change?More enterprise deals at a lower discount
TimingDid it happen earlier or later than planned?Annual renewal billed a quarter early
One-timeWill it repeat?Offsite, legal settlement, migration project
FXDid exchange rates move?Overseas payroll paid in a stronger currency

For lines driven by quantity and price, split the variance with the standard formula:

  • Volume effect = (actual units minus budget units) multiplied by the budget price
  • Price effect = (actual price minus budget price) multiplied by the actual units

The two add up to the total variance. If they do not, there is a mix or data issue to find.

Step 4: Trace each driver to the source transactions

An explanation is only as good as its evidence. Go from the reported number to the account, from the account to the subledger or system of record, and from there to the individual transactions.

LineWhere the answer usually is
RevenueBilling system and CRM: new deals, expansions, churn, credits, recognition schedule
PayrollHRIS and payroll: hires, start dates, raises, bonuses, contractors, FX
Software and servicesAP invoices and contracts: renewals, price changes, new vendors
Cloud and usage costsProvider usage reports: volume, rate cards, committed spend
Travel and eventsExpense system: dates, attendees, one-off events

In the example, the $27,000 on CC001 traces to three source rows:

GL accountSourceAmountDriver
6100 ContractorsInvoice INV-4471, extended contractor engagement+$14,200Volume
6420 SoftwareAnnual renewal billed in Q3, budgeted in Q4+$8,900Timing
6150 TravelTeam offsite, Sep 18+$3,900One-time

Each line now has a number, a source and a driver. That is the evidence the commentary will rest on.

Step 5: Classify it: timing, one-time or structural

The classification decides what happens to the forecast, which is what leadership actually cares about.

ClassTestForecast action
TimingWill it reverse in a later period?No change to the full-year number; re-phase the quarters
One-timeWill it not repeat, and not reverse?Absorb it in the year; no change to the run rate
StructuralHas the underlying run rate changed?Update the forecast going forward

Seasonal patterns are a special case: they repeat with the calendar and should already be in the budget phasing. For the full test, see Structural vs. Seasonal Variance.

In the example: the software renewal is timing (Q4 will come in $8,900 under). The offsite is one-time. The contractor extension is the open question: if the engagement continues, it is structural and the forecast needs to move.

Step 6: Write variance commentary that holds up

Good commentary answers four things in two or three sentences: what moved, why, whether it repeats, and what happens next. Use this structure:

Commentary template

[Line] was [amount, %] [over/under] budget, driven by [driver and source]. This is [timing / one-time / structural]. [Forecast impact]. [Owner and next step].

Weak commentaryStrong commentary
"CC001 was over budget due to higher costs. We are monitoring.""CC001 was $27K (9%) over budget. $14.2K is a contractor extension (INV-4471), $8.9K is an annual software renewal billed a quarter early, and $3.9K is the September offsite. The renewal reverses in Q4 and the offsite will not repeat. If the contractor engagement continues, Q4 opex rises by about $14K; the CC001 owner confirms by Oct 15."

Rules that keep commentary useful: lead with the number, name the driver not the account, separate facts from judgment, give one forecast implication, and name an owner with a date. Avoid "due to timing" without saying what is timing and when it reverses. For more examples and a review checklist, see How to write variance commentary.

Step 7: Present it to the board

Boards want to know three things: is the plan still achievable, did anything change in the business, and what are you doing about it. Structure the variance section to match:

  1. Headline: the net variance against plan in one sentence, and whether it changes the full-year view or runway.
  2. Material items only: the few variances above threshold, each with its driver and class.
  3. Timing vs. permanent: show what self-corrects next quarter separately from what changes the run rate.
  4. Forecast impact: the updated full-year number and the assumption that moved it.
  5. Decisions or asks: anything the board needs to approve or weigh in on.

The question that catches teams out is the follow-up: "how do you know?" Keeping the source evidence from Step 4 attached to each line is what lets you answer it in the room rather than in an email the next day.

Special case: why billing revenue does not match the general ledger

This is one of the most common variance questions, and the answer is usually that the two systems measure different things at different times. There are seven usual causes:

CauseWhat you see
Recognition timingBilling shows the invoice; the ledger recognizes revenue over the service period, with the rest in deferred revenue
Accruals and reversalsThe ledger carries estimates for delivered but unbilled work that reverse when the invoice is issued
Credits, refunds and write-offsAdjustments made in one system and not yet reflected in the other
CutoffInvoices dated at period end land on different sides of the close in each system
FXBilling in the customer's currency, ledger in the entity's functional currency at a different rate
Multiple entitiesA customer billed by one entity with revenue recorded in another, or intercompany entries not eliminated
Usage billed in arrearsOverage or usage invoiced after the period in which the usage happened

The fix is a documented mapping: how each billing record becomes ledger entries, by type. Once it is written down and versioned, the reconciliation stops depending on one person. That mapping is part of a finance ontology. For the full reconciliation, see Why billing revenue doesn't match the general ledger.

Keep the explanation, not just the number

The most expensive part of variance work is doing it twice. When a variance is resolved, record the driver, the source rows, the classification, the owner and the decision next to the number. Next quarter, when the same line moves, the team starts from the last answer instead of from scratch. Over a year, this is what shortens decision latency: the time from a number moving to a decision being made.

Checklist

  • The variance is real: cutoff, accruals, mapping, phasing and FX ruled out
  • It is above the materiality threshold
  • It is split into named drivers that add up to the total
  • Each driver is traced to source transactions
  • It is classified as timing, one-time or structural
  • The commentary states the forecast impact, the owner and a date
  • The evidence and the decision are recorded for next time

Frequently asked questions

What is an acceptable budget variance percentage?

There is no universal number. Many teams investigate anything over 5% to 10% of the line, combined with a dollar floor so that small lines do not create noise. The right threshold is the one your CFO and board agree on and apply consistently.

Do favorable variances need explaining too?

Yes. A favorable variance is often timing (spend that will still happen) or an early sign of a structural change. Treat it with the same steps; boards ask "is it real?" about good news too.

What if I cannot trace a variance before the meeting?

Say what you know, what you do not, and when you will know. "Two thirds of the variance is traced to a renewal billed early; the remaining $9K is under review with AP and will be confirmed by Friday" is a credible answer. Guessing is not.

How often should variance analysis be done?

Monthly after close at minimum, with a quarterly view for the board. Teams with a rolling forecast also re-check material lines whenever the forecast is updated.

E
Eddie Ningombam
Founder, PhrasIQ

Building InSightOS, the decision infrastructure layer for enterprise FP&A teams. Previously in finance operations and data infrastructure. Writing about decision latency, financial reasoning, and what it takes for FP&A to own the strategy conversation.

Get new articles in your inbox
FP&A strategy, variance analysis, and decision infrastructure. No noise.
✓ You're subscribed. First issue incoming.