TC 170: Estimated Tax Penalty Assessed

What the code actually does

TC 170 posts in two different ways under one code, and IRM 20.1.3 spells out both directly. IRM 20.1.3.2.1 defines it as "Manual assessment of an ES penalty by IRS, or self-assessment using Form 2210, Underpayment of Estimated Tax by Individuals, Estates and Trusts, Form 2210-F, Underpayment of Estimated Tax by Farmers and Fishermen, or Form 2220, Underpayment of Estimated Tax by Corporations, as applicable." ES here means Estimated Tax — the addition to tax IRC §6654 imposes on individuals, estates, and trusts, and IRC §6655 imposes on corporations, for failing to pay enough tax throughout the year through withholding and quarterly estimates. Most TC 170s are the first kind: a taxpayer who owed the penalty computed it on the return, and it posted with no separate IRS action. IRM 20.1.3.2.1 notes the tell: "Self-assessed ES penalty will have the same DLN as the TC 150 return" — the original return’s own document locator number, not a separately worked adjustment.

Document 6209’s own transaction-code table confirms the same dual definition independently: "Computer generated self-assessment from TC 150 or manually assessed. ES penalty for failure to make adequate ES payments. Applicable to Form 990C, 1040, 1041, 990T, 990PF and 1120, except on Adjustment or Revenue Receipt input." That broader list of forms — trusts, private foundations, exempt organizations — confirms this is not an individual-only code; wherever a filer computes its own ES penalty on the return itself, or the IRS assesses one by hand, TC 170 is what records it.

Self-assessed vs. IRS-assessed — why the distinction controls the fix

The first move on seeing a TC 170 is figuring out which of the two it actually is, because the answer decides which abatement grounds are even available. IRM 20.1.3.2.2’s penalty reason code (PRC) table — the codes an employee must enter to process a manual abatement — treats a self-assessed and an IRS-assessed 170 differently. PRC 016 exists specifically for cases where "the original penalty was self-assessed (TC 170 posted with return), and the penalty is being adjusted because the taxpayer or IRS is providing a corrected computation." PRC 010 covers the same self-assessed origin adjusted for a superseding return. Neither exists for an IRS-assessed penalty adjusted the same way — that path runs through PRC 013 instead, reserved for a penalty where "the original penalty was IRS assessed (TC 176)."

The distinction is not paperwork trivia. A self-assessed 170 usually means the taxpayer’s own Form 2210 or Form 2220 computation is the first thing to re-check — a transposed payment date or a missed withholding figure on the form itself is the most common source of an overstated penalty, and it is the taxpayer’s own arithmetic to fix, not an IRS assessment to contest. A manually assessed 170, by contrast, means an IRS employee — not Master File — built the number, which makes it worth pulling the underlying computation and verifying it against the account transcript before assuming it is correct.

The narrow grounds that can actually reduce it

The single most important fact about this penalty is what does not reduce it. IRM 20.1.3.2.7.1 states it without qualification: "The penalty for underpayment of estimated tax cannot be removed or waived for reasonable cause alone." That rules out the argument that works for most other penalties — a client’s illness, a preparer’s error, a documented hardship — none of it, standing alone, gets a TC 170 abated. The relief that does exist is narrower and statute-specific. The rule worth being able to say out loud in a client meeting: no reasonable cause, no First-Time Abate — only the casualty-and-disaster equity waiver and the retired-after-62-or-disabled gate actually reach this penalty.

For individuals, IRC §6654(e)(3)(A) allows a waiver where "by reason of casualty, disaster, or other unusual circumstances the imposition of such addition to tax would be against equity and good conscience" — and the IRM is explicit that this standard is "not equivalent to reasonable cause": reliance on a competent tax advisor’s advice, which supports reasonable-cause relief from other penalties, does not by itself support this waiver. A second, narrower ground under IRC §6654(e)(3)(B) applies only where the taxpayer retired after turning 62, or became disabled, in the underpayment year or the year before it, and the underpayment was itself due to reasonable cause — the one place reasonable cause re-enters the analysis, and only as a gate condition, not a standalone defense. For corporations, the IRM is blunter still: the ES penalty "generally does not qualify for a waiver, with very specific exceptions" — the last one applied in 2001, for corporations affected by the September 11 attacks.

A waiver request must be in writing and signed by the taxpayer to be considered — an oral request is not enough, per the IRM’s own instruction for evaluating these claims.

What TC 170 gets confused with

TC 170 and TC 176 both assess the same ES penalty and can look interchangeable on a transcript, but Document 6209 draws the line cleanly: TC 170 is a self-assessment or manual assessment, while TC 176 is strictly a "Computer-generated assessment ... for failure to make adequate ES payments" with no manual doc code behind it at all. The practical difference is what a later correction requires — an account carrying only a self-assessed TC 170 is not "restricted," so the penalty will still recompute automatically when payments or withholding change; an account where an employee has manually posted a TC 170 or TC 171 becomes restricted, and every later change has to be worked by hand.

It is also worth distinguishing this penalty from the structurally similar Failure to File penalty cluster. TC 160 is the manually computed Delinquency Penalty assessment — the FTF counterpart to TC 170 — and the two codes look like siblings on a transcript. They are not siblings in what relief reaches them: IRM 20.1.1.3.3.2.1 lists First-Time Abate relief as available for the "Failure to File (FTF) penalty ... Failure to Pay (FTP) penalty ... and Failure to Deposit (FTD) penalty" — a list the ES penalty is not on. Treating a TC 170 like a TC 160 for abatement purposes, and offering reasonable cause or First-Time Abate as the argument, is the single most common way this penalty gets mishandled.

The practitioner’s actual next step

Before arguing relief, check whether the number is even right. Because the penalty is computed from actual payments and withholding, IRM 20.1.3 confirms it "must be recomputed if there is a change to withheld income tax or to payments or to credits available before the due date for payment" — a corrected W-2, a late-posting estimated payment, or a payment applied to the wrong quarter can overstate the assessed amount with no waiver argument necessary at all.

If the computation is correct, test it against the two narrow waivers above before looking anywhere else — casualty/disaster/unusual-circumstances equity relief under §6654(e)(3)(A), or the retirement/disability gate under §6654(e)(3)(B). If neither fits and the balance is real, the ES penalty does not disappear just because the client cannot pay it: recompute the CSED from the actual assessment date rather than assume it tracks the underlying return, and if the account genuinely cannot pay, evaluate Currently Not Collectible status or an Offer in Compromise for the liability as a whole rather than relitigating a penalty that reasonable cause cannot reach.