Every close cycle, accounting teams ask the same question: what changed, and why? Variance analysis is where accountants become storytellers. The challenge is that the story has to be audit-ready, backed by evidence, and delivered before anyone else in the company sees the financials. The math is simple. The explanations are not.

Variance analysis and flux analysis are two terms for the same discipline. Strictly speaking, variance analysis compares actuals to a budget or forecast, while flux analysis compares actuals across time periods.

In practice, most controllers do both during close and refer to the entire exercise as flux. Most teams still perform this work by exporting trial balance data into a spreadsheet, manually comparing periods, scanning for large movements, and writing explanations one account at a time. For a company with 200 GL accounts across multiple entities, that process can consume one to two full days of the close window. The issue is not that variance analysis is inherently complex. It is that most teams are still doing the preparation manually.

This guide covers how to set materiality thresholds that actually work, what good variance explanations look like with real numbers, the evidence auditors expect, and how to build a review queue that routes only material variances to humans.

Why variance analysis matters

Most finance teams treat variance analysis as a reporting obligation. It is also one of the most effective controls in the close process.

• Catches errors before they reach stakeholders. Variance investigation surfaces mispostings, missed accruals, and duplicate entries that reconciliations alone do not always catch.

• Flags fraud signals. Unusual patterns in discretionary accounts, round-number entries, or variances that reverse cleanly the following month are all indicators worth investigating.

• Drives resource prioritization. A tiered review queue means the controller’s time goes to the 15 accounts that actually require judgment, not all 200.

• Creates performance accountability. When department heads know their actuals will be compared to budget every month, spending decisions get made more carefully.

• Supports faster audit cycles. Explanations prepared during close with evidence already attached reduce the back-and-forth during audit fieldwork.

What to compare in variance analysis and how often

Not every comparison serves the same purpose. The table below outlines the most common approaches, what each one reveals, and when it is most useful.

A common gap is that many accounting teams skip balance sheet flux during the monthly close. Income statement flux gets the attention because revenue and expenses are what leadership asks about. But balance sheet accounts are where errors hide. A prepaid balance that grows every month without explanation, a receivable that never collects, or an accrued liability that reverses and re-accrues in the same amount month after month are all signals that something deeper is wrong.

Revenue, payroll, and intercompany accounts deserve tighter scrutiny because they are high visibility, high volume, or high risk. New accounts, unusual accounts, and any account that changed materially in the prior period should also get attention.

Static vs. flexible budget variance

Most budget comparisons use a static budget: the plan set at the start of the period, fixed regardless of what actually happened to volume. Static budget variance tells you whether actuals beat or missed the original plan. It does not tell you whether operations performed well given the volume that actually occurred.

A flexible budget adjusts cost and revenue targets to reflect actual volume. If you planned to produce 10,000 units but produced 12,000, a flexible budget recalculates what costs should have been at 12,000 units before comparing to actuals. The difference between the flexible budget and actuals isolates operational efficiency. The difference between the static budget and the flexible budget isolates the volume effect.

Example: A SaaS company budgets 600,000 in hosting costs based on 500,000 active users. Actual users came in at 620,000, and actual hosting costs were 730,000.

• Static budget variance: 730,000 minus $600,000 = 130,000 unfavorable. Looks like a cost overrun.

• Flexible budget at actual volume: 600,000 times (620,000 divided by 500,000) = 730,000 minus $744,000 = 14,000 favorable. Operations actually ran more efficiently than planned.

Without the flexible budget step, the team investigates a $130,000 overrun that does not exist. The real story is that volume drove the increase, and the team delivered below the volume-adjusted cost target.

This is the logic behind management by exception: focus investigative effort on variances that reflect genuine operational deviation, not volume changes the business already knows about. Flexible budget analysis separates the two so the controller’s attention goes where it actually matters.

Types of variance analysis

Revenue variance measures the difference between actual revenue and budgeted or prior-period revenue. It is the first place leadership looks and the first place errors surface. A revenue variance can reflect a real business change, a recognition timing issue, or a contract modification that was not communicated to accounting.

Cost variance covers the difference between actual costs incurred and what was planned or expected. It applies broadly across COGS and operating expenses and is often the starting point for margin analysis.

Profit variance is the net result of revenue and cost variances combined. It answers whether the business performed better or worse than plan at the bottom line, and why.

Material variance applies primarily to manufacturing and product businesses. It breaks down into price variance (did raw materials cost more or less than expected?) and usage variance (did production consume more or less material than planned?).

Labor variance compares actual labor costs to standard or budgeted labor. It splits into rate variance (were employees paid more or less per hour than planned?) and efficiency variance (did the work take more or fewer hours than expected?).

Overhead variance measures the difference between applied overhead and actual overhead incurred. It is most relevant in cost accounting environments where overhead is allocated using a predetermined rate.

