Free tool · runs in your browser

Flux analysis demo: watch a checked review run, then break it

One synthetic company's August close, reviewed step by step on this page: read the export, check it's complete, compute the movements, flag what crossed the threshold, show the draft commentary, and list what still needs a person. Then break the export on purpose and watch the review stop instead of producing a wrong answer.

The company is Northwind Trading, the same synthetic products business and the same product revenue accounts as the worked flux analysis example — that page and this one build out different supporting detail (cash receipts, credit memos, FX) behind receivables, so its receivables figures won’t match this demo's. August is compared against July. An account is flagged only if it moved more than $50,000 and more than 10 percent — both, not either.

Every number below is computed by this page from the exports. The draft commentary is the one part that isn't: it was written in advance for this data, and it's labeled that way everywhere it appears. Nothing is uploaded, nothing is saved, and nothing leaves your browser. New to flux review itself? Start with the definition first.

Before you start: break it (optional)

Delete a transaction from the export The August ledger export arrives without one $2,000 office supplies bill — the same failure worked through on the GL-to-trial-balance page. Nothing in the export itself shows it's missing. Flip a sign in the export The $41,600 credit memo line on trade receivables comes through as a debit instead of a credit.

Each step runs when you click Next, so you can see what it did before moving on. Short on time? There’s a link to run the rest straight through.

JavaScript required

This demo computes everything in your browser as you click through it, so it needs JavaScript turned on to run. Nothing else on this site does.

Why the checks come first

A flux review is only as good as the export under it. If a transaction is missing, the account it belonged to just looks quiet, and a quiet account doesn't get flagged, so nobody asks. That's why this demo refuses to compute anything until the export ties to the trial balance, and why the refusal names the account and the amount rather than just saying something is wrong.

The same order matters more when software, not a person, is doing the prep. An agent reading an export can't tell a missing entry from a slow month either. If you're testing one, start with the checks it should face before it touches your data, and see how I grade agents against a reference answer.

What it isn't

It isn't a tool for your own data. The company, exports and figures are fixed and synthetic. For your own numbers, use the template or account breakdown.
It doesn't write commentary. The drafts are pre-written for this data and shown for illustration. This page computes the movements, the drivers and the residual beside them; it can't tell whether a stated cause is true.
It doesn't decide anything. Which one-test-only accounts deserve a line, whether a source says what the draft says, and whether the file is ready to sign are left to a person, as they should be.

Want this as a workbook you keep? The free flux template is the single-sheet version. 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.

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.

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