Using AI tools with client data: what the Code implies

What the AICPA confidentiality section and section 7216 imply when client data meets AI tools: who they bind, two scenarios and what to do.

US rule; elsewhere, check your own regulator · Updated November 20, 2026

US rule for AICPA members and for return information under section 7216. Check your own regulator if you hold a licence or membership elsewhere. General information, not legal advice.

The rule in brief

The AICPA Code of Professional Conduct deals with confidential client information in section 1.700. The official text, including the rule's exceptions, is on the AICPA site and is the authority. This page does not restate it. What follows is a practitioner reading of what that section implies for AI tools. It is not the Code's wording and it is not an AICPA position on AI.

The core point is simple. The rule says a member in public practice shall not disclose any confidential client information without the specific consent of the client (ET 1.700.001.01), and the Code defines confidential client information as any information obtained from the client that is not available to the public (ET 0.400.11). Putting it into a tool that stores, reuses or lets others see it is a decision about that information, and the accountant has to be able to defend the decision.

The Code also has an interpretation on third-party service providers (ET 1.700.040). A provider is an entity the member does not control, or an individual not employed by the member who assists in providing professional services (ET 0.400.52). Before disclosing confidential client information to one, the member should either have a contract with the provider to keep the information confidential, with reasonable assurance that the provider has procedures to prevent its unauthorized release, or get the client's specific consent. A company that runs an AI tool on its own servers is an entity the member does not control. Whether a given tool is a service provider in the Code's sense is a judgment for the member; reading the interpretation is the place to start.

For US return information there is a second, legal layer. Section 7216 limits a preparer's disclosure and use of return information. The regulation defines disclosure as making information known to any person in any manner, and use as referring to or relying on it as the basis for an action (26 CFR 301.7216-1(b)(4) and (5)). Unless a regulation permits it or the taxpayer gives written consent, a preparer may not disclose it or use it for any purpose other than preparing the return (26 USC 7216(a) and (b)(3); 26 CFR 301.7216-3(a)(1)).

Who it binds

  • AICPA members are bound by the Code. Whether you are a member, and whether a state board has a matching rule, is a fact to check. State boards of accountancy have their own rules; check your own board for its wording.
  • Preparers and people assisting them are bound by section 7216. The regulation's definition reaches people in the business of preparing returns, those paid to assist in preparing them, and individuals who work for any of those and assist in the preparation (301.7216-1(b)(2)).
  • Anyone under a contract is bound by its confidentiality terms, which are often stricter.
  • Accountants outside the United States should check their own regulator. A person who is not an AICPA member and not a preparer is still bound by the firm's contract.

What the Code implies for AI tools

Three questions come out of the confidentiality section for any tool that sees client data.

  1. Is the information confidential client information? Names, figures, identifiers and the existence of an engagement usually are. Treat anything specific to a client as in scope.
  2. Does the client's consent, or an exception in the Code, cover this use? The official text lists the exceptions, and the third-party service provider interpretation (ET 1.700.040) sets out the contract-or-consent route. If none applies, the information should not go in.
  3. Can the accountant show control? That means knowing where the data goes, who can see it, how long it is kept and how to delete it. A tool whose terms you have not read, or that cannot answer these questions, fails the test.

The same questions apply to a tool built into software you already use. A built-in assistant is still a recipient.

Two scenarios

These are illustrations, not real cases.

Scenario 1: pasting a trial balance. A reviewer is stuck on a classification question. She pastes a client's trial balance, including the client name and a note about a pending dispute, into a public AI assistant and asks for help. She has not read the tool's terms and the firm has not approved it. This is the case the confidentiality section exists for. The client information has gone to a recipient the client never agreed to. If the file also held return information, section 7216 adds a second problem: the regulation describes disclosure as making information known to any person by any means. The reviewer should tell the firm promptly, and the firm decides what else follows.

Scenario 2: an approved tool under a written agreement. A firm has approved one tool for client data and signed terms that restrict retention and reuse. The firm's contract with the reviewer names the tool and the limits. The reviewer uses the tool only for the approved purpose, checks every output against the source, and records its use. The same three questions have documented answers. This is the pattern a policy is designed to produce.

What to do

  1. Read the section in the AICPA Code, with its exceptions, before you rely on this page.
  2. Use only tools the firm has approved for client data, in writing.
  3. Strip client detail from any question you ask a tool, and ask the firm before using even an altered extract.
  4. Check every output against the source document. You own the work.
  5. Write a policy. The guide on AI-use policies and the template give a structure.
  6. If client data goes somewhere unapproved, tell the firm at once and keep your notes.
  7. For US return information, ask the firm's responsible CPA or counsel whether a tool's terms and processing location raise a section 7216 question. Do not assume they do not.

Where the official text is

  • The AICPA Code of Professional Conduct, section 1.700, on the AICPA site.
  • 26 USC 7216 and 26 CFR 301.7216-1, -2 and -3.
  • Your state board of accountancy, for its own rules.

Frequently asked questions

Does the Code say anything about AI by name?

The rule and its interpretations do not mention AI. The Code's text adds nonauthoritative notes under the confidentiality rule and the third-party service provider interpretation that point to an AICPA staff article, "Ethics Staff Insights: AI through an ethics lens", on threats to compliance when members use AI. This page applies the confidentiality section to a new kind of tool; read the official text and that article for anything more specific.

Is a paid tool safer than a free one?

Not automatically. What matters is what the terms say about retention, reuse, processing location and deletion.

May I use a tool if I remove the client's name?

Removing a name lowers the risk and does not remove it. Figures and context can identify a client, and derived information can itself be return information. Ask the firm.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Terms used on this page

Section 7216

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required