Preparing a clear chronology for a tax dispute

A clear tax-dispute chronology should connect each event to its evidence and explain why the date matters. Separate agreed facts, disputed facts and the taxpayer’s interpretation so an adviser can assess the case without untangling a narrative from scattered emails.

Use neutral descriptions and preserve inconsistencies for review. Include decisions, submission dates, payments and requests for extensions, not only events favourable to the case.

Begin with the disputed issue and relevant period

State the question the chronology needs to help resolve, such as when income arose, who owned an asset or whether a response was made in time. Identify the taxpayer, tax and periods concerned. HMRC checks can involve different returns, accounts and records, so a useful chronology needs a defined scope. ^[1] It should not become a life history containing events with no connection to the actual dispute.

Write a short issue statement, then list the categories of evidence available: contracts, invoices, bank records, returns, letters and call notes. This gives the preparer a starting map before dates are entered. If several issues overlap, label them separately so the same event can be linked to more than one question without being duplicated inconsistently in different versions of the narrative.

Separate transaction events from procedural events

Record the underlying commercial or personal events independently from the later tax process. For a disposal, that might include agreement, completion, payment and transfer of ownership. For the enquiry, it includes return submission, HMRC requests, responses, decisions and review steps. These dates serve different purposes and should not be collapsed into the day the taxpayer first discussed the issue with an adviser.

Use columns for event date, description, parties, evidence reference and relevance to the disputed point. Where the date is uncertain, mark the range or uncertainty and explain its source. Do not assign the date of a bank payment to a contract merely because the signed document is missing. A chronology should expose evidential gaps for review, not conceal them behind apparently precise but unsupported entries.

Distinguish evidence from interpretation

Describe what the source shows in neutral terms, then place any interpretation in a separate column or adviser note. A contract may record an agreed obligation, while a later email suggests how the parties understood it; neither should be rewritten to match a preferred conclusion. If documents conflict, include both and identify the inconsistency. This allows the adviser to assess the evidence rather than discover omitted material later.

Mark recollections and later reconstructions explicitly. Identify who supplied the account, when it was recorded and whether the person had direct knowledge. Avoid presenting a collective business memory as though every participant independently confirmed it. If a fact is agreed with HMRC, link to the correspondence establishing that agreement. A point discussed informally but not accepted should remain labelled as disputed or unconfirmed.

Connect the chronology to figures and deadlines

For monetary events, include the amount, currency and relevant calculation reference without turning the chronology into a replacement ledger. Where timing affects a return figure, link the event to the schedule explaining the treatment. For procedural entries, record issue and receipt dates and the required action separately. Keeping a timeline of HMRC correspondence describes the correspondence register that can support this part of the chronology.

Keep deadline calculations subject to appropriate review. An event's significance may depend on the particular tax procedure or document, so do not infer that every letter allows the same response period. If an extension was agreed, include the evidence and its precise scope. This helps the adviser distinguish a genuine missed deadline from a misunderstanding about which obligation a particular date concerned.

Produce a concise review version with a complete index

Arrange entries in date order and use stable document references. Keep the full evidence in an indexed folder, with a shorter chronology containing the events material to the dispute. Do not remove unfavourable events simply to make the summary shorter. Instead, explain their relevance and allow the adviser to decide how they affect the assessment. A balanced chronology is a tool for finding the true position, not an argument assembled by omission.

For assistance organising a dispute file for review, see HMRC enquiry response support. Provide the issue statement, chronology, key notices and nearest deadline. Explain where dates or facts remain uncertain. The resulting advice can then focus on the disputed matters and evidence gaps rather than spending the first stage reconstructing a sequence from filenames, scattered messages and unexplained calculations.

Before a major submission or handover, save a dated version and record changes made afterwards. If a new document alters the timeline, preserve the earlier entry and explain the correction rather than silently editing the history. This makes it possible to understand what was known when an earlier response was prepared and why the current account differs in a specific, documented way.

Illustrative scenario

A business prepares a chronology of an enquiry spanning two advisers. Each entry links to a letter or receipt, and unanswered questions are marked explicitly for the new representative.

Preparation checklist

• List events in date order
• Link supporting documents
• Mark disputed facts
• Identify deadlines and gaps