CP2000 Crypto Notice: Why the IRS Number May Be Wrong

Last Updated on July 10, 2026 by Patrick Camuso, CPA

Quick answer (read this first):

What it is: A CP2000 crypto notice is a proposed adjustment generated by the IRS Automated Underreporter program when third-party data, increasingly Form 1099-DA proceeds from crypto brokers, does not match a filed return. It is not a bill and it is not an audit, but it proposes additional tax, interest, and often a 20 percent accuracy-related penalty, and it runs on a 30-day response clock.

Why the number is usually wrong: Brokers report gross proceeds, frequently without cost basis. Where that happens, the matching system can treat the entire sale amount as gain, which means the proposed tax is calculated as though the crypto cost nothing to acquire. The real liability is often materially lower than the proposed amount, and in some cases the taxpayer is actually owed a refund.

What to do: Do not pay before reconciling the notice, do not ignore it, and do not file an amended return through normal channels in place of responding. Reconcile the notice against accurate lot-level records, then respond through the notice process with documentation establishing the correct basis and gain by the deadline.

Why these are surging: Form 1099-DA gross proceeds reporting began with 2025 transactions, with forms furnished and filed in 2026. The IRS now receives standardized crypto proceeds data at a scale it has never had before, and material discrepancies that meet the matching program’s selection criteria can generate notices at scale.

What a CP2000 Crypto Notice Actually Is

A CP2000 crypto notice is a proposed adjustment produced by the IRS Automated Underreporter program, usually shortened to AUR. A CP2000 is not itself a determination that additional tax is legally owed, it is the IRS’s proposed adjustment based on the information available to it before the taxpayer’s explanation and supporting records arrive. The system cross-references the information returns the IRS receives from third parties, including Forms W-2, 1099-B, 1099-K, 1099-MISC, and now Form 1099-DA from crypto brokers, against what appears on the taxpayer’s filed return. When the computer detects a mismatch, it generates a CP2000 proposing additional tax and interest computed from the available third-party data, and the proposal may include a systemically calculated 20 percent accuracy-related penalty.

The word proposed carries the whole meaning here, because a CP2000 is not a bill, not a final assessment, and not an audit, and the taxpayer has the right to agree, partially agree, or disagree with documentation before anything becomes final. The automated system identifies the mismatch and calculates the proposal, IRS personnel review the case using the return and the third-party data available to them, and the penalty is typically computed systemically rather than through a person weighing the taxpayer’s individual circumstances. Federal law generally requires written supervisory approval before the IRS asserts a penalty, with an exception for penalties calculated automatically through electronic means, and systemically proposed AUR penalties can remain within that exception when no response arrives. Where IRS personnel later make an individualized determination about the penalty, additional supervisory approval requirements may apply, a procedural question worth reviewing separately whenever the penalty is material.

A close sibling of the CP2000 notice for cryptocurrency mismatches, the CP2501, flags the same kind of discrepancy without stating a proposed dollar amount and is handled through the same reconciliation process. Either notice means the same underlying thing, that the IRS received third-party data it could not match to the return, and the response discipline is identical.

The deadline is the single most important line on the notice. The response is generally due 30 days from the date printed on the CP2000, or 60 days for taxpayers outside the United States, and that clock is not the same as the 90-day deadline that appears later on a Statutory Notice of Deficiency.

Why the CP2000 Amount May Be Materially Overstated for Crypto

Where the broker reported proceeds without cost basis, the proposed amount on a crypto CP2000 can be materially overstated, sometimes dramatically. Crypto brokers report gross proceeds, the total amount received from each sale, but in many cases they do not report cost basis, either because the asset was acquired before basis reporting began, transferred in from another platform or wallet, or held in a way that leaves the broker with no custody lineage to calculate what it originally cost. We explain the structural reasons behind that gap in our guide to why 1099-DA forms arrive with missing cost basis. The AUR system matches the proceeds against the return, and where the IRS receives proceeds with no corresponding basis information, the proposed adjustment can effectively treat the entire sale amount as taxable gain unless the taxpayer establishes basis.

An investor who bought Bitcoin for ninety thousand dollars and sold it for one hundred thousand has a real gain of ten thousand. If the broker reported one hundred thousand in proceeds with no basis and the return did not reconcile cleanly against that figure, the AUR system can propose tax on the full one hundred thousand.

