How to prepare a clean compliance review pack

A review pack should make it possible for a qualified reviewer to understand the period without guessing what each file means. It is not a pile of attachments. It separates facts, evidence, calculations, assumptions and decisions needed.

Use it before a GST, TDS, income-tax or management review, but do not treat it as proof that a return is ready to file. Current requirements must be confirmed for the particular entity and period.

The first page should state:

• entity name and registration context, where relevant;
• period covered and the purpose of the review;
• preparer, preparation date and version;
• the systems or reports used; and
• the person authorised to approve any final submission.

This prevents a common error: reviewing the right report for the wrong entity or period.

Each key number should point to a report, schedule or document. A practical index looks like this:

Use stable file names, for example “A3_Bank-reconciliation_2026-03_v1”. Avoid names such as “final-final-new.xlsx”.

For every important total, retain a simple bridge:

Source total → adjustments or exclusions → reconciled total → unresolved difference

The reviewer should be able to see whether a difference is timing, an identified correction, an assumption or genuinely unexplained. Never hide a difference by changing the total without an audit trail.

An exception is not a failure. It is a transparent record of something not yet confirmed. Record:

• description and amount, if known;
• why it is open;
• evidence requested;
• the person responsible for answering; and
• whether the item blocks filing, needs judgement or can be followed up later.

Examples include an unreconciled bank entry, missing supplier invoice, disputed customer credit note, or a classification question. A reviewer can work efficiently only when these are visible.

Preparation, review and approval are different actions. A clean pack identifies who prepared the workings, who reviewed them and who has authority to approve a final filing or submission. Do not assume that sharing a spreadsheet means approval has been given.

Start with the index, summaries and redacted samples where possible. Do not send passwords, one-time passwords, API keys, portal credentials or unrelated personal information. Share additional records only through an agreed method and only when the reviewer needs them.

• One entity and one period are clearly stated.
• Key totals trace to source reports.
• Reconciliations show dated explanations for differences.
• Assumptions and open questions are visible.
• Sensitive data is minimised and credentials are excluded.
• The person who may approve a final action is identified.

General-information disclaimer: Filing dates, forms, classifications and evidence requirements can change. Confirm current requirements on the relevant official portal or with a qualified professional before taking action.