TC 161: Abatement of Failure to File Penalty

What the code actually does

TC 161 is the credit transaction that abates a Failure to File penalty already assessed, in whole or in part. Doc 6209 §8A (the IRS’s own internal Master File Codes reference, a free public PDF on IRS.gov) titles it “Abatement of Failure to File” and states verbatim: “Abates previously posted Failure to File (FTF) Penalty (TC 160/TC 166) assessment in whole or in part.” Its remarks add: “Penalty is not recomputed by computer.” That last sentence is the important one — TC 161 records a discretionary, human-entered figure, not the system correcting its own math. That is a genuinely different mechanism from TC 167, covered below.

Notice exactly what TC 161 reaches: “previously posted Failure to File (FTF) Penalty (TC 160/TC 166)” — both the manually computed assessment (TC 160) and the computer-generated one. One abatement code answers either kind of assessment. The reverse is not true: TC 167 cannot touch a TC 160 at all. TC 161 can abate either a TC 160 or a TC 166.

Four common roads to the same code

A bare TC 161 on a transcript does not say why the penalty came off, and the real reason changes the conversation with the client considerably. Three of the four common reasons are relief determinations: First-Time Abate, reasonable cause, and a manual Automatic Exemption from Penalty (AEP) grant, which the IRS enters by hand when its own error kept a qualifying return from getting AEP at posting. The fourth is an error correction: the penalty should never have posted. IRM 20.1.2.2.1 gives the concrete example: “If IRS assessed a late filing penalty in error on a timely filed return... abate the penalty with Transaction Code (TC) 161 and Penalty Reason Code (PRC) 027, timely mailed/timely filed.” A PRC 027 abatement means the return was never actually late — nothing about the client’s compliance history or the strength of a reasonable-cause narrative is at issue, because there was never a valid penalty to excuse in the first place.

Confirming which of these actually happened belongs in the file. A First-Time Abate (FTA) uses up relief the client may need again on a future year, and when the history qualifies the IRS applies it before reasonable cause (IRM 20.1.1.3.3.2.1 ¶(12)); a reasonable-cause abatement does not, and the module still shows as compliant (the module is the IRS’s record for one tax period within the account). A PRC 027 correction does not use up that relief — it was never a real penalty, so it costs nothing on the compliance-history ledger. A manual AEP grant shows as PRC 043 plus a TC 971 with action code 996 (IRM Procedural Update SBSE-20-0626-0643, paragraph (4) of its added IRM 20.1.1.3.3.2.6). Like FTA, it spends the clean history: once action code 996 posts, the IRS computer will not consider that return type for AEP until three more years of timely filing and payment are on record (IRM Procedural Update sbse-20-0626-0643 ¶(17)).

Sequencing the relief request

When the penalty genuinely is valid and a relief request is the actual path, sequence matters. 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 states the compliance-history test in plain terms: the taxpayer qualifies if “the same return type, as the original return, was timely filed for the prior three years,” with no penalty in that lookback window other than an estimated tax penalty, unless the IRS abated it for reasonable cause or IRS error. The IRM wording asks whether the taxpayer “has filed” the same return for the three preceding years (IRM 20.1.1.3.3.2.1 ¶(4)), but IRS.gov requires that return to be “timely filed” for the prior three years and ¶(4) also disqualifies a history with any unreversed penalty other than an estimated tax penalty, so do not assume a history of late filing qualifies for First-Time Abate; on a business account, a Form 1120 or 1120-S that the taxpayer filed late without a penalty also disqualifies the taxpayer (¶(6)). FTA needs no documentation of hardship or cause, so it is the faster, cheaper request for a return due before January 1, 2027. For a return due on or after that date, FTA is no longer available and AEP replaces it. And for 2025 tax-year returns, 2026 quarterly returns, and later periods on the forms it lists, IRS.gov describes AEP as a companion program that applies a three-year compliance test automatically and can suppress the penalty before the IRS assesses it. A posted TC 166 failure-to-file penalty on a 2025 tax-year or 2026 quarterly return may mean the return did not receive AEP consideration or failed the AEP history test, and First-Time Abate remains available only for those returns due before January 1, 2027 and only if the First-Time Abate history test is met. AEP has 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, whose ¶1 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 the procedural update by number: the published IRM 20.1.1 has no 20.1.1.3.3.2.5 or 20.1.1.3.3.2.6 subsection as of October 2026.

Reasonable cause is the fallback when the compliance history does not support FTA. IRM 20.1.1.3.2 sets the 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.” That is a facts-and-circumstances showing, not a checklist, and it takes real documentation to support — worth reserving for the cases where FTA genuinely is not available.

What people mistake TC 161 for

TC 161 and TC 167 are the pair most worth separating cleanly, because 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; per Doc 6209, the penalty it abates “is not recomputed by computer.” TC 167 is the opposite: a “Generated Transaction” that reverses only a TC 166, triggered, in Doc 6209’s words, “when a change occurs in return due date or tax due at due date.” A TC 167 on the account does not mean the client received relief, and it does not mean a TC 161 request is unnecessary if the penalty (or part of it) is still standing.

People also confuse TC 161 with TC 162, since both can follow a TC 160 or TC 161 posting in short order. They are not the same kind of code: TC 161 moves a dollar amount off the account. TC 162 moves nothing — it only removes the restriction that a manual entry leaves behind, so the system can compute the penalty normally again going forward.

The practitioner’s actual next step

Run the compliance-history check before drafting anything — The Federal Tax Desk’s Penalty Abatement Analyzer checks First-Time Abate and reasonable-cause eligibility together, accounts for the ongoing AEP transition, and sequences which one to request first, rather than guessing. Confirm first that the penalty is right, because a wrong penalty comes off without spending the waiver. When the history qualifies, the IRS applies First-Time Abate first, even if the request argues reasonable cause (IRM 20.1.1.3.3.2.1 ¶(12)).

If FTA is off the table, build the reasonable-cause narrative around ordinary business care and prudence — what specifically prevented timely filing, and what the client did once the obstacle was known — rather than a general hardship story.

If the transcript shows a PRC 027-style correction rather than a relief grant, say so plainly to the client: the account is clean because the penalty was wrong, not because a relief benefit was spent. That distinction protects a future year that might actually need FTA.