When the Inland Revenue Department (IRD) opens a field audit or investigation, the difference between a manageable review and a multi-year dispute is usually the first thirty days. Hong Kong's tax system runs on self-assessment with limited pre-lodgement scrutiny, which is why the Department places weight on information gathered after returns are filed. Field audits, sometimes called "field audits and investigations," are the IRD's primary tool for testing whether the profits tax, salaries tax, or property tax figures a taxpayer reported match the underlying records.

What triggers an IRD field audit or investigation

The IRD does not audit at random. Three patterns tend to bring a desk enquiry to a field visit:

None of these triggers mean a problem exists. They mean the Department wants to look more closely, and how you respond shapes what they find.

The seven-year records duty

Once a field audit begins, the IRD will issue information-gathering notices requiring production of books and records. Hong Kong taxpayers have a statutory duty to keep sufficient records to enable the Department's verification, and the baseline retention period is seven years from the end of the transaction year. The duty covers:

Records may be kept in paper or electronic form, provided they remain accessible, legible, complete, and capable of being reconstructed on request. A scanned PDF of a paper original is treated as equivalent to the original if it is legible and unaltered. Records kept outside Hong Kong in electronic form are acceptable if they can be produced within a reasonable time when requested.

Information-gathering powers in practice

The IRD's information-gathering notices are the engine of every field audit. In broad terms, the Department can require the taxpayer to:

These notices are administrative rather than judicial, but compliance is not optional. Producing records in a structured way, indexed to the notice's requests, shortens the review and reduces the scope of follow-up questions. Producing records in an unstructured way — bulk folders, unlabelled PDFs, mixed personal and business material — extends the review and increases the chance the Department forms an unfavourable view.

First-thirty-days response playbook

The opening month sets the tone. A practical sequence:

Days 1–5: triage and scope. Read the notice carefully. Identify the tax years, tax types, and transaction categories in scope. Confirm the deadline and the delivery format the IRD expects. Do not volunteer material outside the notice at this stage.

Days 5–15: assemble, do not dump. Pull records into a structured set: financial statements, general ledger, source documents, payroll records, and tax working papers, indexed by year and category. A clean index now saves months later.

Days 15–25: written explanations. For positions the notice challenges, prepare concise written explanations with documentary support. Quantify adjustments before the Department quantifies them for you.

Days 25–30: representation decision. Decide whether the matter warrants professional representation before the next deadline. Once representation is engaged, communications route through that channel.

When to engage professional representation

A short desk enquiry on a single transaction can often be handled in-house. A field audit involving multiple years, transfer pricing, or allegations of under-statement is a different matter. Representation should be considered where the review covers more than two years of accounts, where the IRD has raised questions about tax residence or transfer pricing, where penalties are likely to be in issue, or where personal exposure for directors is foreseeable.

Penalties posture: the s.80 route exists

The Department has a statutory route for serious cases. The mechanics allow the Department to initiate proceedings in respect of wilful or reckless mis-statements, with exposure including a financial penalty and a treble charge mechanism for under-stated amounts. The mechanism is a tool the Department holds; engagement in the field audit is the stage at which the Department's view of the taxpayer's honesty is formed. Clear records, prompt responses, and credible explanations influence whether that route is taken.

Keeping the next audit short

The strongest defence against a long audit is a record-keeping system that survives contact with the IRD. Records kept in one defined location, backed up off-site, independent of any single employee or device, and indexed to retention end dates are easier to produce. Records kept only on one laptop, in one email inbox, or in one manager's head are harder to produce, and harder to defend.

Bring your bookkeeping under control

If you are running a Hong Kong business and want a structured way to keep books, retain records for the right period, and be ready when the IRD opens a review, CompanyForge bookkeep can help. It is currently invite-only via a waitlist, with concierge onboarding for each accepted account so the setup reflects how your business actually operates. Join the waitlist and we will work with you through setup: https://companyforge.ai/bookkeep/

CompanyForge · Bookkeep

Put this guide into practice

Bookkeep is currently invite-only beta with concierge onboarding. Join the waitlist and we will map your entity structure before setup begins.

CompanyForge · ForgeOps Compliance

Never miss another statutory deadline

ForgeOps tracks NAR1, Business Registration renewal, and every other recurring HK filing across every entity you control — with holiday-roll-aware alerts sent before the window closes, not after.