FCA authorised · FRN 724952 0117 325 0027Quote & buy →
Aipedia: Bookkeepers
When cloud accounting AI makes an error, the client will usually claim against the bookkeeper, not the software vendor. The bookkeeper chose the tool, accepted its output and owes the client the duty of care.
Part of: AI in Bookkeepers
In short
Bookkeepers rely on AI features in cloud software for matching, coding, capture and filing. When those features go wrong, the instinct is to blame the vendor. In practice the client contracts with the bookkeeper, software terms commonly limit or exclude the vendor's liability, and professional rules put the duty to work carefully on the member. In an AAT Comment interview, AAT's president put it simply: "Accountability does not transfer to the vendor when the processing does." PI usually responds to the client's claim, subject to its terms, and the insurer may then consider whether any recovery from the vendor is possible.
A client hires a bookkeeper to keep accurate records and, often, to file returns. The client usually has no contract with the software vendor, or only a standard subscription it never read. If the records are wrong, the natural claim is against the person who was paid to get them right. A court will ask whether the bookkeeper took reasonable care, and using a tool is part of how the work was done, not a separate actor that takes over responsibility.
In an AAT Comment interview of 18 August 2026, AAT's president said: "Accountability does not transfer to the vendor when the processing does", and that AI should suggest rather than write to the ledger. That is opinion, not AAT policy, but it reflects the general legal position.
The ICB rules are in its Professional Conduct Regulations. None of these rules mentions AI, and none creates an exception for software errors.
Cloud accounting subscriptions are standard terms. They commonly say the software is provided "as is", that the user is responsible for checking output, and that the vendor's liability is capped, often at fees paid over a period, with indirect and consequential loss excluded. AI features may carry extra wording saying suggestions should be reviewed. Whether such terms are enforceable depends on the contract and the law, but they make recovery from the vendor uncertain and usually small compared with a client's claim.
A software update changes how an AI coding feature handles a VAT rate for one type of transaction. For several weeks it posts entries at the wrong rate across many users. A bookkeeper files VAT returns for four clients during that period without spotting the change. When the error is found, all four clients claim the costs of correction. The vendor acknowledges the bug in a release note but points to its terms. The bookkeeper's position depends on whether a reasonable review would have caught the error, for example by comparing VAT by rate with the previous quarter.
PI usually responds to the clients' claims if the bookkeeper is found negligent, subject to the policy terms, excess and limit. Claims from several clients caused by one software fault may raise aggregation questions. Once an insurer has paid, it commonly has the right to step into the insured's shoes and pursue any third party that caused the loss, which could include a vendor, subject to the vendor's terms. Separately, where two parties are liable for the same damage, the law allows contribution claims between them; see the Civil Liability (Contribution) Act 1978 and PI. Do not agree with a vendor to waive claims without checking your policy, as that could prejudice the insurer's position.
Related pages: AI auto-categorisation and AI bank reconciliation.
Apex arranges PI for bookkeepers, and a broker can review how your policy handles aggregation, notification and recovery for software-related claims. See the AI in bookkeeping hub and AI clauses in insurance policies.
Possibly, but recovery is often limited. Vendor terms commonly cap liability and exclude consequential loss. Whether you have a claim depends on the contract and the facts. If your insurer pays a client claim, it may pursue the vendor itself.
It helps show you acted reasonably in choosing tools, but it does not replace review. The question is whether a careful bookkeeper would have spotted the error. Using a widely used product is not a defence on its own.
If the bug may have affected client work and could lead to a claim, it is likely to be a circumstance you should notify. Check your policy's notification clause and speak to your broker promptly.
No. It was said by AAT's president in an AAT Comment interview published on 18 August 2026. It is opinion rather than AAT policy, though it matches the PCRT AI guidance point that members remain ultimately accountable.
Tell us about your firm and the work you do. A broker will review how your current PI treats AI-assisted work, or arrange new cover. No fee for a quote. Or call 0117 325 0027.
Start a PI quote Request a callbackApex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority. Registered in England and Wales, company number 07014570. This page is general information about how AI is used in the profession and how insurance may respond. It is not legal, regulatory or insurance advice on your circumstances, and it does not guarantee that cover will be available or on what terms.
