Guide
Can accountants use ChatGPT with client data? Five rules
Accountants can use ChatGPT or Claude with client data only on a business plan that doesn't train on your data by default (ChatGPT Business, Claude Team or the Enterprise plans), within what your engagement letters and professional rules allow, and never in a personal account. For US tax preparers there's a specific line: section 7216 of the tax code makes it a misdemeanor to knowingly or recklessly disclose or use return information without the client's consent, and in June 2026 the IRS Office of Professional Responsibility told practitioners to handle client data only with secure, enterprise-approved AI. Most finance work can be done with client identifiers swapped for labels.
Short answer
- Business plan only, with training off by default.
- Engagement letters and professional rules decide what client data may go in.
- US tax returns: IRC 7216 and the IRS's June 2026 AI guidelines; get written consent or keep it out.
- Default: swap names and identifiers for labels.
Five rules for a finance team
- Company accounts only. ChatGPT Business and Claude Team don't train on your data by default. Personal ChatGPT plans do unless each person turns it off.
- Check the engagement letter. If it limits who may see client data, an AI provider counts. Add a clause, or keep the data out.
- US tax return information: section 7216 covers preparers who knowingly or recklessly disclose or use it beyond preparing the return; the penalty is a fine of up to $1,000 in most cases, up to a year in prison, or both. The IRS Office of Professional Responsibility's June 2026 AI guidelines (Alert 2026-19) say client data belongs only in secure, enterprise-approved AI, but don't settle when section 7216 consent is needed. The cautious course: written consent first, or no return information in AI at all.
- Anonymize by default. Client name, tax ID, bank details and addresses become [Client], [ID], [Account] before anything is pasted.
- A person checks every number. AI explains and drafts; the ledger and the workpapers are the source.
A summary, not legal or professional advice; sources and dates below. In Japan, the Personal Information Protection Commission has asked companies to check that personal data entered into AI isn't used beyond producing the answer.
A worked example
Illustration: a made-up business. A 9-person bookkeeping and tax firm finds three habits in one week: a bookkeeper pasting a client's bank export into a personal ChatGPT account to categorize transactions; a senior using Claude to draft engagement letters; and nobody sure whether tax returns had ever gone into an AI tool.
- The bank export: moved to the firm's Claude Team account, with the client name, account numbers and payee names replaced by labels first. Categories come back the same.
- Engagement letters: fine as they are; they contain no client data until the senior fills it in.
- Tax returns: the partners decide that return information stays out of AI tools until they've taken advice on section 7216 and updated their consent forms.
They write the five rules on one page, with the partner who answers questions named at the bottom.
Put it in place this week
- Ask who uses which AI and on which account.
- Move work to a business plan and close personal-account use for client work.
- Read your engagement letters for data-sharing limits.
- Decide on tax return information with your adviser.
- Write the five rules on one page and name who answers questions.
Next step
Once the rules are set, put them into the AI itself: shared skills for the month-end checklist and variance note can carry "replace client names with labels" so nobody has to remember. Claude skills for finance covers which to build; the AI usage policy template covers the rest of the company.
Skills for this
- AI practiceCompany AI use policy draftDrafts a short, plain-language AI use policy: approved tools, data never to paste, review and disclosure rules, owners, and points flagged for legal review.
- Legal basicsData processing agreement checklistChecks a DPA for roles, subprocessors, security measures, breach notice, transfers, deletion, and audits against what your team can actually do.
- FinanceMonth-end close checklistBuilds a month-end close checklist for a small company: reconciliations, accruals, deferred revenue, payroll, and review, with owners and day offsets.
Questions
Can accountants use ChatGPT with client data?
Only on a business plan that doesn't train on your data by default, such as ChatGPT Business or Claude Team, within what your engagement letters and professional rules allow, and never in a personal account. US tax preparers also need to consider IRC 7216, which restricts disclosing return information without consent.
Does IRC 7216 apply to using AI on tax returns?
Section 7216 makes it a misdemeanor for a preparer to knowingly or recklessly disclose or use return information beyond preparing the return. The IRS Office of Professional Responsibility's AI guidelines (Alert 2026-19, June 2026) cite section 7216 and require secure, enterprise-approved AI for client data, but don't say when consent is needed. The cautious course is written client consent first, or keeping return information out of AI tools. Ask your adviser.
How can finance use AI without client data?
Use it for the method and the writing: checklists, variance notes from figures you've anonymized, letter templates, explanations of standards. Replace client names and identifiers with labels and put them back yourself.
AI skill
Have your AI draft your company's AI use rules
Put this skill in AI Skill Pod and everyone on your team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise): one invite link, free to start. Company AI use policy draft has your AI draft your firm's AI rules from your tools, client contracts and data: the approved accounts, the client data that never goes in, who reviews, and what to show a lawyer.
14 days free · No card needed
Sources
- 26 U.S. Code § 7216 (Cornell LII) — a return preparer who knowingly or recklessly discloses or uses return information for other purposes commits a misdemeanor: a fine of up to $1,000 in most cases ($100,000 for some), up to 1 year, or both (read 2026-11-05)
- IRS Office of Professional Responsibility: Issue Number 2026-19, Introductory Guidelines for Responsible AI Use in Federal Tax Practice (24 June 2026) — practitioners must strictly handle all client data using only secure, enterprise-approved AI; cites IRC 6713 and 7216(a) and Circular 230; doesn't address consent (read 2026-11-05)
- Journal of Accountancy: IRS outlines AI risks, Circular 230 duties for tax practitioners (26 June 2026) (read 2026-11-05)
- The Tax Adviser: The many implications of Sec. 7216 — consent requirements for disclosures (read 2026-11-05)
- ChatGPT pricing — Business: no training on business data by default (read 2026-11-05)
- Anthropic Privacy Center: commercial products — not used for training by default (read 2026-11-05)
- OpenAI Help: Data controls — personal plans train on chats by default unless turned off; read through search-result text (read 2026-11-05)
- Japan Personal Information Protection Commission: notice on generative AI services (2 June 2023) (read 2026-11-05)