Budget variance is the broadest category: any difference between an actual result and the approved budget for that line. It is the default comparison most finance teams run at month-end and the one that drives most management reporting conversations.

Variance analysis formulas

The math behind variance analysis is straightforward. The complexity is in the interpretation, not the calculation.

Worked example: Budgeted revenue for March was 2,000,000. Actual revenue came in at 1,820,000.

• Variance amount: 1,820,000 minus $2,000,000 = (180,000) unfavorable

• Variance percentage: (180,000) divided by 2,000,000 = (9.0%) unfavorable

That 9% gap triggers investigation. Whether it reflects a real business shortfall or a recognition timing issue is what the analysis has to answer.

Setting materiality thresholds that actually work

Materiality thresholds determine which variances require investigation and which can be documented without further analysis. Thresholds that are too tight flag dozens of immaterial accounts and consume time on explanations nobody reads. Thresholds that are too loose allow real errors and trends to slip through.

The most effective approach is a dual threshold: a dollar amount and a percentage, with review triggered when either is exceeded. A threshold of 25,000 or 10% means a 2 million revenue line still gets reviewed because it exceeds the dollar threshold, while a $5,000 variance on a 15,000 travel account also gets reviewed because it exceeds the percentage threshold.

Not all accounts should share the same thresholds. Revenue, payroll, and intercompany accounts warrant tighter thresholds. Discretionary operating expenses can tolerate wider thresholds.

These are starting points. A useful calibration method: set internal flux thresholds slightly below the auditor’s materiality level for the relevant financial statement line so explanations are ready when audit fieldwork begins.

Numerical thresholds are necessary but not sufficient. SEC Staff Accounting Bulletin No. 99 makes clear that exclusive reliance on quantitative benchmarks is not appropriate. A variance can be small in dollar terms and still matter if it involves a related party, masks an offsetting error, affects a covenant, or represents a meaningful trend.

One principle many threshold-based approaches miss: sometimes the signal is a variance that should have appeared and did not. A quarterly tax payment that fails to post in the expected period may show no variance at all in period-over-period comparisons. The best processes include an expectations layer that flags missing activity, not just abnormal movement.

Three variances you would actually see at close

Textbook variance analysis uses clean, hypothetical numbers. Real variance analysis involves messy operational context, judgment calls, and evidence that lives outside the GL.

Example 1: revenue decline that is not actually a decline

Revenue is $180,000 lower than prior month. The sales team says nothing changed. The immediate assumption is that the business is softening.

Investigation: pulling the detail by customer reveals the largest customer’s revenue dropped 210,000 while all others collectively increased $30,000. Drilling in, the picture becomes clear. Last month included a cumulative catch-up adjustment under ASC 606. The customer amended their contract midway through the prior quarter, and the modification required reallocating the transaction price across remaining performance obligations under ASC 606-10-25-13(b). That reallocation generated a 210,000 catch-up recognized entirely in the prior month. This month is the first clean month at the new contracted rate.

Both months are correct. No journal entry is needed. But without drilling into customer-level detail and reviewing the contract amendment, a controller would report that revenue declined. The real story is the opposite.

Evidence: contract amendment with effective date, ASC 606 modification analysis, revenue recognition schedule showing the catch-up entry and forward run-rate, customer-level revenue detail for both periods.

The narrative: “Revenue decreased 180K MoM. Driven by $210K non-recurrence of an ASC 606 cumulative catch-up adjustment recognized in the prior month for [Customer] contract modification (ASC 606-10-25-13(b)). Current month reflects the new contracted run-rate. Underlying revenue excluding catch-up increased 30K. No adjustment required. Contract amendment and revenue schedule attached.”

Example 2: opex variance from annual license reclassification

Professional services expense is 92,000 higher than prior month. Prior month: $340,000. Current month: 432,000. The variance is 27%, well above typical thresholds.

Investigation: the increase traces to a single vendor. The annual software license renewed in the current month, and the vendor switched from monthly to annual billing without advance notice. The full annual amount (85,000) was expensed in one month. Prior months carried this cost at 7,083 per month.

This is not an increase in spending. It is a prepayment that should be amortized over the license term. Under ASC 340-10, costs paid in advance for services received over future periods should be recognized as prepaid assets and amortized as the benefit is consumed.

Adjusting journal entry:

The reclassification moves 11 months of the license (85,000 less 77,917) to prepaid. After the reclassification, the MoM variance drops from $92,000 (27%) to 14,083 (4%), which falls below typical thresholds.

Evidence: vendor invoice showing annual billing, prior-year invoice showing monthly billing, contract renewal terms, amortization schedule, JE approval.

Example 3: payroll variance that requires operational data

Salary expense is 47,000 lower than prior month. Prior month: $812,000. Current month: 765,000. The variance is (5.8%), just over the 5% threshold for payroll.

