CP23: What It Means and How to Respond

What the notice actually says

CP23 opens with a single sentence: "We corrected your return because we found a difference between the amount of estimated tax payments on your tax return and the amount we posted to your account." Unlike its sibling CP24, the correction here runs against the taxpayer — the recomputation produced a balance due, not a refund. The notice restates the corrected figures and tells the taxpayer to pay by the date shown or contact the IRS if they disagree. (For where CP23 sits among the other IRS notices, see the IRS Notice Library.)

IRS.gov's own CP23 page does not cite a statute, an IRM section, or a fixed number of days before collection action starts, and it never mentions a lien or a levy the way CP504 does. What it does say plainly is that the most common cause is "an incorrect entry on the estimated tax line of the tax return," and that a correction may need to go through Form 1040-X rather than a phone call if the discrepancy is on the taxpayer's side.

What actually triggered it

CP23 issues when the estimated tax credits claimed on the return and the credits the IRS actually posted to the account disagree, and the recomputation produces a balance due of $1.00 or more. IRM 21.3.1.6.16 defines this notice; the same discrepancy resolved into an overpayment of $1.00 or more is IRM 21.3.1.6.17's CP24, and a result landing within a dollar of even is IRM 21.3.1.6.18's CP25 — one determination, three notices, split entirely by arithmetic sign and size.

The ordinary causes are the same ones that produce a CP24 in the other direction: a payment the taxpayer claimed that never actually posted, a payment applied to the wrong tax year or the wrong taxpayer, or a prior-year overpayment the client elected to carry forward that the IRS's records show differently than the return does. A CP23 is the version of this mismatch a client is far more likely to actually read, because it comes with a bill attached.

Response deadline and what happens if you miss it

The Taxpayer Advocate Service states the window to contact the IRS if disagreeing is 60 days from the notice date. IRS.gov's own CP23 page does not repeat that number — it tells a disagreeing taxpayer to call by the date printed on the notice, and tells an agreeing taxpayer to "pay the amount owed by the date shown on your notice to avoid additional penalties and interest."

That last phrase is the operative one. CP23 is a balance-due notice, and missing the payment date does the same thing missing any balance-due notice's date does: penalties continue to accrue and interest keeps running until the account is paid in full. What CP23 does not do — and this is worth confirming before advising a client — is state that it carries lien or levy authority the way CP504 does. There is no §6331(d) levy warning language anywhere on the CP23 page. An unpaid CP23 balance simply ages into the ordinary collection notice stream toward CP501, CP503, and eventually CP504.

The practitioner's actual next step

Pull the account transcript before assuming the notice is wrong. CP23 is generated off the IRS's own posted-payment record, and the fastest way to find the actual mismatch — a payment posted to the wrong period, the wrong spouse, or simply missing — is to match every estimated payment the return claimed against the transcript line by line, identifying the transaction code behind any payment that moved somewhere unexpected. The Federal Tax Desk's IRS Transcript Analyzer does that reconciliation directly.

If the transcript confirms the IRS is right, the balance is due by the date on the notice — there is no math-error abatement right to fall back on here (see the differentiation section below), so the practical options are payment in full, an installment agreement sized against IRM 5.14, or Currently Not Collectible status if the client genuinely cannot pay. If the transcript shows the client's original return was correct and the IRS's posting is the error, a written response with supporting documentation is the more durable route — IRS.gov's own instruction for a disputed CP23 is simply to call the number on the notice by the date shown, but a phone call isn't memorialized, and a documented posting mismatch is worth the paper trail a call alone won't create.

What CP23 gets confused with — and why the distinction matters

The notice CP23 is genuinely confused with is CP24, and the confusion is warranted: fetched live, both IRS.gov pages open with the identical sentence, word for word. CP24 reports the same estimated-tax-credit discrepancy resolved into an overpayment; CP23 reports it resolved into a balance due. Same investigation, same underlying posting defect, opposite sign — and the practical asymmetry runs one direction. A CP23 client almost always calls, because they now owe money. A CP24 client rarely does, because a refund does not get audited by the person receiving it, even when the same defect produced both notices in different years or for different clients.

The distinction practitioners get backwards is the math-error abatement right. Because CP23 is assessed "in the same manner as in the case of a mathematical or clerical error," the natural assumption is that the taxpayer holds the same 60-day abatement-on-request right that ordinary math-error assessments carry under IRC §6213(b)(2). IRC §6201(a)(3) says otherwise, in an explicit carve-out read verbatim here: the Secretary may assess the overstated credit "in the same manner as in the case of a mathematical or clerical error appearing upon the return, except that the provisions of section 6213(b)(2) (relating to abatement of mathematical or clerical error assessments) shall not apply with regard to any assessment under this paragraph." A CP23 client who assumes they can force an automatic abatement simply by requesting one within 60 days, the way they could with an ordinary math-error notice, is wrong — and advice built on that assumption will cost the client the response window instead of protecting it. The rule to give a client: an ordinary math-error notice has a 60-day undo button, but CP23 doesn't — respond by the date on the notice, because there is no automatic clock working in your favor here.

CP23 is also worth separating from CP12, which reads similarly but is not the same determination. CP12 opens with "We corrected one or more mistakes on your tax return" — any mistake, not specifically an estimated-tax discrepancy — confirmed directly against IRS.gov's own CP12 page, which also confirms CP12 carries no mention of the §6213(b)(2) abatement right either. A CP12 balance due can still, depending on the underlying error, be an ordinary math-error assessment with real abatement rights attached; a CP23 balance due, by definition, is the one category of math-error-style assessment where that right was legislated away.