TC 611: Dishonored Remittance With Return

What the code actually does

IRS Document 6209, Section 8A is precise about the scope: TC 611 "reverses a dishonored payment submitted with return," and "reduces TC 610 credit in whole or in part." A partial reversal is possible when a bank returns only part of a combined remittance unpaid.

The mechanism is automatic in the ordinary case. Doc 6209 states that "if not accompanied by a secondary TC 280, a TC 286 is systemically generated." A practitioner does not need to look for a separate assessment action to explain a new balance appearing on a module (the account record for one tax period) that previously showed TC 610 as paid in full.

Why a client sees a balance appear out of nowhere

The sequence a client experiences is jarring: a return that looked paid in full suddenly shows a balance due, with no notice of deficiency, no audit letter, and no correspondence they remember opening. TC 611 followed by a systemically generated TC 286 is almost always the explanation.

The penalty is not discretionary interest on an assessment — it is a statutory penalty under IRC §6657, which sets it at "2 percent of the amount of such instrument, except that if the amount of such instrument is less than $1,250, the penalty under this section shall be $25 or the amount of such instrument, whichever is the lesser." In practice that means a bounced amount under $1,250 draws the SMALLER of $25 or the amount itself, not a flat $25 floor — a $10 check draws a $10 penalty, not $25. The statute also carries its own built-in exception, separate from ordinary reasonable-cause abatement: it "shall not apply if the person tendered such instrument in good faith and with reasonable cause to believe that it would be duly paid" — a defense worth raising before assuming a systemically generated TC 286 has to stand.

Confirming it before assuming an IRS error

Before treating a new balance as a Service mistake, confirm the transaction sequence with a full account transcript rather than the balance-due notice alone. IRM 21.5.7.3 reminds researchers to check CC (Command Code) TXMOD and CC IMFOL/BMFOL — internal, employee-only transcript-research command codes — for the full posting history, not just the current module balance.

A TC 611 dated the same as, or shortly after, the original TC 610 is the tell. Where a secondary TC 280 already accompanies the reversal, no separate TC 286 will follow — an employee assessed the penalty manually instead of the system generating it, which is worth distinguishing when calculating what is actually owed.

What TC 611 gets confused with

It gets confused with TC 612, the correction of a TC 610 posted in error. Both debit the module against a prior TC 610, but 612 exists for the IRS's own data-entry mistake and carries no penalty consequence, while 611 exists for the taxpayer's bank declining the payment and typically does.

It gets confused with an ordinary balance-due assessment. Reading TC 611 as "IRS says I owe more tax" misses that the code changes nothing about the tax liability itself — it only reverses a payment that never actually cleared.

It gets confused with the transcript decoder tool's generic dishonored-payment entries for other payment types. The specific prior code matters: TC 611 only ever reverses TC 610, never a subsequent payment or a designated payment — those reverse under their own dedicated codes instead.

The practitioner's actual next step

Pull a full account transcript, not the balance-due notice, to see the TC 610/611 pair and whether a TC 286 followed automatically.

Confirm with the client's bank why it returned the payment before assuming fraud or IRS error — insufficient funds, a stop payment, or a routing-number mismatch each has a different fix.

If a TC 286 penalty posted, first test the client's facts against §6657's own built-in exception — it requires both good faith and a reasonable basis to believe the check would clear — before falling back to ordinary reasonable-cause abatement; the statutory exception is the more direct fit when the client can show both.

Verify whether the return itself is now technically unpaid as of its due date, since that affects failure-to-pay penalty and interest computations distinct from the bad-check penalty.