CP60: What It Means and How to Respond
By Forrest Baumhover, CFP®, EA · Last verified August 23, 2026
CP60 doesn't touch your return at all — it reverses a payment the IRS decides was posted to the wrong account, and there's no §6213(b)-style right forcing them to put it back.
What the notice actually says
CP60 tells a taxpayer that the IRS reviewed their account, found a payment that had been "erroneously applied," and removed it. Removing that payment restores (or creates) a balance due, and the notice lays out the date and dollar amount of the payment that came off the account, plus the new amount now owed.
Nothing about CP60 revisits the return itself — no line items are recalculated, no credit is disallowed. The entire notice is about which account a payment was credited to, not whether the return as filed was correct. That distinction is easy to blur against its nearest relative, CP11, and is covered in full below because it's the single highest-value thing to get right on this page. (For where CP60 sits among the IRS's other balance-due notices, see the IRS Notice Library.)
What actually triggered it
A payment gets flagged for removal when the IRS's own reconciliation determines it was never the taxpayer's payment to apply in the first place, or that it landed on the wrong period. Common fact patterns: a mailed check or voucher with a transposed SSN/EIN that posted to a different taxpayer's account, an estimated payment coded to the wrong tax year, a payment a joint filer made that later needed to be split or reallocated after a separate return was filed, or a payment that a different taxpayer disputed as theirs and the IRS moved it back to them. The account-maintenance function that catches these doesn't explain its reasoning on the notice beyond the date and amount removed — it states the correction, not the underlying story.
Before calling the number on the notice, pull the account transcript and check the posted transaction codes in the IRS Transcript Decoder. The removed payment often isn't gone — it shows up re-credited to a different period or a different taxpayer identification number on the same transcript, which is a materially different conversation with the IRS than a payment that's actually missing.
Response deadline and what happens if you miss it
CP60 does not carry a fixed statutory response window the way a math-error notice or a levy notice does. IRS.gov's own description of CP60 states only that the taxpayer should "pay the amount you owe by the date stated on the notice" — that date is whatever the specific notice prints, not a number set by the Internal Revenue Code. There is no CDP hearing right, no Tax Court petition right, and no comparable abatement statute attached to CP60 itself.
Missing the printed due date does what missing any balance-due deadline does: the unpaid amount continues to accrue interest and applicable failure-to-pay exposure, and the account can proceed into the standard collection notice stream (CP501, CP503, and eventually CP504) if it isn't resolved or put into a payment arrangement.
The practitioner's actual next step
First, verify the payment actually existed and was correctly applied before assuming the client owes the balance — a cancelled check, bank statement, EFTPS confirmation number, or Direct Pay confirmation is exactly the kind of proof IRS.gov tells taxpayers to have ready. Cross-check that proof against the account transcript pulled earlier before calling; if the payment reappears elsewhere on the transcript rather than disappearing entirely, that changes what you're asking the IRS to fix.
If the proof supports the client, mail or fax the documentation to the address on the notice, or call the number listed with it in hand — a Form 2848 on file lets a practitioner handle that call directly. If the proof doesn't exist or the removal is correct, pay by the date on the notice to stop further interest, or size a payment plan against Internal Revenue Manual (IRM) 5.14, the IRS's own collection-procedures handbook section, with The Federal Tax Desk's IA Payment Calculator if full payment isn't realistic before the client calls.
What CP60 gets confused with — and why the distinction matters
CP60 gets lumped together with CP11 constantly, because both land a client at a new balance due they didn't put there themselves. The mechanisms are not the same, and neither is the dispute right that comes with each one. CP11 corrects the return itself under IRC §6213(b) math-error authority, and by statute it comes bundled with a specific, enforceable right: a written abatement request filed within 60 days of the notice date forces the IRS to unwind the assessment, no discretion involved, under §6213(b)(2)(A).
CP60 doesn't touch the return, and it doesn't come with that statutory lever. IRS.gov's own CP60 guidance cites no IRC section and describes no fixed response window — just a due date printed on the notice and an invitation to call with proof if the taxpayer disagrees. Disputing a CP60 is an administrative conversation, not a statutory right on a clock: the IRS decides whether the documentation is convincing, and there's no deadline that automatically reverses the reversal the way §6213(b)(2)(A) automatically reverses a math-error assessment. If a client has already paid the CP60 balance while assembling proof and later establishes the original payment should never have been removed, the formal backstop for getting that money back is a refund claim for the overpayment under IRC §6511 — generally three years from filing or two years from payment, whichever is later. It works, but it's slower and less automatic than CP11's built-in abatement right, which is exactly why treating the two notices as the same kind of problem gives a client the wrong sense of how much leverage they have.