Flux analysis is a period-end review in which finance compares each account balance with a prior period, flags every movement above a defined threshold, and documents the business reason behind it before the numbers are reported.
Flux analysis differs from variance analysis in scope and purpose. Variance analysis explains budget against actual for management. Flux analysis is a close control applied account by account, on the balance sheet and the income statement, to catch errors before they reach the financial statements. In SOX environments it is often a key control whose documentation the external auditor reviews.
A flux analysis rests on three parameters:
- Comparison basis: prior month, same month of the prior year, or prior quarter, depending on seasonality
- Dual threshold: a percentage combined with an absolute amount, for example 10% and 50,000 euros, so that small accounts with large swings and large accounts with small swings are both handled sensibly
- Explanation standard: a cause backed by evidence, never a restatement of the movement itself
The structural weakness of flux analysis is that it only sees movements. An error that repeats every month, such as a supplier overcharging at the same rate, produces no flux at all and passes the review untouched. Flux analysis catches breaks, not steady leaks, which is why supplier overbilling prevention has to happen at transaction level.
Phacet covers the part flux analysis cannot see. The agent that can control supplier billing checks each invoice before it becomes a balance, and the agent that can check your analytical mapping table confirms that figures sit in the right accounts, so the period-end review explains real movements rather than coding errors. The review itself belongs to the close calendar.
