TC 131: Reversal of TC 130 Refund Freeze

What the code actually does

TC 131 is, in the IRS's own words, the "Reversal of TC 130 Refund Freeze." Per Doc 6209 §8A, it "releases the TC 130 Account refund freeze if input as the same type as the original TC 130, permits refunding of overpayment if other freeze conditions are not present." Two conditions sit inside that one sentence, and both have to hold before a client actually sees a refund: the TC 131 has to match the original TC 130's type, and nothing else on the account can still be holding the refund back.

That second condition is the one worth double-checking before telling a client money is coming. TC 130 is only one of several account freezes that can sit on a module at the same time — a TC 131 clearing this specific hold does nothing about an unrelated freeze posted for a different reason, and the refund still won't move until every hold clears.

Two ways a V- freeze actually ends — and why the difference is the whole story

Doc 6209's freeze-code chart lists the release for TC 130's V- freeze in five words under its "Freeze Release" column: "TC 131 or TC 824." They are not two paths to the same result. TC 131 is a true release — the liability that justified the freeze turned out not to require this money, so the credit is simply freed to refund. TC 824 is a transfer — Doc 6209 describes it as moving "overpayment credits frozen by TC 130 Account Refund Freeze" to satisfy the liability on the other account, and only then releasing the freeze as a side effect of the money already being gone.

For the client, that is the difference between good news and news that needs an explanation. A TC 131 on the transcript means the freeze lifted clean and a refund should follow. A TC 824 instead of a TC 131 means the freeze lifted because the IRS kept the money — the practitioner's job at that point is tracing where the credit went and confirming the underlying liability it paid down was actually correct, not explaining a refund that was never coming.

A second job TC 131 does on DMF-linked accounts

Doc 6209 adds a narrower, second use for the same code on Debtor Master File-linked liabilities: "DMF: agency refund of a prior offset of refund reversal correcting a prior agency refund." Read plainly, this describes TC 131 also recording the case where the agency that received a prior Treasury Offset Program payment refunds it back — correcting an offset that shouldn't have happened, rather than releasing a freeze that was never actually paid out. That is a narrower, DMF-specific reading than the general freeze release above, and it is worth distinguishing before assuming every TC 131 on a DMF-linked module means the same thing as one tied to a purely internal IRS liability.

The marker that confirms it — TC 132

A reversed TC 130 also generates its own automatic marker, TC 132, described in Doc 6209 as simply "A TC 130 which was reversed." It carries no independent action of its own — it is a system-generated confirmation, not something an employee inputs — but its presence next to a TC 131 is a useful cross-check that the reversal actually processed rather than merely being requested.

The practitioner's actual next step

Read the release code, not just the fact that something reversed the freeze. A TC 131 means check for any other freeze still active on the module before promising a timeline; a TC 824 means trace the transfer to the receiving account and confirm the amount matches what the client was actually owed.

On a DMF-linked account, confirm which TC 131 scenario actually applies — a straightforward freeze release, or the narrower agency-refund correction Doc 6209 describes — before explaining to the client why a number changed on the transcript a second time.

If the underlying TC 130 came from the OIC (Offer in Compromise)-hold variant rather than an outstanding liability, confirm the accepted offer's own terms before assuming TC 131 closes the matter for good — this is not the same posture as a rejected offer under TC 481, which carries entirely different statute and appeal consequences.

What TC 131 gets confused with

TC 131 and TC 824 both end a TC 130 freeze, both can post on the same reversed hold, and a quick transcript read can mistake one for the other — reading the wrong one is the single most common way a practitioner ends up promising a client a refund that was actually just used to pay a different balance. The fix is the one described above: read which specific code posted, not just that the freeze is gone.

The pattern of a freeze code needing a matching, code-specific reversal isn't unique to TC 130. TC 470 works the same way — it takes a matching TC 472 to release it, and assuming any reversal-looking code clears any freeze produces the same kind of transcript misread in either code family. Confirm the release code is actually the one paired with the freeze in front of you, on either page, rather than assuming a general "something reversed" is enough.