This article is stated as at 22 November 2026. The Companies House filing changes from 1 April 2028 are announced and depend on implementing regulations, and the FRC's AI guidance is non mandatory, written for audit firms and may be revised. Take advice on your own circumstances before acting.
An AI accounts review tool earns its place the way a good senior does: by reading every page against every other page before the manager picks up the file. It fits best after the preparer’s self review and before manager review. The preparer clears only the mechanical points, and anything touching judgement, disclosure or presentation goes to someone more experienced. Responsibility does not move: the directors still approve and sign the accounts under the Companies Act 2006, and the firm and its engagement partner still answer for the work and the report.
Where does an AI review tool go in the workflow?
Many practices run three layers of review on a set of small company accounts. The preparer checks their own work, a manager reviews the file, and the partner considers the judgement areas and approves issue. The tool belongs between the first and second layers. Run it once the preparer has finished and self reviewed, and before the manager, who then starts with the obvious points cleared and a record of how each was dealt with.
Running it after the manager has signed off turns it into an expensive afterthought, because a late point reopens a file everyone thought was closed; running it instead of the manager is worse, as we explain below.
| Stage | Who | What happens | What the file shows |
|---|---|---|---|
| Preparation and self review | Preparer | Drafts the accounts and checks their own work | Completed preparer checklist |
| AI accounts review | Tool, run by the preparer | Reads the full set and records points | The tool’s report, listing every point |
| Clearing points | Preparer for mechanical points, manager for the rest | Each point accepted, rejected as not applicable, or referred | Outcome and reason against each point |
| Manager review | Manager | Reviews the accounts, the cleared points and anything referred | Manager review notes and sign off |
| Partner review | Engagement partner | Considers the judgement areas and approves issue | Partner sign off before the directors approve and sign |
If you are still deciding which product to use, our guide to choosing an accounts review tool covers the questions to put to a vendor and how to test the answers.
Who clears the points the tool raises?
Letting the preparer close every point on their own work brings back the self review problem that manager review exists to catch. ISQM (UK) 1 puts the principle plainly in paragraph 31(b): the work of less experienced team members should be “directed, supervised and reviewed by more experienced engagement team members.” A tool’s report does not change that, though it does give the reviewer a better list to start from.
What works is a short written policy saying who may close each type of point.
| Type of point | Typical examples | Who may clear it |
|---|---|---|
| Mechanical | A total that does not cast, a note that does not agree to the balance sheet, a comparative not brought forward | Preparer, with the outcome visible to the manager |
| Disclosure and presentation | A disclosure missing or out of date, note wording that no longer matches the numbers, the small companies statement | Manager |
| Judgement | Accounting policies, estimates, going concern, related parties | Manager, referred to the partner where significant |
Add one rule on top: if the preparer wants to reject a point outside the mechanical category, the rejection goes to the manager.
Each point should close with one of three outcomes and a reason in a sentence: accepted and corrected, rejected as not applicable (and why), or referred to the manager or partner. A point closed with no reason leaves no evidence that anyone applied judgement, and an inspector cannot tell clearance from dismissal. Our note on what each review point should show sets out the detail.
Sign off stays with the partner and the directors
No software changes the legal position. Under section 414 of the Companies Act 2006, the annual accounts must be approved by the board and signed on its behalf by a director, and the signature goes on the balance sheet. For accounts prepared under the small companies regime, the balance sheet must carry a statement saying so (or the micro entity equivalent) in a prominent position above the signature. If accounts that do not comply are approved, every director who knew they did not comply, or was reckless as to whether they complied, and failed to take reasonable steps to secure compliance or prevent approval commits an offence.
For the practice, responsibility for the work and for the accountants’ report stays with the firm and the engagement partner. The FRC’s guidance on generative and agentic AI, published on 30 March 2026, says for audit that “regulatory accountability for the deployment of AI tools and the quality of audit outputs remains unchanged” and that “the human auditor is always accountable”. It was written for audit, but no partner would argue that the principle is weaker for unaudited accounts.
Some matters are outside what a tool reading the accounts can see. The partner’s view on going concern, what the directors have represented, and what the partner knows about related parties from conversations with the client all sit outside the document. Those stay with the partner and the directors, and our guide to signing off AI reviewed accounts looks at them in more depth.
Does ISQM (UK) 1 apply to an AI accounts review tool?
It depends on what else the firm does. Paragraph 5 of ISQM (UK) 1 applies the standard in the UK to firms performing engagements under the FRC’s performance standards: audits under ISAs (UK) and a short list of other assurance and related engagements. Accounts preparation is not on that list. ICAEW describes it as an engagement in which the practitioner gives no assurance conclusion, with management responsible for the information and the underlying records.
A practice that only prepares accounts should therefore anchor its tool policy in its professional body’s requirements and its own quality procedures. ISQM (UK) 1 is still a sensible model to borrow from, and paragraph 10 expects firms doing only reviews or compilations to need a less complex and less formal system than a firm auditing listed entities.
A firm within ISQM (UK) 1 scope that uses the tool in its system of quality management or on in scope engagements should treat it as a technological resource from a service provider. Paragraph 32(f) requires appropriate technological resources, paragraph 32(h) requires resources from service providers to be appropriate for use, and paragraph A105 is blunt: “the firm remains responsible for its system of quality management.” Paragraph A47 adds that quality risks may arise from the use of such a resource, so the tool belongs in the risk assessment, with its risks and the firm’s responses recorded. Where the same people prepare and audit, it is usually simpler to run one policy for both kinds of work.
Drawing on the application material, a workable policy looks like this:
- Approve the tool firm wide before use (paragraph A101 allows a firm to prohibit an application until it is approved).
- Check the paragraph A100 matters: inputs, confidentiality, that the tool operates as designed, and that its outputs serve their purpose.
- Train users and write down how the tool is to be used, including the engagement partner’s responsibilities (paragraph A104).
- Set out which point types a preparer may clear, as above.
- Include tool use in engagement file inspections.
Our guide to quality management for accounts preparation covers how this sits alongside file review.
The FRC’s three risks, and how the workflow answers them
The FRC’s March 2026 announcement encourages firms to consider how their use of AI tools fits within their quality management obligations. The guidance itself names three risks: “the risk that the output of the AI tool is deficient”; “the risk that the output is misused, despite the output itself being appropriate”; and “the risk that the firm’s methodology permits approaches, which include the use of the AI tool, that fail to meet auditing standards”. Applying them to accounts preparation is an analogy rather than a requirement, but they map neatly onto the preparer, tool, manager and partner workflow.
Deficient output is answered by approving the tool before use, checking that it reflects current standards, and keeping a person reviewing what it produces. The FRC lists “having a human review and/or oversee the outputs and operation of the tool” as a mitigation.
Misuse is mostly automation bias: a clean report read as evidence that the accounts are right. The FRC warns that if the auditor “lacks some relevant technical knowledge or exhibits automation bias, the outputs of the system may be deficient”, and ICAEW’s practice guidance says “AI should never be treated as an authoritative source”. A clean report shows only that the tool found nothing among the things it checks for. Our piece on evidencing human review of AI output covers how to show that on file.
Partners should watch the methodology risk most closely. It usually takes the form of a policy, written or tolerated, that a junior may skip manager review on small jobs when the tool comes back clean. We would not allow it: manager review happens on every file, whatever the tool reports.
Client data, vendor updates and standards changes
Before any client trial balance goes into a tool, confirm where the data is stored and processed and whether it is used to train models. ICAEW’s ethics guidance warns against “loading confidential information into public Generative AI tools”, and many practices will want a DPIA for the review tool before rollout.
ISQM (UK) 1 paragraph A107 flags the risk that a provider’s methodology is not updated for changes in professional standards. The live example is the FRS 102 Periodic Review 2024 amendments, including the new Section 23 five step revenue model and the new Section 20 lessee accounting, which apply to periods beginning on or after 1 January 2026. Ask the vendor to show you the checks it runs on those sections, because a tool that has not been updated risks passing accounts against superseded requirements.
The government has also announced that from 1 April 2028 accounts must be filed at Companies House in iXBRL using commercial software, with web and paper filing closing. More review will then happen inside software, so decide now where the review tool sits beside it.
Key dates
| Date | What happens |
|---|---|
| 26 June 2025 | FRC publishes its first guidance on AI in audit |
| 1 January 2026 | FRS 102 Periodic Review 2024 amendments apply to periods beginning on or after this date |
| 30 March 2026 | FRC publishes its Generative and Agentic AI Guidance for audit firms |
| 1 April 2028 | Accounts must be filed in iXBRL using commercial software; web and paper filing of accounts closes (announced) |
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
Is it safe to upload client trial balances to an AI review tool?
It can be, once you have checked how the vendor handles the data. Confirm where it is stored and processed, who can access it, and whether it is used to train models. ICAEW warns against loading confidential information into public generative AI tools, so a general chatbot is the wrong place for client accounts. Record your checks, and consider a data protection impact assessment before rollout.
How do we check the tool reflects the FRS 102 changes from January 2026?
Ask the vendor to show the checks it runs for periods beginning on or after 1 January 2026, in particular the new Section 23 revenue model and the new Section 20 lessee accounting. Then test it on a set of accounts where you know the right answer. ISQM (UK) 1 paragraph A107 flags the risk that a provider's methodology is not updated for changes in professional standards.
Who clears the tool's points in a sole practice with no manager?
The practitioner clears them, because there is nobody more senior to refer them to. ISQM (UK) 1 paragraph A29 accepts that the requirements on direction, supervision and review may not be relevant for a sole practitioner. You should still record an outcome and a reason against every point, and treat a clean report as the start of your own review, not the end of it.
Should we test an AI review tool on accounts we have already signed?
Yes, it is a sensible way to approve a tool before live use. Run it on past signed files and compare its points with what your reviewers found, noting what it missed and what it raised that was not relevant. ISQM (UK) 1 paragraph A101 allows a firm to prohibit an application until it has been determined to operate appropriately and approved for use.
Sources
- Companies Act 2006, section 414 (Approval and signing of accounts)
- Companies House update to accounts filing from April 2028
- ISQM (UK) 1, Quality Management for Firms that Perform Audits or Reviews of Financial Statements, or Other Assurance or Related Services Engagements (Updated September 2025)
- Innovative new guidance supports audit firm adoption of emerging AI technologies
- Generative and Agentic AI Guidance: Risks, mitigations and illustrative examples (HTML version)
- FRC publishes landmark guidance providing clarity to audit profession on the uses of AI
- Generative AI guide: ethics
- Using AI with confidence: how to validate AI content
- Accounts preparation
- Implementation of the changes to FRS 102