TC 621: Dishonored Installment Payment

What the code actually does

IRS Document 6209, Section 8A scopes TC 621 to extension-related remittances: it "reverses a dishonored payment submitted with a tentative Form 1120 return or Forms 7004/2758/8736," reducing the TC 620 credit in whole or in part.

The consequence is the same as its individual-payment counterpart: "if not accompanied by a secondary TC 280, a TC 286 is systemically generated." IRC §6657 itself carries a built-in exception to that penalty — 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, as TC 611 already covers for the return-remittance version of this same penalty. The extension itself, evidenced by a companion TC 460, is not affected by the payment bouncing — the extension can remain valid even though the money behind it did not clear.

The extension survives even when the payment does not

This is the detail worth knowing cold. TC 620's own posting logic generates the TC 460 due-date extension independently of whether the payment ultimately clears — the request itself earns the extension, not the check's eventual clearing.

That means a client can face a bad-check penalty under IRC §6657 for the dishonored check, plus interest and failure-to-pay exposure on the unpaid extension balance, while still keeping a validly extended filing deadline. Those are separate problems and separate defenses.

Reading the sequence on the transcript

Look for TC 620, followed by TC 621 dated close behind it. Where a secondary TC 280 accompanies the 621, an employee assessed the penalty manually and no automatic TC 286 will separately appear; where it is absent, expect the systemic TC 286 on the same or a following cycle.

IRM 21.5.7.3 directs the same research path used for every code in this batch — CC (Command Code) BMFOL with definer P, the IDRS command that pulls an account's payment history for a date range — before concluding a payment tracer is even necessary; a dishonored-check reversal is not a missing payment, and tracing it as one wastes the research cycle.

This sequence is worth documenting carefully in the file, since a client disputing the resulting penalty months later will want to see exactly which cycle the dishonor posted in and whether the secondary TC 280 was present, rather than reconstructing it from memory at the time of an appeal.

What TC 621 gets confused with

It gets confused with TC 622, the correction of a TC 620 posted in error by the IRS itself. Both reduce a prior TC 620, but only 621 stems from an actual returned payment and only 621 carries the automatic penalty exposure.

It gets confused with a revoked extension. The extension (TC 460) and the payment (TC 620/621) are tracked independently; a dishonored check does not, by itself, undo an approved extension.

It gets confused with the plain-payment dishonor pattern on TC 611. The two are structurally identical but apply to different underlying transactions — 611 to a return remittance, 621 to an extension remittance — and mixing them up misreads which form generated the original payment.

The practitioner's actual next step

Confirm the extension (TC 460) is still valid on the module (the account record for one tax period) before addressing the payment problem — the two are not the same fight.

Identify why the check was dishonored with the client's bank before assuming an IRS processing error.

Address the resulting TC 286 bad-check penalty on its own reasonable-cause terms if one posted.

Recompute failure-to-pay exposure from the original extended due date, since the balance has effectively been unpaid since then, not since the reversal posted.