TC 651: Dishonored Federal Tax Deposit

What the code actually does

IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) defines TC 651 as reversing "a dishonored payment submitted as a Federal Tax Deposit," scoped to employment and excise-tax MFTs (Master File Tax account types) 01, 03, 09, 10, 11, 12, 14, and 16 — the family TC 650 posts against, plus MFT 14.

The penalty consequence follows the same pattern as every dishonored-payment code: "if not accompanied by a secondary a TC 280, a TC 286 systemically generates."

Two penalties can stack from one bad check

This detail is easy to miss. A dishonored federal tax deposit is not just a returned-payment problem under IRC §6657; it also means the deposit, as of the date it bounced, was never actually made on schedule — which can separately trigger the Failure to Deposit penalty under IRC §6656 the deposit was supposed to satisfy in the first place, on top of whatever the bad-check penalty itself adds.

The two penalties rest on different statutes and different reasonable-cause standards. Treating a TC 651 as a single bad-check event, and stopping there, misses the second exposure: the Failure to Deposit penalty rate rises with how many days late the deposit ultimately was, while the bad-check penalty is 2 percent of the returned instrument ($25, or the instrument's amount if less, when the instrument is under $1,250), so the two together can add up to more than either one alone. Building a reasonable-cause case for one penalty without addressing the other leaves real exposure on the table. A fact that excuses the dishonored check, such as a bank processing error, does not automatically excuse the underlying deposit being late. The two arguments need to be made separately.

Confirming the deposit schedule was actually missed

Not every dishonored deposit produces a Failure to Deposit penalty — if a replacement deposit was made within the schedule's own timing rules, or the employer qualifies for a safe harbor, the penalty may not apply at all. IRM 21.5.7.3.2 directs the same account-wide research used across these codes — CC (Command Code) IMFOL/BMFOL and the IAT (Integrated Automation Technologies) TC Search Tool, the internal command-code tools an IRS employee uses to reconstruct a payment history — to trace the full deposit and reversal timeline before assuming the worst case, since the timeline itself often determines whether any penalty applies at all.

Because TC 650 deposits can roll between adjoining tax periods, confirm which specific deposit actually bounced before assuming the current-period shortfall on the module (the record for one tax type and period) is the dishonored one — a deposit that rolled forward before the dishonor posted can leave the wrong quarter looking short. Reviewing the client’s full transcript for both the current and adjoining periods, rather than relying on a single-period balance-due notice, is usually the fastest way to see which deposit the TC 651 actually reversed.

What people mistake TC 651 for

People confuse it with TC 652, a correction or credit transfer of a TC 650 deposit, whoever caused the misposting. 652 carries no automatic penalty; 651 reflects an actual returned payment and typically does.

People confuse it with a single, isolated penalty event. In practice it is often two: the bad-check penalty on the dishonored instrument itself, and a separate Failure to Deposit penalty on the underlying missed deposit.

People confuse it with the general "payment bounced" pattern seen in TC 611 or TC 621. The mechanism is identical, but only a dishonored FTD carries the deposit-schedule consequence layered on top.

What to do next

Separate the bad-check penalty analysis from the Failure to Deposit penalty analysis; they have different triggers and different reasonable-cause arguments, and conflating them in a single abatement request risks losing the argument that would otherwise have succeeded on its own.

Confirm with the bank why the bank dishonored the deposit, since a bank or EFTPS processing error can support the bad-check exception under IRC §6657's own built-in test (good faith and reasonable cause to believe the check would clear). That test fits the bad-check penalty better than ordinary reasonable-cause abatement, as on TC 611; the late deposit still needs its own §6656 case. Document the reason in writing, since a verbal explanation from the bank rarely survives to the abatement request months later.

Check whether a timely replacement deposit was made after the dishonor, which can limit or eliminate the deposit-schedule penalty, and note the exact date it posted for the reasonable-cause narrative.

Reconstruct the full deposit history across adjoining periods before concluding which specific TC 650 the TC 651 actually reversed, since attaching the wrong deposit to the wrong reversal can lead to a reasonable-cause argument built on the wrong facts entirely.