I'm Darrin Mish. For 32 years I've practiced federal tax litigation \u2014 routine audits, Tax Court cases, and everything in between. If you're facing an IRS issue, here's what you need to know first.<\/p>\n
A CP2000 notice and an IRS audit are two different procedures with two different legal frameworks. The IRS does not count CP2000 cases in its audit statistics. The agents who handle CP2000s are not auditors. The letter you got proposing an extra $14,000 in tax is not an audit notice.<\/p>\n
But that does not mean a CP2000 is harmless. It does not mean it cannot escalate. And it does not mean the distinction matters for the money you may end up owing.<\/p>\n
The honest answer is that a CP2000 lives in a procedural gray zone. It is less than an audit, more than nothing, and the way you handle it determines whether it ends quietly or turns into a bigger problem.<\/p>\n
After 32 years of dealing with these notices, here is what you need to know about the relationship between a CP2000 and a real IRS audit.<\/p>\n
A CP2000 comes from the IRS Automated Underreporter program, or AUR. The AUR is a computer system that compares information reported by third parties (W-2s, 1099s, K-1s, brokerage statements) to what you reported on your return. When the computer finds a mismatch, it generates a proposed adjustment and sends you a CP2000.<\/p>\n
The IRS does not officially classify this as an examination. It is a document matching notice. The legal authority comes from a different part of the Internal Revenue Code than a formal audit.<\/p>\n
A real audit, by contrast, is a formal examination of your return under IRC Section 7602. An auditor (called an examiner inside the IRS) is assigned to your case. They request documents. They evaluate your records. They make their own determinations about whether items on your return were correctly reported.<\/p>\n
For 2024, the IRS conducted 505,514 audits. Of those, 393,783 were correspondence audits handled by mail, and 111,713 were field audits handled in person or in an IRS office. That same year, the IRS issued roughly 1.19 million CP2000 and CP2501 notices. CP2000s are more common than audits by more than 2 to 1.<\/p>\n
The two processes feel similar from the receiving end – both involve letters from the IRS proposing more tax – but they are separate animals.<\/p>\n
The CP2000 process follows a predictable sequence.<\/p>\n
The notice arrives in the mail. It identifies the specific items the AUR system flagged as mismatches and proposes additional tax, penalties, and interest. You have 30 days to respond.<\/p>\n
If you agree, you sign the response form and pay the proposed amount. The IRS assesses the tax. The case closes.<\/p>\n
If you disagree, you check the disagreement box, attach documentation explaining why the IRS is wrong, and mail the response back. The IRS reviews your response. If they accept it, the case closes with no additional tax. If they partially accept it, they send a revised proposal. If they reject it, the case moves to the next stage.<\/p>\n
If you ignore the notice or fail to resolve it, the IRS sends a Statutory Notice of Deficiency. This is the 90-day letter under IRC Section 6213. You have 90 days to petition the United States Tax Court (150 days if you are outside the United States). If you do nothing during the 90 days, the IRS assesses the tax and you owe it.<\/p>\n
At no point in this sequence does the case become an audit in the formal sense.<\/p>\n
An audit starts differently. Instead of a CP2000 proposing a specific adjustment, you receive a letter telling you that your return has been selected for examination. The letter requests records. It identifies the year (or years) under examination and often the specific issues the IRS wants to look at.<\/p>\n
For a correspondence audit, you mail your records and exchange letters with the examiner. For a field audit, you meet with the examiner in person, usually in their office, sometimes at your home or business.<\/p>\n
The examiner reviews your documentation, may request additional records, may interview you, and ultimately issues a report. If they propose changes, you receive Letter 525 (for a mail audit) or Letter 915 (for a field audit). You have 30 days to respond to the audit report. The path from there mirrors the CP2000 path: agree, disagree, or get pushed into the Statutory Notice of Deficiency framework.<\/p>\n
The key difference is depth. A CP2000 looks at one or two specific mismatches the computer flagged. An audit looks at whatever the examiner wants to look at. They can ask about anything on the return. They can expand the scope to other years. They can go places the AUR computer would never go.<\/p>\n
Both a CP2000 and an audit can end at the same place: the Statutory Notice of Deficiency, also called a 90-day letter.<\/p>\n
The Statutory Notice of Deficiency is Letter 3219 (from a mail process) or Letter 531 (from a field process). It is the IRS’s formal determination that you owe additional tax. It gives you 90 days to petition the United States Tax Court before the tax gets assessed.<\/p>\n
This is the single most important deadline in the entire process. Once a Statutory Notice of Deficiency is issued, the only way to challenge the tax without paying it first is to file a Tax Court petition within 90 days. Miss that deadline and your only remaining option is to pay the tax and sue for a refund – a much harder route.<\/p>\n
A CP2000 that you ignore or mishandle leads to a Statutory Notice of Deficiency. An audit that goes against you leads to a Statutory Notice of Deficiency. From the 90-day letter onward, the two processes look identical.<\/p>\n
Here is where it gets practical. While a CP2000 is not itself an audit, certain responses to a CP2000 can trigger one.<\/p>\n
You write back to the IRS explaining that the $50,000 they think you underreported was actually reported on a different schedule. The IRS reviews your explanation, decides it does not fit the math elsewhere on the return, and refers the case to Examination. Now you have an audit.<\/p>\n
The AUR system flags a CP2000 for one year. The examiner notices that you have had similar mismatches the prior two years that were never reconciled. The case gets referred for a multi-year audit.<\/p>\n
CP2000s on smaller dollar amounts almost always stay in the AUR system. CP2000s involving significant unreported income (six figures or more) sometimes get pulled into Examination, especially if the IRS sees indicators that more is going on.<\/p>\n
If your CP2000 response, the third-party data, or other items on your return suggest something more than an honest mistake, the case can be referred to Criminal Investigation. This is rare. But it happens.<\/p>\n
Sometimes a taxpayer trying to explain a CP2000 inadvertently raises new issues. You explain that the unreported income came from a side business, the IRS reviews the side business, and now you have an audit of the Schedule C activity that was not previously on the radar.<\/p>\n
The fact that a CP2000 is not an audit cuts in two directions.<\/p>\n
On one hand, it is less serious than a real audit. The scope is narrower, the procedures are more automated, and the path to resolution is more predictable.<\/p>\n
On the other hand, a CP2000 can become an audit if mishandled. A response that contradicts your return creates new issues. A response that admits more than it needs to expands the IRS’s interest. A response that ignores the notice entirely guarantees a Statutory Notice of Deficiency.<\/p>\n
The right approach is to treat a CP2000 with the same care you would treat an audit. Document everything. Limit your response to the specific items at issue. Do not volunteer information that was not requested. Get help if the numbers are significant.<\/p>\n
The wrong approach is to assume that because it is “just a notice,” you can handle it casually. Casual handling is how CP2000s become audits.<\/p>\n
A CP2000 is not technically an audit. It is an automated proposed adjustment from the IRS Automated Underreporter program. The procedures are different, the personnel are different, and the IRS does not count it as an examination in its statistics.<\/p>\n
But the consequences can mirror an audit. The same Statutory Notice of Deficiency is waiting at the end if you do not resolve the case. The same Tax Court petition deadline applies. The same final assessment hits your account.<\/p>\n
And a mishandled CP2000 can absolutely escalate into a real audit. The question is not whether the CP2000 itself is an audit. The question is whether you give the IRS reason to make it one.<\/p>\n