Client Tax Data in AI Tools: the §7216 Rules for CPAs

Does pasting client tax data into an AI tool raise a §7216 disclosure question?

Yes, sending client return data to a third-party AI tool raises a disclosure question under IRC §7216. The IRS information center explains that Treasury regulations govern preparers’ disclosure or use of tax return information; the final regulations took effect December 28, 2012.

Start with the proposed input, not the product name. Ask whether the material is tax return information and, if so, whether a specific authorization applies or written consent is needed. Resolve that before an upload or paste.

Replacing a name with a placeholder is a useful precaution, but this page cannot determine whether the remaining facts fall outside the rule. Do not treat a summarized client situation as cleared for disclosure merely because direct identifiers are absent.

Our guide to AI for accountants covers broader workflows. This checklist addresses the data decision that should precede them.

What does written consent under 26 CFR 301.7216-3 require?

Under 26 CFR 301.7216-3(a)(1), consent must be written, knowing and voluntary, and obtained before disclosure or use unless §7216 or 301.7216-2 specifically authorizes it.

The verified requirements are:

• Obtain written consent before the disclosure or use, not afterward.
• Ensure that consent is knowing and voluntary.
• Do not condition services on consent: that makes it involuntary. The stated exception concerns consent to disclosure to another tax return preparer for preparation or auxiliary services.

Do not assume that an AI vendor falls within that exception. Have a qualified adviser assess the proposed arrangement.

This article does not provide consent wording or establish what a compliant form must contain beyond those verified requirements. Ask your adviser to check the applicable requirements before adopting a form. A generic AI-generated consent document is not evidence that those requirements have been met.

Checklist: before, while and after using an AI tool

Resolve disclosure authority before input, verify the draft while working, and preserve the basis for your decisions afterward. The actions below are recommended implementation steps tied to the cited rules or guidance, not a claim that each record or approval is expressly mandated.

Before:

• Assess the proposed input for tax return information and identify the applicable authorization or obtain prior written, knowing, voluntary consent. (IRC §7216; 26 CFR 301.7216-3)
• Check that services are not conditioned on consent, subject to the stated exception for disclosure to another preparer for preparation or auxiliary services. (26 CFR 301.7216-3)
• Read the plan’s data/privacy terms and your professional confidentiality rules before pasting client data; note unresolved retention or training questions. We have not verified vendor data terms here. (IRS OPR 2026-19 privacy and confidentiality concerns)
• If your firm is a covered financial institution, designate a Qualified Individual to oversee its information security program. (16 CFR 314.4)
• Assess the proposed AI workflow within the written risk assessment of reasonably foreseeable internal and external risks to customer information’s security, confidentiality and integrity. (16 CFR 314.4)
• If a service provider acts as the Qualified Individual, require it to maintain a program that protects you; your firm keeps responsibility for compliance. (16 CFR 314.4)

While:

• Use placeholders rather than actual client details wherever possible, without treating that substitution as a legal exemption. (IRC §7216; IRS OPR 2026-19)
• Use the plan and account whose terms you reviewed, as a practical control for the assessed workflow. (16 CFR 314.4)
• Check the draft’s figures, citations and conclusions against source documents and current law. (Circular 230 §10.22, as addressed in IRS OPR 2026-19)

After:

• Keep the consent or a note explaining the authorization relied on with the engagement record. (26 CFR 301.7216-3)
• Record who reviewed the draft, when, and what was corrected. (Circular 230 §10.22)
• Reassess the workflow if vendor terms or the intended use change. (16 CFR 314.4)

Rules and guidance checked 2026-10-19 on IRS pages and 2026-10-20 on eCFR pages. Evidence suggestions below are workflow recommendations.

What do ChatGPT and Claude plan terms say about client data?

We have not verified either vendor’s retention, training-use or business-protection terms for this page. A plan name or price therefore cannot establish whether it suits your client-data workflow.

Read the specific plan’s data/privacy terms and your professional confidentiality rules before pasting client, patient or employee data. Keep unresolved questions separate from purchasing decisions.

Prices below are USD list prices shown to a US visitor, excluding tax. Readers in the UK, Australia and India should check locally because prices, taxes and rules differ.

Prices and plans checked 2026-10-19 on the vendors’ official pages.

For broader plan comparisons, see ChatGPT for professionals and Claude for professionals. Our bench has no prompts for this exact task and country, so this article quotes no test score; the methodology explains our evaluation approach.

How can I draft a client memo without entering actual client details?

Use a placeholder-only prompt for drafting structure, then complete and verify the memo within your approved workflow. Do not fill the placeholders with actual return information unless the disclosure assessment permits it.

The prompt cannot determine whether your input is legally de-identified. Our prompt library for accountants offers additional drafting patterns.

Draft an internal memo for a US tax preparer using only the
placeholders and generalized information below. Do not request
names, taxpayer identifiers, addresses, account numbers or
actual client amounts.

Client category: [GENERAL CLIENT CATEGORY]
Tax period: [PERIOD PLACEHOLDER]
Filing situation: [GENERALIZED SITUATION]
Issue: [QUESTION FOR PREPARER REVIEW]
Relevant facts: [PLACEHOLDER FACTS OR HYPOTHETICAL RANGES]
Authorities to address: [PREPARER-SUPPLIED AUTHORITIES OR NONE]
Firm position: [POSITION OR OPEN]

Use these headings:
Facts as supplied
Issue
Analysis
Open questions for the preparer
Documents to request through the firm's approved process

Do not invent facts, figures or citations.
Keep placeholders and hypothetical ranges unchanged.
Identify missing facts under Open questions.
Mark legal statements for verification against current law.
Do not conclude that disclosure to this tool is authorized.

End with:
"Draft for preparer review under Circular 230 §10.22;
not client-ready."

Limits: A licensed professional in your jurisdiction must check the input’s status under §7216, any authorization under 301.7216-2, consent requirements, Safeguards Rule coverage, applicable confidentiality rules and current vendor terms. The professional must also verify the memo’s facts and legal conclusions. This page explains the cited US federal sources; it is not legal or tax advice.

FAQ