A reconciliation proves a balance. A flux analysis asks whether the balance makes sense at all.
A balance sheet flux analysis compares each account's balance with the previous month and the same month last year. Any movement above an agreed threshold must be explained by a known business event. Unexplained movements are often posting errors, missed accruals or journals in the wrong account. Run it after reconciliations and before the final close review.
A reconciliation can agree perfectly and still be wrong. If a cost was posted to the wrong balance sheet account, both the ledger and the supporting report may move together. A flux analysis looks at the shape of the numbers instead: which balances moved, by how much, and whether that matches what the business actually did this month.
Export the trial balance for this month, last month and the same month last year, one row per balance sheet account.
=C2-D2=IFERROR(F2/ABS(D2),0)=AND(ABS(F2)>=MinAmount,ABS(G2)>=MinPct)Name the threshold cells so they are visible and consistent. Add a column for the explanation and one for the reviewer's initials.
A good explanation names the cause and links to the evidence: "Receivables up because of the large customer order invoiced on the last working day; collected in the first week of next month, see remittance." Avoid "normal movement". If you can't say what caused a movement, it isn't explained.
Flux analysis pairs naturally with the balance sheet reconciliation process and the suspense account reconciliation. Run it every month: the second month is when the patterns start to show, and by the third you'll know which accounts deserve attention.
Save each month's flux file with its explanations. Next month, the reviewer can see whether last month's "timing" movement actually reversed. Explanations that repeat month after month for the same account are worth a closer look: they often hide an error that has become routine.
"Flux analysis" is the common US term. UK teams often call it "balance sheet review" or "movement analysis". The method is identical.
Reviews every balance sheet reconciliation with an on-device AI and 20 review tests, flags vague and wrong-account reconciling items, and builds a risk-ranked review queue. Runs in your browser on your own computer: nothing is uploaded.
12 questions on how strong your close controls are. Free to use online.
The Balance Sheet Reconciliation Library covers the balance sheet with nine working papers: a known error blocks sign-off, every supported balance needs an evidence reference and every aged item needs an owner and a next action. Excel, no macros, one-time price.
A comparison of account balances between periods, with an explanation for any movement above a set threshold. It catches errors that reconciliations can miss.
Yes. Run it on both. Balance sheet flux finds misposted balances; income statement flux finds missed accruals and costs in the wrong month.
Combine a percentage with a minimum amount, agreed with the controller. A percentage alone flags tiny accounts; an amount alone misses smaller accounts that matter.
The controller or a senior accountant who didn't prepare the reconciliations, so the review is a genuine second look.
Last updated 21 October 2026. General guidance for finance teams; check it against your own policies, systems and local rules.