How CPA Firms Can Use AIWithout Tripping over IRC 7216.

Busy season is exactly when AI looks most tempting, and exactly when a careless shortcut can turn into a confidentiality problem. This guide walks through what Section 7216 covers, where AI tools raise real questions, and the controls worth insisting on. It is general information, not legal advice. Your firm's counsel and your own consent policy have the final word.

What Section 7216 Actually Covers

Section 7216 of the Internal Revenue Code makes it a crime for anyone in the business of preparing tax returns, or providing services in connection with them, to knowingly or recklessly use or disclose a taxpayer's return information without consent, except as the regulations allow. The regulations live at Treas. Reg. §§ 301.7216-1 through -3.

Two things make it bigger than it first looks:

• "Tax return information" is broad. It covers anything a client gives you for the purpose of preparing a return, and what you compute or derive from it. A scanned 1099 sitting in a shared folder counts.
• There are two penalty tracks. Section 7216 itself is a criminal misdemeanor. Section 6713 adds a civil penalty for each improper use or disclosure, with an annual cap, and higher amounts where identity theft is involved.

Where AI Tools Raise Questions

An AI tool is not automatically a problem. The regulations allow a preparer to use return information to prepare the return, and to disclose it in some situations without consent. The questions come from what else might happen to the data. Ask four things of any tool:

1. Where is it processed? Disclosures to a preparer located outside the United States generally need the taxpayer's consent, and Social Security numbers face extra restrictions. If a vendor processes data offshore, find out before you upload anything.
2. Is it used for anything else? If a provider can use your clients' data to train or improve its models, that may be a use beyond preparing the return. Get the provider's terms in writing.
3. Who can see it? A shared chatbot account where every staff member pastes client files is a very different risk from per-person access to specific folders.
4. Can you get it back out, and delete it? Know what happens to the data when you stop using the tool.

Controls Worth Insisting On

Whatever tool you choose, these controls make Section 7216 compliance easier to run in practice:

• Connections, not uploads. Tools that connect to QuickBooks, Xero, Gmail or Drive through OAuth read only what each person has access to. Nobody pastes client files into a box.
• Per-person access. One partner's inbox shouldn't become the whole firm's inbox.
• Cited answers. If every number links to the report or document it came from, your preparers can verify it in seconds.
• Human approval before anything leaves. Document requests and reminders should wait as drafts until a person approves them.
• Locked projects for sensitive client work, kept apart from the rest of the workspace.
• A clear exit: revoke access tokens on disconnect and delete data when you close the account.

Consent: When You Need It, and What It Looks Like

When a use or disclosure isn't covered by an exception, you need the taxpayer's written consent before you make it, and the consent has to meet the format rules in the regulations and Rev. Proc. 2013-14: specific language, the name of the recipient, and the particular information to be disclosed. Many firms add an AI-specific consent to the engagement letter and keep it with the client file. Your counsel can tell you whether your workflow needs one.

A Simple Rollout Plan

1. Write a one-page AI-use policy: approved tools, what never goes into them, and who reviews outputs. (Our Firm AI-Use Policy Template is a starting point.)
2. Run vendor due diligence with the four questions above. Our AI Vendor Due-Diligence Checklist has the full list.
3. Start with prep, not judgment. Let AI gather, match and draft (see tax prep with AI), and keep preparers signing off.
4. Review after one busy season, and tighten the policy where you found gaps.

How MetaWurks Approaches It

MetaWurks connects to your firm's tools through OAuth and never stores passwords. Every answer cites its source, and email drafts wait for your approval. We never sell your data. We're confirming no-training terms in writing for every model provider we use, and we'll walk you through them on a 1:1 call. Your firm keeps its own 7216 consent process; we give you the controls that make it easier to follow.