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 (the IRS’s reference guide to its data-processing codes) describes when it fires: it is the "computer generated assessment of Failure to File (FTF) 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, charged for no more than five months (IRM 20.1.2.3.7.1), 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 a useful thing to tell a client looking at this code. A systemic penalty is not a refusal of relief, because the taxpayer made no request and the IRS considered no reasonable-cause claim. 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.

The IRS computes it 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 (the record for one tax type and period) come off before the IRS applies the percentage.

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 IRS applies the percentage to a number near zero. A client can be badly late and owe no penalty for it, though IRC 6511(b)(2)(A) can still bar the refund.

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 an income tax return filed more than 60 days late (counting any extension), that floor is the lesser of $525 or 100 percent of the tax on returns required to be filed in 2026 (Rev. Proc. 2024-40, sec. 2.53), and can exceed the percentage calculation entirely.

The five-month cap is the other point to confirm (IRM 20.1.2.3.7.1). The percentage stops accruing after five months (IRM 20.1.2.3.7.1), 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 people mistake TC 166 for

People confuse it 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, people confuse it 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.

What to do next

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 under IRC §6651(a) for an income tax return filed more than 60 days late (counting any extension) is the operative figure instead of the percentage.

Check the client’s prior three years before building a reasonable-cause file. That history decides First-Time Abate for tax years before 2025 and for 2025 quarterly returns, Automatic Exemption from Penalty (AEP) at processing for a 2025 tax-year return or a 2026 quarterly return due before January 1, 2027 (with First-Time Abate as the fallback if AEP did not consider it and the history qualifies), and AEP rather than First-Time Abate for returns due on or after January 1, 2027 of the forms IRS.gov lists, with AEP in every case requiring the taxpayer to file within three years of the original due date.

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