TC 502: Correction of TC 500 Processed in Error
By Forrest Baumhover, CFP®, EA · Last verified September 9, 2026
TC 502 restores the original collection statute date after a military deferment posted in error — but it releases only the account hold, not the interest and penalty freezes riding alongside it, which is the detail a practitioner needs before telling a client the correction is complete.
What the code actually does
IRS Document 6209, Section 8A titles TC 502 "Correction of TC 500 Processed in Error" and describes exactly what it undoes: it "corrects an erroneously posted military deferment and restores the original Collection Statute Expiration Date."
That word "restores" is the whole point of the code, and it is the opposite direction from what TC 500 itself does. TC 500 suspends the collection statute for a servicemember under one of two regimes — military deferment or combat zone service — and pushes the CSED out. TC 502 exists for the case where that suspension should never have gone on the account in the first place, and it puts the original date back rather than setting a new one.
The release is only partial — interest and penalty freezes stay
This is the detail most worth flagging, because Doc 6209 states it as a limitation rather than as background: TC 502 "releases Hold established by TC 500," but the same sentence continues, "TC 502 does not release the interest and/or penalty freezes," and requires that "a TC 290 must be input with the appropriate TC" to finish the job.
A practitioner reading TC 502 as a complete undo of TC 500 will miss this. The account-level hold that TC 500 put in place — tied to a debit balance on the module — does come off. What does not automatically clear are the separate freezes on interest and penalty computation that TC 500 also triggers. Those need their own transaction, and Doc 6209 is explicit that it takes a manually input TC 290 carrying the appropriate transaction code to release them. A module can show TC 502 and still be carrying an interest or penalty freeze from the original, erroneous TC 500 until that second step happens.
A related mechanical detail: the code that disappears
Doc 6209 records something easy to miss on a raw transcript printout: "TC 500 changed to 503 when posting TC 502." Once the correction posts, the original TC 500 entry itself gets relabeled internally to TC 503 rather than staying visible as a 500 that was simply reversed nearby. TC 503 has no independent meaning of its own and no separate governing rule beyond this relabeling — it is a bookkeeping artifact of how the correction is recorded, not a code a practitioner needs to research on its own.
The practical effect is that a practitioner reviewing a corrected module should not expect to find the original TC 500 sitting unchanged next to a TC 502; the system's own internal relabeling can make the "before" picture harder to reconstruct from the posted transcript alone, and pulling the entry through IDRS — the IRS’s Integrated Data Retrieval System, the internal database the transcript is only a printout of — may be needed to see the original entry as it was actually input.
What TC 502 gets confused with
It gets confused with the waiver code that follows a legitimate deferment. TC 500's own page records that "a new expiration date is input with TC 550" when the suspension is genuine — TC 550 sets a new, later CSED. TC 502 does the opposite: it discards the suspension and puts the original date back, because the deferment itself should not have been recognized. Seeing one instead of the other on a module tells a practitioner whether the case behind it was a valid military deferment or a processing error.
It also gets confused with a complete reversal, for the reason described above — the account hold releases, but the interest and penalty freezes are a separate, manually triggered step. A module that shows only TC 502 with no companion TC 290 may still be carrying stale freeze conditions from the original erroneous posting.
Finally, do not read TC 502 as evidence the taxpayer did anything wrong. Doc 6209 describes it as correcting an "erroneously posted" deferment — the error is in how the deferment was recorded on the account, not necessarily in anything the servicemember represented.
The practitioner's actual next step
Confirm the restored CSED against the original assessment date rather than assuming TC 502 alone settles the statute question — recompute it with the collection statute calculator.
Check specifically for a companion TC 290 releasing the interest and penalty freezes; its absence means those freezes may still be sitting on the module after the CSED itself has been fixed.
Do not expect to find an untouched TC 500 on the transcript once TC 502 has posted — the original entry is systemically relabeled to TC 503, which has no separate meaning of its own.
Where the client is an actual servicemember with a genuine deferment, distinguish that fact pattern from this one before advising — TC 550's extended date, not TC 502's restored one, is what should be on that account.