TC 235: Abatement of Daily Delinquency Penalty

What the code actually does

TC 235 abates a previously assessed Daily Delinquency Penalty — in whole or in part — reversing either TC 234 (manually assessed) or TC 238 (system-generated). Both underlying assessments are the same IRC §6652(c) penalty; TC 235 does not distinguish between them in what it does, only in which transaction it reverses.

Why the relief path here is narrower than practitioners expect

IRM 20.1.1.3.3.2.1, First-Time Abate, confirms that the Daily Delinquency Penalty under IRC §6652(c) does not qualify for First-Time Abate — that IRM subsection lists Form 990 among the returns First-Time Abate does not reach. That leaves reasonable cause as the only administrative relief avenue for this penalty. Note the scope of The Federal Tax Desk’s Penalty Abatement Analyzer here: it ranks FTA and reasonable-cause factors for failure-to-file, failure-to-pay, failure-to-deposit, and accuracy-related penalties — it does not yet model the exempt-organization Daily Delinquency Penalty at all, so the reasonable-cause case here has to be built by hand rather than run through that tool. A reasonable-cause case follows the same general standard as elsewhere — did the organization exercise ordinary business care and prudence, and what specifically prevented timely filing — but there is no procedural shortcut available the way there is for many other penalties. There’s no First-Time Abate safety net here — reasonable cause isn’t the backup plan, it’s the only plan.

What a strong reasonable-cause case actually needs

Because FTA is off the table, the reasonable-cause narrative has to do real work. The strongest cases document a specific, dated event — a preparer’s error the organization reasonably relied on, a natural disaster, a death or serious illness of the person responsible for filing — connected directly to why the return could not be filed on time, plus evidence the organization corrected course once the problem was discovered. A generic "we were busy" or "we didn’t know about the deadline" explanation is weaker here than it might be for a penalty where FTA remains a fallback if reasonable cause fails; for TC 234/238, reasonable cause succeeding or failing is often the entire outcome.

What people mistake TC 235 for

TC 235 is easy to conflate with the transcript’s other manual penalty-abatement codes — TC 271, for instance, which is the manual abatement of the failure-to-pay penalty, not a general-purpose code. Each of these codes is specific to its own penalty and its own relief standard, the same way TC 235 is specific to the Daily Delinquency Penalty under IRC §6652(c) and carries the FTA-ineligibility limitation described above. A manual abatement code on a transcript does not by itself say which relief standard applied — the specific code does.

TC 235 is also worth distinguishing from abatement of the general failure-to-file penalty (typically reversed under different codes tied to IRC §6651). That penalty remains FTA-eligible for many taxpayers; this one is not. Advising a client on the strength of the wrong penalty’s relief rules — assuming FTA is available here because it usually is elsewhere — produces a materially wrong analysis of the organization’s actual options.

The practitioner’s actual next step

Confirm which penalty transaction (TC 234 or TC 238) the abatement is reversing and verify the amount matches — a partial abatement should reconcile against the specific days or gross-receipts figure the original computation used.

Build the reasonable-cause case before requesting abatement, not after a denial — since First-Time Abate is unavailable, there is no lower-effort first attempt to make; the reasonable-cause request is the whole case from the start. File it on Form 843, Claim for Refund and Request for Abatement — mailed to the return address on the penalty notice if the request responds to one, per Form 843’s own instructions, or to the service center where the organization would file its current-year return otherwise.

Whether the organization has paid the penalty decides what the Form 843 asks for. If the penalty is unpaid, the form requests abatement under IRC §6404(a). If the organization paid it, the form is a refund claim, and IRC §6511(a) requires the organization to file it within 3 years of filing the return or 2 years of paying the penalty, whichever is later (IRC §6665(a)(2) treats the penalty as tax). Calendar the deadline from the payment date: that date is certain, while the 3-year date depends on which filing counts as the return. A claim filed after the window fails regardless of merit.

Verify the remaining balance after abatement, and confirm the organization has corrected whatever caused the original delinquency, since a repeat late filing the following year will face the same penalty with a materially weaker reasonable-cause argument behind it.

A denied Form 843 is not the end of the road — the organization retains the right to protest the denial to IRS Appeals, and, after paying the penalty, to file a refund claim and ultimately sue for refund in district court or the Court of Federal Claims. Reasonable cause is the only administrative relief avenue here, but it is not the client’s only avenue, period. §6652(c) is an assessable penalty outside the deficiency procedures, so no notice of deficiency ever issues for it, and full payment followed by a refund suit is the default route to court, since an organization cannot represent itself in federal court and that suit requires retaining counsel.

That full-payment picture has one narrower exception: if the IRS moves to collect the unpaid penalty by lien or levy, the organization gets a Collection Due Process hearing, and IRC §6330(c)(2)(B) lets it challenge the liability itself there, since it never received a notice of deficiency or otherwise had a prior opportunity to dispute the liability. Request that hearing within 30 days of the lien or levy notice on Form 12153; a CDP determination is then petitionable to Tax Court within 30 days under §6330(d), without paying first. Neither deadline is jurisdictional — the Supreme Court held the Tax Court-petition deadline subject to equitable tolling in Boechler, P.C. v. Commissioner, 596 U.S. 199 (2022), and the Tax Court extended the same reasoning to the CDP lien-hearing request deadline in Organic Cannabis Foundation, LLC v. Commissioner, 161 T.C. 13 (2023). Tolling is a narrow, fact-intensive exception, though — treat both deadlines as firm in practice, since missing either forecloses this narrower path back to the refund-suit route above.

If the unabated penalty threatens the organization’s ability to operate while the reasonable-cause case is pending, the Taxpayer Advocate Service is a parallel option — file Form 911, Request for Taxpayer Advocate Service Assistance, describing the hardship.