Two other structural causes produce the same result. A transfer between the investor’s own wallets that a broker erroneously classified as a disposal generates phantom proceeds on the third-party side with no matching sale on the return. And a taxpayer using a different lot identification method in their own records than the broker used in its reporting produces a mismatch on covered transactions even when the taxpayer’s accounting is internally consistent, though the taxpayer’s method must independently satisfy the applicable identification and basis-allocation rules for the position to hold. We analyze that structural divergence in depth in our guide to the crypto tax three-record problem. None of these situations necessarily reflect underreporting, and all of them can contribute to information-reporting mismatches that may generate notices. A CP2000 can also be entirely correct, because omitted sales, omitted staking income, duplicate basis claims, and unsupported basis positions all produce legitimate proposed adjustments, which is one more reason reconciliation comes before any response position.

Oversight bodies have examined the automated underreporter program repeatedly, and historical reports from the Treasury Inspector General for Tax Administration and the National Taxpayer Advocate have identified weaknesses in its matching systems along with high post-assessment reconsideration and abatement activity. Those findings reinforce the value of reviewing a CP2000 carefully rather than assuming the proposed amount is final, though they do not establish that any particular notice is wrong, and that history predates the arrival of crypto data, with all its basis gaps and transfer misclassifications, into the pipeline. Some courts have held that when a deficiency determination rests solely on a third-party information return, the IRS is not automatically entitled to its usual presumption of correctness, a line of reasoning associated with Portillo v. Commissioner. In our practice, the corrected liability on a crypto CP2000 has often come in well below the proposed amount once accurate basis is established, and in some cases the reconstruction shows a loss where the notice proposed a six-figure gain.

The 30-Day Clock and What Happens If It Runs Out

If the taxpayer does not respond, the IRS generally issues a Statutory Notice of Deficiency, formally the CP3219A and sometimes called the 90-day letter. That notice is the legal prerequisite to assessment, and it opens the last administrative window, because the taxpayer can petition the US Tax Court within 90 days, or 150 days where the notice is addressed to a person outside the United States, and if no petition is filed the IRS assesses the proposed tax and penalty when the window closes. From there the matter moves into the collections sequence, running through escalating balance-due notices toward liens, levies, and wage garnishment.

A taxpayer who ignores a CP2000 proposing tax on one hundred thousand dollars of proceeds with no basis ends up with an assessed liability calculated as though their crypto cost nothing, plus the 20 percent penalty, plus interest that has been accruing since the original due date. The notice that could have been corrected with documentation becomes a debt the IRS is actively collecting.

The two deadlines are not symmetrical, because the AUR unit may grant additional response time on the CP2000 when the request comes before the deadline, though the extension should be confirmed rather than assumed. The Tax Court deadline on a Statutory Notice of Deficiency, whether the standard 90 days or the 150 days that applies to foreign addresses, cannot be extended by the IRS, because it is the jurisdictional filing window and it closes permanently. Every option the taxpayer has is widest inside the first window and narrows at each step after it.

A missed deadline narrows the path without closing it entirely. Audit reconsideration or other post-assessment administrative remedies, refund claims after payment, and collection due process rights all remain available, but each is slower, more procedural, and less favorable than responding inside the original window. On large proposals, additional interest accrual can also be reduced or stopped without conceding anything, because a remittance toward the proposed amount can slow or suspend it while the dispute continues, depending on whether the remittance is treated as a payment that satisfies liability or as a properly designated Section 6603 deposit that suspends underpayment interest on the deposited amount. The designation and documentation determine which procedural channel returns the funds, which is a detail worth handling deliberately rather than by default.

How to Respond to a CP2000 Crypto Notice

Every CP2000 response resolves into one of three positions, and choosing correctly depends entirely on what accurate records show.

Agreeing is appropriate when the proposed change is actually correct, which happens, because a CP2000 can also identify genuinely omitted disposals, unreported staking or reward income, or other valid adjustments. Where the taxpayer genuinely omitted income and the IRS figure holds up against real records, the response is signing the form, arranging payment, and considering whether the same omission exists in other years. Even in agreement, the penalty deserves separate attention, because the 20 percent accuracy-related penalty is not automatic and can be challenged on reasonable cause and good faith grounds at the same time the tax is conceded.

Partial agreement fits the common crypto pattern where the IRS is right that a disposal went unreported but wrong about the gain. The taxpayer acknowledges the transaction, supplies the correct basis with documentation, and pays tax on the real gain rather. The response states the disagreement on the response form, attaches the lot-level support, and explains the difference between the broker’s proceeds figure and the actual taxable amount.

