Preliminary Analytical Procedures: Building a Stronger Risk Assessment
EQC video briefing · Supporting source
Audit Quality: Connect Risk, Procedure, Evidence and Conclusion
Strong audit documentation tells one connected story. This video shows how assessed risks should lead to responsive procedures, persuasive evidence and a properly supported conclusion. It highlights the importance of professional judgement, appropriate challenge, timely review and clear working papers so that an independent reviewer can understand the audit trail.
Preliminary analytical procedures help Hong Kong auditors turn financial and non-financial information into a focused understanding of where material misstatement risks may arise. Used as part of the risk assessment process contemplated by HKSA 315, they can reveal unexpected movements, relationships or inconsistencies that warrant further inquiry, while also helping the team develop a clearer engagement-specific audit strategy.
The quality risk is not simply failing to calculate a ratio or compare two periods. It is failing to show how reliable data, informed expectations, investigated results and the understanding of the entity and its controls led to the assessed risks and tailored audit responses. This article is general professional technical education for Hong Kong auditors; teams should apply professional judgment and consult current authoritative standards and source material in the circumstances of each engagement.
Key Audit Issues
Analytical work is absent or performed too late
Where preliminary analysis is omitted, or is prepared only after risks and audit responses have already been selected, the team may miss changes in operations, financing, margins, liquidity, estimates or reporting patterns that should inform risk identification. The working papers may then appear to be a retrospective compliance exercise rather than evidence of a risk assessment that drove planning.
The data population is not demonstrably reliable
Trend and ratio analysis is only as persuasive as the data used. Unreconciled management reports, changing chart-of-account mappings, incomplete non-financial measures or inconsistent comparative periods can create misleading movements and obscure genuine anomalies. The audit file should make clear what information was used and how its suitability for the analysis was considered.
Expectations are generic rather than entity-specific
A comparison with the prior year alone may be too shallow when the entity has changed products, markets, pricing, systems, financing, accounting policies or operating capacity. Generic benchmarks can lead to unexplained differences being dismissed and predictable business drivers being overlooked. Expectations should reflect the entity’s business model, reporting framework and information available at the planning stage.
Unusual relationships are not investigated or corroborated
Management explanations for unexpected results are useful starting points, but unsupported explanations do not resolve an audit implication. Broad or highly aggregated analysis can also conceal offsetting movements. Without focused follow-up and corroboration where appropriate, the team may understate risks at the financial statement or assertion level and design responses that do not address the source of the variation.
Risk assessment, controls understanding and audit response are disconnected
Documentation is vulnerable when it records analytics, control narratives, risk assessments and detailed procedures in separate silos. A reviewer should be able to trace significant results to the relevant risks, relevant assertions, understanding of controls and the nature, timing and extent of the planned work. Information obtained later in the audit should also prompt reconsideration when it affects the initial assessment.
Tailored Audit Procedures
Establish a dependable analytical base
Obtain the trial balance and other relevant financial and non-financial information for the current and comparative periods. Reconcile or otherwise agree the information used for the analysis to appropriate underlying records, and record material limitations, reclassifications or changes in the basis of preparation before drawing conclusions.
Refresh the understanding of the entity and its environment
Discuss significant developments with management and relevant personnel, including changes in strategy, revenue sources, key suppliers or customers, funding, systems, estimates, controls and external conditions. Read available governance or management information where relevant, and use that understanding to identify meaningful financial and operational drivers for the analysis.
Develop and document reasoned expectations
Build expectations using information that is relevant to the entity, such as prior-period results adjusted for known changes, budgets, volumes, headcount, contractual terms, capacity, pricing or other drivers. Select comparisons and levels of disaggregation that are capable of revealing matters relevant to the financial statements, rather than relying on standard ratios without considering their relevance.
Perform focused trend and relationship analysis
Compare amounts, ratios and relationships across periods and, where useful, by month, location, product, customer group, revenue stream or account. Identify unexpected or inconsistent movements, including results that conflict with the auditor’s understanding of the entity, and preserve the calculations and source data in the audit file.
Investigate anomalies and assess their audit implications
Make targeted inquiries about significant differences, evaluate the plausibility of explanations and obtain corroborating information when appropriate. Consider whether the result indicates a risk of material misstatement, a relevant control issue, a potential fraud-risk factor or a need to revise the auditor’s understanding, and identify the financial statement areas and assertions affected.
Translate findings into a tailored audit plan and revisit them
Link the conclusions from the preliminary analysis to assessed risks and to the planned nature, timing and extent of further audit procedures. Update the analysis and risk assessment when new information conflicts with the initial understanding or indicates a changed risk, and ensure any technology-assisted workflow, including Audit Program 4.1 (AP4.1) if used, remains subject to auditor judgment and review.
Controls and Evidence to Consider
Traceable source-data record
Retain the trial balance, reports and non-financial data used, together with reconciliations, extraction dates, relevant mappings and explanations of significant data limitations. This provides a clear basis for assessing whether the analysis was prepared from suitable information.
Reproducible expectation and calculation schedule
Document the periods compared, benchmarks or business drivers selected, methods, calculations, thresholds for follow-up and significant judgments. The schedule should allow an experienced reviewer to understand how expectations were developed and why the selected analysis was relevant.
Exception-resolution trail
Maintain a clear record of unexpected movements, inquiries made, management explanations, corroborating information considered and the resulting conclusion. Cross-reference each significant exception to any affected risk assessment, controls understanding or planned audit response.
Review and linkage evidence
Use a risk-assessment workpaper or equivalent documentation that connects preliminary analytics to identified risks, relevant assertions and the audit plan, with evidence of timely preparer and reviewer consideration. Where Audit Program 4.1 (AP4.1) is used, retain the relevant output and evidence of auditor review, adaptation and approval rather than treating system-generated content as a substitute for judgment.
Related Reading
Practical compliance support
Turn insight into practical next steps
Speak with EQC about audit quality, quality management, AML / CTF compliance, inspection readiness, technical documentation, or Audit Program 4.1 (AP4.1) workflow support for your practice.