Imagine you take a tax position you believe is defensible, file your return, and three years later the IRS disagrees. The deduction is disallowed, you owe the tax plus interest — and then the agent tacks on a 20 percent accuracy-related penalty. That extra 20 percent often hurts more than the tax itself, and unlike interest, it isn't deductible.
There's a small, two-page form that exists for exactly this scenario. Form 8275, the Disclosure Statement, lets you put a debatable position on the table when you file, attaching a short legal argument that says, in effect: "Here's what I did, here's why I think I'm right, and here's the authority I'm relying on." When that disclosure is "adequate" and the position has a reasonable basis, the substantial understatement and disregard-of-rules portions of the accuracy-related penalty vanish — even if the IRS later wins on the merits.
This guide walks through who should be filing Form 8275, the standards it satisfies, the difference between Form 8275 and Form 8275-R, what counts as adequate disclosure, and the common mistakes that turn this penalty shield into wasted paper.
What Form 8275 Actually Does
Form 8275 is an attachment to a federal income tax return. It tells the IRS, in plain language, about a specific item or position on the return that might otherwise be invisible to the examiner. The disclosure has one purpose: defeating the accuracy-related penalty under Internal Revenue Code Section 6662 by transforming a position into one that has been "adequately disclosed."
Two things to understand up front:
- Disclosure doesn't make the position correct. If the IRS audits and wins, you still owe the tax plus interest. The deduction or credit is still disallowed.
- Disclosure removes the penalty layer. The 20 percent accuracy-related penalty on the resulting underpayment goes away if the disclosure is adequate and the position has at least a reasonable basis.
That penalty layer is the value proposition. On a $40,000 disputed deduction at a 32 percent marginal rate, the underlying tax is $12,800. The accuracy-related penalty would be another $2,560. Form 8275, properly filed, neutralizes that $2,560.
The Three Confidence Standards You Need to Know
Tax practitioners constantly trade in three terms of art. They sound similar, but they sit at very different points on the certainty spectrum:
- Reasonable basis — roughly a 20 percent or better chance the position would prevail if litigated. More than frivolous, more than not patently improper, but well short of likely correct.
- Substantial authority — somewhere around a 40 percent chance of prevailing. Less stringent than "more likely than not" but stronger than reasonable basis. Supported by a weight of authority from cases, regulations, revenue rulings, and other recognized sources.
- More likely than not — better than a 50 percent chance of prevailing. The standard required for tax shelter and reportable transaction items.
Form 8275 matters most in the gap between reasonable basis and substantial authority. If your position has substantial authority, no disclosure is required to avoid the accuracy-related penalty — the strength of the position is its own shield. If your position is below reasonable basis, no amount of disclosure helps. The form does its work in the middle: a position with a reasonable basis that doesn't quite reach substantial authority can still defeat the penalty when properly disclosed on Form 8275.
Form 8275 vs. Form 8275-R: A Critical Distinction
The IRS issues two separate disclosure forms, and confusing them is a recipe for getting an examiner's full attention.
Form 8275 (Disclosure Statement) is for positions that are consistent with — but not clearly addressed by — existing Treasury regulations. The classic case: a regulation is silent on an unusual fact pattern, you interpret it a certain way, and you want to explain your reasoning on the record.
Form 8275-R (Regulation Disclosure Statement) is for positions that directly contradict a Treasury regulation. Filing 8275-R is a formal statement that you believe the regulation itself exceeds the agency's statutory authority or is otherwise invalid. It's an invitation to litigate the regulation, not just the result.
The practical guidance from veteran practitioners: never file 8275-R unless you have to. It almost guarantees IRS scrutiny because you're not just taking an aggressive position — you're telling Treasury its regulation is wrong. Most challenging positions can be framed as interpretations or factual distinctions and disclosed on the standard Form 8275 instead. Reserve 8275-R for the rare situation where you genuinely intend to challenge a regulation's validity.
A useful test: if your argument is "the regulation doesn't quite reach my facts," you want Form 8275. If your argument is "the regulation is invalid," you want Form 8275-R — and you should probably have litigation counsel involved.
When Form 8275 Is Required vs. When the Return Already Discloses Enough
Each year, the IRS publishes a revenue procedure listing positions that are considered adequately disclosed simply by filling out the standard line items on the return. The most recent guidance — Revenue Procedure 2024-44 — covers returns filed on 2024 forms for taxable years beginning in 2024 (with limited extension to short years beginning in 2025). The pattern repeats annually with similar substance.
Items typically considered adequately disclosed without Form 8275 — assuming the related schedules are completed fully — include:
- Charitable contributions properly reported on Schedule A and accompanied by required substantiation forms (Form 8283 for noncash gifts above thresholds).
- Moving expenses reported on Form 3903 (where still deductible — note the post-TCJA limits).
- Employee business expenses reported on Form 2106 (where applicable).
- Fuels credits reported on Form 4136.
- Treaty-based return positions disclosed on Form 8833.
- International boycott transactions reported on Form 5713.
If your position fits one of these categories and you've completed the appropriate form fully and accurately, you don't need Form 8275 to get accuracy-related-penalty protection.
If your position doesn't fit a listed category, Form 8275 is the mechanism for adequate disclosure. The revenue procedure also calls out specific situations where Form 8275 is always required regardless of any other disclosure — most notably understatements arising from transactions between related parties. If the related-party relationship is in the picture, you need Form 8275 to disclose both the transaction and the relationship.
What "Adequate" Disclosure Actually Looks Like
Filing the form is the easy part. Filling it out so that it actually provides penalty protection is where many disclosures fall apart.
The form has three parts:
- Part I identifies the item: the line number on the return, the form schedule, the description of the item, and the amount.
- Part II is the legal argument — the "detailed explanation."
- Part III covers pass-through entity information when the disclosure relates to a partnership, S corporation, estate, trust, REMIC, or FASIT item.
Part II is where adequacy is won or lost. A useful explanation includes, at minimum:
- A clear statement of the facts. Not generic — the specific transaction, parties, dates, amounts, and economic substance.
- A clear statement of the position taken. What you reported on the return, where, and at what amount.
- The authority you're relying on. Code sections, regulations, revenue rulings, revenue procedures, court cases, congressional intent. Cite by name and citation, not vaguely by topic.
- The application of authority to facts. A short paragraph connecting why those authorities support your treatment of these facts.
Courts and the IRS have repeatedly held that a vague reference to a Code section, without explanation, is not adequate disclosure. Conversely, a tightly written one-page explanation with proper citations is generally sufficient even when the legal question is complex. Quality matters more than length.
A useful sanity check before attaching the form: hand it to a colleague who hasn't worked the issue and ask whether they can identify, in 60 seconds, exactly what was reported and why. If they can't, the explanation isn't adequate.
Timing: File With the Original Return
Form 8275 must be attached to the original tax return for the year of the position. That's not a soft preference — it's the rule that gives the form its protective effect.
- Filed with the original return: Protection against the accuracy-related penalty kicks in for items disclosed (assuming the position has a reasonable basis).
- Filed with a qualified amended return filed before the IRS contacts you about an audit: Generally treated as adequate disclosure.
- Filed for the first time after an audit begins: No protection. The penalty applies if the IRS prevails.
This is the single most common mistake practitioners see: the position is defensible, the explanation is well-drafted, but the form was attached to a Form 1040-X filed after the agent's first information request. By then, the disclosure window has closed.
Practitioners who handle close-call positions routinely build a "disclosure decision" into their return-review workflow. If a senior reviewer flags a position as needing analysis, the file moves into a queue where the practitioner decides — before filing — whether (a) the position has substantial authority and needs no disclosure, (b) the position has a reasonable basis and should be disclosed on Form 8275, or (c) the position should be removed from the return entirely.
Form 8275 and the Section 6694 Preparer Penalty
Form 8275 isn't only a taxpayer-protection form. It also protects tax return preparers from the Section 6694 preparer penalty for unreasonable positions.
Section 6694(a) imposes a penalty on the preparer — separate from any penalty on the taxpayer — when an understatement results from an unreasonable position. The penalty is the greater of $1,000 or 50 percent of the preparer's fee for that return. For a $4,000 return preparation fee, that's $2,000 out of the preparer's own pocket.
The standards that protect the preparer:
- Undisclosed position: Requires substantial authority.
- Disclosed position (via Form 8275 or 8275-R): Requires only reasonable basis.
- Tax shelter or reportable transaction: Requires "more likely than not" regardless of disclosure.
When a preparer prepares and signs a return that includes Form 8275 disclosing the position, and gives that return to the taxpayer, the preparer is not subject to the Section 6694 penalty for that position — even if the taxpayer later removes the form and files without it. Practitioners should retain a copy of the original return as-prepared (with Form 8275 attached) in their files for exactly this reason.
In practice, the conversation between CPA and client over a close-call position often comes down to: "I can sign this return only if we attach Form 8275, because without it my preparer-penalty risk is too high." That's a legitimate professional standard, not posturing.
Common Mistakes That Sink the Disclosure
A small number of recurring errors account for most failed disclosures:
- Filing after the audit starts. As noted above — too late.
- Generic, conclusory explanations. "The taxpayer believes this is deductible under Section 162" is not adequate. The explanation needs facts, position, authority, and reasoning.
- Wrong form choice. Filing Form 8275 when the position is genuinely contrary to a regulation (should be 8275-R), or filing 8275-R when an interpretation argument would have worked (should be 8275). The 8275-R mistake is more costly because it draws scrutiny you didn't need.
- Disclosing the wrong taxpayer-year combination. Each Form 8275 covers one return. A position taken across multiple years needs disclosure on each year's return.
- Ignoring related-party rules. Forgetting that related-party transactions require Form 8275 disclosure regardless of whether other safe harbors apply.
- Failing to update for tax shelter or reportable transaction status. If the position falls into either category, disclosure on Form 8275 alone doesn't save you — you also need Form 8886 (Reportable Transaction Disclosure Statement), and the substantive standard rises to "more likely than not."
- Tax shelter items with no reasonable belief of more-likely-than-not success. Disclosure of a tax shelter item that you couldn't reasonably believe would more likely than not prevail does not avoid the penalty — Form 8275 is not a fix for aggressive shelter positions.
A Practical Workflow for Close-Call Positions
For practitioners and well-organized taxpayers, the following workflow tends to produce defensible disclosures:
- Identify the position early. Flag it during return preparation, not during final review.
- Research and write a position memo. Even one page. Facts, position, authorities, conclusion. This memo becomes the basis for the Form 8275 Part II explanation.
- Score the confidence level. Reasonable basis (20%)? Substantial authority (40%)? More likely than not (50%+)? Be honest — practitioners who routinely overrate their positions get reputations.
- Decide on disclosure. Below substantial authority but at least reasonable basis: disclose on Form 8275. At substantial authority or above: disclosure optional. Below reasonable basis: don't take the position.
- Draft Form 8275 from the position memo. Trim to essentials: the IRS examiner needs to understand what you did and why, not your full research.
- Attach to the original return and file by the due date. No exceptions.
- Retain the position memo and a copy of the disclosed return. If audited, you'll need both.
How Bookkeeping Quality Affects Your Disclosure Strategy
Form 8275 disclosures work only if the underlying facts are clean. The Part II explanation cites specific transactions, dates, parties, and amounts — and if your books don't support those numbers, the disclosure protects nothing.
The connection is simple: positions taken on the return reflect categorizations made in the books. If your chart of accounts is sloppy, if transactions are bundled into miscellaneous expense, if related-party transactions aren't flagged, the practitioner drafting your Form 8275 is working from a foggy starting point. Conversely, when the books distinguish related-party payments from arm's-length transactions, when documentation links each material expense to its substantiation, and when the audit trail is preserved chronologically, drafting an adequate disclosure becomes mechanical.
Plain-text accounting helps here because every transaction lives as a readable line of code, every account is explicit, and every adjustment is recoverable from version control. The same dataset that builds your financial statements also generates the citations you'll quote in Part II.
Keep Your Records Audit-Ready From Day One
Whether or not you ever attach a Form 8275 to a return, the quality of your bookkeeping determines what your defensible positions actually look like. Beancount.io offers plain-text accounting that gives you complete transparency and version-controlled records — exactly the kind of audit trail that makes drafting a disclosure (or defending an audit) straightforward rather than scrambled. Get started for free and see why developers and finance professionals are switching to plain-text accounting.