CP523: What It Means and How to Respond

What the notice actually says

CP523 tells a taxpayer who already has an installment agreement that the IRS is terminating it because of a default, and that if nothing changes, the IRS intends to seize — levy — wages and bank accounts to collect the balance. IRS.gov states the deadline plainly: contact the IRS "as soon as possible but no later than 30 days from the date of the notice." Several lettered variants exist (CP523B, CP523G, CP523H, CP523L, CP523M, and CP623 among them) depending on which collection unit is handling the case, but the core mechanics — default, 30-day cure window, termination, levy warning — are the same across the family. (For where this fits in the broader collection stream, see the IRS Notice Library.)

What CP523 is not is the notice that itself unlocks that levy. Read closely, IRS.gov's own CP523 page never mentions Collection Due Process, never cites Form 12153, and its listed reference tools point to Publication 1660 (Collection Appeal Rights) and Form 9465 — not the CDP package. That's the single highest-value fact on this notice, covered in full below, because CP523 gets treated as either background noise or the final word, and it's neither.

What actually triggered it

CP523 only goes to a taxpayer who already has an installment agreement in place — it's a default notice, not an initial collection notice. The most common triggers are a missed monthly payment, a new balance due from a return filed while the agreement was active that never got rolled into it, or a required return that went unfiled. Any of those breaches the agreement's terms, and the IRS treats the account as in default whether or not the taxpayer realizes it yet.

CP523 is also frequently the second letter in a two-step sequence. CP521 is the IRS's routine monthly payment reminder for an installment agreement in good standing — no threat, no default, nothing beyond the scheduled payment. CP523 is what CP521 is not: a taxpayer who's been getting CP521s without incident and then gets a CP523 has crossed from on-track to in-default, usually because a payment was missed or a new liability landed on top of the existing agreement.

Response deadline and what happens if you miss it

The response window is 30 days from the date on the notice — IRS.gov states it as contacting the IRS "as soon as possible but no later than 30 days." That window does two things at once: it's the practical deadline to cure the default or work out a fix, and it lines up with the statutory levy protection in IRC §6331(k)(2)(D), which bars the IRS from levying for 30 days after an installment agreement is terminated — and, if the taxpayer files a Collection Appeal Program request within that 30 days, keeps the bar in place for as long as the appeal is pending.

Miss the window without curing the default or filing a CAP appeal, and the agreement terminates automatically. The full remaining balance becomes due, the IRS can file a Notice of Federal Tax Lien if one isn't already on file, and — once whatever Collection Due Process condition attaches to the liability is satisfied — the wage and bank levies the notice warns about become available. CP523's own FAQ also flags the same passport-certification consequence covered in depth on the CP71C page: a seriously delinquent balance can get a passport denied or revoked, separate from and in addition to the levy threat.

The practitioner's actual next step

Start by confirming the default is real before calling the IRS. A payment posted late, misapplied to the wrong period, or a return still processing can all generate a CP523 off an account that isn't actually broken — pull the transcript first. If the default checks out and it's a single missed payment, curing it before the 30 days run is the fastest, cleanest fix; the agreement never actually terminates.

If the client can't cure but wants to keep paying, contact the IRS about reinstatement — it can carry a user fee and may require catching up or restructuring — or size a new installment agreement correctly this time with The Federal Tax Desk's IA Payment Calculator before proposing one, rather than repeating whatever assumption produced the first default.

If the client disputes the termination itself — the default didn't happen, or the amount is wrong — the appeal path is the Collection Appeal Program under Publication 1660, typically filed on Form 9423. That's a different, faster process than the Collection Due Process hearing tied to LT11 or Letter 1058: CAP doesn't toll the collection statute the way a CDP request does, and a CAP determination isn't reviewable by the Tax Court. It stops the immediate levy threat; it doesn't preserve the same downstream rights.

What CP523 gets confused with — and why the distinction matters

Two separate mix-ups happen with this notice. The first is treating CP523 like CP504: assuming that because both mention a levy, they carry the same authority. They don't. CP504's own bite is limited to a state tax refund through the State Income Tax Levy Program. CP523, by contrast, is a genuine warning about wage and bank levy — the agreement that was holding collection back is gone, and nothing in the notice limits the threat to a state refund.

The second mix-up runs the other way: assuming CP523 is functionally the same as LT11 or Letter 1058 because both mention levy on wages and bank accounts. It isn't. LT11/Letter 1058/CP90 is the Collection Due Process notice — it opens the 30-day window to file Form 12153, and a timely request tolls the collection statute and preserves Tax Court review. CP523's own page cites none of that; its appeal path is CAP.

The actual legal question — whether the IRS can go straight to levy once the CAP window closes — turns on IRC §6330(a), not on anything CP523 itself says. A CDP notice is "required only once" per taxable period. If the taxpayer already received an LT11, Letter 1058, or CP90 for this liability — common, since many installment agreements get set up in response to exactly that notice — no new CDP notice is owed, and levy can follow once §6331(k)(2)(D)'s protection lapses. If no CDP notice was ever sent for this liability, the IRS still owes one under §6330(a) before it can actually levy, regardless of what CP523 warns. The rule to keep straight: CP523 warns about levy, but it doesn't authorize it — only an earlier or later CDP notice does that.