TC 621: Dishonored Installment Payment

What the code actually does

IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) 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. Doc 6209 does not show TC 621 reversing the companion TC 460 — the TC 460 can stay on the module (the record for one tax type and period) even though the money did not clear.

A dishonored check does not remove the TC 460 by itself

TC 620 generates the TC 460 when it posts, and Doc 6209 shows TC 621 only reducing the TC 620 credit. The TC 460 posting does not decide whether the extension is valid: Treas. Reg. §1.6081-3(a)(3) requires the corporation to remit the properly estimated unpaid tax by the payment due date.

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 the TC 460 stays on the module. 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.2 lists the research commands an IRS employee runs to pull an account's payment history, CC (Command Code) BMFOL among them, 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 people mistake TC 621 for

People confuse it with TC 622, a correction or credit transfer of a TC 620 payment, whoever caused the misposting. Both reduce a prior TC 620, but only 621 stems from an actual returned payment and only 621 carries the automatic penalty exposure.

People confuse it with a revoked extension. The extension (TC 460) and the payment (TC 620/621) are tracked independently; a dishonored check does not, by itself, remove the TC 460, and a Form 7004 extension still depends on the remittance.

People confuse it 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.

What to do next

Confirm the extension (TC 460) is still valid on the module 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 unextended due date, since the balance has effectively been unpaid since then, not since the reversal posted.