When the IRS slides a 20 percent accuracy-related penalty onto a small business audit, most owners assume the only way out is to prove they had reasonable cause and acted in good faith. That's a hard, fact-heavy fight. There is another path that has very little to do with whether you actually owed the underlying tax: did an actual human manager personally sign off, in writing, before the IRS first told you the penalty was on the table?
If the answer is no — or if the IRS cannot produce paperwork proving it — the penalty can be wiped out entirely on procedural grounds, regardless of the merits. This is the world of Internal Revenue Code Section 6751(b), the "supervisory approval" requirement that Congress enacted in 1998 to stop revenue agents from using penalties as bargaining chips. After more than two decades of mostly being ignored, two cases — Chai v. Commissioner and the Graev trilogy — turned this dusty subsection into one of the most powerful procedural defenses a small business taxpayer has. Final Treasury regulations issued in December 2024 then redrew the boundaries again.
Here is what every small business owner, controller, and tax preparer should understand about Section 6751(b), what changed under the 2024 final regulations, and how to actually use the defense.
What Section 6751(b) Says — and Why It Matters
The statute is short. The operative language reads: "No penalty under this title shall be assessed unless the initial determination of such assessment is personally approved (in writing) by the immediate supervisor of the individual making such determination or such higher level official as the Secretary may designate."
Four words do most of the work:
- "Initial determination" — the moment the IRS first formally decides a penalty applies.
- "Personally approved" — a real person, not a system, has to bless it.
- "In writing" — there must be a paper or electronic record.
- "Immediate supervisor" — the approver has to be the actual manager of the agent who proposed the penalty.
If any one of those is missing, the penalty cannot be assessed. Full stop. The legislative history is unusually candid: Congress was responding to taxpayer testimony that some agents were piling on penalties as leverage to push faster settlements. Requiring a manager's signature in writing was meant to put friction in the system.
The Cases That Woke the Statute Up: Chai and Graev
For nearly twenty years after Section 6751(b) was enacted, almost no one raised it as a defense. That changed in 2017.
In Chai v. Commissioner, the U.S. Court of Appeals for the Second Circuit held that the IRS must obtain written supervisory approval of the initial penalty determination no later than the date the IRS issues the notice of deficiency (or, if the penalty is first raised by the IRS in answer to a Tax Court petition, no later than the date the answer is filed). Late approval — even by a day — was fatal.
Shortly afterward, in the third installment of the Graev v. Commissioner trilogy, the U.S. Tax Court reversed its own earlier position and adopted the Chai timing rule for cases everywhere, not just the Second Circuit. Together, these decisions made Section 6751(b) a genuine litigation tool: the IRS now had to prove, with documents, that a real supervisor signed off in writing before the penalty was formally communicated to the taxpayer.
What followed was a flood. Hundreds of Tax Court cases over the next several years tested every word of the statute — what counts as an "initial determination," who qualifies as an "immediate supervisor," whether a digital signature is "in writing," and so on. Different circuits started reaching different conclusions, and the Treasury Department eventually stepped in.
What the December 2024 Final Regulations Changed
After a proposed rulemaking in April 2023 and two years of comments, Treasury published final regulations under Treasury Regulation §301.6751(b)-1 on December 23, 2024, applicable to penalties assessed on or after that date. They settled (or at least clarified) several recurring fights.
Timing — Now Tied to Assessment, Not the Notice of Deficiency
The most consequential change is also the most controversial. Under the final regulations:
- For penalties subject to pre-assessment Tax Court review (most accuracy-related, fraud, and similar penalties asserted in a notice of deficiency), supervisory approval must be obtained at any time on or before the IRS mails the notice that gives the taxpayer the right to petition Tax Court.
- For penalties not subject to pre-assessment review (many information-return penalties, certain assessable penalties), approval is required before the penalty is actually assessed — which can be much later.
This is a more taxpayer-unfriendly rule than the Chai court adopted, which used the first formal communication of the penalty (often the 30-day "Letter 525" examination report) as the cutoff. The IRS argued, and Treasury agreed, that the statute's text is keyed to assessment, not the first letter. Litigation over this point will almost certainly continue in circuits that previously followed the Chai timing rule, but for now the regulation is the operative standard.
"Personally Approved (In Writing)" — Broad
Treasury declined to require a particular form. Any writing — including electronic — counts as long as the writer intended it as approval and signified assent. A scribbled "Approved – J.S. 4/12" on a routing slip can be enough. So can an email reply that says "agree with proposed penalties." The IRS does not need to use a special form.
"Immediate Supervisor" — Functional, Not Title-Based
The final rule defines an "immediate supervisor" as any individual with responsibility to review another individual's proposal of penalties. This is broader than some courts had read the statute. Acting supervisors, team leaders with review authority, and supervisors above the immediate level can all qualify. The earlier debate over whether only the formally designated direct manager qualified is largely resolved in favor of flexibility.
"Initial Determination" — When the Examiner Communicates a Definite Penalty Position
The final regulations clarify that the "initial determination" is the first communication formally proposing penalties as a definite IRS position, not preliminary discussion, brainstorming, or "I might propose this" conversations during the audit. Working drafts and internal deliberations don't trigger the clock.
Which Penalties Section 6751(b) Does — and Doesn't — Cover
This is where small business owners often go wrong. The statute carves out important exceptions.
Section 6751(b) Does Not Apply To
- Section 6651 failure-to-file and failure-to-pay penalties (the everyday late-filing and late-payment penalties)
- Section 6654 estimated tax penalty for individuals
- Section 6655 estimated tax penalty for corporations
- Section 6662 accuracy-related penalty when calculated automatically through electronic means (e.g., the IRS computer flags math errors or simple substantial understatement triggers without human involvement)
- Any other penalty "automatically calculated through electronic means"
If a system-generated CP-series notice arrives demanding a late-filing penalty, do not waste energy on a Section 6751(b) argument. There was no human discretion to supervise.
Section 6751(b) Does Apply To
- Section 6662 accuracy-related penalties (negligence, substantial understatement, substantial valuation misstatement, transfer pricing) when an examiner proposes them
- Section 6663 civil fraud penalties
- Section 6707A reportable transaction penalties
- Section 6694 preparer penalties
- Section 6038 and Section 6038A information-return penalties (Form 5471, Form 5472, etc.)
- Section 6677 foreign trust reporting penalties
- Section 6721 and Section 6722 information-return penalties (when discretionarily proposed by an examiner rather than auto-calculated)
- Trust fund recovery penalties under Section 6672
- The 75 percent fraud penalty when proposed in audit
If you are looking at any of these on an examination report, a 30-day letter, or a notice of deficiency, Section 6751(b) is in play.
How the Defense Actually Works in a Real Case
The mechanics are straightforward once you know what to ask for.
Step 1: Spot the Penalty Early
Every IRS examination report — the Form 4549, Form 886-A, or the 30-day letter — lists each penalty by code section. Circle them and check the list above. If any non-exempt penalty appears, Section 6751(b) is potentially live.
Step 2: Request the Penalty Approval Form
Once the case is in Appeals or Tax Court, the taxpayer can request, through informal discovery or a Branerton letter, copies of:
- Form 8278 (Assessment and Abatement of Miscellaneous Civil Penalties)
- Civil Penalty Approval Form, Form 5816, or an internal Civil Penalty Lead Sheet
- Email or memo correspondence reflecting supervisory approval
- The supervisor's signature, date, and printed name
The procedures the IRS is supposed to follow are documented in the Internal Revenue Manual at IRM 20.1.1.2.3 and IRM 4.19.13.5.2. Knowing those citations helps when an examiner pushes back.
Step 3: Check the Three Elements
Compare the approval form against the file. The IRS must show all three:
- Identity of the agent who made the initial determination and the supervisor who approved it (and that the approver had review authority).
- In-writing approval of the specific penalty by code section — not a generic "I approve the report."
- Timing — approval before the IRS mailed the notice that gave Tax Court rights (under the 2024 regulations) or, in pre-2024 cases in some circuits, before the first formal communication of the penalty.
Step 4: Make the IRS Prove It
In Tax Court, the IRS has the burden of production on penalties. If the IRS cannot produce signed approval paperwork that ticks all three boxes, the penalty fails as a matter of law — no reasonable cause analysis required. If the IRS produces something but it is dated after the cutoff, or signed by someone who wasn't the proposing agent's actual reviewer, the same result follows.
Step 5: Use the Argument at Appeals First
Tax Court litigation is expensive. Section 6751(b) arguments often work at IRS Appeals, where Appeals officers have authority to concede penalties on procedural grounds rather than send the case to court. A well-written protest letter that cites Section 6751(b), Chai, Graev, and the final regulations puts pressure on the file early and cheaply.
Common Mistakes Taxpayers Make
- Conceding the penalty in the audit report response. Once you sign Form 870 or otherwise consent to assessment, the procedural defense disappears.
- Waiting until trial to raise it. Raise Section 6751(b) at the first opportunity — in the audit, in the Appeals protest, and in the Tax Court petition. Late-raised arguments can be waived.
- Confusing exempt and non-exempt penalties. Don't fight a Section 6654 estimated tax penalty on supervisory approval grounds; it is statutorily exempt.
- Assuming reasonable cause is the only defense. Procedural attacks and substantive defenses are independent. Run both.
- Not asking for the file. The defense is documentary. Without the approval forms, you cannot evaluate it.
What This Means for Your Recordkeeping
If you are the taxpayer, the Section 6751(b) defense is about what the IRS did or didn't do — not what you did. But the defense is much more effective when the rest of your tax record is clean, because:
- It is easier to credibly raise procedural defenses when your books are organized and you are not also fighting substantive issues you can't explain.
- An audit produces fewer penalty proposals to begin with when your underlying records support every position.
- If the procedural defense fails, the substantive defense (reasonable cause, good faith reliance on a tax professional, substantial authority) depends on contemporaneous records — bank reconciliations, journals, supporting receipts, tax preparer communications.
Accurate, contemporaneous bookkeeping is the foundation under both defenses. Reconstructing records after an audit notice arrives is far harder than maintaining them in the first place.
Sample Language for a Penalty Protest
For owners or representatives drafting a written protest to Appeals, the Section 6751(b) argument can be folded in as a standalone section:
"Petitioner contests the proposed [accuracy-related / fraud / information-return] penalty under IRC § [6662 / 6663 / 6038 / etc.] on procedural grounds under IRC § 6751(b)(1). Section 6751(b)(1) prohibits assessment of the penalty unless the initial determination is personally approved in writing by the immediate supervisor of the examining agent prior to the issuance of the notice giving Tax Court rights, consistent with Chai v. Commissioner, the Graev trilogy, and Treasury Regulation § 301.6751(b)-1. Petitioner requests that the IRS produce, as part of the administrative file, the Civil Penalty Approval Form, Form 8278, or other documentation showing the identity of the supervisor, the date of approval, and the specific penalty approved. If the IRS cannot produce documentation satisfying all three elements, the penalty must be conceded."
That paragraph alone has resolved many cases at Appeals.
Coordinating With Other Penalty Defenses
Section 6751(b) is best used in combination with substantive defenses, not as a substitute for them:
- Reasonable cause and good faith under IRC § 6664(c)
- Substantial authority for the position (often relevant for substantial-understatement penalties)
- Adequate disclosure on Form 8275 or 8275-R
- Reliance on a tax professional (with the proper Boyle-line documentation)
A typical winning playbook in a small business audit penalty fight: lead with Section 6751(b) to put the IRS on the defensive about its paperwork, then lay out the reasonable-cause facts as the fallback. If the procedural defense wins, the merits never matter. If it loses, the merits step in.
Keep Your Financial Records Audit-Ready From Day One
Section 6751(b) is a powerful procedural defense, but the strongest position in any IRS examination is one where the underlying records hold up on their own — so the penalty fight never has to start. Clean, contemporaneous books make it easier to substantiate every line on a return, respond to audit information document requests, and demonstrate good faith if penalties are proposed. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready — your full ledger lives in human-readable files you can audit, search, and hand to your tax advisor without exporting from a black-box platform. Get started for free and see why developers and finance professionals are switching to plain-text accounting.