TC 521: Reversal of a Litigation Freeze

What the code actually does

TC 521 closes out a litigation freeze. IRS Document 6209, Section 8A describes it as recording "reversal of a previously posted TC 520," and IRM 25.3.8.5 explains the effect: resolving the freeze "allows the account to reenter the business stream." Collection resumes, notices resume, and the module comes back out of the litigation status it had been parked in.

The important thing is what it asserts. A TC 521 is the substantive closure — the case ran and finished. It is not a statement that the freeze was wrong.

Why it is not the same as the correction code

A litigation freeze can be lifted by two different transactions, and the IRM is unusually firm that practitioners and caseworkers must not treat them as one. IRM 25.3.8.2.2 instructs: "when finding an incorrect Closing Code correct it by inputting or requesting input of a TC 522 to remove the TC 520," and then adds, in the manual’s own capitals, "DO NOT INPUT TC 521."

The Tax Court and collection due process subsections put the same distinction positively. For a -W freeze, the action Appeals takes to close it "could be either posting: TC 522 to correct an erroneous input or a case withdrawn or meeting Appeals criteria for a disregarded or non-processable case, or TC 521 to close the litigation freeze."

So the code that posted is a record of what happened to the client’s case. A TC 521 means it was litigated and closed. The correction code means it was erroneous, withdrawn, or never properly before Appeals at all — three quite different histories, and ones a practitioner may be asked to explain years later.

The statute consequence, and a real trap

Where the original freeze carried one of the suspending closing codes, the period between the two postings is time the collection statute did not run. The reversal date is therefore half of a calculation, not a conclusion, and quoting a statute expiry without pairing the two dates will be wrong.

Doc 6209 records an older-account trap explicitly: "if TC 520 posted prior to cycle 8624, TC 550 must be input to extend the CSED." On genuinely old liabilities the extension does not follow automatically from the reversal; a separate waiver transaction has to carry the new date. Its absence on such a module is worth noticing rather than assuming the statute was extended, and the arithmetic is worth running through the collection statute calculator rather than adjusting a previously quoted figure.

There is also an access constraint that explains delay. IRM 25.3.8.5.1 records that in refund litigation "only the Refund Litigation Coordinator for the campus, which initially opened the case, may enter TC 521," and that one "must be input for each module that contains a TC 520 with cc 73." A single person at a single campus, module by module, is a realistic explanation for a freeze that has outlived its case.

What TC 521 gets confused with

It gets confused with a favourable outcome. It is not one. The freeze closed because the proceeding ended, and it ended whichever way it ended — the code is silent on who won. A client told their TC 521 means the matter went their way has been told something the transcript does not support.

It gets confused with the correction code, as above, and the consequence is the reverse error: reading a correction as a resolved case, or a resolved case as an administrative fix.

And it gets confused with the end of collection risk. Reentering the business stream is the beginning of collection activity, not the end of it — balance due notices resume, and the enforcement sequence that follows can run through to a levy notice. Where the original freeze arose from a collection due process request on an LT11 or Letter 1058 levy notice, the reversal is the point at which that protection stops, which is exactly when a client most needs to hear from their representative.

For a client who cannot pay what resumes, the reversal is also the moment the alternatives become live again — an instalment agreement, an offer, or hardship status. Running the numbers before the notices arrive, with the CNC eligibility calculator or its equivalent, is a better use of the interval than waiting to see what the Service does.

The practitioner’s actual next step

Confirm which reversal code posted before characterising the history to a client or to the Service.

Pair the two dates and compute the suspension rather than quoting a statute date from the original assessment.

On pre-1986 cycle freezes, look for the separate waiver transaction carrying the new statute date, and note its absence if it is not there.

Check that every module carrying the freeze was reversed, since the IRM requires module-by-module input for at least one closing code.

Expect collection to resume, and warn the client before the notices arrive rather than after — reading the freeze and its reversal as a pair with the IRS Transcript Decoder is how to date that.