
What Section 7216 Requires
IRS Section 7216, formally 26 U.S.C. § 7216, makes it a federal crime for a paid tax return preparer to knowingly or recklessly use or disclose a client's tax return information for any purpose other than preparing that return, unless the client has signed a valid written consent first. The rule applies to every paid preparer, not just CPAs and enrolled agents, and it covers the underlying information gathered to prepare a federal return, not just the finished document.
The IRS Section 7216 Information Center and the Treasury regulations at 26 CFR 301.7216-1 through 301.7216-3 spell out exactly when consent is required, what it has to say, and when you can skip it.
Quick Answer
IRS Section 7216 (26 U.S.C. § 7216) requires a paid tax preparer to get the client's written consent before using or disclosing their tax return information for any purpose beyond preparing that return. Treasury Regulation 301.7216-3 and Rev. Proc. 2013-14 set the required content, including specific language when data goes to a preparer located outside the United States. Preparing the return itself, sharing with the IRS, and routine quality checks inside the firm don't require consent; outsourcing to a third-party processor, marketing other services with client data, or sharing it with another business usually does. Violations can trigger both a criminal misdemeanor charge and a separate civil penalty.
When You Don't Need Consent
Section 7216 exempts several routine, in-house uses from the consent requirement:
- Using the information to prepare the return itself, including related state and local returns
- Disclosing it to the IRS or in response to a valid court order or administrative order
- Sharing it with another preparer inside the same firm for preparation, review, or quality control
- Running a conflict-of-interest check before accepting a new engagement
- Providing it in response to a peer review or to your professional liability insurer
Consent becomes necessary once the data leaves that narrow lane, think outsourcing data entry or return preparation to a third-party processor, adding client data to a marketing list for other services, or sharing it with an affiliated business like an insurance or advisory arm. If you're evaluating new tax prep platforms, weigh this alongside security posture, see find me tax software options that prioritize top security measures, before assuming a vendor's data-use terms fit inside the no-consent exceptions.
What a Valid Consent Must Include
- A clear statement of the specific purpose the preparer will use or disclose the information for
- The identity of who will receive the information, if it's being disclosed to a third party
- A statement that signing is voluntary and not a condition of getting the return prepared
- Specific wording naming the country if data will go to a preparer located outside the United States
- The taxpayer's signature or affirmative electronic action, plus the date
- For electronic consent, a way for the taxpayer to withdraw it and access or print a copy
Penalties for Unauthorized Disclosure
Penalties and the Offshoring Rule
A criminal violation of Section 7216 is a misdemeanor: up to a $1,000 fine, up to one year in prison, or both, for each violation, according to 26 U.S.C. § 7216(a). A separate civil penalty under 26 U.S.C. § 6713 runs $250 per unauthorized use or disclosure, capped at $10,000 in a calendar year for most violations, rising to $1,000 per violation with a $50,000 annual cap when the disclosure is tied to taxpayer identity theft. Both can apply to the same incident, and each affected client record counts as a separate violation. Because specific penalty language and consent wording can change, confirm your forms with a tax attorney or compliance professional before rolling them out.
One rule trips up firms that outsource work: if you send client data to a preparer located outside the United States, Treas. Reg. 301.7216-3 and Rev. Proc. 2013-14 require the consent to specifically name that fact and identify the country. A generic consent form that doesn't mention offshore processing doesn't satisfy the requirement, even if the client signed it.
Check Your AI and Software Vendors
Feeding client tax data into a generative AI tool, a new practice-management platform, or any third-party service that wasn't part of preparing the specific return can trigger the same consent requirement as outsourcing. Before adopting a new tool in 2026, confirm what it does with client data and whether you need a fresh signed consent, not just an updated terms-of-service click-through.
Build Consent Into Your Data Security Program
Section 7216 consent is a legal formality, but the underlying question, who can see your clients' tax data and why, is also a core piece of the data security program the FTC Safeguards Rule and IRS Publication 4557 expect every tax practice to maintain. A written information security plan (WISP) should document every vendor and tool that touches client return data, which is the same inventory you need to know whether a 7216 consent is required. If you don't have one yet, start with the IRS WISP template or, for a one-person practice, the WISP template for sole proprietors.
Consent paperwork doesn't protect data that leaks through a phishing email or a compromised vendor account. Pair your 7216 process with basic controls: review phishing attacks on tax professionals and business email compromise prevention for tax firms so data you've properly disclosed doesn't end up exposed by a separate incident.
Need Help Mapping Your Client Data Flows?
A free assessment can help you see where client tax data goes, which vendors touch it, and where your WISP and 7216 consent process need updates.
Frequently Asked Questions
Rev. Proc. 2013-14 requires the consent to state clearly what engagement or period it covers. A consent signed for one return doesn't automatically carry over, so most firms have clients sign a fresh consent each filing season rather than relying on an open-ended one from a prior year.
Using software to prepare the return itself doesn't require separate client consent, that's the core exception. Consent becomes relevant if the vendor uses the data for something beyond return preparation, such as analytics, model training, or marketing, so check the vendor's data-use terms directly.
Section 7216 is the criminal statute; Section 6713 is the matching civil penalty. The same unauthorized disclosure can trigger both: a misdemeanor charge under 7216 and a separate dollar penalty under 6713.
No. Treasury regulations require consent to describe the specific use or disclosure and, where relevant, name the recipient. A vague, open-ended consent that doesn't describe what's being disclosed or to whom doesn't meet the requirement.
From requirement to defensible practice
Turn IRS and FTC expectations into a WISP your office can follow
A useful compliance path makes the obligation clear, identifies the evidence to retain, and connects written policy to the safeguards used every day.
People also look for
Keep exploring Tax security & WISP
Understand what tax professionals need to document, protect, and prepare before an IRS or FTC review.
- Common question: free WISP templateStart with a written information security planUse a practical WISP framework built around the safeguards tax practices need.
- Common question: IRS Publication 4557 requirementsRead the Publication 4557 guideSee how the IRS expects tax professionals to safeguard taxpayer data.
- Common question: IRS WISP requirementsReview the WISP requirementsWork through the required sections and the evidence your practice should retain.
- Common question: FTC Safeguards Rule checklistUse the FTC Safeguards checklistTranslate the rule into a clear list of security and documentation tasks.
- Common question: tax practice incident response planPrepare a tax-office incident planKnow who to contact, what to preserve, and how to respond to a client-data incident.



