Under Section 7216, a disclosure that goes past what the tax return preparation process requires generally needs the taxpayer's consent. That consent must come before the disclosure, and it must be in the form the IRS points to. Partners and operations leads at small accounting firms face this question whenever a lender, a software vendor, or a related business asks for client tax data.
This post turns that rule into three consent points. They are built from an IRS FAQ on Section 7216 and a Tax Adviser article on the same section. The Tax Adviser article says it should by no means be considered a comprehensive guide to Section 7216, and the same caution applies to this post. Treat the three points as an order for asking questions, not as a full map of the rule. Read the cited pages in full before you act.
The three points are these. First, sort each disclosure before deciding whether consent applies. Second, get consent before any disclosure happens, and check that it is in the form the IRS points to. Third, keep disclosure and use apart, and track any withdrawal.
The order matters. Sorting comes first because the consent rule targets one kind of disclosure, the kind that goes past preparation work. Until a firm knows which side of that line a request falls on, it cannot decide what the consent step should look like. Timing and form come second, and they matter whenever consent is the route the firm takes.
Point 1: Sort each disclosure first
Each disclosure has to be sorted before the firm can say whether consent applies. The Tax Adviser article says that preparers must evaluate each disclosure to determine which category it falls into, so sorting comes first.
| Sorting element | What the source says | Source |
|---|---|---|
| Disclosure category | Preparers must evaluate each disclosure to determine which category it falls into | Tax Adviser |
| General consent rule | Any disclosure beyond what is necessary for the tax return preparation process requires the taxpayer's consent | Tax Adviser |
| Consent timing | Taxpayer consent must be obtained before any disclosure is made | Tax Adviser |
| Lender staff question | Q16: Are the staffs of banks and credit unions receiving tax returns for mortgage applications tax return preparers? | IRS FAQ |
| Consent to disclose question | Q8: When and how does a tax return preparer obtain consent to disclose tax return information? | IRS FAQ |
The article's central line is that any disclosure of taxpayer information that goes beyond what is necessary for the tax return preparation process requires the taxpayer's consent under Section 7216. The article states this as a general rule. Two words do most of the work. The first is "beyond," which sets consent against disclosures that go past what preparation requires. The second is "necessary." The excerpt does not define the tax return preparation process any further, so the firm has to apply that boundary to each request and write down what the return work actually needs.
The article refers to categories without naming them in the excerpt, so the firm will need to find them in the full text. A simple way to keep sorting consistent is a short note for each request: what data is involved, who would receive it, and what purpose the request gives. That note is my suggestion, not a requirement from either source. It does give a reviewer the facts needed to measure the disclosure against the sentence about necessity.
Take a request to pass client return data to an outside software vendor. Whether that request goes past the preparation work is the first thing to settle. The sources here do not decide that question for vendors, and the firm should not assume that an answer for one arrangement carries over to another.
A second request might ask for client data so a related business can use it for something other than preparing the return. The test is the same. If the disclosure goes past what the preparation process requires, the Tax Adviser sentence says consent is required, in general. The firm then moves on to the timing and form checks in Point 2.
The excerpt lists no exceptions to that general rule. That does not mean there are none. The firm should not read the general rule as a complete list of when consent is required, and it should not read the silence of the excerpt as proof that no exceptions exist.
Lender requests deserve their own look. The IRS FAQ addresses lender-side staff directly in Q16: "Q16 Are the staffs of banks and credit unions that receive copies of tax returns in connection with applications for mortgages included within the definition of tax return preparers?" The question shows the IRS has treated this as a live issue. The excerpt gives only the question, so the answer on the page will decide how a firm should handle a mortgage lender's staff. Read that answer before sending anything to a lender.
The IRS also asks the disclosure question directly. Its Section 7216 FAQ includes Q8: "When and how does a tax return preparer obtain consent to disclose tax return information?" The question points to the right subject. The excerpt shows only the question, though, so it cannot tell you when or how consent is obtained. Read the full answer on that page before relying on it.
Point 2: Get consent before any disclosure, in the required form
Consent has to be in place before the disclosure happens. The Tax Adviser article states that, to ensure compliance with the law, taxpayer consent must be obtained before any disclosure is made. Consent gathered after information has already reached an outside party does not match that sentence. Once sorting shows that consent applies, timing is the first consent check on any request.
| Check | Requirement | Source |
|---|---|---|
| Timing | Taxpayer consent must be obtained before any disclosure is made | Tax Adviser |
| Form language | Specific language must be included under Revenue Procedure 2013-14, section 5.04(e)(ii) | IRS FAQ |
| Consent to disclose | Q8: When and how does a tax return preparer obtain consent to disclose tax return information? | IRS FAQ |
The timing rule applies to the consent itself, not only to the data. If a request arrives before consent is in hand, it waits. The sources do not describe a grace period or any exception for early requests, so the firm should not invent one.
One way to apply this is to write down two dates for each disclosure: when consent was given and when the data would go out. If the consent date is not earlier, the request waits. That step draws only on the word "before" in the article, and the sources say nothing more about it.
Form is the second check. The IRS FAQ gives this instruction: "See also Revenue Procedure 2013-14, section 5.04(e)(ii) for specific language that must be included in the consent form." A consent form is therefore a document with required content, not just a signature line. A form that looks complete may still lack the language the section calls for, so compare the form against the section itself before using it with any client.
The sources reproduced here do not show that language, so this post cannot tell you the required wording. Get Revenue Procedure 2013-14 and read section 5.04(e)(ii) directly.
Before any form goes out, confirm three things. The consent is dated before the disclosure it covers. The form matches the section the FAQ cites. The form covers the specific disclosure being proposed. The first two come from the sources. The third is my own practical check, not a requirement from either one.
The FAQ also asks about consent to use tax return information. That question, Q11, belongs under Point 3, because disclosure and use are separate questions.
Point 3: Keep disclosure and use apart, and track withdrawal
Disclosure and use are separate questions in the IRS FAQ. The Tax Adviser article says taxpayers may terminate their consent at any time. The FAQ asks about consent to disclose in Q8 and about consent to use in Q11: "When and how does a tax return preparer obtain consent to use tax return information?" Because the FAQ treats the two separately, a proposed use of client data should be checked on its own, even when a disclosure of the same data has already been cleared.
| Question | What the source says | Source |
|---|---|---|
| Consent to disclose | Q8: When and how does a tax return preparer obtain consent to disclose tax return information? | IRS FAQ |
| Withdrawal | Taxpayers have the right to terminate their consent at any time | Tax Adviser |
| Suspicious return use | Q21: May a tax return preparer use tax return information to identify a suspicious or potentially fraudulent tax return? | IRS FAQ |
For the same reason, the firm should not treat consent for one purpose as settling another. The sources do not say whether consent given for one purpose can ever extend to a different one, so the firm should not assume that it can.
Here are the sourced rules side by side, so the three points can be checked against one list.
| Topic | What the source says | Source |
|---|---|---|
| Disclosure beyond what is necessary for return preparation | Requires taxpayer consent under Section 7216, in general | Tax Adviser |
| Timing of consent | Must be obtained before any disclosure is made | Tax Adviser |
| Consent form content | Specific language must be included under Revenue Procedure 2013-14, section 5.04(e)(ii) | IRS FAQ |
| Sorting disclosures | Preparers must evaluate each disclosure to determine which category it falls into | Tax Adviser |
| Withdrawal | Taxpayers have the right to terminate their consent at any time | Tax Adviser |
Each row links to the page it came from, so every statement can be checked against the text there.
The Tax Adviser sentence about withdrawal concerns the taxpayer's right to terminate consent. The excerpt does not say what happens to disclosures made before a withdrawal, so do not assume an answer. Find it in the full text before a withdrawal arrives, not after.
Operations leads can take one practical step. This is my suggestion, not a source requirement: keep a record for each client showing when consent was given, what it covers, and whether it has been withdrawn. With that record, a proposed disclosure is checked against the consent on file rather than against someone's memory of a conversation.
Withdrawal also needs a short internal process. When a client withdraws, the firm should be able to find the change quickly, which is one reason to keep consent records in a single place. The Tax Adviser sentence says only that consent may be terminated at any time. The firm's own process has to decide how quickly a withdrawal is recorded, because the sources do not set that timing.
Running one request through the three points
Run a request through the three points in order: sort it first, compare dates second, and check the form last. Here is how that might look for one proposed disclosure to a lender.
Start with sorting. Does the disclosure go past what the return work requires? If it does, the general rule says consent is required. Next, pull the consent on file and compare its date with the date the data would be sent. If the consent came later, the disclosure waits. Last, open the consent form and compare its wording with the section the FAQ cites. Only when every check passes should the data move. If a check cannot be passed, the firm holds the disclosure or gets the missing material first. Either way, the disclosure stays on hold until the gap is closed.
Where the sources stop
Each source does a different job here. The IRS FAQ is the agency's own page. It supplies the Q8 and Q11 questions, the Q16 question about lender staff, the Revenue Procedure reference, and the Q21 question. The Tax Adviser piece is an article, and it supplies the sorting, timing, and withdrawal statements. Neither source, as quoted here, answers every question a firm will face.
A reader who wants to verify a statement can start with the cited page, find the quoted sentence, and read the material around it. The quotes were chosen for the rule each one states, and the surrounding text may add conditions the excerpt leaves out. That is why readers should read the full pages before acting.
The gaps are specific. The IRS excerpts show Q8, Q11, and Q16 as questions without their answers. The FAQ also includes Q21, which asks whether a tax return preparer may use tax return information to identify a suspicious or potentially fraudulent tax return or suspicious patterns of conduct. This post cannot answer that question. The excerpts also do not reproduce the consent language in Revenue Procedure 2013-14, do not define the boundary of the preparation process, and do not say what happens to disclosures already made when consent is withdrawn.
None of that makes the three points less useful. They tell a partner which questions to ask, and in what order. Is the disclosure past what the preparation process requires? Is consent in place before the disclosure, and in the form the IRS points to? Is use covered as its own question, and is the consent still active? Answering those with the full pages in hand is the work that remains.
A separate resource may help with the data side of the job. The U.S. Small Business Administration notes that "The Federal Communications Commission (FCC) offers a cybersecurity planning tool (The Small Biz Cyber Planner 2.0)." That tool deals with cybersecurity planning, not Section 7216 consent, so it does not answer the questions in this post. A firm that holds and moves client data may still find it a useful companion when it plans how to protect what it keeps.
If a request falls into one of the gaps, the firm has three general options: hold the disclosure, get the full text of the cited page or Revenue Procedure before deciding, or put the question to an adviser who works with Section 7216 directly. The three points tell that adviser which facts to bring: the sorting note, the consent date, and the consent form.
Not legal or tax advice.
Related guides: 3 ways to handle a client's disclosure consent in Drake · Accounting Client Intake Checklist for a Clear Handoff · ACH invoice fees: 4 facts to check before a client pays.