Industry News & Expert Tips
Financial Support Evidence and Documentation: Building an Auditable Basis for Conclusions
Practical audit procedures, evidence points, and documentation considerations for Hong Kong audit teams.
Practice Overview
Last updated: 16 September 2026
Financial support evidence is more than a collection of invoices, schedules and confirmations. For Hong Kong auditors, it is the traceable basis on which risk assessments, audit procedures and conclusions can be understood and evaluated. A sound file connects the matter being tested to the relevant financial statement assertion, identifies the source and period of the information, records the work performed, and explains how the result affects the conclusion. This is particularly important where records are dispersed across finance systems, group entities, service providers or management-maintained spreadsheets.
At a high level, HKSA 500 focuses on obtaining sufficient appropriate audit evidence, while HKSA 230 addresses documentation of the work performed, evidence obtained and conclusions reached. The practical objective is not to create volume for its own sake, but to preserve a clear, contemporaneous trail that permits an experienced auditor to understand significant matters and professional judgments. Where support is missing, inconsistent or received late, the team should reassess the evidence available and its effect on the planned audit response rather than simply treating the gap as a filing issue.
Key Audit Issues
Unsupported balances and transactions
A general-ledger balance or management schedule may appear plausible while lacking underlying records that demonstrate occurrence, completeness, accuracy, valuation, rights and obligations, or cut-off as relevant. The risk increases for material, unusual, manual or year-end transactions, estimates, related-party matters and balances derived from multiple systems. A file should distinguish what is management representation or explanation from the independent support that corroborates it.
Information produced by the entity
Reports, ageing analyses, reconciliations and spreadsheets are often central to the audit, but their usefulness depends on the relevance and reliability of the underlying information. Documentation can become weak when it retains a report without recording its purpose, source system, report parameters, population, key formulas or the work performed to evaluate it. The audit response should reflect how the information will be used and the risk addressed.
Insufficient linkage from risk to conclusion
Working papers may contain documents and tick marks but still fail to show why the procedure addressed the assessed risk, which assertion it covered, how exceptions were evaluated, or why the evidence supports the stated conclusion. This creates a documentation and review pitfall, especially when a conclusion is carried forward from a prior year or when several procedures collectively address one significant matter.
Conflicting or low-reliability evidence
Evidence from internal records, counterparties, banks, legal agreements and subsequent events may not agree. A common pitfall is to retain the favourable item without resolving the inconsistency or assessing the reliability of each source. Contradictions may indicate an error, a control weakness, an incomplete population or a need to modify the nature, timing or extent of further audit work.
Late support and reporting consequences
Requests for financial support made near completion can leave insufficient time to test the information, investigate exceptions or complete review. If sufficient appropriate evidence cannot be obtained, the matter is not resolved by a file note alone. The engagement team should evaluate the implications for the audit approach, communications and the auditor's report using the applicable requirements and the engagement facts.
Tailored Audit Procedures
Map significant matters to required support
For each significant balance, transaction stream, disclosure or judgment, identify the relevant assertions, assessed risks and the evidence expected to address them. Record the source, owner, period covered and the planned corroborating procedure. This evidence map helps the team identify missing support early and prevents a schedule from being accepted merely because it agrees to the general ledger.
Evaluate entity-produced reports and schedules
Where a client-generated report or spreadsheet is used, understand its origin and purpose and test the aspects relevant to the audit use. Depending on the risk, this may include agreeing report parameters to source records, testing selected data fields to underlying documents, assessing the completeness of the population, reperformance of key formulas and documenting version control.
Inspect and corroborate underlying documentation
Select items using a method responsive to the risk and inspect relevant agreements, invoices, delivery or service evidence, bank records, board approvals, correspondence or other primary records. Where appropriate, corroborate internally generated information with external evidence or independent sources, and document the attributes tested as well as the results.
Test completeness and period-end cut-off
Use reconciliations, sequence checks, post-year-end transactions, subsequent receipts or payments, and other relevant searches to identify items omitted from the financial records or recorded in the wrong period. Investigate reconciling items and exceptions rather than relying solely on management's explanation, and retain evidence showing how the population and period tested were established.
Reperform key calculations and analyse anomalies
Recalculate material amounts, allocations, ageing, interest, foreign-currency translation or other relevant computations from the agreed inputs. Compare relationships and movements with expectations developed from the entity's business and financial information. Document the expectation, threshold for follow-up, explanations obtained, corroboration performed and the conclusion on significant variances.
Resolve evidence gaps and document the conclusion
For missing, late or contradictory support, identify the affected assertion and population, perform additional or alternative procedures where feasible, and evaluate exceptions individually and in aggregate. The working paper should record the procedure performed, evidence obtained, professional judgment applied, consultation or review where relevant, and the effect on the conclusion. If a limitation remains, escalate it within the engagement process and consider its implications under the applicable auditing requirements.
Controls and Evidence to Consider
Controlled source records and retention
Maintain identifiable source records for material transactions and balances, with document dates, counterparties, approvals and retention arrangements. A controlled repository or records process should preserve the link between the accounting entry and its underlying support and restrict unauthorised alteration or deletion.
Periodic reconciliations with documented review
Prepare timely reconciliations between subledgers, bank records, operational systems and the general ledger, with evidence of preparer and reviewer actions. Reconciling items should be described, investigated and cleared or tracked through resolution rather than rolled forward without explanation.
Report governance and spreadsheet discipline
For reports and spreadsheets used in financial reporting, retain the report logic, extraction parameters, version, key assumptions and evidence of review. Controls over master data, user access, manual journals and changes to formulas or inputs can strengthen the reliability of information produced by the entity.
Transaction authorisation and independent corroboration
Material or unusual transactions should have documented business purpose, delegated approval and support such as contracts, counterparties' records, bank evidence or board documentation, as relevant. A clear audit trail and independent corroboration help demonstrate that recorded amounts are valid, complete and recorded in the appropriate period.
Related Reading
Apply Technical Insight to Your Audit Workflow
EQC can discuss audit-quality priorities, documentation, inspection readiness, and Audit Program 4.1 (AP4.1) workflow support relevant to your practice.