Investigation: the headcount report shows a net decrease of three FTEs in the finance department. Two departures occurred mid-month with no replacement overlap, and one open role from the prior month remained unfilled. The $47,000 decrease is driven by partial-month vacancy across these positions. No journal entry is needed.

This example illustrates why variance analysis requires operational data, not just GL data. The GL shows salary expense decreased. It does not tell you why. A controller who explains this variance without referencing the payroll detail is guessing. A controller who attaches the evidence is proving it.

Evidence: payroll register for both periods showing active employees and pay dates, headcount report showing current vs. prior month FTEs by department.

The narrative: “Salary expense decreased $47K (5.8%) MoM. Net decrease of 3 FTEs in the finance department due to mid-month departures and open roles not yet backfilled. Replacement hiring underway. Payroll register and headcount report attached.”

Variance analysis explanation template

The most time-consuming part of variance analysis is not finding the variance. It is writing the explanation. The most common failure mode is vague explanations that raise more questions than they answer. “Timing differences” is not an explanation. “Normal operating fluctuations” is not an explanation. These are placeholders that get copied forward month after month until nobody remembers what they originally referred to.

A strong explanation covers six elements:

The test is simple: a reviewer who was not involved in the investigation should be able to read the explanation, review the evidence, and sign off without asking a follow-up question.

One additional field worth including: does this recur? Many variances are one-time. Others are structural. Flagging recurrence up front saves the same investigation from happening next month.

Evidence requirements by variance type

A variance explanation without evidence is an assertion. The evidence for a revenue shortfall is different from the evidence for a payroll overspend.

• Revenue variances: Signed contracts or order confirmations, invoices, revenue recognition schedule or waterfall, ASC 606 policy memo if recognition timing is at issue, cutoff analysis showing delivery or service completion dates.

• Headcount and payroll variances: Payroll register for both periods showing active employees, pay rates, and pay dates. Headcount report showing current vs. prior month FTEs by department.

• Operating expense variances: Vendor invoices, purchase order approvals, contract amendments or renewal terms, reclassification support, usage metrics from the platform or service. For software and SaaS expenses specifically, the usage report matters as much as the invoice.

• Intercompany variances: Intercompany invoices or transaction detail from both entities showing what drove the movement between periods.

• Accrual variances: Supporting calculation with assumptions, and prior period comparison showing the accrual pattern.

• One-time or unusual items: Documentation that supports both what the item is and why it is non-recurring.

The common thread: evidence should arrive with the variance, not after the reviewer asks for it. Teams that write the explanation first and hunt for evidence later are the ones sending frantic emails on day 4 of close asking AP for an invoice from two months ago.

Building a review queue (instead of reviewing everything)

If your controller reviews every account’s variance explanation personally, you have built a process that does not scale. The solution is a review queue that routes variances based on materiality, risk, and whether the explanation requires judgment.

• Tier 1: Auto-document, no review required. The variance is below both thresholds. The preparer documents the variance amount and a standard note. The reviewer does not need to see this.

• Tier 2: Preparer documents, reviewer skims. The variance exceeds one threshold but the root cause is known and recurring. Examples: a seasonal marketing campaign that spikes every Q4, a payroll increase from annual merit raises, or a hosting cost increase from an anticipated contract renewal. The preparer writes the explanation and attaches evidence. The reviewer confirms it is reasonable without conducting an independent investigation.

• Tier 3: Full review. The variance exceeds both thresholds, OR it is the first occurrence, OR it involves a sensitive account, OR it requires a journal entry, OR an expected variance did not appear. These get the controller’s full attention.

If a company has 200 accounts, a well-calibrated threshold matrix might flag 40 for Tier 2 and 15 for Tier 3. The controller reviews 15 accounts deeply instead of 200 superficially. The quality of those 15 reviews goes up. The documentation trail proves every account was assessed, even the ones below threshold.

A useful calibration check: if more than 50% of accounts hit Tier 3 every month, thresholds are too tight. If fewer than 5% hit Tier 3, thresholds may be too loose or have not been updated as the company has grown. Review thresholds quarterly and coordinate with your auditors during planning discussions.

What changes at month-end

Variance analysis during close is harder than at any other time, for three reasons.

• The numbers keep moving. Late journal entries, accruals posted in the last few days, and reclassifications change the trial balance underneath the analysis. An explanation written Monday morning may be wrong by Tuesday afternoon because someone posted a $60,000 accrual to the same account.

• The evidence is scattered. The GL tells you what happened. It rarely tells you why. Explaining a payroll variance requires the headcount report. Explaining an OpEx spike requires the vendor invoice and sometimes a conversation with the department head who approved the purchase.

• Explanation quality degrades under time pressure. A controller with eight hours to explain 200 accounts will write thorough, evidence-backed narratives for the first 30 and increasingly terse notes for the rest. The last 50 accounts get “timing” or last month’s explanation copied forward. This is where stale flux commentary accumulates, and it is what auditors notice first.

