TC 130: Entire Account Frozen From Refunding

What the code actually does

TC 130 posts to the entity section of an account — not to one specific tax period — and its own label in the Master File reference is blunt about the scope: "Entire account is frozen from refunding, overpayment is applied to NMF. Credits of $25.00 or more." Per IRM 21.5.6.4.43, the V- freeze it sets is "generated when there is a liability on another account with the IRS" — the freeze exists because of a debt somewhere else on record, not because of anything wrong with the return sitting in front of the practitioner.

That "another account" framing is the detail worth holding onto. A TC 130 can freeze refunds on a clean, fully-paid current-year return simply because an old liability sits on a different tax period, a different tax type, or a Non-Master File (NMF) record the IRS has linked to this one — the freeze reaches the whole entity, not just the module that happens to be generating the overpayment.

Where the freeze actually comes from

TC 130 carries a numeric field that the two primary sources describe, somewhat inconsistently, as an "indicator" in the IRM and a "closing code" in Doc 6209 — the same field, two names, worth flagging so a 99 or a 24 spotted on a transcript isn't mistaken for something else. Per IRM 21.5.6.4.43: "The TC 130 has a specific indicator to identify the agency with the outstanding liability. If the indicator is 99, the freeze is the result of a state or federal agency debt on the Debtor Master File (DMF). If the indicator is other than 99, it is the campus where the TC 130 was input." A 99 means the debt belongs to someone outside the IRS entirely — child support enforcement, another federal agency, a state — routed through the Treasury Offset Program. Anything else identifies which IRS campus entered the freeze for its own internal liability.

Doc 6209 adds a second, narrower closing-code pattern: "TC 130 with closing code 03, 12, or 24–32 should correspond to a BMF liability written off with TC 530 and will have similar TC 130 closing code." In plain terms, a liability on the taxpayer's Business Master File (BMF) record can be formally written off as currently uncollectible on the BMF side and still generate a matching TC 130 hold against the same taxpayer's IMF refunds — the write-off stopped active collection, it didn't forgive the debt or stop this freeze from working against a different account.

A third variant carries no liability at all. Doc 6209 notes: "A TC 130, Offer in Compromise (OIC) hold, on the Command Code (CC) IMFOL indicator field indicates that the overpayment is being held due to the monitoring of an accepted offer" — for an offer accepted before November 1, 2021, the IRS keeps refunds through the calendar year of acceptance as one of the offer's own terms. That reading has nothing to do with a rejection; see TC 481 for what actually happens when an offer is turned down instead of accepted, since the two outcomes read very differently on the same account. Treat this variant as increasingly a legacy artifact rather than something a fresh acceptance generates: per IRM 5.19.7.3.2, the IRS stopped systemically inputting TC 130 for OIC monitoring in June 2022, so an OIC-hold TC 130 found on a current transcript usually traces back to an offer accepted before that programming change, not a new one.

The $25 threshold — and what doesn't get held

On individual (IMF) accounts, the freeze only bites above a specific dollar line. Doc 6209: "IMF: Freeze only if more than $24.99... Credits under $25.00 before interest will be refunded, but TC 130 Freeze will not be released." Two things follow: a small overpayment goes out to the taxpayer as normal even with a TC 130 sitting on the account, and — the detail worth catching — the freeze itself stays in place regardless, because the small refund didn't resolve whatever the freeze exists for. A practitioner who sees a small refund issue and assumes the freeze cleared is reading the transcript backward. Above that threshold, per IRM 5.19.10.3.12, a frozen refund generates a matched pair rather than releasing automatically: a "Delay in Processing Your Refund" notice goes to the taxpayer, and an internal case — CP44 for an individual account, CP188 for a business account — routes to the IRS's Compliance Services Collection Operations (CSCO) for the underlying liability to be worked. Practitioners often use "CP44" loosely to mean the taxpayer notice itself; strictly it's the internal case number, but either way it confirms the freeze produced a live, working case somewhere in the IRS rather than a dead entry on a transcript.

How it gets released — TC 131 versus TC 824

Doc 6209's own freeze-code summary states the release condition in five words under its "Freeze Release" column: "TC 131 or TC 824." Those two codes are not interchangeable outcomes, and which one actually posts tells the practitioner something the freeze itself never revealed — whether the refund is coming or whether it just got spent. TC 131 reverses the freeze directly: per Doc 6209, 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." Nothing changed hands — the liability that justified the hold turned out not to require taking this money, and the refund flows once TC 131 posts, assuming no separate freeze is also sitting on the account.

TC 824 ends the freeze a different way. Doc 6209 describes it as a transaction that "transfers overpayment credits frozen by TC 130 Account Refund Freeze" and, in doing so, "releases TC 130 Account Refund Freeze." Here the freeze existed for exactly the reason it looked like it did: the credit gets moved to pay the liability on the other account instead of coming back to the taxpayer. Seeing TC 824 instead of TC 131 next to a reversed TC 130 is the transcript telling the client the freeze worked as designed, not that it lifted for free.

The practitioner's actual next step

Identify the indicator before promising the client anything about timing. A 99 sends the research toward the Treasury Offset Program and the Debtor Master File, which IRM 21.5.6.4.43 routes to IRM 21.4.6, Refund Offset Research, Reversals, and Injured Spouse Processing — a call to Treasury's offset line, not the IRS, resolves the underlying debt question there. If the return behind that 99 was filed jointly and the debt belongs to only one spouse, don't stop at identifying whose debt it is — Injured Spouse relief (Form 8379) is the taxpayer protection IRM 21.4.6 is titled around — specifically IRM 21.4.6.5.4, Form 8379 Injured Spouse Allocation — and it can return the non-liable spouse's share of the refund even though the freeze reached the whole joint account. Anything else points back to an IRS campus and an internal liability that needs its own research — a transcript pull (CC ENMOD for the entity-level freeze indicator, CC IMFOLE or CC BMFOLE to see the module the TC 130 is actually pointing to) before advising the client of a balance due elsewhere.

If the closing code lands in the 03, 12, or 24–32 range, check the connected BMF account for a TC 530 write-off before treating the IMF freeze as a live, disputable liability — the underlying debt may already be formally uncollectible even though it is still holding this refund.

Once TC 131 or TC 824 actually posts, read which one it is before telling the client what happened to the money — a 131 means the refund is coming, an 824 means it already went somewhere else. Confirming that distinction from the transcript takes a minute and avoids promising a refund that already moved.

What TC 130 gets confused with

TC 130 and TC 470 both read, at a glance, as "something is freezing this account," and both turn out to depend heavily on a closing code or indicator most transcript tools print without explaining. They are not the same freeze. TC 470 pauses collection and notices on a pending claim the IRS is actively working; TC 130 pauses refunds because of a liability the IRS says already exists somewhere else on record. The TC 470 lesson — read the closing code before assuming what a freeze means — applies here too, but the thing the code is telling you is different in kind: TC 470's codes describe what is frozen and why it might suspend a statute; TC 130's indicator describes whose debt this actually is and where to research it.

TC 130 is also easy to mistake for a rejected offer once a practitioner knows to check OIC status. It usually isn't one. The OIC-hold variant of TC 130 posts on an accepted offer being monitored — the taxpayer got the deal, and the freeze is the IRS holding refunds under that deal's own terms, not evidence anything went wrong. TC 481 records an actual rejection, with its own statute consequences and appeal rights that a TC 130 OIC hold never triggers. Confirm which one is actually on the transcript — an accepted offer under monitoring and a rejected offer restarting two statute clocks call for entirely different advice.