Claude for Accounting
Claude and Section 7216: Using AI on Client Tax Data Without Crossing the Line
The rules that govern a tax practice's use of Claude were written long before AI assistants existed — and they map onto AI use surprisingly cleanly. None of them bans the tool. All of them constrain the implementation. Here is the map.
The four rule sets that apply
IRC §7216 — consent before use
Tax return information may be used or disclosed by a preparer only as permitted, and knowing or reckless violation is a criminal matter, not a fine-and-move-on matter. The operative question for AI is simple: does putting this return information in front of this tool, configured this way, fall inside the permitted uses or the client's written consent? That question is answerable — but only if the firm actually asks it, per engagement, before the data moves.
FTC Safeguards Rule — preparers are financial institutions
Under GLBA, a tax practice is a financial institution and must maintain a written information security plan. Any AI tool that touches customer information becomes a third-party service provider your WISP has to name, assess, and monitor. IRS Publication 4557 says the same thing in the IRS's own voice.
Circular 230 — diligence and supervision
Practice before the IRS requires due diligence and supervision of work done on your behalf. AI-assisted work product is work done on your behalf: the preparer signs, the preparer reviews, and the review is documented like any other.
AICPA confidentiality — what may leave the engagement
The confidential client information rule predates AI and covers it completely: client information goes to a third party only with consent or another recognized basis. An AI workspace under firm-controlled commercial terms is a materially different analysis from a personal account on a consumer tool.
Why “just ban it” fails
Staff are already using AI — the only question is whether they are using it inside a workspace the firm controls or on personal accounts the firm cannot see. A ban does not stop the second thing; it guarantees it. The compliant posture is the opposite of a ban: give people the good tool, configured correctly, and make the safe path the convenient one. That means the firm runs Claude on an enterprise plan with single sign-on and commercial data terms — the terms and security posture Anthropic documents publicly on its Trust Center — so the WISP's third-party-provider section has something concrete to cite, and shadow AI has nothing left to offer.
The compliant shape, in practice
- Consent runs ahead of data. Where §7216 requires consent for a use, the consent exists before return information reaches a Claude workspace — built into the engagement letter cycle, not chased after the fact.
- Workspaces are scoped per engagement. One client's materials cannot appear in another client's context, and independence-sensitive work runs under a profile that cannot reach other clients' tools. Claude's project and connector controls are what make this enforceable rather than aspirational.
- Outputs are workpapers. Prompts and outputs on client work are retained as evidence, reviewed under Circular 230 diligence, and tie into the file like anything else a preparer relies on.
- The WISP tells the truth. The written plan names Claude, cites the vendor documentation, records the per-engagement connector allowlists, and describes the training staff actually received — including what may and may not leave the building. Anthropic's Help Center documents the workspace and admin controls the plan references.
One more thing worth saying plainly: this article is implementation guidance, not legal advice. The firms that get this right involve the person who owns their §7216 consent forms early — the point is that the consent framework and the AI rollout are one project, not two.
Where Skoor fits
This compliant shape is exactly what a Skoor implementation installs: Claude on firm devices under an enterprise workspace, per-engagement scoping, a WISP that names the tools truthfully, and a governance rubric a reviewer can hold in one hand. Anthropic's own materials on Claude in financial services are a good companion read; the Skoor offer for firms is at Claude for CPA firms.
Learn More
Run Claude inside the lines
Consent-first, WISP-documented, engagement-scoped — implemented in two weeks at a fixed fee.
See the CPA offer