Most practitioners will encounter this situation at some point in their careers: a client discloses, or you discover, that the return you are preparing contains fraudulent information. The client underreported income, fabricated deductions, or asks you to claim a credit they know they do not qualify for. What you do in the next hour matters more than almost anything else in your professional practice.
This guide covers the complete tax preparer liability framework for client fraud situations: the three scenarios that create fraud exposure for preparers, what Circular 230 Section 10.21 requires (and importantly, what it does not require), the IRC 6701 aiding-and-assisting penalty and where it applies, how to withdraw from an engagement properly without creating additional exposure, what the engagement letter should have said before this situation arose, the Section 7216 confidentiality boundary that governs what you can and cannot disclose, how to document the withdrawal file, when to refer the client to legal counsel, when to notify your E&O carrier, and how to manage OPR referral risk.
This guide is informational and does not constitute legal advice. The fraud scenarios described here create real legal risk for practitioners, and the appropriate response to a specific situation may require consultation with an attorney familiar with tax practitioner regulation and malpractice defense. All regulatory citations should be verified at IRS.gov against the current version of 31 C.F.R. Part 10 and the applicable IRC sections before relying on them in any specific matter.
When Client Fraud Becomes the Preparer's Problem: The Three Scenarios
The practitioner's legal exposure in client fraud situations depends heavily on what the practitioner knew, when they knew it, and what they did after learning it. The analysis differs across three distinct scenarios.
Discovery of prior fraud: the client's past returns contain fraud you did not prepare
A new client provides prior-year returns for review or context, and the practitioner identifies what appear to be fraudulent items (income clearly underreported based on lifestyle, deductions that do not match documentation, credits that the client clearly does not qualify for). The practitioner did not prepare these returns and had no involvement in the prior fraud. The risk here is narrow but real: if the practitioner uses the fraudulent prior returns as a basis for the current return without appropriate scrutiny, they may be incorporating the fraud into their own work product. The appropriate response is to advise the client of the noncompliance and its potential consequences, and to address the current-year return based on the actual facts rather than the fraudulent prior-year baseline.
Client admits fraud mid-preparation: the disclosure during engagement
During the current engagement, the client discloses (or the practitioner discovers) that the information provided is fraudulent: income figures are intentionally understated, deduction documents are fabricated, or the client explicitly states they want to claim an item they know is improper. This is the most legally significant scenario because it creates a clear record of the practitioner's knowledge of the fraud before the return is completed. Continuing to prepare the return after this disclosure creates IRC 6701 exposure and OPR exposure. The correct response is to stop work and advise the client that the engagement cannot continue on the basis of fraudulent information.
Practitioner suspects but cannot confirm: the ambiguous red-flag situation
The client's income seems inconsistent with their lifestyle, deduction documentation has unexplained gaps, or certain numbers do not reconcile. The practitioner has not confirmed fraud but has red-flag concerns. This is the most common scenario, and it is the one where Circular 230's reasonable inquiry standard under Sections 10.22 and 10.34 most directly applies. The practitioner is not required to perform a forensic audit, but Circular 230 requires competence and due diligence. A practitioner who prepares a return while ignoring obvious red flags that a reasonable practitioner would have investigated cannot claim ignorance as a defense if fraud is later established.
Circular 230 Section 10.21: The Advise-and-Withdraw Standard and What It Actually Requires
Circular 230 Section 10.21 (verify exact current language at IRS.gov against 31 C.F.R. Part 10) addresses a practitioner's duties when they know a client has not complied with federal tax laws. The section is frequently oversimplified in professional discussions. Here is what it actually requires and what it does not require.
What Section 10.21 requires
Section 10.21 requires a practitioner who knows of a client's noncompliance, error, or omission to promptly advise the client of the noncompliance and of the consequences under the Code and regulations. The practitioner must advise the client to take corrective action where appropriate. This duty to advise the client is affirmative: the practitioner cannot simply ignore discovered noncompliance and continue the engagement as if the information was not received.
What Section 10.21 does NOT require
Section 10.21 does NOT require the practitioner to report the client's noncompliance to the IRS. The duty is to advise the client, not to disclose to the government. Section 10.21 also states that the duty to advise applies notwithstanding any duty of confidentiality imposed by law, but it does not authorize violation of that duty. The practitioner who advises the client of the noncompliance and the consequences has fulfilled the Section 10.21 obligation; whether the client chooses to correct the noncompliance is the client's decision. If the client refuses to correct known fraud and expects the practitioner to continue the engagement incorporating the fraudulent items, the practitioner's obligation is to withdraw.
VERIFY EXACT SECTION 10.21 LANGUAGE AT IRS.GOV
The description of Section 10.21 in this guide is a summary for practitioner educational purposes. The exact language of 31 C.F.R. Part 10 Section 10.21 governs; verify the current regulatory text at IRS.gov before relying on any paraphrase. Regulatory text is authoritative; summaries are not. The "prompt withdrawal" characterization that appears in some professional discussions is a shorthand that does not fully capture the nuance of Section 10.21's actual requirements.
IRC 6701 Aiding and Assisting: The Line Between Negligence, Recklessness, and Willful Participation
IRC 6701 imposes a civil penalty on any person who aids or assists in the preparation of any portion of a return, affidavit, claim, or other document in connection with any matter arising under the federal tax laws, knowing that it will be used in connection with any material matter arising under the federal tax laws, and knowing that if it were so used it would result in an understatement of another person's tax liability.
The knowledge standard under IRC 6701
The IRC 6701 penalty requires knowledge: the person providing assistance must know that the document will be used to understate a tax liability. This is a different and higher standard than the negligence standard applicable to some other preparer penalties. A practitioner who prepares a return based on client-provided information that turns out to be fraudulent, without having had reason to know of the fraud, does not face IRC 6701 exposure on that basis alone. The risk arises when the practitioner knew (or had specific reason to know) the information was fraudulent and continued to use it.
IRC 6701 penalty amounts: verify at IRS.gov
The penalty amounts under IRC 6701 (currently specified as separate amounts for returns involving individuals and returns involving corporations) must be verified at IRS.gov before discussing potential exposure with a client or in any professional context. Penalty amounts are subject to inflation adjustments and statutory change. This guide does not state specific IRC 6701 penalty amounts as definitive without directing the practitioner to verify current figures at IRS.gov.
IRC 6701 IS NOT THE SAME AS IRC 6694
IRC 6694 addresses return preparer penalties for understatements due to unreasonable positions or willful or reckless conduct. IRC 6701 addresses persons who aid or assist in the preparation of fraudulent documents. The two penalties are distinct and can both apply in a given situation, but they have different knowledge standards and different penalty structures. Conflating the two understates the IRC 6701 exposure in cases involving actual knowledge of fraud.
IRC 6694 Reasonable Cause Defense: How Your Position Standard Documentation Protects You
In the ambiguous red-flag scenario (Scenario 3 above), the IRC 6694 reasonable cause defense is the practitioner's primary protection. If a position taken on a return turns out to be wrong because the client provided fraudulent information, and the practitioner can demonstrate reasonable cause and good faith reliance on client-provided documentation, IRC 6694 penalties generally do not apply to the preparer.
What reasonable cause reliance requires
Reasonable cause reliance on client-provided information is not unconditional. The practitioner must have made reasonable inquiries when the information appeared incorrect or incomplete, and the practitioner's reliance must have been in good faith. A practitioner who takes a position without asking any questions about items that are facially inconsistent with the rest of the return cannot claim good faith reliance. The inquiry standard is what a competent practitioner exercising reasonable diligence would have asked given the circumstances.
Documentation is the defense
The practitioner who contemporaneously documented their inquiries (what they asked the client, what the client said, what documentation they reviewed) is in a materially better position than the practitioner who asked the same questions without any written record. Intake checklists, client questionnaires, file notes from client conversations, and copies of the documentation the client provided all constitute the contemporaneous record that supports a reasonable cause defense. This documentation does not need to be elaborate; it needs to be contemporaneous and specific.
The Withdrawal Procedure: How to Disengage Properly Without Creating Additional Exposure
The mechanics of withdrawal from an engagement due to fraud concerns require care. A withdrawal that is too aggressive (for example, one that explicitly states the reason in writing) may create a document that exposes the client's information in ways that violate Section 7216 or that creates additional legal problems for both the practitioner and the client. A withdrawal that is too vague may not adequately document the practitioner's termination of the engagement, leaving ambiguity about whether the practitioner is still responsible for the work.
Stop work immediately
As soon as the practitioner determines that continuing would require incorporating fraudulent information into the return, work on that return must stop. Do not prepare partial drafts that include the fraudulent items with the intent of "fixing them later." Once an item is in a draft return, it is harder to document that the item was never going to be used.
Advise the client of the noncompliance (Section 10.21 duty)
Before withdrawing, fulfill the Section 10.21 duty: advise the client that the information or position requested is inconsistent with federal tax law and explain the potential consequences. This conversation should be documented in a contemporaneous file note (not in the client-facing withdrawal letter). The client should understand that the practitioner cannot continue the engagement on the basis of the fraudulent or inaccurate information.
Send a written withdrawal letter
The withdrawal letter should state that the practitioner is terminating the engagement and is no longer able to provide the requested services. The letter should not state the specific reason for withdrawal (to avoid potential Section 7216 issues and to avoid creating a document that could be used in a government proceeding). A brief, professional statement that the practitioner is unable to continue and that the client should seek other professional assistance is sufficient. The letter should request the return of any original documents the client provided and should note that copies will be retained in the practitioner's file.
Revoke any outstanding Form 2848
If a Form 2848 was filed authorizing the practitioner to represent the client before the IRS, revoke it promptly after withdrawal. A practitioner who has withdrawn from an engagement but whose Form 2848 remains on file with the CAF Unit remains the authorized representative in the IRS's records and may receive IRS correspondence for a client they are no longer representing.
Preserve the engagement file
Retain all documents the client provided, all correspondence, all work product in any state of completion, and the detailed contemporaneous notes of what occurred and when, for at least the applicable statute of limitations period. The engagement file is the practitioner's defense record if a malpractice claim or OPR complaint arises later. Do not destroy any portion of the file out of discomfort with its contents.
What the Engagement Letter Must Say Before Fraud Surfaces: Scope Limitation and Withdrawal Trigger Clauses
The practitioner who has a well-drafted engagement letter in place before a fraud situation arises is in a materially different position than one who does not. The engagement letter is the pre-fraud protection system; the withdrawal is the response to a fraud event the protection system did not prevent. The two most important fraud-specific clauses are the scope limitation clause and the withdrawal trigger clause. See the engagement letter fraud-protection clauses guide for the full framework.
The scope limitation clause
The engagement letter should explicitly state that the practitioner is preparing the return in reliance on information provided by the client, that the practitioner is not independently auditing or verifying the client's financial information unless specifically agreed in writing, and that the accuracy of the return depends on the accuracy of the information the client provides. This clause does not eliminate the practitioner's duty to make reasonable inquiry when information appears incorrect, but it establishes the baseline framework for the engagement and documents the division of responsibility between practitioner and client.
The withdrawal trigger clause
The engagement letter should include a clause stating that the practitioner may terminate the engagement if: (a) the client provides information that the practitioner determines cannot be used in a compliant return; (b) the client requests the practitioner to take a position that lacks a required legal basis; or (c) continued representation would require the practitioner to violate applicable professional standards. This clause gives the practitioner documented contractual authority to withdraw without breach of contract when a fraud situation arises, rather than having withdrawal characterized as an abandonment of the client mid-engagement.
Duty of Confidentiality vs. Duty Not to Assist: The Section 7216 and Common Law Privilege Boundary
Tax practitioners operate under a duty of confidentiality that limits what they can disclose about client tax information. Understanding what that duty covers, and what it does not, is essential in fraud situations.
Section 7216 and the practitioner's duty of confidentiality
IRC Section 7216 prohibits a tax return preparer from knowingly or recklessly disclosing or using tax return information other than for the purpose of preparing the return or as authorized by the client. See the Section 7216 disclosure rules guide for the complete framework. The Section 7216 prohibition applies to the tax return information itself; it does not immunize a practitioner from the duty to comply with legal process (such as a subpoena or IRS summons) or from the duty to withdraw from an engagement where continuing would require assisting in fraud.
Attorney-client privilege and most preparers
It is important to note that most tax preparers are not attorneys and therefore do not hold common law attorney-client privilege in the traditional sense. The Kovel arrangement (where a CPA works under the direction of an attorney and shares the attorney's privilege in certain circumstances) requires an actual attorney-client relationship with a supervising attorney. An enrolled agent or unenrolled preparer who is not working under an attorney's direction does not have attorney-client privilege; the confidentiality protection is Section 7216, not privilege. This distinction matters when practitioners are advising clients about the information they share with the practitioner during a fraud discussion.
The boundary the practitioner must not cross
The duty of confidentiality under Section 7216 prohibits the practitioner from disclosing client fraud to the IRS voluntarily (absent legal compulsion). But the same confidentiality obligation does not require the practitioner to continue assisting with fraud in order to protect the client's information. Withdrawal is the mechanism that terminates the practitioner's assistance without disclosing the client's information. The practitioner who withdraws and preserves the file has met both the confidentiality obligation and the obligation not to assist.
Documenting the Withdrawal: What to Put in the File, What Not to Put in Writing
The withdrawal file is the practitioner's defense record if a client complaint, OPR referral, or malpractice claim arises from the fraud situation. The contents of the file and the client-facing withdrawal letter must be carefully calibrated.
What belongs in the internal file (not client-facing)
The internal file should contain: a dated contemporaneous memo describing what the practitioner learned, when they learned it, what inquiries they made, what the client said, and what the practitioner advised the client under Section 10.21; all documents the client provided during the engagement; all drafts of work product in any state of completion; a copy of the withdrawal letter sent to the client; and any notes from subsequent client contacts after the withdrawal. This memo is for the practitioner's defense and should be written clearly and factually, without editorializing about the client's conduct.
What the withdrawal letter should not contain
The withdrawal letter sent to the client should not describe the specific fraudulent conduct (this creates Section 7216 issues and may create a document that can be used in a government proceeding), should not include legal opinions about the client's potential criminal exposure (the practitioner is not the client's criminal defense attorney), and should not contain inflammatory or accusatory language. The letter is professional notice of termination, not a recitation of the practitioner's findings.
Referring the Client to Legal Counsel: How to Make the Referral Without Amplifying Risk
When fraud is confirmed or strongly suspected, the client needs an attorney, not just a different preparer. The practitioner's role in the referral is to direct the client toward legal counsel without describing the specifics of the fraud situation to the attorney in a way that could compromise the client's privilege or the practitioner's own exposure.
The scope of the practitioner's referral
The practitioner should advise the client that their situation may have legal implications beyond the scope of tax preparation services and that they should consult a tax attorney before taking any further action, including filing the return themselves or engaging another preparer. The practitioner should provide the referral without characterizing the nature of the legal issue to the attorney directly; that characterization is for the client to make to their attorney under the protection of privilege.
When to Call Your E&O Carrier: The Notification Trigger and How It Affects Your Defense
Most E&O insurance policies for tax preparers include a reporting clause that requires the insured to notify the carrier promptly when the insured becomes aware of a claim, a circumstance that could give rise to a claim, or an event that might trigger coverage. A fraud situation involving a client is precisely the kind of circumstance that can give rise to a future malpractice claim (from the client) or a regulatory complaint (from the IRS). See the E&O insurance and fraud exclusions guide for the coverage considerations specific to fraud-related situations.
When to notify the E&O carrier
Review your policy's reporting clause language. Most policies require notification when you "become aware of circumstances that could give rise to a claim," not just when an actual claim is made. A client fraud situation that leads to withdrawal may result in a client complaint if the client is unhappy with the withdrawal or with subsequent IRS attention on their account. Notifying the carrier promptly (per the policy's timeline) preserves your coverage and allows the carrier to advise you on next steps before the situation develops into an actual claim.
Fraud exclusions and E&O coverage
Most E&O policies contain a fraud exclusion that eliminates coverage for claims arising from the insured's own fraudulent conduct. This exclusion is relevant when the practitioner continues to prepare a return after having actual knowledge of fraud; in that scenario, the practitioner's own conduct (not just the client's fraud) becomes an element of any claim. The practitioner who withdraws properly before completing a fraudulent return preserves the distinction between the client's fraud and the practitioner's conduct, which is the distinction E&O coverage depends on.
OPR Referral Risk: What Facts Trigger an IRS OPR Complaint and How to Respond
A client fraud situation can result in an OPR referral in several ways: the client files a complaint against the practitioner after the withdrawal (alleging abandonment or malpractice); a Revenue Agent examines the return and refers the preparer to OPR; or the IRS's analytics flag the practitioner's return patterns. The OPR consequences of continuing to prepare returns where fraud is suspected are a separate and serious liability layer on top of the civil penalty and malpractice exposure.
How proper withdrawal reduces OPR referral risk
A practitioner who: (a) stopped work when the fraud concern arose; (b) advised the client of the noncompliance and its consequences as required by Section 10.21; (c) withdrew from the engagement by written letter; (d) preserved the engagement file; and (e) revoked the Form 2848 is in a strong defensive position if an OPR referral arises from the same client situation. The practitioner's conduct was the opposite of the conduct that generates OPR complaints: they terminated rather than participated, advised rather than concealed, and documented rather than ignored.
Building the Pre-Fraud Protection System: Intake Red Flags, Engagement Letter Clauses, and Annual Client Certifications
The best fraud protection system is one that identifies problems before they reach the engagement stage and establishes the contractual framework for handling them if they arise. The three components are: intake red-flag screening, engagement letter fraud-protection clauses, and annual client certifications.
Intake red-flag screening
The client intake process should flag situations that warrant heightened inquiry: lifestyle that appears inconsistent with reported income, deduction claims in categories known for documentation problems (business meals, home office, vehicle, cash charitable contributions), income sources that are difficult to verify (cash businesses, international income, barter arrangements), and prior preparer changes without a clear explanation. Red flags are not proof of fraud; they are signals to ask more specific questions and to document the inquiry and the client's responses.
Engagement letter fraud-protection clauses
As described in Section 6 above and in the engagement letter fraud-protection clauses guide, the scope limitation clause and the withdrawal trigger clause are the two most important pre-fraud protections. They establish the division of responsibility, the reliance framework, and the practitioner's contractual authority to withdraw. See also the Circular 230 practitioner duties guide for how Circular 230's scope-of-service obligations interact with engagement letter terms.
Annual client certifications
A client certification, signed annually with or as part of the engagement letter, in which the client represents that all information provided is accurate, complete, and not intentionally misleading, creates a contemporaneous record of the client's responsibility for the accuracy of the information. If fraud is later discovered and the client attempts to blame the practitioner, the signed certification is direct evidence that the client represented the information as accurate. It does not make the practitioner immune from liability, but it significantly strengthens the reasonable reliance defense.
Regulatory Verification Notice and Claims Subject to Review
The following items in this guide require verification before relying on them in any specific matter: (1) Circular 230 Section 10.21 exact language: verify against the current version of 31 C.F.R. Part 10 at IRS.gov; the description in this guide is a summary, not the authoritative text. (2) IRC 6701 penalty amounts: not stated as specific dollar figures in this guide; verify current amounts at IRS.gov before discussing exposure with a client. (3) The statement that preparers do not have a general duty to report client fraud to the IRS: accurate under current law as of the publication date, but the governing rules (Circular 230 and IRC Section 7216) should be verified at IRS.gov before advising a client on disclosure obligations. (4) Attorney-client privilege and non-attorney preparers: this guide's description is informational; specific privilege questions in a specific matter require legal counsel. (5) E&O policy reporting triggers: these vary by policy; review the specific policy language, not this guide's summary. This guide does not constitute legal advice. Practitioners facing a specific client fraud situation should consult qualified legal counsel.
Related Guides in the Practitioner Liability and Circular 230 Cluster
- Section 7216 Disclosure Rules Guide: the governing framework for what a tax return preparer may and may not disclose about client tax information
- Circular 230 Practitioner Duties Guide: the full regulatory framework governing practice before the IRS, including Sections 10.21, 10.22, and 10.34
- OPR Investigation Guide: the OPR disciplinary process and how to respond if a fraud situation results in an OPR referral
- E&O Insurance and Fraud Exclusions Guide: coverage types, fraud exclusions, and when to notify the carrier in a client fraud situation
- Engagement Letter Fraud-Protection Clauses Guide: the complete engagement letter framework including scope limitation, withdrawal trigger, and client certification provisions
- IRC 7201, 7202, and 7206: Criminal Tax Statutes for Civil Practitioners: IRC 7206(2) criminal exposure for preparers who aid or assist a client filing a false return, the elements, willfulness, and when to recommend criminal defense counsel
Frequently Asked Questions
What does Circular 230 Section 10.21 require when a practitioner discovers client fraud?
Section 10.21 requires the practitioner to promptly advise the client of the noncompliance and of the consequences under the Code and regulations, and to advise the client to take corrective action. It does NOT require the practitioner to report the client's noncompliance to the IRS; the duty is to advise the client, not to disclose to the government. Verify the exact current language of Section 10.21 at IRS.gov against the current version of 31 C.F.R. Part 10 before relying on any summary.
When does IRC 6701 apply to a tax preparer?
IRC 6701 applies when a person knowingly aids or assists in preparing a tax document that will be used to understate a tax liability. The knowledge standard is the key: a preparer who relies in good faith on client-provided information that later proves fraudulent does not automatically face IRC 6701 exposure. The risk arises when the preparer had actual knowledge that the information was fraudulent and continued to use it. Verify current IRC 6701 penalty amounts at IRS.gov before discussing exposure in any specific matter.
Does a tax preparer have a duty to report client fraud to the IRS?
No. As a general matter, tax preparers do not have a duty to report client fraud to the IRS. Circular 230 Section 10.21 requires advising the client of the noncompliance, not disclosing to the government. IRC Section 7216 prohibits unauthorized disclosure of client tax return information. Practitioners who receive legal process (such as a subpoena or IRS summons) should consult legal counsel before responding. The duty to withdraw is separate from any duty to report.
How should a tax preparer document their withdrawal when client fraud is discovered?
Document the withdrawal in two places: (1) internal file: a dated contemporaneous memo describing what the practitioner learned, when, what inquiries were made, what the client said, and what the practitioner advised under Section 10.21; and (2) client-facing withdrawal letter: a brief professional notice terminating the engagement without describing the specific fraudulent conduct. Revoke any outstanding Form 2848 and preserve the entire engagement file for the applicable statute of limitations period. Notify your E&O carrier per your policy's reporting clause timeline.
What engagement letter clauses protect a preparer when client fraud surfaces mid-engagement?
The two most important fraud-specific clauses are: (1) a scope limitation clause stating that the practitioner is relying on client-provided information without independent audit or verification; and (2) a withdrawal trigger clause authorizing the practitioner to terminate the engagement if the client provides materially inaccurate information or requests a position that violates professional standards. Annual client certifications in which the client represents the accuracy of their information also strengthen the reasonable reliance defense. See the engagement letter guide for the full framework.