Digital Reporting (UK) Team iXBRL Governance

iXBRL Audit Trail: Compliance Requirements Your Auditors Actually Expect

"Auditors do not only ask whether the tag is valid. They ask who decided it, when, and why."

- Digital Reporting UK

The Question Auditors Are Starting to Ask

An auditor reviews the completed accounts and asks why a related-party transaction was tagged a certain way. If the tagging was done by an outsourcer and your team only approved the final file, can you show who made the decision and what working supports it?

That question is becoming more common because iXBRL tagging is part of the financial reporting process. If a tag affects how figures are interpreted by HMRC, Companies House or reviewers, the decision should be documented and defensible.

Why Auditors Care About iXBRL Audit Trails

iXBRL is machine-readable, so incorrect or inconsistent tags can create filing rejection, manual review, and audit questions. Auditors want evidence that tags match the accounts narrative, tax computation and underlying working papers.

  • High-risk items need visible rationale, especially related-party balances, provisions, deferred tax and acquisition adjustments.
  • Judgement calls should show who decided the tag and what evidence supported the decision.
  • Year-on-year tag changes should be explainable without reconstructing the process later.

The Three Questions Your Trail Must Answer

  1. Who? Who made or approved the tagging decision, including name, role and date.
  2. What? What was tagged, which tag was used, and whether an alternative was considered.
  3. Why? Why the tag is correct, with reference to the accounts, accounting standard, tax position or client instruction.

What Auditors Actually Ask For

1. Tagging Decision Log

A record of the line item, tag applied, decision owner, date and rationale. This can be a spreadsheet, portal export or structured vendor report.

2. Evidence of Review

Proof that someone competent reviewed the tagging before submission, such as a portal approval, email sign-off or internal memo.

3. Exception Log

A list of unusual tags, prior-year changes, manual overrides, low-confidence tags or items linked to new standards.

4. Validation Evidence

Confirmation that CRN, period dates, mandatory fields, taxonomy version and computation checks were completed.

5. Version Control

If a file was amended or resubmitted, keep notes showing what changed, who approved the change and why it was needed.

How to Build an iXBRL Audit Trail

  1. Create a tagging decision template. Include account, description, tag, category, decision owner, rationale, reviewer, review date and status.
  2. Focus on high-risk tags. Not every standard tag needs deep commentary; prioritise judgement-heavy and unusual items.
  3. Require vendor transparency. If outsourcing, require decision logs, confidence flags, exception reporting and change tracking.
  4. Add a review and sign-off step. A partner or senior accountant should confirm high-risk tags were reviewed before submission.
  5. Store the evidence together. Keep decision logs, vendor reports, sign-off memos, submitted files and acceptance confirmations in the same working paper folder.

A Practical Folder Structure

Working Papers / Company Name / Year / iXBRL/
Tagging Decision Log.xlsx
Vendor Tagging Report.pdf
iXBRL Review Sign-Off Memo.docx
iXBRL File Submitted [date].html
HMRC Filing Confirmation [date].pdf

Audit Trail Readiness Checklist

  • You have a tagging decision log or vendor export.
  • High-risk tags have documented rationale.
  • Review and approval before submission is documented.
  • CRN, period dates and mandatory fields are validated.
  • Amended or resubmitted files have a change log.
  • Documents are retained with the working papers and easy to retrieve.

Get Audit Trail Documentation With Every Tag

Digital Reporting (UK) can provide iXBRL tagging support with decision logs, review evidence and structured documentation for audit-ready working papers.

Discuss Audit Trail Support

Frequently Asked Questions

Do auditors always ask for an iXBRL audit trail?

Not always, but the request is becoming more common. Larger firms and newer audit teams are more likely to ask for decision evidence.

How long should we keep the trail?

Keep it for at least six years, aligned with tax record retention, and longer if the company is under enquiry or in a regulated sector.

If the vendor tags the file, who owns the audit trail?

The vendor should provide the tagging log, but your firm should review, approve and retain the evidence with its working papers.

Back to Blog