Section 7216 client consent is a taxpayer’s authorization, meeting applicable requirements, for a tax return preparer’s specified disclosure or use of tax return information when the action is not otherwise permitted under an applicable exception.
Why does Section 7216 matter during a practice sale?
An acquisition can involve disclosing tax return information to people outside the seller’s existing preparation relationship. Each proposed disclosure and use needs its own lawful basis before access occurs.
The valuation hub helps sellers present the practice’s economics, but transaction diligence does not make taxpayer information ordinary commercial inventory. A buyer may reasonably need to assess service complexity or client concentration without being entitled to receive an unrestricted archive of returns. Start by defining the diligence question, then select the least revealing evidence that answers it lawfully.
The IRS Section 7216 information center identifies regulations and guidance governing disclosures, uses, and exceptions. It specifically distinguishes information disclosed for sale-related due diligence from a transfer. That distinction makes a staged access process more useful than assuming every acquisition request has the same treatment.
Are an NDA and taxpayer consent interchangeable?
No. An NDA is a contractual confidentiality commitment between its parties; taxpayer consent addresses a particular authorization under the relevant tax-information rules.
A confidentiality agreement can limit a recipient’s behavior, require security, restrict onward disclosure, and provide remedies. Those protections matter. They do not independently establish an exception or supply the taxpayer’s required authorization. Similarly, a consent does not make an insecure data room acceptable or eliminate contractual and professional obligations.
Think of the review as several connected questions: may the seller disclose this information, may this recipient use it for this purpose, and can both parties protect it appropriately? Record the answer to each. If the legal basis has not been established, an executed NDA is a reason to continue controlled diligence, not permission to upload identifiable returns.
What information should the access plan distinguish?
Distinguish the data, recipient, purpose, timing, and onward flow. A label such as client list or financial file may obscure the information actually contained in the document.
| Requested material | Commercial purpose | Question to resolve before access |
|---|---|---|
| Aggregate service revenue | Evaluate the earnings base | Does the aggregation adequately protect identities? |
| Client-level fee schedule | Analyze concentration and retention | What information and lawful basis permit this disclosure? |
| Sample tax return | Assess preparation complexity | Is this sample necessary and properly authorized? |
| Complete client archive | Plan continuing service | What rules govern the actual transfer and intended use? |
| Buyer advisory campaign | Offer additional services | Is the proposed use separately permitted or consented? |
The table is a planning framework, not a determination that any row is automatically allowed. Have counsel evaluate the proposed facts, including information that appears outside a completed return but may still fall within the relevant definition.
How should the seller evaluate an exception?
Identify the exact exception, then verify every condition against the proposed disclosure or use. Avoid general statements that selling a practice makes all client data transferable.
The sale-related provisions can have defined scopes and conditions. A permitted list or a disclosure supporting specified due diligence should not be generalized into unrestricted access to every tax document. The IRS’s published Section 7216 regulations and Revenue Procedure 2013-14 provide the underlying regulatory and individual-return consent framework referenced by the information center.
Prepare a short legal-basis record for each access category. State the data included, the purpose, recipient, applicable exception or consent, limitations, and approving reviewer. If the buyer changes its request from valuation diligence to marketing a separate service, reopen the analysis. The purpose has changed even if the proposed recipients and spreadsheet remain identical.
What makes a consent usable for the intended action?
The consent must meet the applicable content, form, timing, and other requirements for the taxpayer and proposed action. A generic authorization embedded in unrelated paperwork may not do that.
The taxpayer-consent regulation requires knowing and voluntary consent and addresses its validity and requirements. Individual-return consents also require attention to the relevant revenue procedure. Have the responsible adviser prepare or approve the actual language rather than copying a short clause from an acquisition checklist.
Describe the recipient, information, purpose, and authorized action as required. Keep evidence of the consent and a process for verifying it before release. If consent is refused or unavailable, change the diligence approach or exclude the affected disclosure until another lawful basis is established. Commercial urgency does not answer the authorization question.
How can the parties stage diligence without oversharing?
Start with commercial facts that can be evaluated in a controlled form, then expand access only after the legal and security basis is documented. The sequence should follow actual analytical needs.
- Define the buyer’s question and the minimum evidence needed to answer it.
- Classify the requested information and proposed recipients or uses.
- Have qualified advisers confirm an applicable exception or required consent.
- Prepare the approved material and apply the agreed access controls.
- Record access, enforce purpose limits, and address retention or deletion when the stage ends.
For early pricing, a coded revenue schedule may answer more than a file containing names, addresses, Social Security numbers, and returns. However, coding alone should not be assumed to remove every legal issue. Review whether the material still reveals or permits identification, and whether the proposed disclosure is allowed under the applicable rules.
What can a consent-readiness example show?
It can show workflow capacity and unresolved access categories, without pretending that a simple completion percentage proves legal compliance.
Assume an illustrative transaction has 240 client records proposed for a particular consent-based disclosure. The seller’s log shows 180 reviewed and approved consents, 30 pending requests, 20 declines, and 10 records needing clarification. The approved category is 180 divided by 240, or 75%. The remaining 60 records require a different treatment before that proposed disclosure.
This is an administrative illustration, not a claim that every practice sale requires consent from every client. The basis must be evaluated first. Track applicable exceptions separately from consent-based releases. Avoid adding those categories together under a misleading all-clear label when they authorize different information, recipients, or uses.
How do consent, security, and engagement documents fit together?
They address different aspects of the transition and should operate as one controlled workflow. A lawful disclosure still needs secure handling and accurate service documentation.
Coordinate the FTC Safeguards Rule and WISP review with data-room permissions, encryption, recipient access, and post-closing system migration. Match the authorized purpose to the buyer’s actual use. If a technology provider or offshore resource is introduced, evaluate that separate flow before information is sent.
The engagement letter identifies the service relationship and agreed scope, while required consent addresses specified information use or disclosure. Neither document should silently carry the entire transition. A buyer acquiring a book of business should know which relationships, service rights, and records can move through the approved process.
What should happen when the transaction ends or changes?
Reconcile authorized access with the new facts. A failed deal, different purchaser, expanded diligence scope, or changed service plan can require revised handling and review.
For a terminated transaction, apply the agreed return, deletion, retention, and confidentiality provisions consistently with applicable requirements. Keep evidence that access was disabled and that recipients addressed copies and downstream providers. Do not assume closing or termination automatically revokes every permission or ends every record-retention obligation; confirm the governing documents and rules.
For a completed transaction, maintain a release log tied to the actual basis for disclosure and intended use. Assign an owner for unresolved records and new requests. The result should be a traceable transition that supports client service while preserving the limits under which the information was made available.
A few common questions
What else should you know?
Does every practice sale require consent from every tax client?
Do not assume a universal answer. The applicable treatment depends on the information, disclosure or use, transaction facts, and conditions of any exception. Counsel should evaluate those details before access. If the planned action requires consent, obtain a compliant authorization; if an exception applies, document its scope and conditions.
Can the buyer inspect tax returns after signing an NDA?
The NDA does not itself establish permission under Section 7216. First evaluate whether the proposed disclosure is permitted by an applicable exception or supported by valid taxpayer consent. Then apply security and purpose restrictions. A legitimate diligence objective and a confidentiality promise do not replace that legal-basis review.
Can acquired tax information support marketing other services?
The proposed use requires a separate review. Permission to disclose information for specified transaction diligence or continuing preparation should not be assumed to authorize unrelated marketing. Identify the actual purpose and relevant conditions, then determine whether an exception or compliant consent supports that use before creating or sending a campaign.
What evidence should the seller retain for client-data releases?
Keep the approved data category, recipients, intended purpose, governing exception or consent, reviewer, and access record. Preserve consent evidence where applicable and document any limits or unresolved records. The record should let another reviewer reconstruct why particular information was released and whether a later request needs a fresh analysis.
Which sources support this guide?
Primary rules and guidance support the factual statements in this article. The worked examples and decision frameworks are original educational analysis.
- Section 7216 information center — Internal Revenue Service
- Revenue Procedure 2013-14 and final Section 7216 regulations — Internal Revenue Service
- Disclosure or use permitted only with taxpayer consent — Electronic Code of Federal Regulations