TC 500: Military Deferment and Combat Zone

What the code actually does

TC 500 stops the collection clock. IRM 5.1.19.3 lists it in the table of case actions that affect a collection statute expiration date, flatly, as "Military Deferment (suspends CSED)." IRS Document 6209, Section 8A adds the mechanics: it "suspends Collections Statute Expiration Date," a "new expiration date is input with TC 550," and a hold is established while the module balance is a debit.

It is one of a small number of transactions that genuinely move a statute date, which puts it in a different class from most of what appears on a transcript. Where it is present, no collection statute calculation is right until it has been accounted for.

Two regimes, and the closing code decides

The first is military deferment proper. IRM 5.1.19.3.9 grounds it in the Servicemembers Civil Relief Act: collection "may be deferred up to 180 days if ability to pay the tax is materially affected because of that person’s military service," and — the sentence that matters for the statute — "the CSED is suspended during the taxpayer’s military service and for an additional 270 days afterward." The IRM states that "the Transaction Code 500 with Closing Code 51 identifies a military deferment."

The second is combat zone or contingency operation, at IRM 5.1.19.3.8, and it works differently. The postponement runs while the taxpayer serves and "for any period of continuous qualified hospitalization from such service... plus 180 days after the last day of service in the area of operation or period of hospitalization," extended further by the days of the filing season spent in the zone, up to 105 days. Different trigger, different arithmetic, same transaction code.

The two are not merely variants. A deferment turns on ability to pay being materially affected; a combat zone posting turns on where the taxpayer was. Which one applies changes both the length of the suspension and what has to be shown to support it.

The combat zone regime also does more than suspend a statute. IRM 5.1.19.3.8 records that while the combat indicator is set, “the taxpayer is still serving in a combat zone and collecting or assessing tax is prohibited” outright — a genuine bar on enforcement rather than a pause in a clock. Where a client wishes to pay or to have a return assessed regardless, the IRM permits it and instructs that they be told the statutes will continue to be suspended anyway.

Document 6209 undercounts the closing codes

Doc 6209’s entry records "Valid CC 50 or 51," and a practitioner relying on it will not recognise most of the postings they actually encounter. The live IRM documents four more. IRM 5.1.19.3.8 sets them out: "Closing Code 52 for the Desert Storm Combat Zone, Closing Code 54 for Bosnia/Former Yugoslavia or Allied Force, Closing Code 56 for Afghanistan or Iraq/Enduring Freedom, or closing code 58 for Combat Zone Hospitalization."

Where the two sources disagree, the IRM is the current one and Doc 6209’s list is the stale one. This is worth knowing generally, not just for this code: Document 6209 is an excellent definitional source and a poor currency source, and a closing code absent from it is not thereby invalid.

What TC 500 gets confused with

It gets confused with a hardship status. It is not one. TC 530 reports an account currently not collectible and does not suspend the statute at all; this code suspends the statute and rests on service rather than on inability to pay. A client who is both a servicemember and in hardship may carry both, and they do entirely different work.

It gets confused with the waiver code that often follows it. Doc 6209 records that a "new expiration date is input with TC 550," so the recalculated statute date arrives as a separate transaction. Reading the TC 500 alone and stopping there misses where the new date actually landed.

And its reversals are not equivalent. The correction code for an erroneously posted TC 500 restores the original statute date as though the suspension never happened, while the waiver code sets a new one — so a reversal on the module has to be identified specifically before any date is quoted. Where a litigation or bankruptcy freeze overlaps the same period, IRM 5.1.19.3 works a detailed example showing that overlapping suspensions are counted only once, which is the other half of getting this arithmetic right.

The practitioner’s actual next step

Read the closing code first, because it decides which of the two regimes — and which arithmetic — applies.

Do not rely on Document 6209 for the valid closing-code set; it lists two of six.

Find the transaction that carries the recalculated statute date rather than computing it from the suspension alone.

Check for overlapping suspensions on the same period and count the overlap once, as the IRM’s own worked example does.

Recompute the client’s collection statute end to end with the collection statute calculator rather than adjusting a previously quoted date.

Read the postings in sequence with the IRS Transcript Decoder, because a suspension and its reversal only mean anything as a pair.