Full disagreement requires a written response addressing every proposed change with documentation, including the reconciliation showing how each line on the notice maps to the taxpayer’s records. This is the path where preparation quality matters most, because the response becomes the record if the matter escalates to Appeals, and a response that opens new issues or contradicts prior filings can widen the scope rather than resolve it. Whichever position applies, the taxpayer disputing any portion should decline to sign a consent to an adjustment that remains disputed, and if the AUR unit does not accept the explanation, the ensuing correspondence sets out the path to reconsideration or review by the IRS Independent Office of Appeals.

When to Dispute and When to Amend

The CP2000 process has its own response channel, and a taxpayer who instead files a Form 1040-X amended return through normal channels has answered a question the IRS did not ask in a system that is not looking for it. The AUR unit processing the notice may not see the amendment for months, the notice clock keeps running, and the crossed wires routinely produce duplicate assessments and processing confusion that takes longer to unwind than the original discrepancy would have taken to resolve. The general rule is that the response to a CP2000 goes through the CP2000 channel, using the response form and the address or fax on the notice, with corrected figures and documentation attached.

Where the notice is correct and the taxpayer also has additional items to report for that same year that the notice did not raise, the IRS directs the taxpayer to complete a Form 1040-X, write CP2000 across the top, and submit it through the notice channel with the response rather than filing it through the normal amendment system. The corrected computation travels with the response, and the AUR unit processes both together. The rule is not that a 1040-X can never touch the notice year, it is that a separately filed amendment neither suspends nor resolves the AUR case, and the notice must still be answered through its own channel by its deadline.

An amended return has its place when the correction extends beyond what the notice raised. Where reconciling the notice reveals that the same basis errors or unreported activity exist in years the CP2000 does not cover, those years are corrected through amended returns filed on their own track, and proactively, because a taxpayer who corrects other years before the IRS matches them is in a better position than one who waits for the next notice. The distinction is simple to state and constantly missed in practice. The notice year gets a notice response, and the other years get amendments, and neither substitutes for the other.

The strongest reason not to amend reactively has nothing to do with IRS processing channels. An amendment built on the same defective records that produced the original mismatch compounds the problem rather than fixing it. Until the transaction history has been reconstructed at the lot level and reconciled against what the broker reported, any filing, whether a notice response or an amended return, is being assembled from numbers that cannot be defended.

What a Defensible Response Requires

The response that resolves a crypto CP2000 is built on reconciliation, not argument. It matches every proceeds line on the notice to a specific disposal in the taxpayer’s records, supplies the documented cost basis and acquisition date for each lot relieved, explains any line the broker reported that was not a taxable event, and presents the corrected gain calculation with the workpapers behind it.

The mechanics of submitting it are worth getting right. The notice itself identifies the accepted submission methods, generally mail, fax, or the IRS Document Upload Tool, and the response should go through a method the actual notice lists, with proof of timely submission retained. As a practical matter, faxing or uploading beats mailing when the deadline is close, and following up with the AUR unit to confirm receipt is a sensible precaution rather than an IRS requirement. Every CP2000 carries an AUR control number, the unique case tracking ID printed on the notice, and any status call requires it. Married filing joint responses need both spouses’ signatures, a detail that bounces otherwise complete responses. And the proposed change is not always in the government’s favor, because the IRS’s own description of the notice acknowledges the adjustment may increase or decrease the tax, and crypto reconciliations sometimes establish that the taxpayer overpaid and is owed a refund rather than a balance.

That standard is exactly where most recipients discover their real problem, because the records that support this kind of response frequently do not exist. Basis lives in a patchwork of exchange exports, abandoned software accounts, and platforms that no longer operate, and the software-generated reports that produced the original return are calculations rather than documentation, built on default assumptions that may not survive scrutiny and that the platform may compute differently today than it did at filing. Software output that cannot trace its lots to documented acquisitions is not substantiation, and a response built on it invites the follow-up questions it cannot answer.

For investors in that position, the substantive work behind the response is cost basis reconstruction, rebuilding the transaction history across exchanges, wallets, and on-chain activity into a lot-level ledger that supports every figure in the reply. Our crypto cost basis reconstruction practice is built around exactly this work, and the reconstruction that answers the notice also establishes the defensible records that prevent the next one.

The penalty component deserves its own line of attack in the same response. The 20 percent accuracy-related penalty is not automatic and can be contested under the reasonable cause and good faith exception, a fact-specific analysis that weighs the taxpayer’s efforts to report correctly, the complexity of the issue, the taxpayer’s knowledge and experience, and any reasonable reliance on professional advice. Those factors carry real force in crypto given how much of the underlying tax treatment remains genuinely unsettled. The timing rule matters here, because penalty defenses raised during the CP2000 process get evaluated as part of the response, while defenses raised after assessment fall into the far slower reconsideration channel.

