This article is stated as at 22 November 2026. The ICO says its guidance on AI, DPIAs, controllers and processors, privacy information and international transfers is under review following the Data (Use and Access) Act 2025 and may change, and it plans to update the IDTA and Addendum during 2026. Take advice on your own circumstances before acting.
Before any client records go into an AI review tool, the practice must decide and document its lawful basis for processing client data under Article 6 of the UK GDPR, for that specific purpose, and the ICO says that decision comes first. For most practices the answer will be legitimate interests. That should be backed by a written legitimate interests assessment, an Article 28 contract with the supplier, a decision on whether a DPIA is needed, and privacy information and engagement letters that say plainly what the tool does.
Choosing the lawful basis for processing client data in an AI tool
There have been seven lawful bases since 5 February 2026. The ICO’s guide to lawful basis lists them and says “There is no hierarchy in the order of the list in the UK GDPR.” For a review of statutory accounts the realistic choice is narrow.
| Article 6(1) basis (UK wide) | Fit for an AI review of client accounts |
|---|---|
| (a) Consent | Rarely. The ICO’s AI guidance says it is hard to make specific and informed for complex AI processing, and it must be as easy to withdraw as to give |
| (b) Contract | Only where processing is objectively necessary for a contract with the individual |
| (c) Legal obligation | Unlikely, as no law requires a review to be done with AI |
| (d) Vital interests | Not relevant |
| (e) Public task | Not relevant to a private practice |
| (ea) Recognised legitimate interest | No. Its annex covers purposes such as safeguarding, emergencies, crime and national security |
| (f) Legitimate interests | Usually the best fit, subject to the three part test and a documented assessment |
The ICO says you must settle your lawful basis before you start, and “you should not swap to a different lawful basis at a later date without good reason”. Its AI guidance adds that each distinct processing operation needs its own purpose and lawful basis, documented and included in your privacy notice, so write the purpose narrowly, for example “checking draft statutory accounts and supporting schedules for errors and disclosure points before manager and partner review”.
Whether a practice is a controller or a processor depends on who decides the purposes and means, and the ICO’s pages don’t settle that for accounts work, so the answer can differ between engagements. The position assumed here is that the practice is the controller for its own review work, and our guide to client data and UK GDPR sets out the wider framework.
Why client consent is rarely the right basis
The engagement letter is signed by one client. But the records that client sends hold personal data on directors, shareholders, employees, customers and suppliers, and none of them signed anything, so a consent clause in the engagement letter can’t be the lawful basis for processing their data. Even for the client, consent is fragile: the ICO says you can’t usually swap from consent to another basis, so if consent is withdrawn the review has no basis to rely on.
Contract is narrower than it looks. The ICO’s AI guidance limits it to processing that is objectively necessary to deliver the service, and a practice could deliver the engagement without the tool, so objective necessity is hard to show even for a sole trader client.
Recognised legitimate interest, Article 6(1)(ea), came into force on 5 February 2026 under SI 2026/82. It needs no balancing test, but its annex is limited to purposes such as safeguarding, emergencies, crime and national security, and routine review of accounts is not one of them.
Applying the legitimate interests three part test to an AI review
Article 6(1)(f) allows processing that is necessary for the legitimate interests of the controller or a third party, unless the individual’s interests or fundamental rights override them, in particular where the individual is a child. The ICO’s legitimate interests guidance breaks this into three questions.
Purpose. “Are you pursuing a legitimate interest?” The ICO accepts commercial interests and the interests of third parties, so a practice’s interest in checking accounts before they reach the partner qualifies, as does the client’s interest in filing accounts without avoidable errors.
Necessity. “Is your use of personal information necessary for that purpose?” The ICO’s AI guidance says a mere possibility that data might be useful is not enough. A review of statutory accounts needs the draft accounts, the trial balance and the supporting schedules, but it rarely needs full nominal ledgers, payroll files or bank narratives. Decide what the tool receives, write it down, and set up uploads so that staff can’t simply drop in the whole client folder.
Balancing. “Do the person’s interests override the legitimate interest?” The ICO says people’s interests are likely to win if they wouldn’t reasonably expect the use, and that the test is objective. An employee named in a payroll note would expect the company’s accountants to see it, but not a third party keeping it to train a product, so the safeguards around the tool carry most of the weight. Where the records include children, such as minor shareholders, the ICO says you must take extra care.
What goes in the legitimate interests assessment
“The UK GDPR doesn’t require you to do an LIA. But you should do one anyway,” says the ICO, because you still have to be able to show you are accountable. There is no standard format, and the ICO’s sample LIA template is a sensible place to start. For an AI review, the assessment should record:
- the purpose, stated as narrowly as the tool is actually used
- whose interests are served, and why they are legitimate
- what data the tool receives, what it does not, and why
- the categories of individual whose data appears in client records
- what those individuals would reasonably expect, and the safeguards you rely on
- the supplier’s role, and whether it uses the data for any purpose of its own
- the conclusion, the date and who approved it
The ICO says you should refresh the LIA if there’s a significant change in the purpose, nature or context. A new supplier, a new module or a change to the supplier’s terms on training should all prompt a review, as should integrating an acquired practice’s systems.
Two categories of data need more than an Article 6 basis. Special category data, such as health related items in payroll records, also needs an Article 9 condition, and the ICO says “There’s no special category condition equivalent to legitimate interests.” Criminal offence data needs a condition in Schedule 1 to the Data Protection Act 2018, often with an appropriate policy document. The simplest course is usually to keep both out of what the tool sees and to say so in the assessment.
The supplier’s role, the Article 28 contract and the DPIA
The ICO assesses controller and processor roles for each processing operation, and says an organisation that decides the purposes and means is a controller “regardless of how they are described in any contract”. Its own example is a prediction service that acts as a processor for client queries but is a controller when it trains its model. So ask your supplier plainly whether it uses client data to train or improve its models. Our list of questions to ask an AI supplier covers the rest of that conversation.
Where the supplier is a processor, Article 28 sets the minimum contract terms. The supplier may act only on your documented instructions and must keep its staff under a duty of confidence and apply Article 32 security. It may use sub processors only with your authorisation and on back to back terms. It must help you with rights requests, breaches and DPIAs, allow audits, and delete or return the data at the end, as you choose. That last term is easy to overlook, and our note on software contract exit terms explains what to look for.
If the tool or any sub processor handles data outside the UK, the transfer needs an adequacy regulation or appropriate safeguards, which include the IDTA or the UK Addendum to the EU standard contractual clauses, used with a transfer risk assessment. The ICO says the EU clauses are not valid on their own.
The ICO says that “In the vast majority of cases” using AI will involve high risk processing, and its list of processing likely to need a DPIA includes innovative technology, including AI. If high risk remains after mitigation, you must consult the ICO before you start. Our note on when a practice needs a DPIA works through that decision, and the DPIA can share most of its facts with the LIA.
What the engagement letter and privacy notice should say about AI
The ICO’s pages say nothing about engagement letters as such, so what follows applies Articles 13, 14 and 28 to the documents a practice already has. The privacy notice must give the practice’s identity and contact details, each purpose, its lawful basis and the legitimate interests relied on. It must also name the recipients or categories of recipient, cover any transfers outside the UK and their safeguards, and state retention periods. It must explain individuals’ rights, including the right to complain to the ICO, and say whether any automated decision making takes place. The right to object has to be brought to people’s attention clearly and separately. Where data comes through a client’s records, Article 14 also requires the categories of data and their source, so the notice should cover the people the practice hears about through clients.
The engagement letter should say that an AI tool assists the review, state the supplier’s role and where data is processed, and explain what the practice sends to the tool and what it keeps out. It should point to the privacy notice and ask the client to make that notice available to its directors and staff. It should also say who makes the judgements: a reviewer reads every point the tool raises, and the partner signs off the file and the accountants’ report. Our piece on evidencing human review explains how to show that on file.
For complaints received on or after 19 June 2026, the practice must acknowledge a data protection complaint within 30 days and tell the complainant the outcome without undue delay, so add that step to the practice’s data protection procedure.
Key dates
Before the first client file is uploaded, settle these in order: the purpose and lawful basis, the LIA, the supplier contract and DPIA, then the privacy notice and engagement letter.
| Date | What happened (UK wide) |
|---|---|
| 19 June 2025 | Data (Use and Access) Act 2025 received Royal Assent |
| 29 January 2026 | SI 2026/82, the commencement regulations, made |
| 5 February 2026 | Lawfulness of processing changes, recognised legitimate interests, purpose limitation and automated decision making provisions in force |
| 19 June 2026 | Complaints duty in force for complaints received on or after this date |
Questions practices ask
Does the Data (Use and Access) Act 2025 make it easier to rely on legitimate interests for AI?
Not for accounts work. From 5 February 2026 the Act added recognised legitimate interest as a seventh lawful basis with no balancing test, but only for listed purposes such as safeguarding, emergencies, crime and national security. The ICO's legitimate interests guidance now gives examples such as IT security and intra group transmissions, but says the three part test still applies to them. An AI review of client accounts still needs a full legitimate interests assessment.
We already use an AI review tool. Is it too late to choose a lawful basis?
The ICO says the basis should be decided before processing starts, and that you should not swap later without good reason. If you started without one, pause new uploads and complete and record the assessment now. Where your purposes have changed, the ICO says you must identify a basis for the new purpose. Where a genuine change justifies a new basis, you must tell people before doing anything new and record the change.
Can we use one legitimate interests assessment for all our clients?
Usually yes, if the tool is used for the same purpose in the same way across clients. The ICO asks for a lawful basis for each distinct processing operation, so a different purpose, such as the supplier training its model on the data, needs its own assessment. Special category and criminal offence data also need an Article 9 or Schedule 1 condition. Refresh the assessment whenever the purpose, nature or context changes significantly.
What changes if the AI supplier uses our client data to train its model?
The ICO treats developing and deploying AI as separate purposes. Its example shows a provider acting as processor for client queries while acting as controller when it trains its own model. If your supplier trains on client data, it needs its own lawful basis, contract is not a good basis for training, and your privacy information must cover that recipient and purpose. Supplier terms that exclude training make the assessment much simpler.
Sources
- A guide to lawful basis
- Legitimate interests
- How do we apply legitimate interests in practice?
- When can we rely on legitimate interests?
- Sample LIA template
- Special category data
- Criminal offence data
- How do we ensure lawfulness in AI?
- What are the accountability and governance implications of AI?
- How do you determine whether you are a controller or processor?
- What needs to be included in the contract?
- When do we need to do a DPIA?
- What privacy information should we provide?
- What are standard data protection clauses, the UK IDTA and the Addendum?
- Adequacy regulations
- The Data (Use and Access) Act 2025 (DUAA): summary of the changes, data protection
- The Data (Use and Access) Act 2025 (Commencement No. 6 and Transitional and Saving Provisions) Regulations 2026
- Data (Use and Access) Act 2025: data protection and privacy changes