TC 240: Assessment of a Miscellaneous Civil Penalty

What the code actually does

TC 240 is a container. IRS Document 6209, Section 8A defines it by exclusion — it posts "when a miscellaneous type penalty is assessed (i.e., other than those penalties which are identified with their own TC or reference no.)" — and directs the reader to the penalty reference number tables for what it actually is in any given case.

IRM 20.1.1.5.2 explains why the arrangement exists. Most penalties get their own transaction code, but "some penalties assessed on a tax module will use a TC 240 with a Penalty Reference Number (PRN) that identifies the type of penalty," and "these reference numbers are generally between 500 and 799." There are far more penalties in the Code than there are spare transaction codes, so the reference number does the identifying.

The practical consequence is blunt: a TC 240 read without its reference number conveys that a penalty was assessed and nothing else. Not which penalty, not under what provision, and therefore not what relief is available.

It is systemic far more often than it looks

The four-code penalty pattern puts TC 240 in the manual slot and TC 241 in its abatement — which invites the inference that a TC 240 means somebody decided something. The IRM corrects that directly. Exhibit 20.1.1-3 carries a caution on the row: "manual input of a TC 240 is limited to rare circumstances. Input of a PRN for a positive amount will result in a systemic TC 240."

So in the ordinary case nobody typed this transaction. Someone entered a penalty reference number with an amount, and the assessment code followed automatically. The decision, such as it was, lives in whatever process produced the reference number — and that may well have been systemic too.

This matters for how a relief request is framed. Approaching a TC 240 as a considered determination to be argued with can be the wrong posture; approaching it as the mechanical output of a reference number, and asking what put the reference number there, is usually the more productive route.

Reading the reversal notation

The penalty codes carry a notation convention that is easy to misread as a different code entirely, and the exhibit states it for the whole family: "when a manual penalty assessment is reversed, the reversed portion is reflected separately from the remaining portion (if any). The reversed portion is also uniquely identified by an ‘R’ following the transaction code for BMF transactions, and by the ‘0’ being replaced by a ‘3’ for IMF transactions."

It then gives this code as its worked example: "the reversed portion of a TC 240 assessment becomes a TC 240R in BMF, and a TC 243 in IMF." A practitioner encountering a TC 243 on an individual account is not looking at an unfamiliar transaction; they are looking at the reversed portion of this one.

The convention also explains why a partially abated penalty shows as two lines rather than one net figure. Both are real, and reading only the remaining portion understates what was originally assessed.

What TC 240 gets confused with

It gets confused with a specific penalty, usually whichever one the practitioner encountered last. The accuracy-related penalty is a common instance: it is assessed by reference number rather than by its own code, so an accuracy-related penalty posts here and its abatement posts as TC 241 — not, as most people expect, under the civil fraud codes. The TC 320 page sets out why those two are genuinely different provisions.

It gets confused with the failure-to-file penalty on partnership and S-corporation returns, which since 2022 has also been assessed by reference number. Those postings use their own systemic pair rather than this code, and telling them apart requires the reference number in both cases.

And its reversal gets read as relief. An abatement here says a penalty came off; it does not say why, and it does not distinguish a granted reasonable-cause request from a correction of something that should never have been assessed. Establishing which relief path is actually available is what the Penalty Abatement Analyzer is for, and it needs the reference number to do it.

The practitioner’s actual next step

Get the penalty reference number before anything else; without it there is no analysis to do.

Look up the reference number in the IRM’s 500, 600 and 700 series exhibits rather than guessing the penalty from context.

Treat the assessment as systemically produced by that reference number unless there is reason to think otherwise.

Read a reversed-portion notation as part of this code rather than as a separate transaction.

Frame the relief request against the underlying provision the reference number identifies, not against this code.

Confirm what actually posted, and in what order, against the module with the IRS Transcript Decoder before quoting the client a penalty total.