Industry News & Expert Tips
Cut-Off Tests and Invoice Evidence: Building a Defensible Audit Response Under HKSA 330
Practical audit procedures, evidence points, and documentation considerations for Hong Kong audit teams.
Practice Overview
Last updated: 16 September 2026
Cut-off testing is more than comparing dates on a ledger and an invoice. Around the reporting date, auditors need to understand the entity’s transaction flows and identify the event that determines recognition under the applicable accounting framework—for example, the transfer of control of goods or services for revenue, or the receipt of goods or services and the resulting obligation for purchases and expenses. An invoice may corroborate amount, counterparty and terms, but its issue date or subsequent settlement date will not necessarily establish the correct accounting period. The risk is heightened where operations involve dispatches, returns, milestones, consignment arrangements, manual journals, late supplier invoices or decentralised records.
Inadequate cut-off work can leave material overstatements or understatements unaddressed and can make the audit file difficult to review because the link from the assessed risk to the procedure, evidence, exceptions and conclusion is unclear. At a high level, HKSA 330 requires responses designed and implemented for assessed risks of material misstatement; the nature, timing and extent of cut-off work should therefore be tailored to the relevant assertions and the entity’s process. This article is general professional technical education for Hong Kong auditors, not engagement-specific audit, legal, tax or regulatory advice.
Key Audit Issues
Recognition trigger is confused with invoice timing
An invoice date, credit-note date or cash receipt may differ from the event that drives recognition. For each material transaction stream, the audit team should identify the relevant accounting trigger and the business evidence that records when it occurred, applying the entity’s contracts, delivery terms and accounting policies rather than treating one date field as conclusive.
One-sided testing misses the related misstatement risk
Revenue cut-off may affect receivables, contract balances, inventory or cost of sales; purchase cut-off may affect payables, accruals, inventory or expenses. A file that tests only sales invoices, or only the accounts-payable ledger, may not address the reciprocal entries or the completeness risk from goods and services received but invoiced later.
Year-end samples are not responsive to the process
Selecting a fixed number of transactions immediately before and after year end without explaining coverage, volume, control frequency, lead time or unusual activity may not respond to the assessed risk. The selection window and extent should reflect how long transactions normally take to progress from the underlying event to recording and the characteristics of the population.
Source evidence is relevant to amount but not timing
Invoices can be internally generated, prepared in advance or processed after the underlying event. More persuasive timing evidence may instead include customer acceptance, dispatch or delivery records, bills of lading, service-completion records, goods-received notes, supplier statements, system time stamps or third-party correspondence, assessed in the context of the transaction.
Exceptions and conclusions are poorly documented
A tick mark or a list of documents does not explain how the evidence supports the period recorded. Missing cross-references to the population, attributes tested, dates observed, inconsistencies identified, management explanations, follow-up work and the final evaluation can prevent a reviewer from understanding whether sufficient appropriate evidence was obtained.
Tailored Audit Procedures
Understand the end-to-end process and the recognition point
For significant revenue, purchasing and other relevant cycles, perform inquiries and walkthroughs to map initiation, fulfilment or receipt, invoicing, journal posting, returns and subsequent adjustment. Identify the systems, responsible personnel, reports and documents that capture each date, and compare the recorded accounting policy with contractual terms and the applicable financial-reporting requirements.
Build a risk-responsive year-end population
Obtain or prepare a population that spans an appropriate period before and after year end and reconcile it, where appropriate, to the general ledger and relevant operational records. Use the entity’s operating cycle, transaction volume, processing lag, manual intervention, unusual patterns and assessed risks to determine the selection window and extent; document why these choices are appropriate.
Test revenue cut-off in both directions
Select entries recorded immediately before and after year end and trace them to invoices and to evidence of the underlying performance or transfer event, such as dispatch, delivery, acceptance or service-completion records. Where appropriate, also select operational events from the same period and trace forward to accounting entries, assessing whether the date recorded accords with the entity’s recognition policy and relevant terms.
Perform a targeted search for unrecorded liabilities and expenses
Inspect selected post-year-end payments, supplier invoices, supplier statements, unmatched receiving records and other relevant evidence, then trace back to the underlying goods or services and the year-end ledger or accrual. Evaluate whether obligations arising before year end were recorded in the appropriate period and whether the evidence supports the amount and classification.
Test relevant cut-off controls when reliance is planned
Where the audit approach includes reliance on controls, test the design and implementation and, as relevant, operating effectiveness of controls over sequential document numbering, dispatch or receiving confirmation, invoice matching, period-close review and approval of manual cut-off adjustments. Consider control deviations in determining the effect on substantive procedures and the audit response.
Investigate exceptions and complete the audit trail
For mismatched dates, missing documents, late entries, unusual credit notes or manual journals, obtain corroborative evidence, evaluate management’s explanation and quantify or project the effect where appropriate. Record the item selected, source and reliability of evidence, work performed, results, professional judgements, exceptions, follow-up and conclusion, with clear cross-references to related misstatement evaluation.
Controls and Evidence to Consider
Documented recognition and cut-off rules by transaction stream
Management can maintain approved accounting policies, process narratives and contract-term guidance that specify the operational event used for recognition in each material stream. Evidence may include current policies, standard terms, responsibility matrices and period-end instructions reconciled to actual system configurations.
Sequential and independently reviewed fulfilment or receiving records
Controls over pre-numbered dispatch notes, delivery acknowledgements, goods-received notes and service-completion records can support completeness and timing when exceptions are investigated. Retain the sequential reports, exception logs, reviewer sign-off and underlying third-party or system-generated records.
Disciplined period-close matching and reconciliation
A close checklist can require reconciliation of operational cut-off reports to sales, purchases, inventory, receivables, payables and relevant accruals, with review of unmatched items and cut-off journals. Useful evidence includes dated reconciliations, journal support, preparer and reviewer identification, and documented resolution of differences.
Late-invoice and subsequent-payment review
A structured review of supplier invoices received after year end, payments made after year end and open receiving records can help identify pre-year-end obligations not yet recorded. Preserve the population, selection criteria, invoice and payment references, links to receiving or service evidence, assessment of recognition date and approvals for resulting adjustments.
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.