TC 721: Dishonored Refund Repayment

By Forrest Baumhover, CFP®, EA · Last verified September 9, 2026

TC 721 means a taxpayer's own check to repay a refund they received in error bounced — an unusual direction of money that still triggers the same automatic bad-check penalty as any other dishonored payment on the account.

What the code actually does

A taxpayer who received a refund they were not entitled to, or received more than they were owed, can voluntarily repay it — that repayment posts as TC 720 and freezes the module "from offsetting and refunding unless TC290/291 is posted with Priority Code 8 or tax balance becomes zero or debit," per IRS Document 6209, Section 8A.

TC 721 is what happens when that repayment check itself bounces. Doc 6209 describes it as a "dishonored check" that "may be equal to or less than the TC 720," and, following the pattern common to every code in this batch, states "if not accompanied by a secondary TC 280, TC 286 is systemically generated."

The direction of money is backwards from every other page in this library

Every other dishonored-payment code in this batch reverses money the taxpayer sent to satisfy a liability. TC 721 reverses money the taxpayer sent to give back a refund they should never have received in the first place — a voluntary repayment, not a required one, and one that still failed to clear.

That distinction does not change the mechanics of the bad-check penalty under IRC §6657, which applies regardless of what the dishonored check was meant to accomplish. It does change the practical stakes: the taxpayer is now back to owing the full erroneous-refund amount, with a bad-check penalty layered on top of an attempt to do the right thing.

Interest follows a companion code, not this one

Doc 6209 notes that TC 721's "companion TC is 770 for interest amount" — the interest consequence of the dishonored repayment posts separately, on the interest-credit code rather than on TC 721 itself. Reconstructing the full financial picture after a dishonored refund repayment means checking both transactions, not just the reversal of principal.

Because this sits inside the broader erroneous-refund process, confirm whether the case is also tracked under the erroneous-refund procedures elsewhere in the account before treating the dishonored repayment as a standalone payment problem.

What TC 721 gets confused with

It gets confused with an ordinary payment reversal for a balance due. TC 721 exists inside the erroneous-refund repayment process, where the underlying "liability" is the refund itself, not an assessed tax balance.

It gets confused with TC 722, the correction of a TC 720 processed in error by the IRS. TC 722 fixes a data mistake and carries no automatic penalty; TC 721 reflects an actual dishonored check and typically does.

It gets confused with a punishment for having taken the refund in the first place. The TC 286 penalty here attaches to the bounced check, not to the fact that an erroneous refund was issued or received.

The practitioner's actual next step

Confirm the full erroneous-refund repayment amount is still outstanding — the dishonored check did not reduce what is owed, it only failed to satisfy it.

Check for the companion interest transaction alongside the reversal, since interest on the repayment does not post on TC 721 itself.

Arrange a replacement payment method promptly, given that the frozen-module conditions on the original TC 720 generally do not favor letting the balance sit unresolved.

Address the resulting TC 286 bad-check penalty as a distinct issue from the underlying erroneous refund.

Sources

Free weekly federal tax analysis for practitioners

Every week, the handful of federal tax changes that actually require action — with primary-source citations, and new IRS practitioner tools the day they ship.

Subscribe free →