How engagement quality review and final analytical procedures challenge significant judgments before the audit report is issued.
Near the end of an audit, the engagement team must step back from detailed testing and ask whether the overall conclusion is supported. Engagement quality review and final analytical procedures serve different purposes, but both help prevent unsupported reporting decisions. One is an independent quality-control review of significant judgments; the other is a final reasonableness review of the financial statements as a whole.
AUD questions often test that these procedures are concluding procedures, not substitutes for required substantive testing. If final analytics reveal an unexpected relationship, the auditor investigates before issuing the report.
flowchart LR
A["Complete major audit areas"] --> B["Aggregate findings"]
B --> C["Perform final analytics"]
B --> D["Engagement quality review"]
C --> E["Resolve open issues"]
D --> E
E --> F["Finalize report conclusion"]
An engagement quality review, when required by firm policy or standards, is performed by a qualified reviewer who is not part of the engagement team. The reviewer evaluates significant judgments and conclusions before the report is released.
| EQR focus | What the reviewer evaluates |
|---|---|
| Independence and acceptance | Whether acceptance, continuance, and independence issues were resolved |
| Significant risks | Whether responses to fraud and other significant risks were appropriate |
| Materiality | Whether materiality and performance materiality were reasonable |
| Significant judgments | Estimates, related parties, going concern, specialists, and complex accounting |
| Misstatements | Corrected and uncorrected misstatements and reporting effects |
| Communications | Required communications with management and governance |
| Report | Whether the proposed report is appropriate |
The reviewer does not reperform the entire audit. The reviewer evaluates whether the engagement team’s significant judgments are supported by the evidence and whether unresolved matters remain.
Final analytical procedures are required near the end of the audit to help the auditor form an overall conclusion about whether the financial statements are consistent with the auditor’s understanding of the entity. They are usually performed at a high level, using financial statement relationships, ratios, trends, budgets, and industry data.
| Final analytic | Possible audit question |
|---|---|
| Revenue trend vs. gross margin | Do sales and margins make sense together? |
| Current ratio and debt covenant trend | Is liquidity consistent with going-concern conclusions? |
| Payroll expense vs. headcount | Does expense align with operational data? |
| Interest expense vs. debt balances | Is financing cost reasonable? |
| Inventory turnover | Does inventory valuation or obsolescence risk remain? |
| Tax expense vs. pretax income | Is the tax result plausible? |
Final analytics are not performed to obtain detailed evidence over every account. They are used to identify unusual or unexpected relationships that may require additional procedures before the report date.
EQR, final analytics, and misstatement aggregation interact. The auditor should not finalize the report while significant review notes, unexplained analytical differences, or unresolved misstatements remain.
| Closing issue | Required response |
|---|---|
| EQR challenge to an estimate conclusion | Provide additional support, revise conclusion, or perform additional work |
| Unexpected final analytical relationship | Investigate and corroborate management explanation |
| Uncorrected misstatements near materiality | Reevaluate aggregate and qualitative materiality |
| New going-concern concern | Revisit management plans, disclosure, and report language |
| Inconsistent disclosures | Correct disclosure or consider reporting effect |
The final stage is not administrative cleanup. It is where the audit team verifies that the evidence, financial statements, disclosures, communications, and report all align.
Documentation should show the final review trail. For EQR, the file should identify the reviewer, matters reviewed, questions raised, responses, and completion before report release when required. For final analytics, the file should show expectations, recorded results, differences, explanations, corroborating evidence, and conclusions.
If an issue is identified late, the auditor documents the additional procedures performed and how the issue was resolved. A conclusion such as “no issue noted” is weak unless the workpaper shows what was compared and why the result was reasonable.
Do not say EQR is performed by the engagement partner as a self-review. The reviewer must be sufficiently objective and qualified.
Do not treat final analytical procedures as optional. They are part of the concluding stage.
Do not use final analytics as a substitute for substantive testing in high-risk areas.
Do not issue the report with unresolved EQR questions or unexplained analytical anomalies.