AI is already in most tax offices: chat assistants, note-takers and new buttons in software you already pay for. The real question is what client data goes in, where it goes next, and who said that was OK.
This guide covers the rules to know first, with the IT side in plain English. It is not legal or ethics advice. Confirm your situation with your attorney or professional guidance.
The short answer
There is no simple yes or no. Federal rules limit how preparers use and share tax return information. The FTC Safeguards Rule requires a written security program and oversight of service providers. The practical answer is maybe: with the right account, settings, written policy and, in some cases, client consent. Your adviser decides the legal part. Your IT setup makes the policy real.
Start with the data: what counts as tax return information
Before anyone picks a tool, decide what data you are talking about. The definition is broad.
Under the Section 7216 regulations, tax return information means "any information, including, but not limited to, a taxpayer's name, address, or identifying number, which is furnished in any form or manner for, or in connection with, the preparation of a tax return" (26 CFR 301.7216-1). It includes information from third parties. It also includes information the preparer derives from it.
So a client's name in a prompt counts. So does a scanned W-2. And "preparer" is not only the person who signs. It includes employees who help prepare returns.
Section 7216: disclosure, consent and the "outside the US" rule
Section 7216 makes it a misdemeanor for a tax return preparer to "knowingly or recklessly disclose or use tax return information" for a purpose other than preparing a return. The regulation lists a maximum penalty of up to one year in prison, a fine, or both. A related civil penalty applies under Section 6713 (26 CFR 301.7216-1).
Three points matter for AI tools:
- "Disclosure" is broad. It means making tax return information known "to any person in any manner whatever."
- Some disclosures are allowed without consent. Section 301.7216-2 lists them. One example covers sharing with another preparer in the United States for help preparing a return or for "auxiliary services" (26 CFR 301.7216-2).
- Location matters. The regulations repeatedly require the taxpayer's consent before disclosure to a preparer located outside the United States. The consent rules also limit sharing a Form 1040 filer's Social Security number with a preparer outside the United States (26 CFR 301.7216-3).
Consent has strict rules. It must be written, knowing and voluntary, signed and dated, and given before the disclosure. It must name the purpose and the recipient, and describe what tax return information will be shared or used. If no end date is stated, it lasts one year.
Whether a given AI tool is a permitted disclosure, needs consent, or should not be used is a question for your adviser. The IT question comes first: where does the vendor process and store data, and who there can see it? Get that in writing.
Safeguards Rule: an AI vendor is a service provider
The FTC Safeguards Rule (16 CFR Part 314) lists "tax preparation firms" among the businesses it covers (16 CFR 314.1). It requires a written information security program. For a tax office, that is your WISP.
Several parts of the rule apply directly to AI tools (16 CFR 314.4):
- Access controls. Limit authorized users to the customer information "they need to perform their duties and functions."
- Service providers. Select providers that can keep appropriate safeguards, require those safeguards "by contract," and periodically assess them.
- Training. Give staff security awareness training that is updated as risks change.
- Change. Adjust the program when your operations change.
IRS Publication 4557, Safeguarding Taxpayer Data, says to "Limit access to taxpayer data to individuals who need to know," and to pick service providers whose contracts require safeguards (IRS Pub. 4557, Rev. 6-2024).
In plain English: an AI vendor that sees client data is a service provider. It belongs in your WISP, your vendor list and your contracts.
What current tax and CPA guidance says about AI
On June 24, 2026, an IRS publication titled "Issue Number: 2026-19. Introductory Guidelines for Responsible AI Use in Federal Tax Practice" was posted on irs.gov (IRS, Issue 2026-19). It ties AI use to Circular 230 and Section 7216. Key lines:
- "Practitioners must strictly handle all client data using only secure, enterprise-approved AI."
- Practitioners must review AI-created documents "before delivery to a client or submission to the IRS."
- Its best practices include secure data handling "and access controls," staff training, vetting third-party AI before purchase, and to "Treat the written text that AI generates as drafts."
AICPA publications point the same way. An August 2026 Journal of Accountancy article suggests asking, before pasting client data into any AI system, whether it is confidential client information and whether consent is required (JofA, Aug. 2026 issue). The Tax Adviser explains that AICPA Statements on Standards for Tax Services Section 1.3 covers protecting taxpayer data, and Section 1.4 covers relying on tools, including AI (The Tax Adviser, April 2026). A risk-management article on the AICPA Member Insurance Programs site (CNA risk control, not an AICPA ethics ruling) suggests engaging legal counsel when deciding whether client disclosure or consent is required for generative AI, and when drafting those documents (AICPA Member Insurance Programs).
Six practical steps for a small office
- List what is already in use. Include chat tools, note-takers, browser add-ons and AI features inside your existing software. Personal accounts count.
- Map where the data goes. For each tool, write down the account type, whether inputs are used for training, how long data is kept, where it is processed and who at the vendor can access it. Use the vendor's terms and admin settings, not its marketing.
- Use firm accounts with admin controls. Free and personal accounts often have different terms. Firm accounts let you require MFA and remove access when someone leaves. Limit each tool to the staff who need it.
- Settle consent with your adviser. For each approved use that touches tax return information, ask whether it is a permitted disclosure or needs Section 7216 consent. Write down the answer before filing season.
- Update your WISP. Add approved AI tools to your service provider list, staff training and incident plan, including what to do if client data goes into the wrong tool.
- Write a short staff AI policy. Name the approved tools, what data never goes in, who reviews AI output and how exceptions are approved. Have each person sign it. Adapt any template with your own adviser. A written policy is a starting point, not a compliance certification.
Frequently asked questions
Can tax preparers use AI with client data? Sometimes, with the right account, settings, policy and, where required, client consent. Ask your adviser how Section 7216 applies to each tool.
Is a paid business AI account automatically safe for client data? No. Business plans may offer better terms and controls, but you still need to read the terms and confirm where data is processed.
Can we use AI if no client data goes in? Often, yes. A generic newsletter or a blank checklist is a different risk from a client's return. Your policy should say which tasks are fine without client data.
Do we have to tell clients we use AI? That depends on your situation and the rules that apply to you. Ask your attorney or professional guidance source.
Want help setting up AI tools for your office?
FIX256 is an IT company in Goshen, NY, working with small CPA and tax offices across New York. We handle the technology side: accounts, settings, access controls and the IT parts of your WISP. Your counsel handles the legal and ethics questions.
Book a free 20-minute call with FIX256.
This article is general information, not legal, tax or ethics advice. FIX256 is an IT company, not a law firm or a CPA ethics authority. Rules, guidance and vendor terms change. Check the current sources below and confirm your situation with your own counsel or professional guidance.
Sources
- 26 CFR 301.7216-1, Penalty for disclosure or use of tax return information (eCFR): https://www.ecfr.gov/current/title-26/chapter-I/subchapter-F/part-301/subpart-ZZZZ/section-301.7216-1
- 26 CFR 301.7216-2, Permissible disclosures or uses without consent of the taxpayer (eCFR): https://www.ecfr.gov/current/title-26/chapter-I/subchapter-F/part-301/subpart-ZZZZ/section-301.7216-2
- 26 CFR 301.7216-3, Disclosure or use permitted only with the taxpayer's consent (eCFR): https://www.ecfr.gov/current/title-26/chapter-I/subchapter-F/part-301/subpart-ZZZZ/section-301.7216-3
- 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule), sections 314.1 and 314.4 (eCFR): https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314
- IRS Publication 4557 (Rev. 6-2024), Safeguarding Taxpayer Data: https://www.irs.gov/pub/irs-pdf/p4557.pdf
- IRS, Issue Number 2026-19, Introductory Guidelines for Responsible AI Use in Federal Tax Practice (June 24, 2026): https://www.irs.gov/pub/opr-taxpros/issue-number-2026-19-introductory-guidelines-for-responsible-ai-use-in-federal-tax-practice.pdf
- Journal of Accountancy, "Accounting ethics in the age of AI" (Aug. 2026 issue): https://www.journalofaccountancy.com/issues/2026/aug/accounting-ethics-in-the-age-of-ai/
- The Tax Adviser, "Tax ethical standards in data protection and reliance on tools" (April 2026 issue): https://www.thetaxadviser.com/issues/2026/apr/tax-ethical-standards-in-data-protection-and-reliance-on-tools/
- AICPA Member Insurance Programs, "Should I disclose my use of gen AI to clients?": https://www.cpai.com/Education-Resources/My-Firm/Data-Security-Risk-Management/Should-I-disclose-my-use-of-gen-AI-to-clients