After the response goes in, processing generally runs several weeks to a few months. The IRS either accepts the documentation and corrects the proposal, replies with next-step options, or sends interim letters requesting additional processing time, which are routine rather than a signal that something has gone wrong. Where the corrected number is still more than the taxpayer can pay, installment agreements, Offers in Compromise where the facts support one, and Currently Not Collectible status turn the balance into a payment strategy rather than a crisis.

Fake CP2000 Notices Target Crypto Investors

Counterfeit CP2000 notices have circulated for years, and crypto investors are a favored target because scammers know the recipient often cannot easily verify what they owe. The tells are consistent across the counterfeits. A real CP2000 directs payment to the United States Treasury, never to an abbreviation like I.R.S., and it never demands payment by wire transfer, prepaid debit card, gift card, or cryptocurrency. Fakes lean on manufactured urgency with 48-hour payment windows, route responses to private post office boxes rather than IRS service centers, and request sensitive information by email or text, none of which the IRS does. Any doubt gets resolved by checking the taxpayer’s IRS Online Account, where genuine notices generally appear, or by calling the IRS at a number obtained independently from IRS.gov rather than the number printed on a suspicious letter.

Why Crypto CP2000 Volume Is About to Surge

The CP2000 has existed for decades, but its collision with crypto is just beginning, and the mechanics point to a sustained rise in notice volume.

Before Form 1099-DA, the IRS had no standardized crypto data pipeline. Reporting arrived in fragments, some exchanges issued 1099-Ks or 1099-Bs, many issued nothing, and the AUR system had little to match against. Beginning with 2025 transactions, custodial brokers report gross proceeds directly to the IRS on a standardized form, with basis reporting phasing in for covered digital assets from 2026. Industry estimates have projected reporting volumes reaching into the billions of information returns annually. For the first time, the matching system has crypto data at the same scale and in the same format it has long had for stocks, and material gaps between broker-reported proceeds and a filed return that meet the program’s selection criteria can now surface at a scale that was never possible before.

Because 2025 reporting is proceeds-only in most cases, the IRS is receiving one half of the gain calculation at scale, which is the exact input that produces phantom-gains notices. Information returns also keep arriving after filing season, whether as corrected forms or delayed originals, and IRS matching does not pause for the data to catch up. A taxpayer can file correctly in April and still draw a CP2000 later in the year when the system matches the return against broker data it received afterward.

The exposure also runs opposite to what most people expect. Analysis published in Tax Notes has argued that the taxpayers most likely to face 1099-DA-driven mismatches are frequently the most active and compliance-minded, because heavy DeFi engagement generates far more on-chain events that brokers and data providers can classify inconsistently. A liquidity pool position can be misread as a disposal, wrapping and bridging can be misclassified as sales, and a transfer between the taxpayer’s own wallets can be recorded as a transfer to a third party, even though none of those events is inherently a taxable sale. Each additional event widens the surface for a classification mismatch between the return and the third-party data, which means exposure driven by data quality rather than by anything resembling avoidance, and it is why the actual form and the broker’s transaction records need review before the cause of any mismatch can be identified. Holders of spot crypto ETFs carry a separate version of the same issue, because certain spot crypto ETFs are structured as grantor trusts that do not report fund-level activity on a standard broker form, leaving the investor with reporting obligations no 1099 covers.

The timing is also predictable, because the AUR does not begin matching a filing year until months after returns are filed, once the bulk of information returns have arrived in its systems, and CP2000 notices typically follow 12 to 18 months after filing as the matching cycles complete. That places the first true wave of 1099-DA-driven crypto notices in late 2026 and running through 2027, landing on top of a program that already flags more than 20 million returns with discrepancies in an ordinary year before crypto data entered the pipeline at scale. The reconciliation work that answers those notices is exactly the work that can be done now, before the notice exists.

Enforcement is expected to ramp in stages rather than arrive all at once, beginning with automated notices rather than millions of simultaneous audits, and most cases will resolve at the correspondence level when discrepancies are explained and substantiated coherently. The direction of travel favors more automation, not less, because the IRS workforce has contracted sharply since early 2025 while the agency has publicly discussed increasing its use of artificial intelligence and advanced analytics to identify noncompliance with greater precision. An agency with fewer people and better matching infrastructure runs its enforcement through the notice channel, which is exactly where crypto’s structural data problems produce the most false positives. That staged rollout is a window rather than a reprieve, because taxpayers who use the early phase to reconcile their records will be in a fundamentally different position when enforcement matures than those who treat the slow start as a reason to wait. We cover how that first wave unfolds in our investor’s playbook for the first wave of 1099-DA tax notices, and the reporting mechanics behind it in our guide to Form 1099-DA.

