Flux & Variance

Income statement flux and balance sheet flux need different data

A month of income statement detail is the balance. A month of balance sheet detail is already the movement. Everything else about how you pull the data follows from that.

	Income statement	Balance sheet
Why the pull differs	Resets to zero each period — a month of detail is just that month's activity	Carries forward — the balance already includes everything before it
What to pull, month over month	Both periods, pivoted with date as the column field	Current period only — that's already the change since last period
What to pull, vs. a fixed anchor	Not typical — IS accounts don't accumulate across periods this way	The full span from the anchor (often prior year-end) through now
What the variance asks	How much activity happened, and why	Whether the resulting balance is where it should be
Seasonality shows up as	Activity concentrated in certain periods	Balance size — a build ahead of a busy period, a reserve sized to what it provisions against

Income statement accounts reset at the start of each period. Balance sheet accounts carry forward. That's taught in the first week of any accounting course and then mostly forgotten as a practical matter — but it decides what you have to pull before you can explain anything.

For an income statement account, one month of detail gives you the balance. You need two to see a change. For a balance sheet account, one month of detail is the change — the balance is everything that came before it.

Income statement flux analysis: pull both periods, pivot on date

Because the account resets, a single month's activity is that month's balance. To compare July against August you need both months of activity in front of you.

The workable way to do that is one pull covering both periods, pivoted with the date as the column field. You get July and August as adjacent columns against whatever row dimension the account is organized around, and the movement is visible by category rather than as a single net number you then have to go decompose.

Pulling the two months separately and comparing them by eye works, but it's slower and it makes categories that appear in one month and not the other easy to miss — which are often the interesting ones.

Balance sheet flux analysis, month over month: pull the current month only

This is the part that catches people, and it's the more useful half of the distinction.

Because a balance sheet account carries, the current month's activity is the movement since the prior month end. If you want to explain what happened to a balance between 7/31 and 8/31, you run August's detail. That's it. The prior month isn't needed, because its effect is already sitting in the opening balance.

That's a meaningfully smaller pull than the income statement equivalent, and treating a balance sheet account like an income statement account — pulling two months to compare them — produces a larger dataset that answers a question nobody asked.

Balance sheet, against a fixed prior point: pull the whole span

When the comparison isn't month over month — against the prior fiscal year-end, most commonly — the same logic scales. The movement you're explaining is everything that happened between that anchor and now, so the pull runs from the anchor through the current month end.

That's a much bigger dataset than a single month, and it's the case where a category-level pivot stops being a convenience and becomes necessary. Reading several months of accumulated detail line by line isn't a realistic way to find what drove the balance.

What you're actually assessing differs too

The mechanical difference has a judgment counterpart.

An income statement variance is usually a question about activity in a period: how much was earned or spent, and what business event accounts for it being different from the comparison period. The explanation points at something that happened.

A balance sheet variance is usually a question about where a balance has accumulated to: whether an asset or liability sits at a defensible level given what the business has been doing. The explanation often points at a pattern over time rather than a single event — a build-up, a drawdown, a timing gap between when something is accrued and when it settles.

This is why the same phrase can be adequate commentary on one statement and useless on the other. "Higher activity in the period" is at least the right shape of answer for an expense account. For a balance that has been climbing for four months, it explains nothing about why the balance is where it is.

Seasonality shows up in both, differently

Seasonality gets treated as an income statement concept — revenue concentrated in certain quarters, spend that follows it. That's real, but balance sheet accounts carry seasonal patterns too, and they show up as the size of a balance rather than as activity in a period.

An inventory balance built ahead of a busy period. A reserve that is legitimately larger at one point in the year than another because of what it's provisioning against. A payable that accumulates and then clears when settlement happens.

None of those are errors, and all of them look like unexplained movement if the comparison period sits on the other side of the pattern. Knowing which of your balance sheet accounts have a seasonal shape is most of what separates a fast review from a slow one — and it's specific enough to each business that it mostly has to be learned rather than looked up.

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.

Found something wrong or missing? Tell me here — anonymous, thirty seconds.