§ InsightsNo. 287

AI accounts review audit trail: what each review point should show

What each point raised by an accounts review tool should carry before a partner relies on it: source, reference, working paper and who cleared it.

Two accountants checking a working paper against draft accounts to confirm an AI accounts review audit trail

This article is stated as at 21 November 2026. The Companies House filing changes from April 2028 are announced but their regulations and commencement date are not yet published, and the FRC's AI guidance is non mandatory good practice that may be updated. Take advice on your own circumstances before acting.

An AI accounts review audit trail needs four things for every point a tool raises: the source document and where in it the issue sits, the exact FRS 102, FRS 105 or Companies Act reference for the edition in force, the working paper the point ties to, and a record of who cleared it, when and why. If any of these is missing, you can’t rely on the point when you sign, and you can’t defend it to a monitoring reviewer.

Why each review point needs its own evidence

The legal position is the same whatever tools the practice uses. Directors must not approve accounts unless they are satisfied that the accounts give a true and fair view (Companies Act 2006, s.393). Under section 414 of the Companies Act 2006, a director commits an offence if they approve accounts they know do not comply, or are reckless about whether they comply, and fail to take reasonable steps to secure compliance or to prevent the accounts being approved.

The practice’s own responsibility sits alongside the directors’. The FRC’s March 2026 announcement on generative and agentic AI says “the human auditor is always accountable” and that regulatory accountability for AI tools and the quality of what they produce is unchanged. That was written for audit, but the same logic applies to accounts preparation: a tool informs the reviewer’s judgement, and the reviewer still owns the conclusion.

Most accounts files in a chartered practice are not audits. The ICAEW’s accounts preparation guidance says a compilation will not constitute an audit or a review, and the practitioner does not verify the client’s information. ISA (UK) 230 does not apply to those files, but its test is a sensible benchmark: an experienced auditor with no previous connection to the work should be able to read the documentation and understand what was done, what was found and what significant judgements were made. A review point that passes that test can be relied on, but one that needs the person who ran the tool to explain it can’t.

There is a cost in pounds too, because a point nobody can trace has to be worked again, often close to the deadline. A private company has nine months from the end of its accounting reference period to file. Companies House charges the company itself, not the practice, between £150 and £1,500 for late filing by a private limited company, and the penalty doubles if the accounts are late two years in a row. So a file that stalls more than six months past the deadline in a second consecutive year costs the client £3,000.

What an AI accounts review audit trail should show for each point

These six elements turn a flag into something a reviewer can rely on, whichever tool the practice uses.

Element What good looks like What the reviewer does with it
Source The document and the exact location: trial balance code, page and note of the draft accounts, the invoice, contract or board minute Opens it and confirms the issue is really there
Reference The standard or Act, the paragraph or section, and the edition, for example FRS 102 (September 2024) paragraph 1AC.35 or Companies Act 2006 s.414(2) Reads the text and decides whether it applies to this client
Working paper The schedule or lead sheet the point ties to, with the figures Agrees the numbers and sees the effect on the accounts
Reason A plain statement of why the point was raised, including what was compared with what Judges whether the reasoning holds
Status and clearance Open, amended, cleared or referred to the partner, with who did it, when and on what basis Sees the point is closed and why
Tool record The tool and model version, the settings and the inputs used Can examine the point again after the software changes

Our guide to choosing an accounts review tool covers the wider questions to put to a vendor.

The reason column is the one most often thin. A CCAB ethics case study published in May 2026 describes an audit team that could not explain why its AI had flagged certain items, beyond “the AI system identified them as anomalous”. A reviewer cannot sign on a flag that only says something looks unusual, so the point has to say what it compared and what didn’t agree.

None of this needs to be long, and a trivial presentation point can carry a one line reason and a one line clearance. The same columns fit into a statutory accounts review checklist, so tool points and human points end up recorded the same way.

Getting the standard or legislation reference right

A point that cites “FRS 102” or “the Companies Act” in general gives the reviewer nothing to check. The reference should name the paragraph or section in the text in force for the period being reported on.

The current edition of FRS 102 on the FRC’s site is dated September 2024, and the Periodic Review 2024 amendments have a principal effective date of 1 January 2026, with early application permitted. FRS 105 has the same effective date for its Periodic Review changes, so December 2026 year ends are among the first ordinary files where the amended text applies. For small entity related party disclosure in periods beginning on or after 1 January 2026, paragraph 1AC.35 requires disclosure by applying paragraphs 33.9 and 33.14, but not 33.7. A tool working from older paragraph references sends the reviewer to the wrong text, even if its point sounds right. The Adapted formats amendments issued on 18 February 2026 take effect from 1 January 2027, so ask any vendor which edition and amendments its references are based on.

The FRC notes that s.393 requires a true and fair view, and that may call for disclosures beyond those FRS 102 itself requires. A tool can confirm the required disclosures are present, but whether the accounts need more is a judgement for the reviewer, particularly in the areas in our guide to judgement areas in small company accounts.

Recording how a point was cleared

A log showing that someone clicked accept records approval, but it says nothing about how anyone reached the conclusion, which is the part a monitoring reviewer asks about.

