Variance Analysis Explanation Examples Your Auditors Will Accept

An auditor sampling your variance commentary reads one sentence and asks one question: can I check this without calling the preparer? Most commentary fails that test. "Revenue was higher due to strong sales" gives the auditor nothing to open, nothing to recompute, and nobody to ask.

This post collects variance analysis explanation examples in pairs, a weak version beside a strong one, so you can see what changes. It then states the four-part test behind the strong versions. If you review commentary for a living, you can apply the test to a draft in about a minute per line.

For the full process around these sentences (thresholds, decomposition, sequencing inside the close), see Flux Analysis: The Complete Guide for Accounting Teams and the glossary entry on variance analysis.

The four-part test

A variance explanation holds up when it carries four things:

1. Driver. The specific business event that moved the number: a contract signed, a price change, a headcount start, a one-time charge.
2. Amount. The dollar contribution of that driver, not the total variance alone. If two drivers explain a $90,000 swing, say how much each one accounts for.
3. Source. A document or system record a second person can open: a signed statement of work, an invoice number, a payroll register, a subledger report.
4. Owner. The person who confirmed the driver, typically the budget holder or the operator closest to the event.

Drop any one and the sentence turns into an assertion. The examples below show each failure.

Variance analysis explanation examples: weak and strong

1. Professional fees (expense, over budget)

Weak: "Professional fees were over budget due to higher legal costs."

Strong: "Professional fees were $42,000 over budget. Outside counsel billed $38,500 for the Q3 lease dispute (invoices 4471 and 4502, approved by the General Counsel) and $3,500 for unbudgeted contract review."

The weak version names a category. The strong version names the matter, splits the amount across two drivers, and cites two invoices.

2. Revenue (under plan)

Weak: "Revenue missed plan because of softer demand."

Strong: "Revenue was $210,000 below plan. Two enterprise renewals ($160,000 combined) slipped from September to October per the CRM close dates, and new-logo bookings in the mid-market segment came in $50,000 short. The VP of Sales confirmed both on October 3."

"Softer demand" cannot be checked. A CRM close date can.

3. Payroll (over budget)

Weak: "Payroll increased due to hiring."

Strong: "Payroll was $27,400 over budget. Three engineering hires started two weeks earlier than planned ($19,800, per the HR start-date report), and a $7,600 sign-on bonus for the Director of Operations was paid in the month it was budgeted for November."

The second driver is a timing difference, and the explanation says so. A reviewer then knows the variance reverses.

4. Cost of goods sold (margin)

Weak: "Gross margin declined because of higher costs."

Strong: "Gross margin fell 2.1 points. A freight surcharge added $64,000 to inbound costs from July onward (carrier notice dated June 28), and the new supplier price on SKU family B added $31,000. We have not yet confirmed whether the surcharge continues in Q4."

The last sentence is the strongest line in the explanation. It tells the reviewer what is still open, and auditors trust a preparer who writes it.

5. Prepaid and accrual balances (balance sheet)

Weak: "Accrued liabilities increased from the prior month."

Strong: "Accrued liabilities rose $118,000. Year-end bonus accrual added $90,000 (one-twelfth of the approved pool in the compensation committee memo) and unbilled contractor hours added $28,000 (timesheets through October 31, invoices not yet received)."

Balance sheet lines need the same four parts. The source here is a memo and a timesheet report instead of an invoice.

6. A variance with no explanation yet

Weak: "Marketing spend variance explained by timing."

Strong: "Marketing spend is $55,000 under budget. The trade show deposit scheduled for October was paid on November 2. I have asked the Marketing Director to confirm that no further October spend is outstanding; her answer is due Thursday."

Sometimes the driver is a guess until someone confirms it. Write the guess as a guess, name the person, and state the date. Never dress an open item as a resolved one.

Where preparers lose points

Four patterns account for most rejected commentary:

• Restating the number. "Expenses increased $50,000" repeats the variance column.
• Citing a category as a cause. "Higher legal costs" and "timing" are labels. They tell the reviewer where to look, not what happened.
• Skipping the second driver. If a $90,000 variance has two causes, an explanation that names one leaves the auditor to find the other.
• Using the passive voice to hide the owner. "It was determined that..." leaves the reviewer asking who determined it.

A faster way to apply the test

Run the four-part test as a checklist on every flagged line before the commentary goes to the reviewer. Mark each line with a check for driver, amount, source and owner. Any line missing a check goes back to the preparer.

Adopt's agents do the first pass of this work for finance teams: they compare periods, apply your thresholds, and draft an explanation with the source record attached. A person reviews each line, and nothing goes final without that sign-off. If you want to see how the drafts read against your own ledger, sign up free.

The sentences above take a human a few minutes each to write well. Tightening them is where a reviewer adds value, so spend the time there instead of on building the comparison.