Keep accounting evidence by transaction date: a Hong Kong archive review

Set the retention basis before sorting files

IRD’s Form BIR51 notes, section D, require sufficient records of income, expenditure, assets and liabilities to establish assessable profits. They state retention of at least seven years after the related transaction date, or until the corporation is dissolved if sooner. This guide addresses established Hong Kong trading corporations reviewing archives during normal operations. A folder’s creation date does not identify when its underlying transactions occurred.

Start the index from invoice dates and check the transaction dates evidenced by those invoices. Keep separate issue, transaction and payment date fields when they differ; ask the accountant to resolve ambiguity. Treat a calculated seven-year anniversary as a review marker. Do not turn it into an automatic deletion instruction or assume that scanning authorises destruction of the original.

Build an index another colleague can use

The worksheet below is a proposed operating control, not a statutory form. Give each transaction a stable reference connecting its ledger entry, documents and locations. Record missing evidence explicitly. A blank receipt field should explain whether payment is pending, the document is missing, or another identified record supports payment. Otherwise, a reviewer cannot distinguish an incomplete archive from an unfinished transaction.

A spreadsheet with controlled editing and a shared archive may suit a small accounts team. Maintaining links takes staff time, so name an owner and keep a usable index copy with the archive. Existing accounting attachments are another option if they preserve the references and retrieval access. Consider integration when repeated broken links, multiple editors or complicated payment matching make manual maintenance unreliable. Specify those failures before buying software.

Test a mixed-date archive

Consider this fictional purchase: goods and an invoice dated 18 November 2019, settled on 20 January 2020, with both records copied into a folder created in 2024. Assuming the purchase transaction date is confirmed as 18 November 2019, its seven-year review marker is 18 November 2026. The later payment needs its own date assessment. As a conservative operational choice, retain the connected packet through the later applicable review point and any continuing hold. The folder date answers neither question.

For a transfer covering several invoices, add a reconciliation showing the amount allocated to each invoice and explain any difference. Link the shared bank statement to every relevant entry. Before approving removal of a shared file, check every transaction it supports. During a retrieval test, a colleague should open the invoice, locate payment and explain the ledger amount without relying on the original bookkeeper’s memory. A file that exists but cannot be opened is a gap to resolve.

Review exceptions and assign the next action

IRD’s record-keeping guide says obligations continue after trading ceases. It also advises keeping loss records until seven years after the end of the year in which earlier losses have been fully set off. Cessation and corporate dissolution are different events; preserve the BIR51 dissolution qualification in the policy. Ask the accountant to assess loss-linked records and uncertain retention dates before approving a disposal batch.

As an internal control, record unresolved tax enquiries, disputes or adviser instructions as holds with named authorisers and review dates. Staff should see these before acting on an age-based report. Reviewers can document why a hold continues or who authorised its release, instead of leaving records indefinitely without an owner. The index organises evidence and decisions; it does not determine every legal obligation affecting a document.

Your next action is to select a small batch of older purchases, including a later payment and a shared bank statement, and complete the worksheet. Assign missing-document recovery to one person and retention questions to the accountant. Have a second colleague retrieve the packet, then record the result and next review date. If the trial exposes recurring systems problems, use those examples to scope integration work and define what a successful retrieval must demonstrate.