TC 167: Systemic Abatement of Failure to File Penalty

What the code actually does

TC 167 is a credit transaction with one narrow job. Doc 6209 §8A (the IRS’s own internal Master File Codes reference, a free public PDF on IRS.gov) titles it “Abate Delinquency Penalty” and states verbatim: “Abates a previously assessed TC 166 when change occurs in return due date or tax due at due date.” Two words matter most in that sentence: it abates a TC 166 — the computer-generated Failure to File penalty — and nothing else. It has no documented power to abate a TC 160, the manually computed version of the identical penalty.

Doc 6209 marks TC 167 a “Generated Transaction,” the same designation it gives TC 166 itself. That pairing is deliberate: the system assessed the penalty automatically, and the system reverses it automatically, using the same due-date and tax-due inputs on both ends.

Why this is not a relief determination

This is the point most worth getting right before advising a client. TC 161 — the manual abatement code — carries its own explicit statement in Doc 6209 that the penalty it abates “is not recomputed by computer.” TC 167 is the mirror image of that: it exists precisely because the computer did recompute the penalty, using its own due-date and tax-due logic, with no caseworker weighing reasonable cause or checking a three-year compliance history. IRM 20.1.2.2.3.1.1 describes the real-world version of this trigger: when an approved extension is found after a late-filing penalty already posted, the system recomputes the “related late filing penalties” rather than requiring a manual abatement request. A TC 167 following that kind of correction is the recomputation, not a grant of relief.

What actually triggers it

Per Doc 6209, exactly two events fire TC 167: a change in the return’s due date, or a change in the tax due as of that due date. In practice that most often means an extension request surfaces after the original penalty already posted (pushing the effective due date later and shrinking or eliminating the penalty period), or a later adjustment changes the amount of tax that was actually due at the original due date (which is the number the Failure to File penalty is computed against). Either way, the recalculation runs on facts about the return itself — not on any argument about why the taxpayer missed the deadline.

What it means for the abatement conversation

A TC 167 on the transcript answers exactly one question: did the due date or the tax-due figure change? It does not answer whether the client has a reasonable-cause or First-Time Abate claim for whatever penalty remains. IRM 20.1.1.3.3.2.1, First-Time Abate, reaches the “Failure to File (FTF) penalty under IRC 6651(a)(1), IRC 6698(a)(1), or IRC 6699(a)(1)” by name, and IRS.gov’s own summary confirms the compliance-history test: “the same return type, as the original return, was timely filed for the prior three years,” with no unabated penalty other than an estimated tax penalty in that window. IRM 20.1.1.3.2, Reasonable Cause, sets the fallback standard: relief “is generally granted when the taxpayer exercised ordinary business care and prudence in determining their tax obligations but was nevertheless unable to comply with those obligations.” Neither test is satisfied, or even addressed, by a TC 167 posting — and for a current-year return, note also that IRS.gov describes a newer companion program, Automatic Exemption from Penalty (AEP), which for tax year 2025 and after can suppress this same penalty automatically before assessment, governed by its own authority — IRM 20.1.1.3.3.2.5, Automatic Exemption from Penalty Administrative Relief, added by IRM Procedural Update sbse-20-0626-0643 on June 17, 2026, which states that AEP is administrative relief granted at original return processing and officially replaces First Time Abate for all eligible original returns due January 1, 2027 and after. Cite that procedural update by number rather than the published IRM: as of August 25, 2026 the consolidated IRM 20.1.1 on IRS.gov has not yet absorbed it — its 20.1.1.3.3.2 series still runs .1 through .4 with no .5 — so a practitioner who looks the subsection up today will not find it.

The practitioner’s actual next step

Confirm what TC 167 actually corrected before telling the client the penalty issue is closed. Pull the account activity around the TC 167 date: a nearby TC 460 means an approved extension was found after the penalty already posted, per IRM 20.1.2.2.3.1.1; no TC 460 nearby points to a tax-due adjustment instead. That context determines whether any penalty balance still remains.

If a Failure to File penalty balance remains after the TC 167 correction, treat it as an open relief question, not a resolved one — run The Federal Tax Desk’s Penalty Abatement Analyzer to check First-Time Abate and reasonable-cause eligibility on whatever is left.

Do not report a TC 167 to a client as evidence of a favorable determination on the merits. It is accurate to say the penalty amount changed; it is not accurate to say the IRS agreed the taxpayer had a good reason for filing late.

What TC 167 gets confused with

TC 167 and TC 161 are the pair most worth separating cleanly, since both are credit transactions that reduce or remove the identical Failure to File penalty and only one of them means a relief determination happened. TC 161 is manual and discretionary — it is the code a First-Time Abate or reasonable-cause request actually produces. TC 167 is systemic and mechanical, tied only to a due-date or tax-due change, with no reasonable-cause or FTA analysis behind it. Seeing either code on a transcript is not, by itself, proof of which situation actually occurred; confirm which one posted before advising the client on what happened.

TC 167 also gets confused with TC 162, since both relate to the system correcting a Failure to File penalty rather than a caseworker granting relief. They are not equivalent: TC 167 is a real credit transaction with a dollar amount attached, reversing a TC 166 assessment outright. TC 162 carries no dollar figure at all — it only removes a restriction so the system can compute correctly, it does not perform the abatement itself.