Flux & Variance
Month-end flux: what it is and how to run it
This period against the last one, account by account: the steps to run it in one close, and what makes the commentary hold up. Four of the five tests that decide whether commentary survives review are arithmetic. One still needs a person.
Month-end flux analysis compares each account's current-period balance against a prior actual period — last month, the same month last year, or year to date — and explains what the movement says about the business. It is actual against actual, which is what separates it from a budget comparison.
How to run it in one close
- Pull both periods and tie them out. Current and prior balances for every account, from the same source. Before explaining anything, check the export is complete: opening plus activity equals closing, account by account. How to check the export.
- Apply thresholds you set before you looked. A dollar amount and a percentage, written down in advance. Where they sit is your judgment, not the template's. To see what a setting would have caught, run it on a close that's already finished: flux thresholds.
- Flag the accounts that cross them. The free template does this from two pasted columns of balances.
- Name the drivers, with amounts and a source for each. What happened, how much, where to look. The drivers should add up to the movement; whatever they don't cover is the unexplained remainder, in dollars. The account breakdown sorts GL detail by driver, and price volume mix splits a revenue movement.
- Run the four arithmetic checks. Do the amounts add up, do the drivers move the same way as the balance, does each name a source, and is there filler where an event should be? The commentary test runs them in your browser.
- Read for cause yourself. Is the named event the reason the balance moved, or just the entry that recorded it? That one still needs a person.
- Route what you can't finish. Some accounts have no reason in the ledger; the answer sits with whoever made the decision. Send those early, and track what's still blocked: what can I flux right now? More on accounts the ledger can't explain.
- Check what didn't move. An account that should have changed and didn't never reaches the queue. What flux review doesn't catch.
To practice the whole sequence on a made-up company's books, with an answer key, work the flux analysis practice case.
The package lands. You open the flux tab, read down the commentary column, and send three accounts back. The note you write is some version of needs more detail.
That hour gets filed under judgment — the part of review that takes experience, the part that supposedly can't be handed to anyone else. Most of it isn't. Most of what sends a note back is arithmetic that nobody wrote down, done in your head, at speed, on a paragraph that was never built to be checked.
I've written up the full version of that hour separately: what a reviewer is actually doing when they read flux commentary. This page is the shorter answer, plus where to go for each piece.
What month-end flux is, and what it isn't
The term gets used for several different comparisons and they aren't interchangeable.
The one this site is built around is this period against the last actual period. Current month versus prior month, on the balance sheet and the income statement, using posted balances on both sides. It's a common starting point, and it's the comparison the rest of this cluster is written against.
It isn't the only comparison in real use, and which ones a given company runs varies. Same-month year-over-year is common too — many businesses want to know this August against last August, not just against July, because MoM alone can't separate a real change from normal seasonal movement. Income statement accounts often get a year-to-date view alongside the monthly one. Balance sheet accounts are frequently compared against the prior fiscal year-end rather than, or in addition to, last month. Each of those asks a genuinely different question, and the mechanics of explaining a YoY or YTD variance aren't identical to a MoM one.
Budget versus actual is a different question again — it tests a forecast, and the answer often lives with the budget owner rather than in the ledger. Plenty of close packages include it; the point is that it answers a different question from the ledger comparisons above, and the two get conflated more often than they should.
Everything on this site is written against MoM specifically. The reasoning mostly transfers — a driver still has to be named, sourced, and add up to the movement, whatever the movement is measured against — but the specific mechanics of YoY and YTD comparisons aren't covered here yet.
Five properties, four of them computable
Commentary that survives review has five properties. It is quantified, directional, sourced, specific, and causal.
- Quantified — the drivers carry dollar amounts, and those amounts account for the movement.
- Directional — the drivers move the same way the balance did. An explanation describing a release, attached to an account that increased, is wrong regardless of how well-written it is.
- Sourced — each driver names where to look. A report, a subledger, a document.
- Specific — no filler. "Due to timing" and "normal fluctuations" name a category, not an event.
- Causal — the named event is the reason the balance moved, not the mechanism that recorded it or the schedule it moved on.
Four of those five are arithmetic or string matching. Only the last one needs a person.
The reason review doesn't feel that way is the container. A paragraph has no addends. You can't sum a sentence, so you sum it in your head and file the result as an impression. Change the container — driver lines with what happened, how much, and where to look — and four of the five stop being opinions and start being formulas.
There's a version you can run in the browser: enter your driver lines and see which tests they pass.
Why commentary gets sent back
Almost always one of three, and almost never because the numbers are wrong.
It restates the number. Saying an account increased by the amount it increased is the variance, not the explanation of it.
It doesn't distinguish timing from a real change, where that distinction matters. Not every movement is one or the other — accounts move for plenty of reasons that are neither. But when a movement will reverse next month and the commentary reads as though it's the new baseline, the reader draws the wrong conclusion about what to expect.
It isn't complete. The drivers named cover part of the movement and the rest is unexplained. Not wrong, just short — and short in a way that's invisible until someone adds it up.
More on each of those, with examples: why flux commentary gets rejected.
What the control actually tests
Worth being honest about this, because it explains why the bar never transfers between reviewers.
Where a flux control checks only that an explanation is present and that a second person signed off, neither of those tests whether the explanation is any good. Quality stays unwritten, which is why commentary gets rewritten by whoever reviews it rather than corrected, and why a new preparer learns the standard by having work returned rather than by reading it.
More on the gap between testing that commentary exists and testing whether it's any good.
What movement-based review doesn't see
Flux looks at accounts that moved. That's the design, and it's also the gap.
An account that should have moved and didn't produces no variance, so it never reaches the queue. A reclass inside the same account family nets to nothing at the level you're reviewing. An accrual that reversed and re-booked flat leaves no trace at all.
What flux review doesn't catch.
There's a related scale problem. A percentage-only threshold flags a small account that swung a lot in proportional terms and nothing in dollar terms, while a large-dollar move sitting inside an already-large account clears the percentage test and never surfaces. The mechanic that works is a dollar floor and a percentage together, as an AND gate, with a per-item floor underneath it.
More on small charges in large accounts, and see how many accounts each threshold would flag.
Two systems that were never built to agree
The operational report says one thing and the ledger says another, and both are internally correct. Different cut dates, different inclusion rules, different definitions of the same word.
You're explaining the ledger movement. Source the driver from operations, name the source, and move on — don't spend close reconciling two systems that were never designed to tie.
Some accounts can be explained from the detail. Some can't.
This is the practical constraint on automating any of it.
Some accounts carry the reason in the transaction detail, already labeled — the description field says what happened and you just read it. Some require compiling the detail first and then interpreting it, which is slower but still possible from what's in the system. And some accounts have no reason in the ledger at all: the driver is a decision somebody made, recorded nowhere, and the only way to get it is to ask.
Knowing which of the three you're looking at, before you start, is most of the time savings.
Why some accounts can be explained from the detail and others can't.
Everything on this site, in order
The pieces below go deeper on each part of the above. Read in any order — each stands alone.
Getting the population right
- Flux analysis vs variance analysis. Actual-to-actual against actual-to-budget, and why the comparison decides what counts as an answer.
- Budget vs actual variance analysis, with a worked example. Which budget variances to explain and whether the explanation adds up; the budget vs actual tool runs it on your numbers.
- What is flux analysis in accounting? The plain definition, why it isn't taught in school, and how it's actually done.
- General ledger doesn't match the trial balance? Check the export first. Before you explain anything, tie the export out account by account: opening + activity = closing.
- Flux flags what moved — the exceptions are structural. A threshold compares an account to itself; most of what goes wrong needs a different comparison.
- What flux review doesn't catch. Its detection mechanism is movement, which leaves a specific residual.
- Explaining an account made of forty small charges. Material in aggregate, immaterial line by line.
- A worked flux analysis example. A revenue account and a receivables account run end to end, with the commentary that comes out.
- Income statement flux analysis. Volume, rate and mix, and why a P&L comparison needs both periods pulled.
- Balance sheet flux analysis. Explaining a level rather than an event, how the common accounts behave, and what a size threshold misses.
- Income statement flux and balance sheet flux need different data. IS accounts reset, BS accounts carry — which changes what you pull before comparing anything.
- Explaining a line that isn't an account. Group packages report financial statement lines, not accounts — and may use a different comparison basis than your internal review.
Writing commentary that holds up
- Four of the five tests your commentary fails are arithmetic. The full mechanic behind the four computed tests.
- Why flux commentary gets sent back. Three reasons, none about the numbers being wrong.
- Why your commentary keeps getting rewritten. The control tests presence; everything past that is reviewer preference.
- When the operational report and the GL don't agree. Two systems, both right, not tying.
- Why some accounts can be explained from the detail and others can't.
- When automated flux drafting helps, and when it costs you more. The routing decision is the skill, not the prompt.
Timing and sequencing
- The accounts you can flux fastest are the ones you booked yourself. Difficulty tracks entry familiarity, not account size.
- What can I flux right now? A free tracker for which accounts are unblocked as close progresses.
- Commentary written against a balance that then moved. The residual test runs a second time.
The entries underneath
- What actually goes into an accounting estimate. The entry is two lines; the method is the work.
- True-up in accounting. The two different things called a true-up, the journal entry, and when a pattern of them is a warning sign.
- Reclass vs adjusting entry. What each usually means, where the published definitions conflict, and why the label matters less than the impact.
- Reversing entries: which accruals to reverse. A reversing entry auto-cancels on day one of the next period; a non-reversing one stays booked until cleared.
- Topside entries. Manual adjustments made outside the entity ledgers, with a worked cutoff example and what flux sees each month.
- The judgment happens once, the entry gets prepared every month. Designs go stale and nothing prompts a re-check.
- The report was right when it was built. Populations stop matching the business silently.
- "Fix it next month" is not a schedule. Correcting the amount and rebuilding the process are two decisions.
The schedules behind the balances
A balance sheet account usually has a schedule underneath it. When the schedule ties to the trial balance, the flux explanation is most of the way written.
- Prepaid expense journal entry, with a worked example. The register, the tie-out and items paid early or recorded late; the prepaid amortization calculator builds the schedule.
- Deferred revenue journal entry. Billing, monthly recognition and the roll-forward; the deferred revenue schedule builds it from a contract list.
- Fixed asset roll-forward, with a worked example. Cost and accumulated depreciation, beginning to ending; the fixed asset roll-forward tool runs it on your register.
- Foreign currency revaluation, with a worked example. The unrealized gain or loss and the entry, and the explanation for the FX line; the FX revaluation calculator runs it on your balances.
- Bank reconciling items: what each one means. Which side each item adjusts and when it needs an entry; the bank reconciliation calculator finds the unexplained gap.
- Payroll accrual calculator. Unpaid days at month end, accrued wages and on-cost, and the entry.
Agents in the close
- Getting started with agents in month-end close. Vocabulary, which accounts are worth trying, and testing an agent cold before it touches real data.
- What agents can and cannot do in the close. Agents can prepare; the judgment calls and the commentary review standard still sit with a person.
- Cold tests of agents on real close work. A standing, dated log of agents run cold against a reference answer computed in advance — not a self-report.
Where to start
- Month-end close checklist — free, every close step in order with what done looks like, and an Excel version.
- Flux analysis demo — see the full review run on a synthetic company, then break it.
- Account breakdown — free, organizes GL detail by driver in your browser.
- The flux analysis Excel template — free, formula-only, no signup.
- Flux thresholds — free, shows how many accounts each dollar and percentage setting would flag.
- The commentary test — free, runs in the browser, no upload.
- The reviewer red-flag checklist — free, the short version of what gets a note sent back.
- The CloseOps Flux & Variance System — $79, starts from your trial balance, builds both flux statements and ranks what to investigate.
CloseOps is productivity software and a documented working method. It is not an audit, a review, a compilation, or any other assurance service, and nothing it produces is accounting advice or an opinion on your financial statements. It helps you run a repeatable close and evidence that you ran it. You remain responsible for your accounting, your judgments, and your numbers.
Practice it: the flux analysis practice case is a full month of a made-up company's books, with an answer key.
Before flux can start: why month-end close takes so long to start.
Related: four of the five tests are arithmetic, and a live grader. Found something wrong or missing? Tell me here — anonymous, thirty seconds.