An analytical review in auditing is a procedure where the auditor evaluates whether reported financial figures are plausible by comparing them against an independent expectation built from prior-period data, ratios, industry benchmarks, or non-financial information like headcount and production volume. When the reported number and the expectation are close, the balance looks reasonable. When they diverge beyond a set threshold, the auditor investigates. Public Company Accounting Oversight Board standards require these procedures at multiple points in every audit of a public company.
The Logic Behind the Procedure
Financial data follows predictable patterns. Payroll tracks headcount. Shipping costs track sales volume. Interest expense tracks outstanding debt. When one of those relationships breaks, it doesn’t automatically mean an error or fraud, but it means the number deserves a closer look.
PCAOB standards describe analytical procedures as “evaluations of financial information made by a study of plausible relationships among both financial and nonfinancial data” and note that those relationships “may reasonably be expected to exist and continue in the absence of known conditions to the contrary.”1Public Company Accounting Oversight Board. PCAOB AU Section 329A – Analytical Procedures Things that might break the pattern include unusual transactions, changes in accounting method, business expansion, or misstatement.
The comparison is always between the reported figure and an expectation the auditor develops independently. That expectation might come from prior-year trends, industry data, budget forecasts, or a calculation built from operational information.2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures The auditor measures the gap. If it falls inside an acceptable range, the balance looks fine. If not, the investigation begins.
Techniques Auditors Use
There isn’t one method. The choice depends on the account, the data available, and how much assurance the auditor needs.
Trend Analysis
The most straightforward approach. The auditor compares a current-period balance to the same balance from one or more prior periods and looks for changes that stand out against the historical pattern. A repair expense account that grew 5% annually for four years and then jumped 40% is an obvious target. The spike may have a good explanation, like a major equipment failure, but the auditor still needs to find out.
Trend analysis works best for accounts with a stable history. It’s less useful for newer business lines or accounts that swing with market conditions, because the baseline itself is unreliable.
Ratio Analysis
Ratio analysis adds context by measuring relationships between accounts and comparing those ratios to three benchmarks: the company’s own prior periods, industry averages, and internal budgets. Common categories include liquidity, profitability, and leverage ratios.
A 42% gross profit margin at a company where the industry average is around 35% doesn’t necessarily signal trouble. The company may genuinely outperform its peers. But the gap needs an explanation, because it could also mean cost of goods sold is understated, which would inflate profits. A debt-to-equity ratio far above industry norms similarly reveals whether a company carries unusual leverage, which affects risk assessments throughout the audit.
Reasonableness Tests
Reasonableness tests are the most persuasive technique because the auditor builds the expected balance from scratch using non-financial data that sits outside the accounting system. The textbook example: estimate total payroll by multiplying average headcount by average pay rate by the number of pay periods, then compare that estimate to the payroll expense on the income statement.
Because the inputs come from operational data rather than the general ledger, it’s harder for an accounting error to hide. If the calculated estimate is $4.2 million and the reported figure is $4.8 million, that $600,000 gap could point to unrecorded termination payments, an incorrect bonus accrual, or ghost employees. The auditor sets a threshold in advance for how much deviation is acceptable before deeper testing kicks in.
When Analytical Procedures Happen in an Audit
PCAOB standards require analytical procedures at three distinct points. The purpose shifts at each stage.
Planning
At the start of every audit, the auditor performs analytical procedures to understand what has changed since last year and to spot areas where the risk of misstatement is highest. PCAOB AS 2110 requires these procedures to enhance the auditor’s understanding of the client’s business and to “identify areas that might represent specific risks relevant to the audit, including the existence of unusual transactions and events, and amounts, ratios, and trends that warrant investigation.”3Public Company Accounting Oversight Board. AS 2110 – Identifying and Assessing Risks of Material Misstatement
The analysis at this stage is deliberately broad. An auditor might notice that accounts receivable ballooned while the allowance for doubtful accounts stayed flat, suggesting the company may not be writing off bad debts appropriately. That one observation can shape the rest of the audit plan by flagging receivables valuation as a high-risk area needing detailed testing.
Substantive Testing
During fieldwork, auditors can use analytical procedures as substantive evidence about whether specific account balances are fairly stated. Interest expense is the classic example. If you know a company’s outstanding loan balances and interest rates, you can calculate what interest expense should be with high precision. When the calculated figure closely matches the reported figure, the auditor may reduce or skip transaction-level testing for that account.
This approach works when the relationship between inputs and the expected output is tight and predictable. It’s less appropriate for accounts driven by management judgment, like warranty reserves, where the underlying assumptions are harder to verify independently. AS 2305 requires the expectation to be “precise enough to provide the desired level of assurance that differences that may be potential material misstatements, individually or when aggregated with other misstatements, would be identified.”2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
Final Review
After all audit adjustments are posted, the auditor steps back and performs one last analytical review of the financial statements as a whole. The goal is to confirm the audited numbers make sense together and that fieldwork adjustments haven’t created new inconsistencies. PCAOB AS 2810 requires the auditor to “read the financial statements and disclosures and perform analytical procedures” to evaluate whether the financial statements are free of material misstatement.4Public Company Accounting Oversight Board. AS 2810 – Evaluating Audit Results
The same standard requires the auditor to assess whether any “unusual or unexpected transactions, events, amounts, or relationships indicate risks of material misstatement that were not identified previously, including, in particular, fraud risks.”4Public Company Accounting Oversight Board. AS 2810 – Evaluating Audit Results It’s a safety net. An auditor who spent weeks inside individual accounts might miss a forest-level problem visible only when looking at the whole picture. A reported net income that doesn’t align with expected tax expense at the 21% federal corporate rate, for example, could reveal a missed adjustment.
Building the Expectation and Setting a Threshold
The quality of an analytical review depends entirely on the quality of the expectation. A vague assumption that “revenue should be about the same as last year” is nearly useless. A calculation that estimates revenue by product line using unit volumes from shipping records and average selling prices from executed contracts is far more powerful, because each input can be verified independently.
AS 2305 identifies five categories of data that feed into well-developed expectations:2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
- Prior-period financials, adjusted for known changes in the business
- Budgets and forecasts, including extrapolations from interim results
- Within-period relationships between accounts, like sales and commissions
- Industry data, such as published gross margin averages for the sector
- Non-financial data such as headcount, production volume, or occupied square footage
Before running the procedure, the auditor also sets a threshold for how much difference can exist between expected and reported before investigation kicks in. Materiality drives that number. A $50,000 variance in a $200 million revenue account probably falls within noise. The same $50,000 variance in a $300,000 expense account is a different story. The more precise the expectation, the narrower the acceptable range, and the more likely a real misstatement will surface.2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
What Happens When the Numbers Don’t Match
When the gap between the expected and reported figure exceeds the threshold, the investigation follows a sequence. The auditor first reconsiders whether the expectation itself was built correctly, checking the methods, data sources, and assumptions used. Flawed inputs produce flawed expectations, so ruling out auditor error comes first.
The next step is asking management to explain the difference. This is where many audits go wrong, by accepting the explanation at face value. AS 2305 is explicit that “management responses should ordinarily be corroborated with other evidential matter.”2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures If management says the spike in repair costs was due to a storm, the auditor needs insurance claims, work orders, or vendor invoices that confirm the story. A verbal explanation alone doesn’t meet the standard.
When no satisfactory explanation emerges, the standard requires the auditor to “obtain sufficient evidence about the assertion by performing other audit procedures to satisfy himself as to whether the difference is a misstatement.”2Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures Unexplained differences at this stage carry elevated risk of material misstatement and may trigger expanded testing across related accounts.
Fraud Detection and Revenue
Analytical procedures play a specific role in identifying fraud, and revenue recognition is consistently the highest-risk area. PCAOB AS 2401 directs auditors to consider performing “substantive analytical procedures relating to revenue using disaggregated data, for example, comparing revenue reported by month and by product line or business segment during the current reporting period with comparable prior periods.”5Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit
Disaggregation matters because fraud often hides in the aggregate. A company’s total annual revenue might look reasonable against the prior year, but breaking it down by month can reveal an unusual concentration of sales in the final week of the reporting period, a classic pattern of channel stuffing. Comparing gross profit margins by location or segment can expose a single division where margins are suspiciously high or moving opposite to the rest of the company.5Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit
Analytical procedures alone are rarely enough to detect fraud. Common weaknesses in audit failures include relying on analytics as the sole test for revenue, using vague expectations without a quantitative basis, and accepting management’s explanations for variances without corroboration. An auditor who says “the revenue increase is consistent with management’s expectation of growth” without checking that claim against contracts, shipping data, or industry trends has not actually performed a procedure.
What the Technique Can’t Do
Analytical review is efficient, but it has real boundaries. The technique is designed to catch misstatements large enough to distort a financial relationship. Small errors spread across thousands of transactions won’t move a ratio or break a trend, so they pass through undetected. That’s by design; analytical procedures are a net for big fish, not a filter for every minnow.
The method also struggles when the underlying relationship between data points is weak or unpredictable. Estimating interest expense from known debt balances and rates produces a tight, reliable expectation. Estimating warranty expense from historical claim rates is looser because the inputs involve more judgment. The weaker the relationship, the wider the acceptable range needs to be, and the less likely the procedure will catch a misstatement that falls within that range.
Analytical procedures also depend on the reliability of the data feeding the expectation. If the auditor builds an expected payroll figure using a headcount number provided by management, and that headcount is wrong, the expectation is wrong too. Using data from sources independent of the accounting system, like third-party shipping records or publicly available industry reports, strengthens the procedure significantly. An expectation built entirely from the client’s own unverified data is circular and provides very little assurance.