TC 720: Refund Repayment

What the code actually does

Document 6209 titles TC 720 plainly: "Refund Repayment." Unlike most of the transaction codes clustered around it in the 720-850 range, TC 720 is a credit, not a debit — it adds money back to the tax module (the IRS's internal record of one tax period on one account) rather than taking it away. Doc 6209 also names its companion: "Companion TC is 772 for interest amount," meaning a TC 720 that carries interest will typically post alongside a TC 772, the correction-of-interest code, rather than a plain interest-allowance code.

The transaction also sets a freeze. Per Doc 6209: "BMF [Business Master File]/IMF [Individual Master File] Tax Module is frozen from offsetting and refunding unless TC290/291 is posted with Priority Code 8 or tax balance becomes zero or debit." In plain terms, once money comes back into a module via TC 720, the IRS will not automatically send it back out or apply it elsewhere until one of those specific release conditions is met.

The freeze it sets, in IRS shorthand: the P- Freeze

The current Internal Revenue Manual gives TC 720 its plainest gloss inside the freeze-code chapter rather than a refund-specific one. IRM 21.5.6.4.31, P- Freeze, states: "The P- Freeze (Refund Repayment, Cancellation, or Deletion) is set by the following: A Transaction Code (TC) 720 (a portion of a refund returned by a financial institution or an erroneous refund repayment)..." That single parenthetical captures both of TC 720's real-world triggers: a bank sending money back, or a taxpayer repaying a refund the IRS demanded back.

The same subsection lists what clears the freeze: "TC 29X posts to the module TC 30X posts to the module TC 820 posts to the module TC 830 posts to the module A Doc Code 24 or 34 credit transfer posts to the module The module balance becomes zero or debit." A TC 830 credit-elect transfer is one of several ordinary account events that can release it — the freeze is not a sign anything is permanently stuck, just that the module needs one of these events before it will move money again.

Why the posting date matters: interest suspension on Category D erroneous refunds

When the IRS demands repayment of an erroneous refund, timing changes how much interest accrues, and the transaction code the repayment posts under is what tells Master File (the IRS's central computer system that holds and updates every taxpayer's account) whether to apply that timing correctly. IRM 21.4.5.14, Interest and Penalty Consideration for Category D Erroneous Refunds, states it directly: "A payment received within 21 calendar (or 10 business) days from the erroneous refund demand date must post with a TC 720 for Master File to correctly suspend interest from the date of demand to the repayment date." The same subsection continues: "Likewise, if the repayment did not post with a TC 720, interest must be manually computed and input" — meaning a repayment that posts under the wrong code does not just look different, it can leave interest wrong until someone corrects it by hand.

That same subsection carries the dollar thresholds driving how far back interest reaches on one of these erroneous refunds in the first place: whether it is "$50,000 or less" or "more than $50,000," and a further line at "$100,000 or more" that shortens the taxpayer's response window from 21 days to 10 business days. A TC 720 posted late, against a large erroneous refund, is therefore not a paperwork footnote — it can be the difference between interest running from a notice-and-demand date and interest running all the way back to the original refund date.

What TC 720 gets confused with

The nearest mix-up is with TC 722, which despite sharing the same numeral family means something entirely different: TC 722 does not record a repayment at all, it corrects a TC 720 that Master File posted in error. Seeing both codes on the same module is not double-counting a repayment — it is the IRS undoing its own mistaken entry.

It also gets confused with TC 721, a genuinely separate event rather than a duplicate repayment: TC 721 posts when the repayment check behind a TC 720 itself bounces. Doc 6209 describes it as a "dishonored check" that "may be equal to or less than the TC 720," and it typically carries its own bad-check penalty. A TC 720 followed by a TC 721 on the same module means the repayment never actually cleared, not that the taxpayer repaid twice.

The other mix-up runs in the opposite direction from what the numbering suggests. Because TC 720 sits numerically close to the manual-refund and refund-issuance codes, it is easy to assume it means money going out. It means the reverse: TC 720 exists specifically because a refund the IRS already issued — through TC 840 or the systemic refund code — is now coming back, either because a bank rejected the deposit as questionable or because the taxpayer is repaying on demand.

What this means for your refund

If a TC 720 shows up on your transcript, it almost never means a new refund is coming — it means money the IRS already sent has come back to your account, and it is now frozen there until specific conditions are met. Two very different situations produce this: your bank flagged the deposit as questionable and returned it to the IRS for review, or you are repaying an amount the IRS determined was refunded to you in error.

If the External Leads process is involved (your bank returned the money on its own), the IRS notes that this "can take several weeks," and the account may not visibly reflect it right away. If instead you received a notice demanding repayment of an erroneous refund, when your payment posts — and whether it posts under this specific code — affects how much interest you owe, so this is a good moment to have a tax professional confirm the posting matches your payment date before assuming the interest calculation is final.

The practitioner's actual next step

Determine which of the two triggers produced the TC 720 before advising a client — an External Leads bank return and an erroneous-refund repayment demand call for completely different next actions, and the code alone does not distinguish them.

If it is an erroneous-refund repayment, confirm the payment actually posted with a TC 720 rather than as a generic payment — IRM 21.4.5.14 is explicit that a repayment posting under the wrong code leaves Master File unable to compute interest correctly, and someone has to catch and fix it manually.

If the freeze looks stuck, check for one of its actual release conditions (a TC 29X, TC 30X, TC 820, or TC 830 posting, or a Doc Code 24/34 credit transfer) rather than assuming an error — the freeze is a deliberate hold on further movement, not evidence something has gone wrong.