TC 661: Dishonored Estimated Tax Payment or Federal Tax Deposit

What the code actually does

IRS Document 6209, Section 8A defines TC 661 as reversing "a dishonored payment submitted as an estimated tax payment or a Federal Tax Deposit," with the automatic-penalty rule common to this batch: absent a secondary TC 280, "a TC 286 is systemically generated."

The dual meaning is a Master File split rather than genuine ambiguity. Doc 6209's own remarks column separates the valid document codes for the individual (estimated-tax) case from the business (FTD) case, and the module's MFT resolves which underlying payment — a TC 660 estimated payment on an individual return, or a TC 650 deposit on an employment or excise return — TC 661 actually reversed.

On an individual account, a second penalty can follow — but not always

A dishonored estimated tax payment does not just disappear from the module — it means the installment it was meant to satisfy was never actually paid on time, which is the specific condition IRC §6654 penalizes. Estimated tax exists to pay tax on income not subject to withholding on a fixed quarterly schedule — a schedule the bounced check failed to meet regardless of when a replacement payment eventually clears.

The bad-check penalty under IRC §6657 and the estimated tax penalty under §6654 are two separate exposures that can both follow the same dishonored check, in the same way a dishonored FTD can trigger both a bad-check penalty and a Failure to Deposit penalty (see the TC 651 page) — but §6654 exposure is not automatic. A taxpayer who otherwise met a safe harbor, or whose remaining payments still covered the year's liability, may owe no estimated tax penalty at all even though the check bounced. Put plainly: a bounced ES check only adds a penalty if you'd have owed one anyway.

Reading the module to tell the two cases apart

Since the reversal code itself does not disambiguate, confirm the MFT on the module before drawing conclusions. An individual income tax module (MFT 30) reversing a TC 660 estimated payment calls for the §6654 analysis above; an employment or excise module reversing a TC 650 deposit calls for the deposit-schedule analysis TC 651 carries instead.

The general payment-tracer research path applies regardless of which case is on the module — the standard IDRS (the IRS's internal Integrated Data Retrieval System) research (CC IMFOL/BMFOL and the IAT TC Search Tool) reconstructs the underlying payment before assuming which penalty regime governs, the same discipline every code in this batch relies on.

What TC 661 gets confused with

It gets confused with TC 651, the FTD-specific dishonor code. TC 651 reverses only a federal tax deposit; TC 661 can reverse either an estimated payment or a deposit, and the MFT is what settles which.

It gets confused with TC 662, the correction of a TC 660 processed in error, which corrects the IRS's own mistake and carries no automatic penalty, unlike an actual dishonored-check TC 661.

It gets confused with a single-penalty event when it is often two on the same account — the bad-check penalty on the returned instrument, plus either the §6654 estimated tax penalty or a Failure to Deposit penalty on the underlying missed payment.

The practitioner's actual next step

Check the module's MFT first — it determines whether this is an estimated-tax or a deposit problem, since the reversal code alone will not tell you.

On an individual account, evaluate §6654 estimated tax penalty exposure separately from the bad-check penalty — check whether a safe harbor or the year's other payments already covered the liability before assuming the penalty applies at all.

On a business account, follow the same dual-penalty analysis TC 651's own page sets out for a dishonored deposit.

Request a transcript, or ask the assigned IRS contact to reconstruct the payment history via CC IMFOL/BMFOL, before advising the client — those are IDRS command codes only an IRS employee can run — rather than relying on the reversal code's label alone.