Every firm has a drawer — physical or mental — where the IRS notices go. And every firm knows the particular drop in the stomach that comes when one of them is a CP2000. The return was filed months ago. The client has moved on. And now there's a letter proposing that the numbers were wrong, with a response date that's closer than you'd like.

I want to make the case that a CP2000 is not the fire drill it feels like — or rather, that whether it becomes a fire drill was decided long before the envelope arrived. It was decided at intake, by whether the number the letter is questioning was ever tied to the document it came from. Get that right and a CP2000 is a one-minute lookup. Get it wrong and it's an afternoon you didn't have.

Let me start with what the notice actually is, because the panic usually comes from misreading it.

What a CP2000 actually is

A CP2000 is not a bill, and it is not an audit. In the IRS's own words, "The CP2000 isn't a bill, it's a proposal to adjust your income, payments, credits, and/or deductions." It's the output of a matching process: the income and payment information that third parties reported — the employers, the banks, the brokerages — didn't line up with what was on the return. A 1099 the client forgot to mention. A brokerage that reported a sale the return didn't. A figure transposed on the way in. The system flags the mismatch and proposes a change.

That proposal can go either way. It often means more tax is owed, but a CP2000 can also propose a refund. At bottom, it's the IRS saying: our paperwork and yours disagree — here's the difference, tell us who's right.

The response window is real but manageable. You generally have 30 days from the date on the notice to reply — 60 if the taxpayer lives outside the United States. If you agree, you sign and return the response form; you don't need to file an amended return. If you disagree, you say so in a signed statement and include the documentation that backs you up. And if nobody replies? The IRS is plain about it: "If you don't reply or we can't resolve the discrepancy, we may send another notice and a bill." That's the path you don't want — the proposal quietly hardening into an assessment because no one answered in time.

So the event itself, handled well, is small: read the mismatch, pull the source document, confirm or contest, reply. The reason it so often isn't small has nothing to do with the IRS. It has to do with where that source document is.

Why it feels like a fire drill

Here's the mechanism. A CP2000 questions one specific number — this interest figure, that sale, this wage box. To answer it, someone at the firm has to put their hands on the document that number came from and confirm what it actually said. A minute's work, if the document is where you can find it.

But the number on the letter was entered a year ago, in the compression of a filing season, by someone moving fast through a stack. If it went into the return as a bare figure — keyed off a page and then detached from that page — then answering the CP2000 means reconstructing a history nobody kept. Which 1099 was this? Who was the payer? Where's the original? Was it the version the client first sent, or the corrected one that arrived in March? The notice didn't create that work. The notice just sent the bill for a shortcut taken in April.

And this is where firm scale turns a nuisance into a pattern. One CP2000 is a bad afternoon. But at a real client base these arrive year-round, and the matching program doesn't care that it's August and you're short-staffed. A firm with hundreds of returns will see them steadily — each one re-opening a return that was supposedly closed, each one asking the same question: can you prove the number?

The firms that handle them calmly aren't the ones with better letter-writers or faster researchers. They're the ones for whom "can you prove the number" was already answered — at intake, before the return was ever filed.

The reconstruct tax

I've started calling this the reconstruct tax: the hidden, deferred cost of a number that sailed through unverified.

In April, an unverified figure costs nothing. It goes in, the return is filed, everyone moves on. The cost is invisible precisely because it's deferred. It shows up a year later — as the afternoon a staffer spends digging through email for a brokerage statement the client swears they sent, or re-requesting a document from a payer, or rebuilding from a bank record what a missing 1099 would have shown. Multiply that by the notices a real client base generates, and the reconstruct tax becomes one of the quieter line items eating a firm's margin. Quiet because nobody books it as what it is: the cost of a shortcut taken a year earlier.

What makes it maddening is that the expensive part isn't the judgment. Deciding whether to agree or contest a CP2000 is the easy, five-minute part — that's the work you were trained for. The expensive part is the archaeology that comes before it: finding the document. And archaeology is pure waste. It produces nothing the firm didn't already have in its hands a year ago and let slip.

The version where it's a one-minute lookup

Now picture the same notice landing at a firm that verified on the way in.

Every figure that went into the return was confirmed against its source at intake — looked at, checked, and, crucially, kept attached to the document it came from. The 1099 isn't a number someone vaguely remembers typing; it's a number with its source one click away, where the next person to need it can find it in seconds.

The CP2000 arrives. Someone opens the return, goes to the figure in question, and pulls up the exact document behind it. Thirty seconds later they know whether the IRS is right or the client is. If the client's right, the signed statement nearly writes itself, with the supporting document already in hand. If the IRS is right, they agree and move on. Either way, the notice never became a project. It was a lookup.

That's the whole difference — and it isn't about working harder when the notice comes. It's about where the proof lives. A firm that keeps each figure married to its source turns every future CP2000 from a reconstruction into a retrieval. A firm that files figures loose pays the reconstruct tax, over and over, for years.

The habit worth building

So the practical takeaway isn't "get faster at answering notices." It's "verify once, at the start, and keep the source attached to the figure." Confirm the number against the document at intake — when the document is already in front of you, when the client is still responsive, when it costs almost nothing — and store it so the source and the figure never come apart. You do the one minute of work now so you never do the afternoon later.

This is, not by accident, the thing I spend my days building toward. My interest in verification happening at intake, with the source kept beside the number, isn't abstract — it comes straight from the CP2000 drawer. A return assembled that way answers its own notices. A return assembled in a hurry, with the numbers cut loose from their documents, generates a year's worth of small, deferred fire drills that someone else on the team will pay for later.

The notice you can answer in a minute and the one that costs you an afternoon are, very often, the same notice. What decides which one you got is a choice the firm made a year earlier, at a desk, with the document still in hand: did we verify it, and did we keep the proof. Answer that well on the way in, and the CP2000 stops being the letter you dread. It becomes the one you clear before your coffee's cold.

Yatin Miglani is an Enrolled Agent in Phoenix, Arizona, and the founder of Sophicor. He writes The Verified Practice on the AI-tax era from the practitioner's chair — the problems he lived before he built for them.

Sources referenced: IRS, "Understanding your CP2000 series notice" — a CP2000 is not a bill; it's issued when income or payment information from third parties (such as employers or financial institutions) doesn't match the return; reply by the date on the notice; if you don't reply, the IRS may send another notice and a bill; if you agree, you don't need to amend your return, irs.gov. IRS, Topic No. 652, "Notice of Underreported Income – CP2000" — "The CP2000 isn't a bill, it's a proposal to adjust your income, payments, credits, and/or deductions"; respond within 30 days of the notice date (60 days if living outside the United States); if you disagree, provide a signed statement with supporting documentation, irs.gov.

— Yatin Miglani

Enrolled Agent · Phoenix, Arizona
Founder, Sophicor · sophicor.com