A CP2000 is one letter on a broader enforcement ladder that runs from soft letters through automated notices to examination, and identifying exactly where a given notice sits determines how much room remains to respond well. Our guide to IRS crypto letters covers the full family, including Letters 6173, 6174, and 6174-A and what each one signals about the data the IRS holds.

For investors facing a crypto CP2000 now, our cryptocurrency tax resolution practice handles the full response, from transcript analysis and lot-level reconstruction through direct communication with the IRS. Work with a crypto CPA established in this market since 2016.

Contact us about your CP2000 notice

Frequently Asked Questions

Why did I get a CP2000 notice for crypto?

The IRS Automated Underreporter system matched third-party data, such as Form 1099-DA or 1099-B proceeds from a crypto exchange, against your filed return and found a discrepancy. Common causes include disposals that were not reported, broker-reported proceeds with no corresponding basis on the return, transfers between your own wallets that a broker erroneously classified as sales, and cost basis method differences between your records and the broker’s reporting. The notice does not mean the IRS figure is correct, and where the underlying form reported proceeds without basis, the proposed amount is frequently overstated.

Is a CP2000 notice an audit?

No. A CP2000 is a proposed adjustment generated by computer matching, not an examination. AUR identifies potential mismatches electronically and IRS personnel review the case using the return and third-party data available to them, so a response is ordinarily the first opportunity to put complete basis records and context into that review. An unanswered or poorly handled CP2000 can still escalate, first to an automatic assessment through a Statutory Notice of Deficiency and in some cases toward examination, which is why the response window matters.

Why is the amount on my crypto CP2000 so high?

The amount on a crypto CP2000 is most often high because the IRS calculated it from broker-reported proceeds with no cost basis. Brokers frequently cannot report what your crypto originally cost, so the proposed adjustment can effectively treat the entire sale amount as gain, as though the assets were acquired for nothing. The proposed tax on this phantom gain can be many times the real liability. Establishing accurate basis through documentation can reduce the number substantially, and in some cases the corrected calculation shows a loss.

Should I just pay the CP2000 amount to make it go away?

Not before reconciling it, because the proposed amount may be built on proceeds with no basis, and paying first shifts the correction into slower refund procedures rather than the notice process. A remittance can make sense as a deliberate move to stop interest while the dispute continues, but the procedural handling determines how the funds come back. The better sequence is reconciling the notice against accurate lot-level records and responding with documentation by the deadline.

Should I respond to the CP2000 or file an amended return?

Respond through the CP2000 channel for the year the notice covers, using the response form and contact information on the notice itself. The amended return process runs through a separate IRS system, and filing a 1040-X in place of a notice response creates processing confusion, duplicate assessments, and delay. Amended returns belong on their own track, for years the notice does not cover where the same errors exist and proactive correction is warranted.

What happens if I miss the 30-day deadline?

If the taxpayer does not respond, the IRS generally issues a Statutory Notice of Deficiency, which opens a 90-day window to petition the US Tax Court. If no petition is filed, the IRS assesses the proposed amount, including the overstated phantom-gains figure and the 20 percent penalty, and the matter moves to collections. Options like audit reconsideration, other post-assessment administrative remedies, and refund claims remain after a missed deadline, but each is slower and less favorable than responding inside the original window.

Can I get the CP2000 penalty removed?

Often, yes. The 20 percent accuracy-related penalty is not automatic and can be contested under the reasonable cause and good faith exception, a fact-specific analysis that considers the taxpayer’s efforts to report correctly, the complexity of the issue, the taxpayer’s experience, and any reasonable reliance on professional advice. Those factors carry real force in crypto given how much of the underlying treatment remains unsettled. Penalty defenses should be raised during the CP2000 response itself, because waiting until after assessment pushes the matter into a much slower reconsideration process.

Will crypto CP2000 notices keep increasing?

Yes. Form 1099-DA gross proceeds reporting began with 2025 transactions, with forms furnished and filed in 2026, giving the IRS standardized crypto data at a scale it has never had, with industry estimates projecting volumes reaching into the billions of forms annually. As those forms enter automated matching, the system is being fed proceeds-only data, the exact input that produces overstated proposals, and corrected or delayed broker forms mean even taxpayers who filed correctly can be matched against data the IRS received after filing. Notice volume is expected to rise substantially as matching cycles complete.