The IRS Section 7216 FAQ asks about outside groups that use tax return data, including Medicaid application preparers, co-op board members, fee-based financial planners and financial aid advisors. Whether any of them must obtain taxpayer consent before a disclosure is made depends on evaluating each instance on its own facts.
Chief takeaways
- The IRS Section 7216 FAQ reaches tax return preparers plus other persons who work with preparers and taxpayers, not just those who sign returns.
- Four named groups appear in the FAQ: Medicaid application preparers, co-op board members, fee-based financial planners and financial aid advisors who use return data.
- Consent must be evaluated before a disclosure is made, and each instance is judged on its own facts for both whether consent is required and what form it takes.
- A use-based test, not a job title, determines coverage: anyone who touches return data for a separate purpose may fall within the rule.
- Offices should log each outside request for return data with the requester, data used, stated purpose, evaluation result and consent form chosen.
Who the IRS rule is written to reach
The FAQ does not stop at the people who sign returns. It says it is "intended to inform tax return preparers and other persons who work with preparers and taxpayers about important rules and regulations that apply to them and the way they do business" ( IRS FAQ). That sentence names two audiences: the preparers, and anyone who works with preparers or taxpayers. The second group can include office staff, bookkeepers, contractors and outside helpers who handle a return or data drawn from one.
For a partner or operations lead, a job title is a weak test. A person may never prepare a return and still touch return data while helping with a different task. Three questions turn on use of return data, while Q18 turns on a return being required in a package. It asks about someone outside the preparer role who uses a copy of a return, or data taken from one, for a purpose of their own.
The Tax Adviser states the test this way: "Each instance needs to be evaluated carefully to determine whether consent is required before a disclosure is made and, if so, what form the consent must take" ( The Tax Adviser). The FAQ supplies the questions, and the article supplies the method for answering each one.
Read together, the two sources give a clear order of work. First, identify who receives return data. Second, decide whether that use requires consent. Third, if it does, settle the form. Staff roles and vendor labels come after those three questions, not before them.
When consent is required before a disclosure
The phrase that carries the most weight is "before a disclosure is made." The Tax Adviser places the consent question ahead of the act of disclosing, so timing is part of the test. A consent question asked after return data has already gone to an outside party does not fit the sequence the rule describes ( The Tax Adviser).
| Consent question part | What it asks | When it applies | Source |
|---|---|---|---|
| Whether consent is required | Whether consent is required before a disclosure is made | Every instance evaluated on its own facts | The Tax Adviser |
| What form the consent takes | What form the consent must take | Only when the first answer is yes | The Tax Adviser |
| Timing of the evaluation | Consent evaluated before a disclosure is made | Before return data leaves the office | The Tax Adviser |
| FAQ's first named group | People who prepare Medicaid applications | Q17 asks whether they are deemed subject to the regulations because they use return data | IRS FAQ, Q17 |
The FAQ shows what a disclosure looks like in practice. Its first question asks about people who "use tax return data in preparing Medicaid applications" ( IRS FAQ, Q17). The FAQ asks whether that use brings the helpers under the regulations.
An office can make the timing visible by logging each outside request for return data when it arrives. The log should record what data was requested, who asked, and the stated purpose. That gives the office a record to evaluate before anything leaves the building.
The form question is where the answer may change from one instance to the next. The Tax Adviser says the evaluation covers "what form the consent must take," which signals that one written form will not fit every use. An office that treats every request the same way will likely miss the cases where the form has to change.
Taken together, a general sign-off is not enough. This post recommends that the review happen at the point of disclosure and record the specific use, so the office can say what was asked, what was decided and why.
Medicaid application helpers and tax data
The FAQ's first named group is the people who prepare Medicaid applications. The question asks whether they are "deemed subject to the regulations because they use tax return data in preparing Medicaid applications" ( IRS FAQ, Q17). The trigger is use. The question does not turn on job title or on whether the helper signs the return.
The four named FAQ questions are compared side by side below, using the FAQ's own wording for each group.
| FAQ item | Group named | Tax data the question describes |
|---|---|---|
| Q17 | People who prepare Medicaid applications | Tax return data used in preparing Medicaid applications |
| Q18 | Members of co-op boards of directors | A tax return included in a package when seeking approval to purchase a co-op |
| Q19 | Fee-based financial planners | Copies of a tax return reviewed to create a financial plan |
| Q20 | Financial aid advisors | Tax return data they utilize |
For an office that prepares or reviews Medicaid applications for clients, the Medicaid row deserves close reading. Staff who draft or review an application may open a prior-year return to pull income figures or household details. Each time a return copy or figure goes into an application file, that movement is the use the FAQ describes. The office can list which employees and contractors work on these files and where return data appears in each one.
Some offices assume application helpers sit outside the tax team and therefore outside the rule. The FAQ question does not test that assumption. It asks about use, so a helper who never signed a return can still fall within it.
Map the Medicaid workflow from intake to submission, and mark every point where a return or return figure is read or copied. That map becomes the starting record for the consent review.
Q17 asks whether Medicaid application preparers are deemed subject to the regulations because they use tax return data in preparing those applications. That question belongs to the instance evaluation, and the Tax Adviser's sentence sets the two questions in order: whether consent is required before the disclosure, and if so, what form it must take. Until both have been answered for the Medicaid workflow, the office should not assume that staff who work on applications are outside the rule.
Co-op board reviewers and returns in purchase packages
The second named group is the members of co-op boards. The FAQ asks whether they are "subject to the regulations because they require a tax return in the package of documents that must be included when seeking approval to purchase a co-op" ( IRS FAQ, Q18). Here the tax office does not request the return. The co-op's approval process asks for it, and the document reaches people outside the tax relationship.
The buyer's accountant or preparer may send the return to the buyer, who then places it in the approval package. The board receives it from a third party. The FAQ places board members themselves under the question, so the review should not stop at the preparer who first gave the buyer a copy.
For a firm that prepares returns for buyers or helps assemble packages, the useful question is where the copy goes after it leaves the office. Note whether the firm sends it, whether the buyer forwards it, and whether the firm knows which board members will see it.
Timing matters as well. The return is required "when seeking approval," so the disclosure happens inside a transaction with a fixed sequence. An office should know when the package is due and whether the return will be included, so it can run the consent evaluation before assembly rather than after submission.
The buyer side of the transaction also deserves attention. A buyer who receives a return from a preparer and then forwards it into a board package has made a second movement of the same data. The FAQ question describes the board's place in that chain, so an office that prepares a return for a buyer should not assume the disclosure ends at its own door.
Fee-based financial planners who review returns
The third group is the fee-based financial planner. The FAQ asks whether such a planner is subject to the regulations "because they review copies of tax return in order to create a financial plan" ( IRS FAQ, Q19). The return is an input to the planner's own product, and the question ties the disclosure to that use.
The fee arrangement does not change the test. The Tax Adviser's rule is to evaluate each instance, deciding whether consent is required before a disclosure and, if so, what form it takes ( The Tax Adviser). The planner's business model is one of the facts of the instance, not a substitute for the evaluation.
A practice that refers clients to planners, or employs them, should identify whether a return copy leaves the tax team when a client asks for a financial plan. If it does, record who receives it and for what stated purpose.
A planner's review of a return can also reveal information the client did not expect to share with a third party. Because the test is about use, the office should describe the planning purpose in its record, not only the fact that a copy was sent.
A client who once asked the office to send a return to a planner has not settled later requests. Each request is its own instance and should be evaluated when it arrives.
Financial aid advisors who use return data
The fourth group is the financial aid advisor. The FAQ asks: "Are financial aid advisors included because they utilize tax return data?" ( IRS FAQ, Q20). The question names its trigger plainly. The advisor uses tax return data. It does not add conditions about who prepared or signed the return.
The advisor's role is to read figures from the return and apply them to an aid calculation or planning recommendation. Q20 names only use as its trigger: the advisor uses tax return data. The use is what matters.
The first action is to find out where financial aid work touches tax files. Some families bring a return to an aid advisor; others have the tax office send figures directly. Log each route. A route that moves return data outside the office is the kind of event the consent test is written to evaluate ( The Tax Adviser).
The second action is to decide, for each route, who inside the office may release return data to an advisor. Limiting that role to a few named people makes the evaluation easier to repeat and to document.
Case-by-case review: the two-part evaluation
The working rule applies to every item in the FAQ, and it has two separate parts. The first asks whether consent is needed at all. The second applies only when the answer is yes, and asks what form the consent should take. Neither part can be settled once for the whole office.
| Intake record field | What it captures | Why it matters | Source |
|---|---|---|---|
| Requester | Who asked for the return data | Identifies the outside party | Author's recommended practice |
| Data used | Which data was used | Ties the record to the specific return data | IRS FAQ, Q20 |
| Stated purpose | What the advisor planned to do with it | Describes the use, not just the transfer | Author's recommended practice |
| Evaluation result | Whether consent was required before disclosure | Answers the first part of the test | The Tax Adviser |
| Form of consent chosen | What form the consent took, if any | Answers the second part of the test | The Tax Adviser |
Financial aid shows the point. The question names a use, not a relationship. The FAQ question asks whether an advisor who uses return data is included; the quoted item states the question and not the answer. The first step is to describe the instance: who asked, which data was used, and what the advisor planned to do with it.
The second step is the form. Because the form depends on the instance, a consent form built for a planner's review may be wrong for a figure taken into an aid calculation. Write down the instance first and choose the form second.
In practice, use a short intake record for each request. It should show the requester, the data, the stated purpose, the result of the evaluation, and the form of consent chosen, if any. The record lets a partner see later why a request was handled as it was. The fields can be adapted to the office's practice while asking the same questions each time.
Choosing how to handle each request
The choice is about how to handle each request, not about which outside group to hire. The planner question shows the pattern: a return copy is used for a stated purpose, and the Tax Adviser's rule requires evaluation before disclosure. Three ways of handling a request follow.
| Option | Fits when | What the cited rules say about it |
|---|---|---|
| Keep return data inside the tax team | No outside party needs the data for its own purpose | Nothing leaves the office, so there is no outside disclosure to evaluate |
| Share a return copy with an outside helper | The helper has a stated purpose that needs the return | Evaluate the instance before disclosure and settle the form of consent it requires |
| Share only the figures the helper needs | The helper needs specific numbers rather than the whole return | Nothing in the cited rules says a smaller disclosure removes the evaluation, so treat it as another instance |
For most offices the default is the first row. Move to the second only when a request has a stated purpose and the evaluation is complete. The third row looks like a shortcut, and the cited rules do not support treating it as one. Recording the choice made for each request keeps the decision visible.
Who records the decision
The Tax Adviser's sentence places the evaluation on "each instance," but it does not say who carries it out. That is for the office to decide. A partner or operations lead is a sensible choice to sign off, because the decision covers both whether consent is needed and what form it takes.
The FAQ and the Tax Adviser article are the two sources cited here. Check both when a decision is made. The FAQ is a list of questions, and the article reflects the rules as they were explained when it was published. Note the date of each check in the record.
Name a single signer for each office to sign each record, with a backup for absences. A signed record listing the requester, the data, the purpose and the form of consent is simple to produce and simple to review.
Why the rules reach staff and outside helpers alike
The FAQ's stated audience is broad. Beyond preparers, it reaches the "other persons who work with preparers and taxpayers" ( IRS FAQ).
That structure explains why the questions are about use rather than job. The rule follows the data. A staff member who opens a return to answer a client's question is working with return data, and so is a contractor who copies figures into a Medicaid form.
Three consequences follow for an operations lead. Training should reach everyone who handles return data, not only the signers. Access to return files should be limited to named roles and reviewed when the workflow changes. Outside helpers should be handled the same way as staff, because the question is what each one does with the data.
Training content can follow the four groups in the FAQ. A short session can walk through the Medicaid workflow, the co-op package, the planner request and the aid referral, asking at each point who sees the data and why. Staff who work in those roles will then recognize their own tasks in the FAQ questions rather than reading the rule as a matter for signers alone.
The FAQ questions turn on use rather than on job title. A title check would miss the aid advisor who uses data, the planner who reviews copies, and the board member who receives a package. A use-based test asks whether each of them falls within the rule.
Related guides: Non-credentialed preparer representation: 4 IRS exam rules · Last known address: 5 rules for IRS client notices · Accountable plan tests: 3 rules before a reimbursement.
Reader questions
Who is the FAQ written for? The FAQ is written for tax return preparers and for "other persons who work with preparers and taxpayers" ( IRS FAQ). That wording covers staff and outside helpers as well as the people who sign returns.
Does a helper have to sign a return to fall under the rule? The Medicaid question asks about people who "use tax return data in preparing Medicaid applications" ( IRS FAQ, Q17). The trigger is use, and signing is not mentioned.
Does the FAQ give the answers to its questions? The four questions identify the groups at issue, and each group must be evaluated under The Tax Adviser's instance test. For each group, run the instance evaluation described by The Tax Adviser.
When does the consent question need an answer? The Tax Adviser says consent is evaluated "before a disclosure is made" ( The Tax Adviser). Asking after the data has gone out does not fit that sequence.
Does a co-op package change the analysis? The co-op question asks whether board members are subject to the regulations "because they require a tax return in the package of documents that must be included when seeking approval to purchase a co-op" ( IRS FAQ, Q18). The package is where the return is disclosed, so the evaluation belongs before the package is assembled.
Does calling a planner fee-based change the test? The planner question turns on reviewing copies of returns to create a financial plan ( IRS FAQ, Q19). The Tax Adviser's test applies to each instance, so the fee label is one fact among others, not a replacement for the evaluation ( The Tax Adviser).
Does one consent cover later requests? The cited sources do not say that it does. The Tax Adviser's language points to evaluating each instance separately, so an earlier decision should not be assumed to cover a later request ( The Tax Adviser).
Not legal or tax advice.