CP30: What It Means and How to Respond

What the notice actually says

CP30 tells the taxpayer the IRS charged a penalty "because you didn't make estimated tax payments or didn't make your payments on time" — the underpayment-of-estimated-tax penalty under IRC §6654. Per IRM 21.3.1.6.20, the IRS gives this notice a more precise internal title: "CP 30 - Estimated Tax Penalty Notice - Reduced Refund," because it most often generates on a return that was otherwise due a refund, with the penalty absorbing part or all of it.

CP30 posts specifically when the penalty the IRS computes is larger than the amount the taxpayer reported on their own return (via Form 2210), and — with one narrow exception — no other IRS settlement notice is going out for that same return. Per IRM 3.14.1.6.18.2, the only settlement notice CP30 can share a return with is a CP51, Non-Compute; anything else disqualifies the account from a standalone CP30 and routes it through a different combined-notice process instead.

What actually triggered it

The trigger is a gap between the required annual payment — generally the smaller of 90% of the current year's tax or 100% of the prior year's tax (110% if the prior year's adjusted gross income was over $150,000) — and what was actually paid on time through withholding and quarterly estimates. On the transcript, this shows as a TC 176, the penalty Master File (the IRS’s central account-processing system) assesses automatically, or occasionally a TC 170, assessed by IRS staff or self-assessed on Form 2210 or 2220.

TC 176 is worth understanding specifically, because it is the more common of the two and it behaves differently from most other assessments: Master File recomputes it automatically whenever the inputs change. The governing IRM language is direct on this — "the penalty 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. In most instances the penalty will automatically recompute." In practice, this means a CP30 caused by an understated withholding figure or a missed estimated-payment credit often does not need a Form 2210 relief argument at all — correcting the underlying data (an amended return reporting the actual withholding, or a payment properly credited to the right period) can resolve the gap on its own, with the systemic recompute handling the rest.

Response deadline and what happens if you miss it

If the notice shows a balance due rather than a reduced refund, the letter states a payment due date and interest continues to accrue on any amount unpaid after it. The notice states no separate appeal deadline — the practical clock is simply how quickly the taxpayer files a correction, if one is due, before interest adds up further. That absence of a fixed response window is itself worth noting to a client used to CDP or Tax Court deadlines measured in a specific number of days — CP30 does not work that way, and treating it as though it carried a 30- or 90-day clock invents urgency the notice itself does not state.

If you disagree with the penalty and do nothing, the assessment stands as posted and, where applicable, reduces your refund exactly as shown, permanently, with no automatic later review triggered on its own. A correction requires actually filing an amended Form 2210 or contacting the IRS directly with the correct figures.

What to do next

First-Time Abate does not reach this penalty at all — IRC §6654 is absent from the IRM's list of penalties eligible for that relief, unlike the failure-to-file and failure-to-pay penalties. Ordinary reasonable cause is unavailable too; per IRM 20.1.3.2.7.1, "the penalty for underpayment of estimated tax cannot be removed or waived for reasonable cause alone."

The relief that does exist runs entirely through Form 2210 and its statutory exceptions: no tax owed for a full 12-month prior year, total tax under $1,000, a casualty/disaster/other unusual circumstance, retirement after 62 or disability within the last two years combined with reasonable cause for that specific waiver, or — often the highest-value fix for a business owner or investor with lumpy income — recalculating the penalty on the annualized-income method (Schedule AI) instead of assuming income arrived evenly across the year.

Whichever ground applies, a successful correction posts to the transcript as a TC 171 — Document 6209 describes it as abating "previously posted 170 or 176 Estimated Tax Penalty in whole or in part," regardless of which of the two assessment codes generated the original charge. A TC 171 by itself does not say which Form 2210 exception (or which data correction) actually produced the reduction — the account's own penalty reason code behind it does — so a practitioner confirming relief actually worked should pull the full explanation rather than treat the TC 171's appearance alone as proof of which argument succeeded.

What people mistake CP30 for

CP30 is easy to conflate with its own reversal pair, CP30A: CP30 tells you the IRS increased the penalty above what you reported, while CP30A tells you the IRS decreased or removed a penalty you reported — opposite directions on the same account. It is also worth separating from CP24, which restates an estimated-payment recalculation that produced a straightforward refund with no penalty attached at all.

It's also easy to assume this is the same kind of penalty TC 160/161-family notices describe — it is not. Those codes cover the failure-to-file penalty under a different statute, with different relief rules (including First-Time Abate, which does not apply here). Document 6209 makes the contrast explicit at the transaction-code level: TC 166, the failure-to-file penalty's own computer-generated assessment, is defined as a "Computer generated assessment of Failure to File (FTF) Penalty on returns posted after the due date without reasonable cause" — the phrase "without reasonable cause" is baked into the code's own definition, which is exactly the relief door TC 176's ES-penalty assessment does not have. Two codes that look structurally identical on a transcript — both generated, both silent, both fixed by a corrected input rather than a filed argument in the ordinary case — sit on top of two penalty regimes with almost nothing in common once relief becomes the question.

Common Questions