CP22A: What It Means and How to Respond

What the notice actually says

CP22A tells a taxpayer the IRS processed a change to their return for a specific tax year and that the change resulted in a balance due. The notice restates the recalculated figures and includes a payment coupon showing the amount owed and the date it needs to be paid. IRS.gov's own plain-language explanation is notably generic on this point: "We sent you this notice because we made the changes to your tax return. You owe because of the changes" — it does not say what prompted the change, only that it happened and money is now owed. The notice's own FAQ effectively concedes the gap: asked "How can I find out what was changed and why?", its answer is the same instruction — call the toll-free number on the notice.

That's a real gap for a taxpayer trying to self-diagnose the notice, and it's also where the confusion with other 'we changed your return' notices starts. CP22A is a balance-due processing notice, not a collection-enforcement notice — it carries none of the Collection Due Process (CDP) rights that attach later, once the IRS actually sends a final notice of intent to levy at least 30 days before levying under IRC §6330, and it does not by itself authorize a levy. (For where it sits relative to the notices that do, see the IRS Notice Library.)

What actually triggered it

Mechanically, CP22A fires whenever a "data processing adjustment" posts to the account and increases the balance due by $5 or more. That adjustment can come from almost any source that changes a figure on the return — a Form 1040-X, a correction made over the phone with an IRS assistor, a response to an earlier notice, or a closed correspondence exam the taxpayer agreed to. The notice itself doesn't distinguish among these; the trigger is the posting event, not the reason behind it.

Because the underlying cause can vary this much, the number on the notice is only as good as the adjustment that generated it. If the figures don't match what was actually submitted or agreed to, that's the basis for a dispute — but the premise of CP22A is that a specific change already posted to the account, not that the IRS is proposing one.

Response deadline and what happens if you miss it

The payment deadline is the date printed on the notice's payment coupon — CP22A does not carry a fixed 30- or 60-day statutory window of its own. Interest on the additional tax has been running since the original due date of the return under IRC §6601, which sets the accrual period from "the last date prescribed for payment" to the date paid regardless of when the adjustment was later assessed — so the clock did not start when the notice was mailed.

Missing the deadline adds a failure-to-pay penalty under IRC §6651(a)(2) — 0.5% of the unpaid tax per month, up to 25% in the aggregate — on top of the interest already accruing. The Taxpayer Advocate Service frames the practical stakes plainly: being proactive before the due date can prevent additional penalty and interest and "eliminate the need for the IRS to take action to collect the balance" — meaning an unresolved CP22A balance is what feeds the standard collection notice stream, starting with a CP501 reminder, if it sits too long.

What to do next

Before advising a client to pay or dispute a CP22A, review the client's account transcript and confirm the adjustment on the notice matches what actually happened on the account — the transaction code and date the adjustment posted should line up with whatever correspondence, 1040-X, or phone conversation supposedly triggered it. The transcript is also the only reliable way to see the taxpayer's collection status directly, rather than guessing at it from which CP number arrived (the last section explains why that distinction matters).

If the balance is correct and full payment isn't realistic, the notice itself points toward a payment plan first — The Federal Tax Desk's IA Payment Calculator will size a proposed installment agreement before the client calls. If the client genuinely cannot pay anything, Currently Not Collectible status is worth screening for before the account ages into enforced collection; an Offer in Compromise is the right track only if the liability itself, not just the ability to pay, is in dispute. If the client disagrees with the change on the notice, the IRS's own instruction is a phone call to the number on the notice with the return and supporting documents in hand — not a formal protest.

What people mistake CP22A for

CP22A is constantly explained online as the "IRS-initiated" counterpart to a "taxpayer-requested" CP21A — audit or third-party mismatch on one side, amended return on the other. That story does not survive a direct check of IRS's own sources: the live IRS.gov pages for CP21A and CP22A currently use identical boilerplate ("we made the changes to your tax return"). Origin isn't what separates them, at least not on the face of either notice.

What actually separates CP21A from CP22A, per IRM 21.3.1.6.14 and .6.15, is the taxpayer's account status at the moment the adjustment posts. CP21A issues when the account is already in Taxpayer Delinquent Account (TDA) status — meaning it was already flagged for collection before this particular change was made. CP22A issues when the account is not yet in TDA status, or is moving into TDA status in the same cycle as the adjustment. In practice, a CP22A is more likely to be the first sign of a new balance on an account that wasn't previously delinquent; a CP21A landing on a client is a signal that the account may already have other collection activity in motion. That is worth confirming on the transcript rather than assuming from the notice number alone — a client who has already been in an installment agreement or CNC status handles very differently from one seeing their first balance-due notice of the year. The rule of thumb worth repeating to a client: the notice number doesn't tell you why you owe, only whether the account was already flagged for collection before this bill showed up.

Common Questions