The single biggest risk in this year's Form 1099-DA rollout is not the form itself but what happens when its gross proceeds figure reaches the IRS without a matching cost basis attached. Because brokers are only required to report proceeds for 2025 transactions, the IRS's automated matching system sees a large number on one side of the ledger and nothing to offset it, which is precisely the condition that generates a CP2000 notice. Our analysis of this filing cycle indicates the traders most exposed are not the ones underreporting deliberately, but those who assumed the broker-furnished form was complete and filed accordingly. This guide walks through exactly how the basis gap forms, why it specifically triggers CP2000 notices rather than a full audit, and the documentation steps that close the gap before the IRS's automated system ever flags a mismatch.
The cost basis gap refers to the difference between what a broker reports as your sale proceeds and what you actually owe in tax, a difference that only becomes visible once your original acquisition cost is factored in, something the 1099-DA is not required to include for the current filing year.
A 1099-DA showing $50,000 in proceeds does not mean $50,000 in taxable income; it means $50,000 changed hands, and the actual gain depends entirely on what was paid to acquire the asset in the first place. When the basis field is blank or zero, the form effectively implies the entire proceeds amount is profit, and any taxpayer who files without correcting that implication is likely reporting a gain far larger than what actually occurred. This is the core mechanic behind nearly every basis-gap-related filing error this season, regardless of which platform issued the form.
Assets that changed custody at least once before being sold, whether moved from a self-custody wallet into an exchange or transferred between two different platforms, carry the highest risk of an incomplete basis record. A position bought and sold entirely within a single custodial account typically retains a complete basis trail, while a position accumulated over time across multiple wallets and consolidated before a sale is exactly the scenario a receiving broker cannot fully verify. Longer-term holders and traders who use both centralized platforms and self-custody as part of a broader strategy face the largest exposure here.
Every 1099-DA filed with the IRS becomes part of an automated cross-check against the taxpayer's own return, and a CP2000 notice is simply the output of that matching process when the two figures do not align within an expected tolerance.
The IRS's information-return matching program compares total proceeds reported across all 1099-DA filings under a taxpayer's identification number against the gain or loss reported on Form 8949 and Schedule D, and it does this without any officer reviewing the underlying facts first. A materially lower reported gain than the proceeds figure implies, with no offsetting documentation on file, is exactly the pattern this system is built to catch. Because the process is automated rather than discretionary, it applies equally to a transcription mistake and a deliberate underreport, and the system itself cannot distinguish between the two.
A CP2000 is a proposed adjustment notice, not a bill and not an audit notification, and it lays out the specific discrepancy the IRS identified along with a proposed additional tax amount based on treating the full unexplained proceeds as taxable gain. The notice includes a response deadline and a form for either agreeing with the proposed change or disputing it with supporting documentation. Because the proposed figure typically assumes zero cost basis by default, most crypto-related CP2000 notices overstate the actual tax owed until the taxpayer supplies the missing basis information.
The notice itself is generated well after the original filing deadline, often many months later, since the IRS's matching process runs on its own internal schedule rather than in real time as returns are submitted. This delay means a taxpayer may not learn about a basis-related discrepancy until well into the following year, by which point the original transaction records can be considerably harder to locate than they would have been at filing time. This lag is part of why proactive documentation at the time of filing is generally a more reliable strategy than planning to address any issues only if and when a notice eventually arrives.
The table below summarizes the most common basis gap scenarios and how directly each one maps to CP2000 exposure.
| Basis Gap Scenario | CP2000 Risk Level | Primary Mitigation |
|---|---|---|
| Asset never left one custodial platform | Low | Verify broker figures match personal records |
| Asset transferred in from self-custody | High | Document original acquisition cost independently |
| Asset moved between multiple platforms before sale | High | Maintain a personal ledger tracking basis across transfers |
| Staking or reward income later sold | Moderate | Record fair market value at the time of receipt |
Beyond the general mechanics of IRS matching, a handful of specific patterns in crypto filings are disproportionately likely to generate a notice this filing season, largely because of how new and incomplete broker-side basis reporting still is.
The most common trigger is straightforward: a taxpayer reports a gain lower than what the proceeds figure implies without attaching any basis documentation to explain the difference, whether because they were unaware of the requirement or assumed the broker's figure was already net of basis. Filing software that pulls broker data directly without prompting the user to verify or supplement basis information can inadvertently produce this exact pattern, even when the taxpayer's underlying records are accurate.
This pattern is especially common among traders using automated tax software that imports 1099-DA data directly without flagging incomplete basis fields for manual review. The software correctly reports whatever the broker furnished, but if that data was incomplete to begin with, the resulting return inherits the same gap, and the taxpayer may not realize an issue exists until a notice arrives months later. Manually reviewing any auto-imported basis figures against personal records before submitting a return, rather than trusting the import process by default, closes this specific failure point.
A second, less obvious trigger involves transactions that span a broker's reporting boundary, such as an asset sold in late December but settled or recorded in early January, creating a timing difference between when the broker reports the proceeds and when the taxpayer recognizes the transaction. These mismatches are usually resolved quickly once documented, but they still generate an initial notice because the automated system flags any deviation from the reported figures regardless of the underlying cause.
The table below outlines the typical CP2000 response process from notice to resolution.
| Stage | What Happens | Typical Timeframe |
|---|---|---|
| Notice issued | IRS identifies a proceeds-to-return mismatch and mails a proposed adjustment | Months after the original filing |
| Taxpayer response | Documentation submitted agreeing or disputing the proposed change | Within the stated deadline, commonly 30 days |
| IRS review | Submitted documentation is reviewed against the proposed adjustment | Several weeks to a few months |
| Resolution | Notice is closed, adjusted, or escalated if unresolved | Varies based on complexity of the response |
Closing the gap before filing is significantly less burdensome than responding to a CP2000 notice after the fact, since it only requires assembling records that already exist rather than reconstructing them under a response deadline.
For every asset that changed custody before being sold, whether moved from a platform such as Kraken into self-custody and back, or between two different exchanges, gather the original purchase date, price, and any associated fees, since fees are generally added to basis rather than deducted separately. Where exact records are unavailable, a documented estimate based on historical market data at the time of acquisition is a reasonable fallback, though it is less defensible than a contemporaneous record if the figure is later questioned.
Assets acquired through staking, airdrops, or other non-purchase means require basis calculated from fair market value at the moment of receipt rather than a purchase price, and each receipt event generally needs to be tracked individually rather than blended into a single average figure. Traders who accumulated rewards gradually over an extended period and consolidated them before a single large sale often find this the most time-consuming part of basis reconstruction, since it requires pulling historical pricing data for each distinct receipt date rather than a single lookup.
Form 8949 provides specific adjustment codes for reporting a cost basis that differs from what a broker furnished, and using the correct code alongside supporting documentation is what allows a taxpayer to close the basis gap on the return itself rather than waiting for a corrected 1099-DA that may never arrive before the deadline. Filing with an accurate, documented basis adjustment substantially reduces the odds of a CP2000 notice being generated in the first place, since the reported gain will already reconcile against the broker's proceeds figure once the adjustment is factored in.
Receiving a CP2000 is not itself a penalty, and most crypto-related notices resolve favorably once the taxpayer supplies the cost basis information the original filing lacked, provided the response is submitted within the stated deadline.
The notice specifies a response window, typically 30 days, and missing that window can result in the proposed adjustment being assessed automatically as though it were undisputed. Responding promptly, even with a request for additional time if the documentation is not yet assembled, keeps the matter in a correspondence process rather than escalating toward a more formal collection action.
A clear written explanation of the actual cost basis, supported by purchase records, wallet transaction histories, or exchange statements covering the asset's full holding period, is typically sufficient to resolve a basis-related CP2000 without further correspondence. Notices that stem purely from a missing basis figure, rather than a genuine underreporting of income, are generally the most straightforward to close once the requested documentation is submitted in full.
The basis gap is largely a first-year phenomenon tied to how the 1099-DA rollout was structured, but the underlying discipline it demands, verifying every disposal against an independently maintained ledger, is one that continues to matter even as broker-side reporting improves in future years.
Rather than treating cost basis verification as a once-a-year task performed under filing-season pressure, traders benefit from reconciling each disposal against personal records shortly after it occurs, while the relevant purchase and transfer details are still easy to locate. This is particularly valuable for anyone who moves assets between multiple wallets or platforms regularly, since the passage of time is what most often turns a recoverable basis gap into an unrecoverable one. A running reconciliation habit also makes it far easier to respond quickly if a CP2000 notice does arrive, since the supporting documentation is already assembled rather than needing to be reconstructed under a response deadline.
Cost basis reporting becomes mandatory for covered securities starting with 2026 transactions, with those statements arriving in early 2027, which will close much of the current gap for newly acquired assets going forward. Older holdings and any asset that changes custody will likely continue to depend on taxpayer-maintained records even after that transition, since a receiving broker can only certify a basis history it directly observed. Building strong personal recordkeeping habits now positions traders to handle both the remainder of this transition period and the more complex classification questions that covered-versus-noncovered status is likely to raise in subsequent filing seasons.
Approaching a CP2000 notice, or the possibility of one, with a risk-managed framework means treating documentation as a routine part of filing rather than a reactive step taken only after a notice arrives. Traders who maintain complete records throughout the year are typically able to resolve any notice quickly, while those reconstructing basis for the first time under a response deadline face a considerably harder task.
The gap exists because brokers are only required to report gross proceeds for 2025 transactions, not cost basis, so any acquisition cost information is either voluntary or entirely absent from the form. This is most pronounced for assets that were transferred in from another wallet or platform before being sold.
You are at higher risk if you reported a gain significantly lower than the total proceeds shown across your 1099-DA forms without documenting the offsetting cost basis. Reconciling your filed figures against your 1099-DA totals before submitting your return is the most direct way to check.
No, a CP2000 is an automated proposed adjustment notice based on a data mismatch, not a formal audit, and most are resolved through correspondence once the taxpayer supplies missing documentation. It does not by itself indicate suspicion of intentional wrongdoing.
The notice typically specifies a response deadline of around 30 days from the date printed on the letter, though extensions can sometimes be requested if more time is needed to gather documentation. Missing the deadline risks having the proposed adjustment assessed without further review.
Yes, filing with an accurate, documented cost basis adjustment on Form 8949 that reconciles with your 1099-DA proceeds figures substantially reduces the likelihood of a notice being generated in the first place. The goal is ensuring your reported gain and the broker's reported proceeds are consistent once your basis documentation is factored in.
This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.





