On an audit, ISA (UK) 230 has the file record who performed the work and when, and who reviewed it, when and to what extent. Where information is inconsistent with the final conclusion on a significant matter, the file shows how the inconsistency was dealt with. On an accounts preparation file, if the tool and the preparer disagree, the file shows which view prevailed and why, and if the point went to the client, it shows what the client said and when.

A good clearance note on a directors’ loan point might read: “Year end balance agreed to loan schedule; repayment after the year end seen on the bank statement; note amended to show the advance and repayment; partner informed.”

The FRC’s March 2026 guidance treats acting on a flag as a conclusion as misuse of output, and its November 2026 Ethics and Technology guidance identifies a risk of automation bias; we cover how to evidence real human review in our note on evidencing human review of AI output.

What the file should record about the tool itself

Some evidence belongs to the tool, not to any single point. The FRC’s June 2025 AI documentation guidance says AI tools used on an audit require documentation in line with ISA (UK) 230. It lists what to record:

  • the version of the tool and the model used
  • any configuration or changes the team made, and the data or prompts it put in
  • how the team made sure the input data was complete and accurate
  • evidence that the relevant central function approved the tool for the engagement
  • how the team used the outputs to reach its conclusion or to decide on further work

The FRC says this guidance is not prescriptive, so on an unaudited file it is a benchmark, not a rule. The version record answers the question of what happens to old points when the software updates itself: without it, nobody can say what produced a point or whether the tool would raise it today. And a tool reviewing an incomplete trial balance cannot find what it was never given, so the file should show that the inputs were checked first.

For firms within the scope of ISQM (UK) 1, paragraphs 32(f) and 32(h) require technological resources, including those from service providers, to be appropriate for use, and the FRC’s scalability information sheet suggests a small firm reviews known limitations before use and again when the tool or its use changes. Whether ISQM (UK) 1 applies to work that is only accounts preparation depends on your regulator’s rules, so check the ICAEW regulations that apply to your practice; our guide to quality management for accounts preparation covers the firm level picture.

The FRC also warns that documenting too much can divert time and resources, so record the tool once per engagement, put the detail into the significant points and keep the trivial ones brief.

Testing a review tool against this standard

When you assess a tool, ask to follow one point from end to end: open the source, read the cited paragraph, agree the working paper, read the reason, and look at the clearance record. If any step needs the vendor to explain it, the trail is not good enough.

The FRC’s March 2026 guidance names five ways AI output can be deficient: hallucinations, omissions, distortions, faulty reasoning and inconsistencies. On files you have already signed off, look for cited paragraphs that don’t say what the point claims, errors your own review found that the tool missed, figures restated wrongly, reasoning that doesn’t follow, and different answers when the same file is run twice. Piloting a tool on past signed files is the fairest way to see this before any live client depends on it.

For anyone buying or running a group of practices, the same test shows whether files across offices would read consistently to an outside reviewer.

Key dates

Date What happens Status
15 December 2022 ISQM (UK) 1 and ISQM (UK) 2 effective In force
1 January 2026 FRS 102 and FRS 105 Periodic Review 2024 amendments effective for periods beginning on or after this date In force
1 January 2027 FRS 102 and FRS 105 Adapted formats amendments effective Issued
April 2028 Software only iXBRL accounts filing at Companies House, web and paper filing closes, and a strengthened audit exemption statement applies Announced

You may also find our article Where AI accounts review fits between preparer and manager review useful.

You may also find our article Software contract exit terms for an accounts review tool useful.

You may also find our article Lawful basis for processing client data in an AI accounts review useful.

You may also find our article Accounts preparation file review and the evidence it should leave useful.

You may also find our article Documenting professional judgement when overruling an AI review point useful.

Questions practices ask

Can I rely on a review point raised by an AI tool without checking it myself?

No. The FRC's March 2026 guidance treats acting on a tool's flag as if it were a conclusion as misuse of output, and says professional judgement must decide what conclusions can be drawn from the output. Open the source, read the cited paragraph and agree the working paper before you clear the point, and record that you did.

Who is responsible if an AI review misses a disclosure error?

The directors remain responsible for approving accounts that give a true and fair view under sections 393 and 414 of the Companies Act 2006, and the practice and the engagement partner remain responsible for their own work. The FRC has said that regulatory accountability for deploying AI tools and for the quality of the output is unchanged, so a tool does not take that responsibility over.

Does the FRC require us to document which AI tool and version we used?

On an audit, the FRC's June 2025 guidance says AI tools require documentation in line with ISA (UK) 230, and it lists the version of the tool and model among the things to record. The FRC describes the guidance as not prescriptive and adding no new requirements. On unaudited accounts files it is good practice rather than a rule.

What happens to old review points if the software updates itself?

Keep the original point, the version that raised it and the clearance note as they were when the file was signed, and don't rerun the file and overwrite them. The FRC's scalability information sheet suggests a firm reconsiders a tool's suitability when the tool or its use changes, so treat a significant update as a reason to retest it.

Does ISQM (UK) 1 apply to the technology we use for accounts preparation?

For firms within its scope, ISQM (UK) 1 requires technological resources, including those from service providers, to be appropriate for use, and the firm stays responsible for its system of quality management. Whether a practice doing only accounts preparation falls within scope depends on its regulator's rules, so check the ICAEW regulations that apply to you.

Sources

Part of the guide: Choosing an accounts review tool: questions to ask and how to test it