TC 187: Systemic Abatement of the Failure to Deposit Penalty

What the code actually does

TC 187 is a generated transaction with a narrow job. IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) gives it in two sentences: it “abates a previously assessed TC 186” and “issues Adjustment Notice.” IRM 20.1.4.13 lists it as “TC 187 — Computer generated abatement,” one of the four codes named in that subsection’s own title.

Both the reach and who made the entry matter. TC 187 abates a TC 186 and nothing else — it cannot touch a manually assessed TC 180. And no employee inputs it. It appears because Master File — the IRS’s central account-processing system — recomputed the penalty and concluded the earlier figure was too high, which means it is a recalculation rather than a decision.

What actually produces one

Two mechanisms account for most real TC 187 postings, and both are worth recognizing because neither requires a request.

The first is a payment finding its home. IRM 20.1.4.21.1 states that “if the payment has posted to the correct account after Master File generated the original penalty (TC 186), an automatic recomputation of the penalty occurs,” and directs the employee simply to notify the taxpayer that the payment has been properly applied or credited. A deposit posted to the wrong period or the wrong entity, then moved, will often clear the penalty by itself.

The second is the tax coming down. IRM 20.1.4.23 is explicit that no manual entry is needed for this: “it isn’t necessary to input a manual TC 181 when reducing (TC 291/301) the net tax to zero, as long as the computer generated (TC186) FTD penalty hasn’t been restricted (TC180/181).” The deposit penalty is computed against the tax required to be deposited, so an adjustment that reduces the net tax to zero removes the penalty with it — automatically, provided the module (the record for one tax type and period) is still computing. That proviso is the whole reason the manual and systemic sides of this family have to be kept apart in a practitioner’s head.

Why it is not evidence of relief

A client who requested First-Time Abate or reasonable-cause relief and later sees a credit against their deposit penalty will reasonably conclude the request was granted. Often it was not. Relief is a human determination, so a granted request posts as a manual TC 181, not as a TC 187. A TC 187 means the arithmetic changed.

The practical consequence runs in both directions. A TC 187 that clears the penalty entirely may leave a client’s First-Time Abate waiver unused and available for a future period (for a return AEP covers that is due on or after January 1, 2027, AEP replaces First-Time Abate), which is worth knowing before spending it. And a TC 187 that clears only part of the penalty is not a partial grant of relief to be appealed — it is a recomputation, and the remaining balance is still fully open to a relief request that has never actually been decided. Reading the code as a determination collapses those two situations into one and gets the next step wrong in either case.

What people mistake TC 187 for

People confuse TC 187 with TC 181, and the standard version of the confusion is that one is a full abatement and the other partial. Neither Doc 6209 nor the IRM supports that. The difference is whether a person or the computer made the entry: IRM 20.1.4.13 calls the 181 a “manual abatement” and the 187 a “computer generated abatement.” The reach differs too — TC 181 abates “180, 186,” so it can reverse either assessment, while TC 187 can only reverse the systemic one. The lower number is the person, and the person can reach both.

The second confusion is more costly. Because a manual abatement restricts systemic recalculation, a practitioner who requests a TC 181 in a case that would have self-corrected can leave the client worse off — the penalty comes off once, and the module then stops recomputing when later facts change. IRM 20.1.4.23’s instruction not to input a manual TC 181 when the tax is being reduced to zero exists for exactly that reason. Where the module is unrestricted and the underlying facts are moving, letting the system produce a TC 187 is the better outcome.

What to do next

Identify what moved before crediting a relief request — a repositioned payment or a tax adjustment produces a TC 187 with nobody having considered the client’s circumstances.

Check whether the abatement was full or partial, and treat any remainder as an undecided relief question rather than a denied one.

Confirm the module is not restricted before assuming a pending correction will flow through, since a manual entry anywhere in the 180/181 pair switches that behavior off.

Where the tax adjustment reduces the net tax to zero, avoid asking for a simultaneous manual penalty abatement on an unrestricted module — Master File generates a TC 187 and the penalty follows the tax down on its own, and a manual entry costs the account its recalculation.

Verify whether First-Time Abate has actually been consumed, using the Penalty Abatement Analyzer, because a systemic abatement leaves the administrative waiver intact for a later period (for a return AEP covers that is due on or after January 1, 2027, AEP replaces First-Time Abate).

On a 2025 or later tax-year return or a 2026 or later quarterly return of a form listed in IRM Procedural Update SBSE-20-0626-0643, check for Automatic Exemption from Penalty (AEP) before you request relief: an unreversed TC 971 action code 996 on the return’s own module shows that the IRS already granted AEP or a prior First-Time Abate there, and the IRS grants AEP when, among other conditions, an unreversed action code 995 sits on each of the prior three years’ modules (12 consecutive quarters for quarterly returns) and the taxpayer filed the return within three years of its original due date, but not when an unreversed 996 sits on any of those modules.