§ Client data, UK GDPR and AI tools in an accountancy practice

Client data, UK GDPR and AI tools in an accountancy practice

Guides

This guide sets out what UK GDPR and the ICAEW Code of Ethics ask of an accountancy practice that puts client data through an AI tool, whether that is a review of statutory accounts or a drafting assistant. It is written for partners who have to decide whether a tool can be used on client files and what the practice should have in place first. It also covers the changes made by the Data (Use and Access) Act 2025 that are now in force.

Controller or processor: who decides what happens to client data

UK GDPR defines a controller as the person or body which, alone or jointly with others, “determines the purposes and means of the processing of personal data”, and a processor as one which “processes personal data on behalf of the controller” (Article 4). The label in a contract does not settle it. The ICO’s guidance on AI says that organisations which determine the purposes and means of processing “will be controllers regardless of how they are described in any contract”.

The practice

The ICO’s guidance on controllers and processors uses an accountant as its example: acting for a client, the accountant is “a controller in relation to the personal data in the accounts”, because accountants “work under a range of professional obligations”, such as a duty to report malpractice found while doing the books. A practice that sends a client’s accounts or working papers to an AI tool is making a controller’s decision, and the duties stay with the practice. Under Article 5(2) the controller must “be able to demonstrate compliance with” the data protection principles.

The tool provider

A provider that processes the data only to deliver the service, on the practice’s instructions, is a processor. That changes if it uses the data for purposes of its own. Article 28(10) says a processor that determines the purposes and means of processing “shall be considered to be a controller in respect of that processing”, and the ICO’s contract guidance says the same of a processor that acts outside the controller’s instructions.

The ICO’s AI guidance applies this to model development. A provider that develops its own models “is likely to be a controller for this element of the processing”. Where each client’s processing is kept completely and auditably separate, the guidance treats the client as sole controller and the provider as processor. Before any client file is uploaded, settle whether client data is used for anything beyond the service, in particular to train the provider’s models.

The Article 28 processor contract

The ICO says a contract is needed every time a controller uses a processor. Article 28(3) requires processing by a processor to be “governed by a contract or other legal act” setting out the subject matter, duration, nature and purpose of the processing, the type of personal data, the categories of data subject, and the controller’s obligations and rights. Article 28(9) requires it to be “in writing, including in electronic form”. Before signing, Article 28(1) says the controller “shall use only processors providing sufficient guarantees” of appropriate measures.

The contract must require the processor to:

  1. Process the data “only on documented instructions from the controller” (Article 28(3)(a)).
  2. Ensure the people authorised to process it “have committed themselves to confidentiality” or are under a statutory duty (28(3)(b)).
  3. Take the security measures Article 32 requires (28(3)(c)).
  4. Engage sub-processors only on the terms of paragraphs 2 and 4 (28(3)(d)).
  5. Assist with data subjects’ rights requests (28(3)(e)) and with the controller’s obligations under Articles 32 to 36, which include security, breach notification and DPIAs (28(3)(f)).
  6. At the controller’s choice, delete or return all the personal data when the services end, and delete existing copies unless the law requires them to be kept (28(3)(g)).
  7. Make available the information needed to demonstrate compliance, and allow for and contribute to audits and inspections (28(3)(h)).

The processor must also tell the controller immediately if, in its opinion, an instruction infringes data protection law. Article 28(2) requires the controller’s prior specific or general written authorisation for sub-processors, and under a general authorisation the processor must give notice of changes so the controller can object. Article 28(4) passes the same obligations down to any sub-processor and leaves the original processor fully liable to the controller if the sub-processor fails.

The ICO describes these terms as the minimum required. Keep the signed agreement, or the accepted online terms with their date and version, on file.

When a DPIA is needed

Article 35(1) requires a data protection impact assessment before processing begins where processing, “in particular using new technologies”, is “likely to result in a high risk to the rights and freedoms” of individuals. The ICO’s AI guidance is direct: “In the vast majority of cases, the use of AI will involve a type of processing likely to result in a high risk.” The assessment is still case by case, and if a particular use is not high risk the practice should record why.

The ICO’s DPIA guidance lists “processing involving the use of innovative technologies” as needing a DPIA when combined with any of the criteria from the European guidelines, one of which is matching or combining datasets. On borderline cases it says: “If in any doubt, we would always recommend that you do a DPIA”.

Article 35(7) sets the minimum contents:

  • “a systematic description of the envisaged processing operations” and their purposes;
  • “an assessment of the necessity and proportionality of the processing operations” in relation to those purposes;
  • an assessment of the risks to individuals; and
  • the measures to address those risks, including safeguards and security measures.

For an AI review of accounts, the description is mostly a data flow: what leaves the practice, in what form, where it is processed and stored, for how long, and who can see it. The ICO’s AI guidance asks for a description of the processing “including data flows”, and for residual risk to be recorded. Ask the supplier questions below first and write the DPIA from the answers.

Supplier due diligence: the questions to ask

These are the questions we would expect a practice to put to any AI tool provider before client data is uploaded. Ask for the answers in writing and keep them with the DPIA.

