Flux & Variance
Flux analysis vs variance analysis: what's the difference?
Flux analysis compares what actually happened in one period to what actually happened in another. Variance analysis is the broader term and often means actual against budget or forecast. In practice the words get used interchangeably — what matters is which comparison you're running.
Flux analysis vs variance analysis comes up constantly in close and FP&A conversations, and both are ways of asking why a number differs from another number. The distinction people draw, when they draw one, is about what it's being compared to.
Flux analysis is actual against actual. This month against last month, this month against the same month last year, year to date against the prior year to date. Both sides of the comparison are things that really happened and are sitting in the ledger.
Variance analysis covers that too, but usually extends to actual against budget or forecast — where one side of the comparison is a number somebody predicted rather than a number that occurred.
Plenty of people use "variance analysis" to mean both, and nobody will correct you. The vocabulary isn't worth arguing about. What the comparison tests is.
The comparison decides what counts as an answer
This is the practical difference, and it's why the distinction is worth keeping straight even though the words are fuzzy.
| Actual vs. actual (flux) | Actual vs. budget | |
|---|---|---|
| What it tests | Whether the ledger reflects what really happened, and what changed in the business | Whether an assumption made earlier held |
| Where the answer lives | In the accounting detail — entries, invoices, subledgers | Often partly with whoever built the budget, not in the ledger at all |
| A good answer names | The business event that drove the movement, quantified and sourced | Which assumption didn't hold — volume, rate, timing, or something unbudgeted |
| When it runs | During close, as the balances are finalized | After close, once actuals are available to compare against the plan |
| Comparison basis | Prior month, prior year same month, or prior year to date | Budget, forecast, or a reforecast |
| Typical owner | Accounting and controllership, as part of close | FP&A, often as part of reporting or a business review |
| Usual purpose | A control — evidence the balances were reviewed and explained | Performance management — explaining results against a plan |
The row that causes the most trouble in practice is the second one. For an actual-to-actual comparison, the reason is somewhere in the accounting records, and finding it is a matter of pulling the right detail. For a budget comparison, the reason may not be in the records at all — the budget assumed something, and understanding what it assumed can mean going to the person who built it.
Why "above budget" isn't an explanation
Budget commentary fails in a specific way. "Coming in above budget" restates the variance rather than explaining it, in the same way "inventory increased $742,500" restates a movement without naming a cause.
A budget variance is the gap between an assumption and an outcome. The explanation that carries information names which assumption didn't hold. That might be volume, pricing, timing, or something that was never in the budget at all — and when the answer genuinely sits with the budget owner rather than in the ledger, saying so is more useful than guessing at it.
Who uses which word
Usage tracks function more than definition.
People in close and controllership tend to say flux, because the actual-to-actual comparison is the one embedded in their control. People in FP&A tend to say variance, because budget and forecast comparisons are the bulk of their work. Auditors often say fluctuation analysis, which is just the long form of flux and shows up in audit programs and workpapers.
Software vendors sometimes draw a harder line between the terms than practitioners do, because it helps distinguish products.
When one package contains both
A reporting package frequently asks for several comparisons at once — month over month, year to date against prior year, and against budget, side by side for the same account.
Which comparison you are running also changes what you pull — income statement and balance sheet accounts need different data even for the same comparison type. Each side has its own walkthrough: income statement flux compares activity, balance sheet flux explains where a balance has accumulated to. The trap is treating all of it as one explanation written three times. A driver that explains this month against last month often says nothing about the year against last year, and neither necessarily says anything about why either differs from budget. They're separate questions that happen to sit in adjacent columns.
This gets harder still when the line being explained is several accounts rolled together, which is common in group reporting.
Does flux analysis vs variance analysis actually matter in practice?
For vocabulary, not much. If someone asks you to run variance analysis and means month over month, they'll say so, or you'll work it out from the file.
For the work, it matters a lot, because it determines where you go looking. Pulling and organizing the general ledger detail is the right first move for an actual-to-actual comparison and can be a waste of an hour for a budget variance whose explanation was never going to be in the ledger.
The useful habit is to check which comparison you're being asked about before you start pulling anything.
If you want to see an actual-to-actual review done end to end, the flux analysis demo runs one on a synthetic company, and this worked example takes a revenue account and a receivables account from data pull to finished commentary. Once your own commentary is written, the commentary test checks whether the drivers actually add up to the movement.
If you work this in Excel: the free flux template flags what needs explaining and shows the residual your drivers don't cover. The CloseOps Flux & Variance System ($79) starts from your trial balance instead: confirm each account's classification and it builds the income statement and balance sheet flux statements, then ranks what to investigate.
Related: what flux analysis is, if you're new to it, month-end flux, start to finish, and why income statement and balance sheet flux need different data.
Found something wrong or missing? Tell me here — anonymous, thirty seconds.