Accounting
Financial Management
Flux Analysis: How to Explain Balance Sheet and P&L Fluctuations at Month End
Last updated: October 13, 2026 · Independent guide · We do not sell rankings or coverage.
Flux analysis is the month-end step where you compare each balance sheet and income statement account with a prior period, flag the movements that exceed your thresholds, and write a short explanation of what caused each one. A movement nobody can explain is often a missed accrual, a misposting or a cutoff error that you can still fix before the books lock.
This guide covers the close step only. Budget-versus-actual review is FP&A variance analysis, and statistical anomaly detection is covered in our guide to AI-assisted variance analysis.
The flux analysis process in six steps
- Freeze a reconciled trial balance. Run flux after reconciliations and recurring entries are posted.
- Choose the comparison periods. Prior month for most accounts, same month last year for seasonal lines.
- Apply dollar and percentage thresholds. Set them per account group and decide whether both or either must be exceeded.
- Investigate and write explanations. Quantify the drivers behind each flagged movement.
- Review, correct and sign off. Errors become adjusting entries, and the analysis is signed before the period locks.
- Retain and recalibrate. File the evidence and adjust thresholds that are too noisy or too loose.
Who does what at each stage
The table below is a typical split for a mid-sized finance team. In a smaller team the controller may prepare and review some groups, but the same person should not prepare and approve the same account.
| Stage | Responsible | Reviewer or approver | Output |
|---|---|---|---|
| 1. Freeze trial balance | GL or senior accountant | Controller | Trial balance snapshot with reconciliations complete |
| 2. Comparison periods | Controller | CFO or chief accounting officer | Documented comparison basis per account group |
| 3. Thresholds | Controller | CFO, informed by the auditor’s materiality | Threshold policy and list of flagged accounts |
| 4. Explanations | Account owner (preparer) | Senior accountant or manager | Quantified explanation with evidence reference |
| 5. Review and sign-off | Reviewer | Controller | Signed analysis and any adjusting entries |
| 6. Retain and recalibrate | Controller | CFO | Filed workpaper and updated threshold policy |
Stage 1: Freeze a reconciled trial balance
The input is a trial balance after bank, subledger and intercompany reconciliations are done and recurring entries such as depreciation, amortization and payroll accruals are posted. The output is a dated snapshot that the flux workbook or tool reads from.
The control here is sequencing. Put flux after reconciliations on your close checklist, and require a fresh pull if anyone posts to the period after the snapshot. Reconciliations prove a balance is supported; flux asks whether its change makes sense. Our guide to cash reconciliation covers the reconciliation side for cash accounts.
Stage 2: Choose the comparison periods
Most teams compare the current month with the prior month for balance sheet accounts, because each balance is a point-in-time position and the prior month-end is the most recent known-good figure. Income statement lines are period activity, so a prior-month comparison catches posting errors but also flags normal seasonality. A same-month-prior-year comparison removes most of that seasonal noise.
The PCAOB’s standard on substantive analytical procedures, AS 2305, makes a related point: it states that “relationships in a stable environment are usually more predictable than relationships in a dynamic or unstable environment” and that income statement relationships tend to be more predictable than balance sheet relationships (PCAOB AS 2305, no date shown).
| Comparison | Best for | Watch out for |
|---|---|---|
| Current month-end vs prior month-end | Balance sheet accounts | Quarter-end and year-end entries that distort the next month |
| Current month vs prior month activity | Catching misposted or missing P&L entries | Seasonal lines and differing number of days or payroll runs |
| Current month vs same month prior year | Seasonal revenue and expense lines | Chart-of-accounts changes and acquisitions that break comparability |
Set a rule for zero or very small prior balances. A percentage change on a zero base cannot be calculated, so judge those accounts on the dollar threshold alone.
Stage 3: Set dollar and percentage thresholds
There is no regulatory threshold for internal flux analysis, so the number is a policy decision. AS 2305 says the amount of difference an auditor can accept without further investigation “is influenced primarily by materiality” (PCAOB AS 2305). For public companies, the PCAOB’s Staff Audit Practice Alert No. 11 lists the threshold for investigating differences, relative to materiality, as one indicator of how precise a management review control is, and a lower threshold is more precise (PCAOB, October 24, 2013). If flux is a key control, agree the expected precision with your auditor.
Published examples vary widely. Ramp, which sells finance software, gives an example of investigating movements above $25,000 or 10%, whichever is triggered first (Ramp, September 9, 2026). Solvexia, which sells finance automation software, uses a combined “$5,000 and 5%” example (Solvexia, February 23, 2026). Treat both as starting points, not benchmarks.
The logic matters most. An and rule (both limits exceeded) cuts noise from small accounts with large percentage swings. An or rule (either limit exceeded) also catches large accounts that move by a low percentage. A practical setup is and logic plus a short always-explain list, such as revenue, cash and accrued liabilities.
Avoid a single percentage rule. The SEC’s Staff Accounting Bulletin No. 99 describes the 5% rule of thumb and says it cannot replace a full analysis, listing qualitative factors such as whether a misstatement “masks a change in earnings or other trends” or affects loan covenant compliance (SEC SAB 99, August 12, 1999). Accounts tied to covenants, compensation or estimates deserve lower thresholds than their size suggests.
Stage 4: Investigate and write explanations reviewers accept
The account owner drills into the journal entries and subledger detail behind each flagged movement. The output is an explanation that answers four questions: what drove the change, how much each driver contributed, whether it will recur, and where the evidence is. AS 2305 states that management responses “should ordinarily be corroborated with other evidential matter,” so your auditor will test the explanation, not just read it.
Explanations fail review when they restate the number (“expenses increased due to higher spend”), name a cause without an amount (“timing”), or hide an unexplained residual.
| Field | What to write | Example (illustration) |
|---|---|---|
| Driver and amount | Each cause with its dollar effect | Audit fieldwork accrual, $48,000 |
| Residual | Any unexplained amount, stated plainly | $0 unexplained |
| Recurring or one-time | Whether the change continues next month | One-time; reverses when invoiced |
| Evidence | Entry number, invoice, contract or schedule | JE 0912, engagement letter dated July 2026 |
| Action | None, or the correcting entry raised | None required |
Worked example: a flux template with explanations
This is an illustration with invented figures. A company closing September 2026 compares month-end balances and monthly activity with August 2026. Its policy flags balance sheet accounts that move by at least $50,000 and 10%, income statement lines that move by at least $20,000 and 10%, and accounts with a zero prior balance on the dollar limit alone.
| Account | Sep 2026 / Aug 2026 | Change | Flag and explanation |
|---|---|---|---|
| Accounts receivable | $1,240,000 / $1,080,000 | +$160,000 (+14.8%) | Flagged. Annual renewals of $172,000 invoiced September 26 to 30 on net 30 terms, less $12,000 higher collections elsewhere. Residual $0. Recurs each September. |
| Prepaid expenses | $96,000 / $60,000 | +$36,000 (+60.0%) | Not flagged: below the $50,000 limit. |
| Accrued liabilities | $310,000 / $245,000 | +$65,000 (+26.5%) | Flagged. Audit fieldwork accrual of $48,000 per the engagement letter and $17,000 bonus true-up from the Q3 calculation. Residual $0. |
| Revenue | $1,450,000 / $1,380,000 | +$70,000 (+5.1%) | Always-explain list: two new subscription customers from September 1 add $70,000 a month. Residual $0. |
| Professional fees | $92,000 / $41,000 | +$51,000 (+124.4%) | Flagged. Same $48,000 audit accrual plus $3,000 of contract review legal fees. One-time. |
| Recruiting fees | $24,000 / $0 | +$24,000 (n/a) | Flagged on dollars (zero base). Placement fee for an assistant controller. One-time. |
The prepaid line moved 60% but stayed under the dollar limit, which is the and rule working as intended; a check against the prepaid expense amortization schedule covers it. The audit accrual appears in two explanations, and a reviewer should confirm they agree.
Stage 5: Review, correct and sign off
The reviewer reads every flagged explanation, samples the evidence, and sends back weak ones. When the investigation finds an error, such as a miscoded invoice or a missing accrual, the output is an adjusting entry and a re-run of the affected lines. The control evidence is the reviewer’s sign-off with a date that falls before the period lock.
The most common failure is signing off with open items to meet the close deadline. Do not lock the period while flagged accounts remain unexplained. If an item must wait, record it as an open item with an owner and a date so it is visible at the next close.
Stage 6: Retain and recalibrate
File the signed analysis and its evidence with your reconciliations. Each quarter, look at the accounts that were flagged and explained as “normal” every month. Those are candidates for a higher threshold or a different comparison basis. Accounts where errors surfaced later without a flag are candidates for a lower one. Record each change and who approved it.
Metrics to track
- Flagged accounts per close. A rising count with no more errors found suggests thresholds are too tight.
- Days from trial balance freeze to flux sign-off. Shows whether flux is delaying the close.
- Send-back rate. The share of explanations a reviewer returns.
- Adjustments raised from flux. The count and value of corrections flux caught.
- Repeat flags. Accounts flagged with the same explanation three or more months running.
- Open items carried forward. Unexplained or partly explained movements left at sign-off, with their age.
How software supports each stage
Your ERP or accounting system handles stages 1 and 2 well. QuickBooks Online has a Profit and Loss Comparison report that compares with the previous period or previous year and shows $ change or % change (Intuit, updated August 4, 2026). Microsoft Dynamics 365 Business Central ships sample financial report column definitions, including current month balance against prior month balance and against the same month prior year (Microsoft Learn, April 1, 2026). In NetSuite, the Comparative Income Statement shows a current and a comparative amount (Oracle NetSuite Help, no date shown), and Oracle’s documentation says variances between columns are built with a custom formula field (Oracle NetSuite Help, no date shown). None of these reports stores explanations or sign-offs, so commentary usually lives in a spreadsheet.
Close management tools cover stages 3 to 5. FloQast lets admins and managers set dollar or percentage materiality thresholds, requires an explanation when a group exceeds its threshold, and shows sign-offs for material fluctuations (FloQast Help, no date shown). Numeric offers dollar and percent, dollar or percent, and other threshold logic, per-account overrides, and an audit trail of threshold changes (Numeric Help, no exact date shown). BlackLine Variance Analysis flags accounts outside configurable thresholds, assigns responsibility for explaining variances and uses customer-defined variance codes to roll up variance amounts; BlackLine does not publish pricing on the page (BlackLine, no date shown). DualEntry compares against the prior period or the same period last year, supports separate income statement and balance sheet thresholds, and can draft commentary from the period’s transactions for you to edit (DualEntry Docs, no date shown). These descriptions come from each vendor’s own documentation.
For the wider picture of checklists, reconciliations and close tooling, see our guide to accounting close automation.
How we researched this
We read the top-ranking pages for “flux analysis” in October 2026, mostly vendor blogs, and noted what they leave out: zero-base rules, and versus or threshold logic, reviewer standards and audit guidance. We used PCAOB and SEC primary sources for audit and materiality points and vendor documentation for every product capability. All pages were checked on October 13, 2026. The worked example uses invented figures.
Related guides
- Month-End Close Checklist Template (2026)
- Trial Balance Template: Prepare, Check and Fix It
- General Ledger Reconciliation: Steps, Frequency and Review
Frequently asked questions
What is the difference between flux analysis and variance analysis?
Flux analysis compares actual balances with actual balances from an earlier period, usually as a month-end close control. Variance analysis in the FP&A sense compares actuals with a budget or forecast to explain performance. Some teams and tools use the terms interchangeably, so define them in your close policy.
What threshold should I use for flux analysis?
No rule sets one for internal flux reviews. Set dollar limits well below your auditor’s materiality, add a percentage limit to filter small accounts, and choose whether both or either must be exceeded. If the review is a key SOX control, agree the precision with your auditor first.
Should flux analysis cover the balance sheet or just the P&L?
Both. Income statement flux catches misposted and missing expenses, while balance sheet flux catches accruals, prepaids and receivables that did not move as expected. Balance sheet accounts are point-in-time positions, so pair them with reconciliations and rollforwards.
What makes a flux explanation acceptable to auditors?
It names each driver with its dollar amount, states any unexplained residual, says whether the change will recur and points to evidence such as an entry number or invoice. PCAOB AS 2305 says auditors should ordinarily corroborate management’s explanations, so an explanation without evidence will be tested anyway.
Sources
- PCAOB, AS 2305: Substantive Analytical Procedures, no date shown (checked October 13, 2026). pcaobus.org
- PCAOB, Staff Audit Practice Alert No. 11: Considerations for Audits of Internal Control Over Financial Reporting, October 24, 2013. pcaobus.org
- SEC, Staff Accounting Bulletin No. 99: Materiality, August 12, 1999. sec.gov
- Intuit, Run a Profit and Loss comparison report (QuickBooks Online), updated August 4, 2026. quickbooks.intuit.com
- Microsoft Learn, Business Central documentation on financial report column definitions, April 1, 2026. learn.microsoft.com
- Oracle NetSuite Help, Comparative Income Statement Report, no date shown. docs.oracle.com
- Oracle NetSuite Help, Adding Time-Based Comparison Columns to Reports, no date shown. docs.oracle.com
- FloQast Help Center, article on Flux materiality thresholds, no date shown (vendor). help.floqast.com
- Numeric Help, Setting thresholds for Flux reports, no exact date shown (vendor). help.numeric.io
- BlackLine, Variance Analysis product page, no date shown (vendor). blackline.com
- DualEntry Docs, Flux analysis, no date shown (vendor). docs.dualentry.com
- Ramp blog, flux analysis article, September 9, 2026 (vendor). ramp.com
- Solvexia, Flux Analysis in Accounting: What it is, Examples, and Why it Matters, February 23, 2026 (vendor). solvexia.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