AreaQuestion to askWhy it matters
Data location and transfersWhere is client data processed and stored, including by sub-processors and support staff? If outside the UK, what transfer mechanism is relied on?Sending data to, or making it accessible by, a separate organisation outside the UK is a restricted transfer (ICO).
Retention and deletionHow long are uploads, outputs, logs and backups kept? Can the practice delete a client’s data on demand, with confirmation?Article 28(3)(g) delete or return; Article 5(1)(e) storage limitation.
Training on client dataIs client data, or anything derived from it, used to train or improve any model? Is that excluded in the contract?A provider using data for its own purposes is treated as a controller for that processing (Article 28(10)).
Sub-processorsWho are the sub-processors, including any model or hosting provider, where are they, and how will changes be notified?Article 28(2) authorisation and right to object; Article 28(4) flow-down.
SecurityIs data encrypted in transit and at rest? Who at the provider can access client files? How are the controls tested?Article 32(1)(a) to (d); Article 28(3)(b) and (c).
Breach notificationHow quickly will the provider tell the practice of a breach, and with what information?Article 33(2) requires the processor to notify the controller “without undue delay”; the practice itself must notify within 72 hours where feasible under Article 33(1).
Instructions and auditWill the provider act only on documented instructions, and what evidence of compliance will it give?Article 28(3)(a) and (h).

Transfers and breaches

The ICO’s brief guide to international transfers, dated 15 January 2026, defines a restricted transfer as “a transfer of personal information to a separate organisation located outside the UK”, and the rules apply whether the sender is a controller, processor or sub-processor. Each restricted transfer needs adequacy regulations, an appropriate safeguard or an exception. Where a safeguard is used, “you must also ensure that you have completed a transfer risk assessment”, and the ICO’s guidance on safeguards names the UK IDTA and the Addendum among them.

Under Article 33(1) the controller must notify a breach “without undue delay and, where feasible, not later than 72 hours after having become aware of it”, unless it is unlikely to result in a risk to individuals, so the provider’s notification promise needs to leave the practice time to meet that deadline.

The ICO’s AI guidance and the Data (Use and Access) Act 2025

The ICO’s guidance on AI and data protection

The current Guidance on AI and data protection says it “was updated on 15 March 2023”, and now carries the notice: “Due to changes made by the Data (Use and Access) Act, this guidance is under review and may be subject to change.” Its chapter on accountability and governance covers DPIAs and controller and processor roles. It remains the regulator’s published position and the starting point for a practice’s AI policy. The same notice appears on the ICO’s guidance on DPIAs, contracts, controllers and processors, and anonymisation.

Changes in force by 21 November 2026

GOV.UK’s commencement plan, last updated 12 October 2026, says the Commencement No. 6 Regulations brought in “the majority of the data protection and privacy provisions in Part 5” on 5 February 2026. Three changes bear directly on a practice using AI tools.

  • International transfers. Section 85 and Schedule 7 came into force on 5 February 2026 (SI 2026/82, regulation 2). Under Article 46(1A), a transfer is made subject to appropriate safeguards where safeguards such as standard data protection clauses are in place and the controller or processor, “acting reasonably and proportionately, considers that the data protection test is met”. The test is that protection after the transfer “would not be materially lower” than under UK GDPR and the relevant parts of the Data Protection Act 2018, and what is reasonable and proportionate depends on all the circumstances, including the nature and volume of the data.
  • Complaints to controllers. Section 103 inserts section 164A into the Data Protection Act 2018, in force from 19 June 2026 (SI 2026/82, regulation 3). A data subject may complain to the controller, who must make that easy, for example by “a complaint form which can be completed electronically”, acknowledge the complaint “within the period of 30 days” and respond without undue delay. A complaint about how a practice used an AI tool could now come to the practice directly.
  • The regulator. On 30 September 2026 the office of Information Commissioner was abolished and its functions transferred to the Information Commission (sections 118 and 119, in force by SI 2026/1015). Article 33 now refers to notifying the Commission. The guidance is still published at ico.org.uk, and we cite it under the ICO name it carries.

Checked against legislation.gov.uk and GOV.UK on 21 November 2026.

Confidentiality under the ICAEW Code and engagement letter wording

What the Code requires

Confidentiality reaches further than data protection. The ICAEW Code of Ethics 2026, which applies from 1 July 2026, deals with confidentiality in subsection 114.

  • Paragraph 114.0 A1 says the safe approach is to “assume that all unpublished information about a client’s or employer’s affairs”, however gained, is confidential. Draft accounts, ledgers and working papers fall within that whether or not they contain personal data.
  • R114.1 requires the accountant to maintain confidentiality within the firm and to take reasonable steps to ensure that personnel under the accountant’s control “and individuals from whom advice and assistance are obtained” comply with the accountant’s duty of confidentiality. Supplier due diligence is how a practice shows it took those steps with a technology provider.
  • Paragraph 114.1 A1 says maintaining confidentiality means protecting information in the course of its “collection, use, transfer, storage or retention, dissemination and lawful destruction”.
  • R114.2 prohibits disclosure, subject to R114.3, which allows disclosure or use where there is a legal or professional duty or right, or where “This is authorised by the client” and not prohibited by law or regulation.

