TC 239: Systemic Abatement of the Daily Delinquency Penalty

What the code actually does

TC 239 is a generated transaction on a business account. IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) states in its first sentence that it “abates a previously assessed TC 238” — TC 238 being the computer-generated Daily Delinquency Penalty on a late or incomplete exempt-organization return under IRC 6652(c).

The penalty is the per-day charge that runs for as long as the failure continues, and the pairing follows the manual and systemic pattern that recurs across this site: TC 234 is the manual assessment and TC 238 the systemic one, while TC 235 is the manual abatement and TC 239 the systemic. The reach differs the way it usually does — TC 235 abates “TC 234/238,” both assessments, while TC 239 reaches only the systemic TC 238. So a granted relief request will post as a 235, never as a 239.

The reconciliation nobody asked for

Doc 6209’s second sentence describes behavior that has nothing to do with abatement in the ordinary sense, and it accounts for a meaningful share of real TC 239 postings. Where a module (the record for one tax type and period) already carries a systemic TC 238 and a person then inputs a manual TC 234, the system reconciles the two rather than letting both stand.

The rule has two branches. If the TC 234 is for less than the previously posted TC 238, “TC 239 is generated in amount of difference and TC 234 is dropped” — the manual figure disappears, and a TC 239 appears for the gap, leaving the net at the lower manual amount. If the TC 234 is for more, “TC 239 is generated for TC 238 amount and TC 239 and TC 234 are posted” — the systemic penalty is backed out in full and the larger manual figure stands alone.

Either way a TC 239 appears without anyone having granted relief, and in the second branch it appears on an account whose penalty just went up. A practitioner reading the credit as good news, or trying to reconcile it against a request that was filed, will misread the account. Establishing whether a TC 234 posted around the same date is the fastest way to tell a reconciliation apart from a genuine systemic abatement.

First-Time Abate does not reach this penalty

The constraint that shapes relief strategy here is categorical. IRM 20.1.1.3.3.2.1 lists, among the situations where relief under the First-Time Abate waiver does not apply, “the Daily Delinquency Penalty (DDP), see e.g., IRC 6652(c)(2)(A) and IRM 20.1.8, Employee Plans and Exempt Organization Penalties.” It also excludes, more broadly, “returns with an event-based filing requirement” and “information reporting that is dependent on another filing.”

So a clean three-year history buys an exempt organization nothing against this penalty, and reasonable cause is the route — argued on the facts of why the return was late or incomplete. It is worth checking the rate the assessment actually used, because the number on the notice is rarely the bare statutory figure. IRC §6652(c)(1)(A) itself sets $20 per day against a $10,000 (or 5%-of-gross-receipts) cap, but IRM Exhibit 20.1.1-3, Penalty Transaction Codes, records in its 23X row that “the penalty rate and maximum penalty are subject to an annual inflationary adjustment,” and IRM 20.1.8.3.2.1 applies the amounts for the year the return was due. For a return required to be filed in 2026, Rev. Proc. 2024-40 section 2.54 sets the rate at $25 per day against a cap of the lesser of $13,000 or 5% of gross receipts, rising to $130 per day and a $65,000 cap once the organization’s gross receipts exceed $1,309,500 for the year. A TC 239 computed off the bare statutory figures, or off an earlier year’s adjusted amounts, is a straightforward arithmetic correction rather than a relief request.

What people mistake TC 239 for

People confuse TC 239 with TC 235, the manual abatement of the same penalty, and the two are genuinely overlapping — both can remove a TC 238. The distinction is whether a person or the computer made the entry, and it decides what the posting means. A person inputs a TC 235, which can follow a reasonable-cause determination; the computer generates a TC 239, which reflects either a recomputation or the reconciliation described above. Reporting a TC 239 to a client as evidence that their abatement request succeeded asserts a determination that did not happen.

People also confuse it with TC 241, the miscellaneous civil penalty abatement, since both are credits on exempt-organization modules that can appear near one another. They abate different things: TC 239 reaches the Daily Delinquency Penalty specifically, while TC 241 reaches whichever penalty its accompanying reference number identifies. On a module carrying both, netting them together will misstate what actually came off and against which charge.

What to do next

Check for a nearby manual assessment before treating a TC 239 as relief, since a TC 234 posting on a module that already had a TC 238 generates one automatically.

Read the net rather than the credit, because in the reconciliation case the penalty can rise even though a credit appears on the transcript.

Do not build a request on First-Time Abate. The IRM excludes the Daily Delinquency Penalty by name, and reasonable cause is the available ground.

Verify the rate and cap against the revenue procedure for the return’s own tax year, since both are inflation-adjusted and a wrong-year computation is correctable arithmetically.

Expect any granted relief to post manually, and confirm what is actually assessed on the module with the IRS Transcript Decoder before advising the organization the matter is closed.