TC 166: Systemic Failure to File Penalty

What the code actually does

TC 166 is the failure-to-file penalty, assessed automatically. IRM 20.1.2.2.5 lists it plainly among the transactions that "reflect systemic assessment or abatement of the penalties" in the chapter: "TC 166/167—systemic assessment/abatement of the penalty for failure to file."

IRS Document 6209, Section 8A describes when it fires: it is the "computer generated assessment of Delinquency Penalty on returns posted after the due date without reasonable cause." The underlying penalty is the one at IRC §6651(a)(1) — five percent of the net tax due for each month or part of a month the return is late, capped at five months, and reduced by any failure-to-pay penalty running in the same month.

Nobody considered reasonable cause

Doc 6209’s phrase "without reasonable cause" describes the condition the system tests, not a determination anyone made. The computer has no facts about the client’s circumstances; it has a due date and a posting date.

That is the single most useful thing to tell a client looking at this code. A systemic penalty is not a refusal of relief, because no request was made and none was considered. It is the default outcome for a late return, and it is the starting point of a relief conversation rather than the end of one.

The relief paths are unaffected by the code’s automatic origin. First-Time Abate reaches the failure-to-file penalty under IRC 6651(a)(1) by name, and reasonable cause remains available on the facts. Working out which applies is what the Penalty Abatement Analyzer is for; the code itself tells a practitioner only that the penalty is there.

It is computed on tax less prepayments

Doc 6209 states the base precisely: the "penalty is computed on the assessment tax less pre payments." Withholding and estimated payments already on the module come off before the percentage is applied.

This explains an outcome that surprises clients and occasionally practitioners. A taxpayer who filed years late but was over-withheld throughout has little or no net tax due, and therefore little or no failure-to-file penalty — the percentage is being applied to a number near zero. A client can be badly late and owe nothing for it.

It also explains the reverse. A self-employed client with no withholding faces the penalty on the full liability, which is why the same lateness produces wildly different penalties for two clients. Where a minimum penalty applies to a return filed sixty days or more late, that floor is a separate rule and can exceed the percentage calculation entirely.

The five-month cap is the other thing clients get wrong, usually in their favour. The percentage stops accruing after five months, so a return three years late and a return six months late can carry the same failure-to-file penalty. What continues to grow in the meantime is the failure-to-pay penalty and the interest underneath both — which is why a client who has been quoted a large figure for a very old return is usually looking at interest rather than at this penalty.

What TC 166 gets confused with

It gets confused with TC 160, the manual assessment of the same penalty. The distinction is who put it on: a person, working a case, or the system, on a schedule. IRM 20.1.1.5.2 labels them exactly that way — "TC 160: Manually Assessed" and "TC 166: Systemically Generated Assessment."

Its two abatement codes are also confused with each other, and the difference runs the opposite way to what most people assume. The same IRM subsection labels them "TC 161: Manually Abated" and "TC 167: Systemically Generated Abatement." The axis is who removed the penalty, not who added it — which is why TC 161 can abate both a manual TC 160 and this systemic assessment, while TC 167 reaches only this one. A granted relief request therefore posts as the manual abatement even where the penalty it removes was assessed by the computer.

Finally, it gets confused with the failure-to-pay penalty. Filing late and paying late are two different penalties with two different code families, and a client can have either without the other. Where both run in the same month, the failure-to-file penalty is reduced by the failure-to-pay amount rather than the two simply stacking.

The practitioner’s actual next step

Read the code as an unexamined default, not as a decision, and open the relief question rather than closing it.

Check the penalty base against prepayments before quoting an exposure — the percentage may be applied to very little.

Consider whether the minimum penalty for a return filed sixty days or more late is the operative figure instead of the percentage.

Check the client’s prior three years for First-Time Abate eligibility before building a reasonable-cause file.

Expect a granted request to post as the manual abatement, and do not read the absence of the systemic abatement as a denial.