TC 287: Systemic Reversal of the Dishonored Payment Penalty

What the code actually does

TC 287 is a systemically generated reversal. IRS Document 6209, Section 8A states that it “systemically reversed any posted, unreversed TC 280/286 when the module status is: ‘06’ with a debit balance and the net TC 28X amount equals the module balance.” IRM 20.1.10.7.3 describes the same event in plainer terms and adds the file scope: “when the collection status code is updated to ‘06’ (taxpayer is not required to file a return on this module), the module is in debit balance, and the net TC 28X amount equals the module balance, then the TC 280 or 286 net penalty amount is systemically reversed. For BMF, it is shown as TC 287.”

Both sources agree on the substance and Doc 6209 marks the code “B” for the Business Master File, so this is a business-account transaction. On an individual account the same write-off happens without carrying this code.

The three conditions, and why they matter together

Each condition is doing separate work, and reading them as a set is what makes a TC 287 interpretable. Status 06 means the taxpayer is not required to file a return on that module — the IRM’s own gloss. The module must be in debit balance, so something is still owed. And the net 28X amount must equal the module balance, meaning the dishonored-payment penalty is the *only* thing left on the account.

Put together, they describe a specific and rather narrow situation: a business module that has been closed out for filing purposes, where every other element has resolved, and the sole remaining balance is a bounced-payment penalty. The system clears it rather than leaving a small penalty-only balance sitting on a module nobody is going to file for again. That is an administrative tidying rule, not a relief provision — and it is why the code appears on some accounts and never on others that look superficially similar.

Why it cannot be requested

This is the practical point, and it saves wasted effort. Because a TC 287 fires only when the three conditions coincide, there is no route by which a practitioner can obtain one. A caseworker cannot input it; the system produces it. A client who has read that this penalty is sometimes reversed automatically, and who wants that outcome, is asking for something no one at the IRS can grant.

The available action is TC 281, the input abatement, and it is available on far broader grounds — IRM 20.1.10.7.4 sets out the bank-error and Treasury-agent-error paths with their own penalty reason codes, and IRM 20.1.10.7.2 directs abatement outright where a dishonored payment code was used improperly. Neither depends on the module reaching status 06. So the correct reading of a TC 287 is retrospective: it explains why a penalty disappeared from an account that has since been quiet. It is never the plan.

What TC 287 gets confused with

TC 287 gets confused with TC 281 on the assumption that they are the manual and systemic halves of one relief mechanism, the way several pairs in this library are. The comparison misleads in an important way. TC 281 reflects a decision about the client’s case; TC 287 reflects nothing about the client at all, only about the shape of the module. Reporting a TC 287 to a client as an abatement of their penalty implies a determination that never happened, and — because the reversal is conditioned on the module having no other balance — it also implies the account is settled, which may be true of that module and not of the taxpayer.

It is also assumed to follow the pattern that a systemic reversal can only reach a systemic assessment. That pattern does hold elsewhere: TC 167 reaches only the computer-generated late-filing penalty, and TC 187 only the computer-generated deposit penalty. It does not hold here. Doc 6209 says a TC 287 reverses “any posted, unreversed TC 280/286,” so the systemic code reaches the manually assessed penalty too. The gating factor for this pair is the state of the account, not who made the assessment.

The practitioner’s actual next step

Read a TC 287 as an explanation of a past event rather than as relief, and check what the module’s status and balance were when it posted.

Never build a strategy around obtaining one. Pursue an input abatement instead, on whichever documented ground fits the facts.

Confirm what the reversal actually cleared, since the conditions require the dishonored-payment penalty to be the only remaining balance on that module — a fact worth verifying rather than inferring.

Check the taxpayer’s other modules before treating anything as resolved, because status 06 speaks to one period’s filing requirement and not to the account as a whole.

Reconstruct the sequence with the IRS Transcript Decoder, and address any separate late-payment exposure through the Penalty Abatement Analyzer, where the administrative waiver is available even though it never reaches this penalty.