How this works in NetSuite

For teams running on NetSuite, the variance analysis workflow tends to follow the same pattern every month. Someone runs a comparative financial report or saved search to pull the trial balance. The data gets exported into Excel. Columns are added for dollar change, percentage change, and explanation. The accountant filters for large movements, opens a separate tab to pull transaction detail for each flagged account, and starts writing.

The problem is not that NetSuite lacks the data. NetSuite’s Financial Report Builder can produce period-over-period comparisons, and saved searches can surface transaction-level detail by account, subsidiary, department, class, or location. The problem is that the explanation and review layer sits outside the system.

Once the export hits Excel, version control breaks down. One preparer downloads detail at 9:00 AM. Another pulls a refreshed report after a late journal entry posts at 1:00 PM. A reviewer comments on an explanation built on numbers that have since changed. The audit trail gets thinner with every handoff.

A stronger variance process keeps source data current rather than frozen at the point of export, preserves the native dimensions teams already use (subsidiary, department, location, class, vendor, customer), and makes evidence one click away rather than buried in a spreadsheet saved to someone’s desktop three days ago. Maxima’s native NetSuite integration addresses this directly, running flux analysis on top of NetSuite’s data model rather than alongside it in a spreadsheet.

What a better workflow looks like

What changes with agentic AI is that variance analysis no longer starts with a blank spreadsheet and a manual hunt for drivers. The work is prepared before the review begins. Material variances are already identified. Drivers are already broken down. Draft explanations are already written with supporting evidence attached. The accountant’s role shifts from assembling the analysis to evaluating it.

In practice, a controller opens to a list of accounts that have already been flagged. Data syncs directly from NetSuite and other ERPs and refreshes continuously, so flux analysis can begin before the books are fully closed. Materiality thresholds are configured by report and by account. Accounts that breach those thresholds are already waiting. The rest are documented and out of the way.

Instead of reconstructing why hosting expense moved 1.34 million, the controller opens to an explanation that already names the drivers, quantifies their impact, and ties the movement to specific transactions. “Hosting expense increased $1.34 million, driven by 1.37 million in retroactive Microsoft Azure billings for April through July posted in November” is an explanation a reviewer can act on. From there, the investigation happens inside the workflow. Last month’s explanation sits alongside the current one. Every number traces back to the underlying transactions, with direct links into the source system.

The workflow also surfaces what thresholds alone miss: accrual reversals without re-accruals, duplicate entries, round-number anomalies, and balances that changed after the analysis was prepared. Once the explanation is reviewed and approved, the audit trail captures each step. Every explanation follows a consistent structure regardless of who prepared it or how much time pressure they were under. The output is not generated text. It is prepared accounting work.

The goal is not to remove accountants from variance analysis. It is to remove the manual assembly work so they can focus on what actually requires judgment: validating the drivers, identifying real issues, and ensuring the financials tell the right story.

Variance analysis should not start with a blank spreadsheet. See how Maxima prepares explanations, traces movements to underlying transactions, and streamlines close review.

Frequently asked questions

How do you set materiality thresholds for variance analysis?

Use a dual threshold: a dollar amount and a percentage, with investigation triggered when either is exceeded. Common starting points are $25,000 or 10% for operating accounts, with tighter thresholds for revenue, payroll, and intercompany accounts. Set your internal thresholds slightly below the auditor’s materiality level so explanations are ready before audit fieldwork begins.

How do you write a good variance explanation?

A good explanation covers six fields: what account and period, what is the dollar and percentage variance, what is the root cause, what evidence supports it, who owns it, and does the variance recur. Avoid vague language like “timing differences” without specifying what the timing difference is. The test: a reviewer should be able to sign off without asking a follow-up question.

What evidence is needed to support a variance explanation?

It depends on the variance type. Revenue variances need contracts, invoices, and delivery documentation. Payroll variances need payroll registers and headcount reports. OpEx variances need vendor invoices, contract terms, and usage metrics. The evidence should be specific to the root cause and attached with the explanation, not after the reviewer asks for it.

What happens when a variance investigation reveals an error?

If investigation uncovers a posting error, a missed accrual, or a misclassification, a correcting journal entry is prepared and posted before the financial statements are finalized. The variance explanation should document both the error and the correction, including the JE reference. This is one of the most valuable functions of variance analysis: it serves as a detective control that catches errors before they reach external stakeholders.

Can variance analysis be done before the books are fully closed?

Yes, and teams that start early gain a significant advantage. Most accounts stabilize within the first day or two of close, and those variances can be investigated immediately. The risk is that late entries may change balances after explanations are written. The mitigation is a system that flags which accounts had post-flux balance changes, so preparers can update only the affected explanations rather than starting over.