Answer
Can an accounting firm put client tax information into an AI tool?
Not without consent in a specific written form, and the rule carries criminal penalties rather than professional ones.
Only with the taxpayer's written consent in the prescribed form. Sending return information to an outside tool is a disclosure under the preparer statute, and that statute carries criminal as well as civil penalties.
The rule most firms have not read is the one that decides this. A federal statute makes it an offence for a tax return preparer to disclose or use a taxpayer's return information other than as permitted, and the regulations under it set out exactly what a consent must look like: separate documents for use and for disclosure, each disclosure or use specifically and separately identified, knowing and voluntary consent, and prescribed wording and formatting for individual return clients. This is not the general confidentiality expectation a firm operates under. It is a criminal provision with a civil penalty running alongside it.
Return information is defined broadly, and that breadth is what catches AI use. It is not only the return. It covers information furnished to the preparer for the purpose of preparing a return, and information the preparer derives in the course of doing so. A client's bookkeeping export, a schedule of expenses, a question about a transaction's treatment, a draft the firm produced — all of it. A preparer pasting a client's figures into an outside tool to ask how something should be treated has disclosed return information, whatever the tool does next.
The exceptions are narrower than the ones people reason from. Disclosures to other preparers within the same firm assisting with the return, and to certain contractors providing services in connection with preparation, are treated differently from disclosures at large — but they are conditioned, they do not extend to anything the firm feels is helpful, and they are not a general permission for whatever software the firm has adopted. Reasoning by analogy to how the firm treats its practice management software is exactly how this goes wrong.
The consent route is available and it is deliberately awkward. It must be obtained before the disclosure, it cannot be bundled with other permissions, each disclosure must be separately identified, and consent cannot be a condition of the firm doing the work. That awkwardness is the point: the statute is designed to make bulk consent to onward disclosure hard to obtain casually, and a firm that drafts a broad technology consent into its engagement letter has probably produced something that is not a consent under the regulation at all.
What remains straightforwardly available is substantial, and firms that draw the line early get the benefit without the exposure. A model that has no return information in the prompt — asked about the treatment of a category of transaction in the abstract, asked to draft a client letter with no particulars, asked to summarise a technical bulletin, asked about the mechanics of a form — has received nothing the statute governs. Most of the value firms actually report from these tools is in that space, and it does not need a consent.
The remaining risk is not the firm's policy. It is the individual preparer in March with a question and a browser open, and the reason it is worth telling staff about the criminal element specifically. A rule that is presented as an internal policy gets weighed against getting the return finished. A rule that is presented as a federal offence with the firm's licence attached is weighed differently, and this one is the second thing.
Most confidentiality rules a firm operates under are professional obligations. This one is a criminal statute, and it is the one most likely to be breached by somebody trying to be helpful.
Siddharth Sharma, Context Theory
Related questions
Does it matter if the tool is hosted by our existing tax software vendor?
It affects which analysis applies, not whether one does. A contractor providing services in connection with return preparation sits in a different category from a disclosure at large, and the vendor's contractual undertakings matter. What does not follow is that any feature the vendor ships is therefore permitted — a general-purpose assistant bolted onto a tax product can be doing something the preparation exception does not reach, and the vendor's own documentation is the place to establish which.
What about non-tax work for the same client?
The statute governs return information, so advisory, audit or bookkeeping work that does not involve information furnished for return preparation is outside it — and subject to the firm's other confidentiality obligations, which are real but different. The practical difficulty is that firms rarely hold the two sets separately, and information furnished for a return does not stop being return information because it was later useful for something else.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Realistic monthly lead-gen software spend | $1,500–$5,000 | Category-wide |
| US SMB retainer, focused one-to-two-service engagement | $1,500–$4,000 | Category-wide |
2026 real estate operating cost survey · plus $1,000–$8,000 variable · verified
2026 agency pricing survey · per month · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Regulation | A federal statute makes unauthorised disclosure or use of a taxpayer's return information by a preparer an offence, and the implementing regulations prescribe the form of consent including separate documents for use and disclosure and specific identification of each. | Section 7216 of the Internal Revenue Code and the consent requirements in §301.7216-3 of the Treasury regulations. |
| Constraint | Return information extends beyond the return itself to information furnished for the purpose of preparing it and information the preparer derives in doing so, which brings a client's bookkeeping export, expense schedule and treatment question inside the statute. | The definition of tax return information in the regulations, applied to the categories of client material staff actually paste into tools. |
| Procurement | Consent must precede the disclosure, cannot be bundled with other permissions, must separately identify each disclosure, and cannot be made a condition of the engagement, which means a broad technology clause in an engagement letter is unlikely to be a valid consent. | Comparing the firm's engagement letter technology clause against the prescribed consent requirements in the regulations. |
| Workflow | A substantial portion of the value firms report — abstract treatment questions, drafting without particulars, summarising technical guidance, form mechanics — involves no return information in the prompt and therefore engages the statute not at all. | Classifying a sample of staff prompts by whether any client-furnished or client-derived particular appears in them. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one