The ICAEW’s generative AI guide makes the practical point, advising “not loading confidential information into public Generative AI tools” and saying “consideration must be given to the type of data that is input”. Read with the Code, that supports a partner’s decision to refuse a consumer chatbot with no contract and no answer on training.

Engagement letter points

The ICAEW’s helpsheet on engagement letters and privacy notices was fully reviewed and updated on 10 March 2026, and its change log says the Part 4 section on AI was updated. ICAEW practice news of 13 March 2026 says the guidance covers:

  • “Whether AI or other software tools will be used in service delivery”;
  • “Limitations of these tools and their potential impact on outputs”; and
  • “Responsibilities for data protection, confidentiality, and due diligence on technology providers”.

Read with R114.3, that suggests a practice’s letters should say that AI and other software tools may be used in delivering the work, so that the client’s authorisation to share information with providers is on record; that the practice remains responsible for the work and its staff review the outputs; and point to the privacy notice for how personal data is handled. Keep the privacy notice consistent with the DPIA and the processor contract. The helpsheet also says the use of AI software to tailor engagement letters “should be considered with caution”, because tailoring needs professional judgement.

Responsibility for the accounts themselves is a separate question, covered in our guide to who answers for accounts an AI tool has helped review.

Minimising and anonymising data before review

Article 5(1)(c) requires personal data to be “adequate, relevant and limited to what is necessary” for the purpose. For an AI review of accounts, that usually means the draft accounts and trial balance, and rarely payroll detail or personal bank transactions.

Pseudonymised is still personal data

Pseudonymisation means the data can no longer be attributed to a person “without the use of additional information”, kept separately and protected (Article 4). The ICO says “Pseudonymised data is personal data in the hands of someone who holds” that information, and warns: “Take care not to confuse pseudonymisation with anonymisation.” Replacing a director’s name with a code reduces risk, and Article 32(1)(a) lists pseudonymisation and encryption among security measures, but the practice is still processing personal data.

Anonymous information

The ICO says “Data protection law does not apply to anonymous information”, and that turning personal data into anonymous information itself “counts as processing personal data”. Small company accounts are hard to anonymise. The company name, the directors, the directors’ loan note and the related party note can identify people in combination, and the ICO’s anonymisation guidance tests whether people remain identifiable, including through its “motivated intruder” test.

What a practice can do

  • Decide, for each type of job, what the tool needs and send only that.
  • Remove or replace names in supporting schedules where the review does not depend on them, and keep the key separately.
  • Record the method in the DPIA so that everyone in the practice follows it.
  • Remember that confidentiality survives anonymisation: anonymised accounts are still unpublished information about a client’s affairs.

These decisions belong in the practice’s quality management records, which our guide to evidence of review and file quality covers. For assessing a tool before adoption, see questions to ask before choosing a review tool and how to test it.

We built Infinite Accountant as an AI review of statutory accounts at the standard of an experienced audit manager, for UK chartered practices. Practices considering it can read our data processing agreement for the trial against the questions in this guide, or start with our guide The Signed Review. The decisions on client data, like the signature on the accounts, stay with the partner.

Further reading

Questions practices ask

Is our practice the controller when we upload client accounts to an AI tool?

For the client work, yes. The ICO gives an accountant acting for a client as an example of a controller for the personal data in the accounts. A provider that processes the data only on the practice’s instructions is a processor, and Article 28 requires a written contract with it.

Do we need a DPIA before using an AI tool on client files?

Probably. Article 35(1) requires one where processing using new technologies is likely to result in a high risk, and the ICO’s AI guidance says that in the vast majority of cases AI use will. If a particular use is not high risk, record that assessment.

Can a supplier use our client data to train its models?

A processor acts only on documented instructions (Article 28(3)(a)), and one that uses data for its own purposes is treated as a controller for that processing (Article 28(10)). The practice should not instruct or allow training without checking that the client has authorised that use of its information (R114.3 of the ICAEW Code) and that the data protection position has been assessed. Ask for a contractual exclusion.

Does anonymising the accounts take them outside UK GDPR?

Only if the result is truly anonymous, which is hard with small company accounts. Pseudonymised data remains personal data for anyone holding the additional information, and the ICAEW confidentiality duty applies either way.

Who do we notify of a breach now that the Information Commissioner’s office has gone?

The Information Commission, which took over the Commissioner’s functions on 30 September 2026 under sections 118 and 119 of the Data (Use and Access) Act 2025. Article 33(1) still requires notice without undue delay and, where feasible, not later than 72 hours after becoming aware, unless the breach is unlikely to result in a risk to individuals.

Do we have to tell clients that we use AI tools?

The ICAEW’s updated terms of business guidance covers whether AI tools will be used in service delivery. Saying so in the engagement letter can also put the client’s authorisation on record, one of the grounds for disclosure in R114.3.

Sources