TC 281: Abatement of the Dishonored Payment Penalty

What the code actually does

TC 281 is the abatement side of the IRC 6657 dishonored-payment penalty. IRS Document 6209, Section 8A states that it “abates previously posted 280 or 286 transaction in whole or in part” — so unlike several abatement codes in this library it reaches both the manually assessed TC 280 and the systemic TC 286. IRM 20.1.10.7.3 gives the input rule: “input TC 281 on IDRS for the net amount of the penalty assessed on that payment.”

“Net amount... on that payment” is a precise instruction and a useful check. Where a client had several payments fail, each has its own penalty and its own abatement; a single TC 281 covering an aggregate figure is not how the IRM directs the work, and a request should identify the specific payment rather than the account balance.

The reason code decides the request

The IRM assigns different penalty reason codes to different causes, and matching the cause to the code is the most concrete thing a practitioner can do here. IRM 20.1.10.7.4 sets out two of them. Where the taxpayer shows the account held sufficient funds and “due to a bank error, the payment was dishonored,” with a letter of explanation from the bank, the abatement is input “with a TC 281, RC 065, and Penalty Reason Code (PRC) 017” on individual accounts, or a TC 281 with PRC 017 on business accounts. Where the failure was instead “due to an Electronic Federal Tax Payment System (EFTPS) or other Treasury Financial Agency (TFA) error,” supported by a letter or incident report from the agency, the code is PRC 032.

A third comes from the assessment subsection. IRM 20.1.10.7.2 directs employees to “abate any TC 286 penalty that generated because of the improper use of a dishonored payment transaction code. Use TC 281 with penalty reason code 045.” That one is the strongest of the three, because it does not depend on the taxpayer producing any document at all — the error was internal.

So the practical question is not whether the client deserves relief but which of these three fact patterns the case is. A request that names the pattern and the reason code is asking a caseworker to follow a written instruction; a request that describes the client’s frustration is asking for discretion this penalty does not offer.

It can post before a return does

Doc 6209 records an unusual capability: a TC 281 “will post prior to return (account with no TC 150) if it is the only transaction with the TC 290 and there is an unreversed TC 280 or TC 286 of equal or greater amount in the module.” IRM 20.1.10.7.3.1 confirms the practical version — where the taxpayer’s return “has not posted to Master File (there is no TC 150 on the tax period module), a bad check penalty abatement (TC 281, which generates with a ‘carrier’ TC 290 .00) can still be input on IDRS.”

That is genuinely useful. A client whose payment bounced on an extension or an estimated payment, with the return not yet processed, does not have to wait for the return to post before the penalty can come off. It also explains a transcript feature that otherwise looks wrong: a TC 290 for zero sitting beside the TC 281 is the carrier the abatement rides on, not a separate assessment of additional tax.

What TC 281 gets confused with

TC 281 gets confused with TC 287, because both remove the same penalty. They are not alternatives a practitioner can choose between. TC 281 is input by a person in response to a determination; TC 287 is generated by the system only when a specific set of account conditions happens to align, and the IRM records it as the business-account form. Asking for a TC 287 is not a request anyone can grant.

It is also mistaken for relief from the late-payment consequences of the same event, which it is not. Abating the dishonored-payment penalty does nothing about the failure-to-pay penalty and interest that ran because the tax went unpaid when the payment failed. Those need their own analysis, and unlike this penalty they are reachable by First-Time Abate — IRM 20.1.10.7.3 is explicit that the waiver “does not apply” to the bad check penalty. A client who gets a TC 281 and still sees a balance has not been treated inconsistently; they have two penalties and only one has been addressed.

The practitioner’s actual next step

Establish the cause first and name the matching penalty reason code in the request — 017 for a bank error, 032 for an EFTPS or Treasury agent error, 045 where the IRS misused a dishonored payment code.

Gather the required document before contacting anyone, since the bank-error and agency-error paths both require a letter and oral testimony is expressly not accepted.

Identify the specific failed payment rather than the account total, because the IRM directs abatement of the net penalty assessed on that payment.

Do not wait for a return to post. The abatement can be input on a module with no TC 150, riding a zero-amount carrier transaction.

Run the late-payment penalty separately through the Penalty Abatement Analyzer, where the administrative waiver is available even though it is not available here.