Flux Analysis Template: Thresholds, Format, and Example Explanations

Deepak Anchala
Co-Founder and CEO, Adopt AI7 November 2026

The trial balance is ready, the flux is due by business day two, and the last version of the worksheet has a column nobody can explain. This flux analysis template gives you a layout you can copy into a workbook today: the columns, the two-part threshold, a status column that makes review visible, and example explanations a reviewer can verify without calling the preparer.
If you want the concept first, read what is flux analysis. This post covers the worksheet.
The flux analysis template layout
Build one row per account on the trial balance. Use these ten columns.
| Column | What goes in it |
|---|---|
| Account | Account number and name |
| Prior period | Final balance, confirmed closed |
| Current period | Balance from the current trial balance |
| $ change | Current minus prior |
| % change | $ change divided by prior |
| Flag | Yes if both thresholds are exceeded |
| Explanation | Driver, amount, and evidence |
| Support | Link or reference to the document |
| Preparer | Name and date |
| Reviewer | Name and date |
Two rules keep the template honest. The prior period must be final, because a comparison against a balance that later changed produces false flags. And the explanation column stays empty for accounts that do not breach, so a filled cell always means someone investigated.
Set thresholds before you open the data
A flux analysis template needs a threshold in two dimensions. A percentage alone flags every small account that moved from $100 to $300. A dollar amount alone ignores an account that fell 90% but holds little money. Flag an account only when it exceeds both.
A working starting point is 10% and $10,000. Adjust from your own materiality: a controller at a company with $20 million in revenue might use $25,000, and a smaller company might use $5,000. Write the thresholds at the top of the worksheet and change them only at the start of a period, never after you have seen the results. A threshold chosen after the fact explains whatever someone already found interesting.
Add a second comparison column if seasonality matters. The same month last year removes the Q4 retail spike, and the prior month catches the duplicated accrual. Flag an account that breaches either comparison.
Example explanations a reviewer will accept
The test for an explanation is whether the reviewer can verify it without returning to the preparer. Name the driver, give the amount, and point at the document. When several drivers contribute, list each with its amount so the parts sum to the change.
| Account | Change | Weak explanation | Usable explanation |
|---|---|---|---|
| Payroll expense | +$84,000 | Higher headcount | Six hires started between March 4 and March 18; $62,000 salary plus $22,000 payroll taxes and benefits per the payroll register |
| Professional fees | +$180,000 | Higher legal and consulting costs | ERP implementation began in March; $180,000 billed per the signed statement of work |
| Deferred revenue | -$95,000 | Revenue recognized | Three annual contracts reached the end of their term; $95,000 moved to revenue per the recognition schedule |
| Accrued expenses | +$60,000 | Timing | December freight invoices of $60,000 arrived after cutoff and were accrued per the receiving log |
| Cash | -$210,000 | Normal activity | Annual insurance premium of $140,000 paid March 9 and quarterly tax payment of $70,000 paid March 15, per the bank statement |
Each weak explanation restates the column. Each usable one gives a reviewer something to open and check.
How to run the template each month
- Load both trial balances. Pull them from the general ledger and confirm the prior period is final.
- Calculate the change. Dollar and percent, for every account.
- Apply the thresholds. Mark every account that exceeds both.
- Investigate flagged accounts. Open ledger detail and find the transactions behind the movement.
- Write and support the explanation. Driver, amount, document.
- Review and sign off. A second person tests each explanation and records name and date.
Look for netting while you work. A flat account can hide a large increase offset by a large decrease, so drill into quiet accounts that carry heavy activity. Carry explanations forward so a recurring movement is recognized as recurring. Place the review in your calendar using the close calendar template, where flux explanations are reviewed on business day three.
Where the template stops helping
Steps 1 to 3 take minutes. Steps 4 and 5 take days, because each flagged account means opening ledger detail and writing up what you find. A template organizes that work. It does not do it.
Adopt's agents take the preparation off your team. They pull the trial balance, apply your thresholds, trace each flagged account to the transactions behind it, and draft an explanation with the support attached. The controller reviews every draft and approves it, nothing enters the close package without that sign-off, and each number traces back to its source transaction. Your team moves from writing explanations to deciding whether they are right.
For the related concepts, see variance analysis and budget vs actual. The Flux Analysis guide covers the full process.
Next step
Copy the layout into your workbook, set both thresholds, and run it against last month's trial balance as a test. Then sign up free to see Adopt draft flux explanations on your own data, or book a pilot to run it through a full close.
FAQs
Related Articles

The Accountant Shortage in Numbers: What It Means for Your 2027 Close

How to Automate Invoice Data Extraction and Categorization from PDFs

See it running on your workflows
Automate your accounting workflows

