CP13: What It Means and How to Respond

What the notice actually says

CP13 tells the taxpayer that the IRS "corrected one or more mistakes" on the return and that, as a result, "you're not due a refund nor do you owe an additional amount because of our changes. Your account balance is zero." IRM 21.3.1.6.9 defines the notice by dollar range directly: "Math Error- Balance Due < $5, Overpayment < $1" — a correction small enough in either direction that the IRS doesn't act on it the way it would a CP11 or CP12. (For where CP13 sits among the other IRS notices, see the IRS Notice Library.)

IRS.gov's own page states the practical consequence plainly: "Payment is not required if the balance due on the notice is less than $5.00," and "An overpayment of less than $1.00 is not refunded without a written request from the taxpayer." Both are stated as IRM policy, not statutory floors — the correction itself is a real math-error assessment either way, just below the threshold the IRS bothers to collect or refund automatically.

What actually triggered it

CP13 is generated by the same IRC §6213(g)(2) math-error categories that drive CP11 and CP12 — an addition or subtraction error, a dependent ID mismatch, a credit phased out based on income already on the return, and the rest of the list CP11.js's own header describes in detail. The only thing that makes a given math error land on a CP13 instead of a CP11 or CP12 is arithmetic: the net effect of the correction happens to fall inside the under-$5/under-$1 band IRM 21.3.1.6.9 sets.

That means the underlying cause is worth checking with the same care a CP11 or CP12 gets, even though the dollar amount looks trivial. Pull the account transcript and compare the corrected figures against the return as filed — a credit phaseout the IRS miscalculated, or a dependent ID typo on the IRS's own side, produces a CP13 exactly as often as it produces a CP11 or CP12, it just happens to net close to even this time.

Response deadline and what happens if you miss it

IRS.gov's own CP13 page doesn't print a fixed day count, telling a disagreeing taxpayer only to "contact us by the date shown on your notice." CP13 is assessed under the same authority as CP11 and CP12 — IRC §6213(b)(1) — which means the same statutory clock applies: IRC §6213(b)(2)(A) gives the taxpayer 60 days from the date the notice was sent to file a written request for abatement, and the Secretary "shall abate the assessment" upon receiving it. The IRS can't pursue collection on the assessment while it remains abatable during that window either, though with a balance under $5 that protection rarely matters in practice.

IRS.gov states the consequence of missing the window in the same language CP10 and CP11 both carry: the taxpayer "will lose formal rights to have the change(s) reversed, as well as your right to appeal our decision to the U.S. Tax Court." The same sentence that follows offers a real fallback: contacting the IRS with supporting documentation after the 60 days "will still" get considered, and the change may still be reversed if the IRS agrees — just without the guaranteed right the timely request carries.

The practitioner's actual next step

Treat a CP13 the same way a CP11 or CP12 gets treated — verify the correction against the transcript and the return as filed before deciding it's not worth the client's attention just because the dollar amount is small. A recurring math error that happens to net near-even this year can net far from even the next, and a client who never learns what caused this year's CP13 has no reason to expect a materially larger CP11 or CP12 in a future year with the same underlying data-entry issue.

If the correction is right and there's a sub-$1.00 overpayment the client actually wants refunded, the notice's own instruction is a written request — IRS.gov doesn't publish a specific address or form for it, so send it to the address on the notice itself, the same way any other written response to a math-error notice goes out. If the correction looks wrong, file the abatement request within the 60 days regardless of the dollar amount, for the same reason it matters on a CP11: it preserves the formal right, and a documented request beats relying on the informal reconsideration IRS.gov still allows after the deadline but doesn't guarantee.

What CP13 gets confused with — and why the distinction matters

CP13's closest relatives are CP11 and CP12 — all three use the identical §6213(b) math-error mechanism and the identical 60-day abatement clock, confirmed directly against each notice's own IRM 21.3.1 subsection (.6.6, .6.8, and .6.9 respectively). The only real difference is the dollar result: CP11 nets to a real balance due, CP12 nets to a real refund, and CP13 nets close enough to zero that the IRS doesn't act on the amount at all. A practitioner who assumes CP13 carries a weaker version of the CP11/CP12 abatement right is wrong — the right is identical; only the dollar consequence of exercising it is smaller.

CP13 is also worth separating from CP25, the near-even-balance notice in the *other* IRS math-error family — the one built on estimated-tax-credit discrepancies under IRC §6201(a)(3) rather than the general math-error authority of §6213(g). CP25 shares CP13's "lands near zero" shape, but not its abatement right: CP23's own page documents that §6201(a)(3) explicitly excludes the §6213(b)(2) abatement mechanism from applying to that family at all. A client holding a CP25 has no automatic 60-day undo button; a client holding a CP13 does. Confusing the two families because both notices happen to net near zero would cost a CP13 client a real statutory right by assuming it doesn't exist.

Common Questions