TC 160: Manually Computed Failure to File Penalty

What the code actually does

TC 160 records a Failure to File penalty that a human — specifically, per IRS Document 6209, an employee in Audit or Collection — computed and entered by hand, rather than the version of the same penalty the Master File (the IRS’s central account-processing system) computer assesses automatically. Doc 6209 §8A (the IRS’s own internal Master File Codes reference, a free public PDF on IRS.gov) titles the code “Manually Computed Failure to File Penalty” and states plainly: “A Failure to File (FTF) Penalty manually computed by Audit or Collection. Penalty is not recomputed by computer.” The rule worth remembering: a TC 160 with no TC 161 posted after it means the penalty is still on the account — nothing has reduced it yet.

The systemic counterpart to TC 160 is TC 166 — not part of this cluster, worth knowing by name only so a transcript reads correctly. Doc 6209 defines TC 166 as a “[c]omputer generated assessment of Failure to File (FTF) Penalty on returns posted after the due date without reasonable cause,” assessed automatically whenever a return posts late with no exception recorded. TC 160 exists for the cases automation does not reach: a penalty an examiner or collection employee determined and input directly, on Doc Codes 47 or 54.

Why the manual origin actually matters

The distinction is not cosmetic. Because an employee enters TC 160 by hand, the module (the IRS’s record for one tax period within the account) stays restricted once it posts: the system will not recompute the penalty on its own, since a person typed in the figure. IRM 20.1.2.2.3.1.1 states this logic directly in a related context: “Manual penalty abatement should not be used in that case, since it will restrict the module from systemic penalty corrections.” That restriction is deliberate, not a defect — but it means a later event that should change the penalty (an extension found, an amended return, a corrected due date) will not fix itself. See TC 162 for the code that actually lifts it.

A TC 160 also tends to sit inside a different fact pattern than the routine “filed three months late” story a computer-generated penalty implies. Because Audit or Collection input it, look for an underlying exam adjustment, a secured delinquent return, or a case an employee actually worked — the number on a TC 160 was a person’s calculation, and a person’s calculation is the one worth checking against the return.

The abatement path — reasonable cause and First-Time Abate

A TC 160 assessment is not the end of the conversation. IRM 20.1.1.3.3.2.1, First-Time Abate, and IRM 20.1.1.3.2, Reasonable Cause, both reach it directly. First-Time Abate (FTA) covers the “Failure to File (FTF) penalty under IRC 6651(a)(1), IRC 6698(a)(1), or IRC 6699(a)(1)” by name — exactly the penalty TC 160 assesses — 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 requires no hardship story and no documentation — it is a compliance-history check, not a facts-and-circumstances showing — which is exactly why you check it first. For 2025 tax-year returns, 2026 quarterly returns, and later periods on the forms it lists, IRS.gov also describes a companion program, Automatic Exemption from Penalty (AEP), that applies a three-year compliance test automatically when the original return is processed, so the penalty is never assessed. A TC 160 comes from a manual exam or collection assessment, not from original return processing, which is where AEP acts, so AEP is unlikely to apply. Check FTA first for a return due before January 1, 2027. 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 subsection as of October 2026. Reasonable cause is the fallback when neither FTA nor AEP applies: IRM 20.1.1.3.2 states 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.”

Run both tests before advising the client either way — The Federal Tax Desk’s Penalty Abatement Analyzer checks First-Time Abate and reasonable-cause eligibility side by side and sequences which one to request first.

What people mistake TC 160 for

TC 160 and TC 161 are easy to conflate because they post on the same Failure to File penalty line — they are opposite entries, not variations on one theme. TC 160 is the debit that assesses the penalty; TC 161 is the credit that abates it, whether the abatement is FTA, reasonable cause, or a correction of an assessment that should never have posted. A transcript carrying a TC 160 with no later TC 161 means the penalty is still standing.

People also confuse TC 160 with its own systemic sibling TC 166, since both post the identical penalty under the identical relief standard and neither one changes what a practitioner should actually do about it. What changes is which abatement code answers it: TC 161 answers either one; TC 167 answers only TC 166 and is systemic: Doc 6209 ties it to a due-date or tax-due change, and IRM 20.1.1.3.3.2.2 shows the IRS also used it for the 2019–2020 systemic late-filing relief, so it records no caseworker's reasonable-cause or FTA analysis. Confirm which assessment code is actually on the transcript before assuming a TC 167 closed out relief the client has not actually received.

The practitioner’s actual next step

Confirm which code actually posted before quoting a strategy — a TC 160 (manual) and a TC 166 (systemic) carry the identical penalty under identical relief rules, but only TC 160 implies a person made a discretionary call worth reviewing against the facts, not just the math.

Check the three preceding years for unreversed penalties before promising First-Time Abate — a single earlier miss, other than an estimated tax penalty, can take FTA off the table entirely and leave reasonable cause as the remaining route after you rule out IRS error and statutory exceptions.

If a later event changes the numbers — an extension surfaces, an amended return posts, an audit adjustment lands — confirm TC 162 actually posted before assuming the penalty recalculated correctly on its own. A manually restricted module does not fix itself.