"Noncovered" isn't a temporary glitch — it's a permanent classification.
Many filers, hitting a blank cost basis field for the first time, assume it's just a sync delay — that waiting one more filing season, or re-importing through a different piece of software, will eventually resolve it. But the covered/noncovered determination is based on an asset's actual historical custody path — whether it stayed inside the same regulated account the whole time — and that historical fact can't be changed after it happens. Waiting won't turn an asset that was once moved to a self-custody wallet, or acquired before 2026, back into a covered one. Understanding this early prevents filers from discovering, at the worst possible moment in filing season, that there was never a fix coming.
A basis number "reconstructed" by tax software carries a different legal weight than one a broker reports.
This is where a lot of filers get confused: running transaction history through cost-basis software to produce a number, versus a broker reporting a number on Form 1099-DA, both feel like "a tool calculated this," but their legal standing is completely different. The 1099-DA figure is official data the broker reported by law, and it's what the IRS matching system checks directly. A software-reconstructed number, by contrast, is just the filer's own supporting documentation — it carries no official standing on its own, and its credibility depends entirely on whether the underlying source material survives: exchange history, blockchain records, the timestamp-conversion trail. If questioned later, "the software calculated it" isn't itself an answer — being able to produce the full reconstruction trail is what actually matters.
Future matching systems are likely to check not just whether something was reported, but whether the timestamps themselves make sense.
Current matching largely focuses on whether a disposition's proceeds were reported at all, but one of the easiest places for basis reconstruction to go wrong is timestamp standard mismatch — the 1099-DA records in UTC, while a filer's own exchange export files might be in local time, and the mismatch can manufacture a false anomaly that looks like the same transaction landing in two different tax years. As matching systems lean more on automated rules and less on manual review, this kind of purely formatting-level inconsistency is likely to get flagged even when the actual tax amount owed is completely correct. That means timestamp conversion deserves to be treated as its own separate checklist item when preparing documentation, not an afterthought buried inside the calculation.
The real-world impact here isn't whether you'll underpay tax — it's how much time it takes to prove you didn't.
A blank cost basis field by itself doesn't cost you a dollar in extra tax, as long as you calculate and report correctly yourself. But it dramatically increases how much preparation is needed to prove that correctness, because there's no ready-made answer on the official form — the entire burden of proof sits with you. For investors who've held long-term, traded across multiple platforms, or moved assets between wallets over the years, that preparation can mean digging up exchange export files from several years back and cross-checking them against raw on-chain transaction records — a workload far larger than simply copying numbers off a 1099-DA. Starting early is the only way to keep that workload from spiraling out of control.
The first look at a 1099-DA form usually brings a moment of relief — finally, an official form that pulls the year's trading together in one place. Then comes the scroll down to the Cost Basis column, where half the rows are blank, followed by a call to the exchange's support line that usually ends with some version of "we can't fix that on our end." That answer sounds like a brush-off, but it actually reflects how the rule itself was written — the blank cost basis field comes from a classification called a "covered asset," not from a broker cutting corners.
Under the U.S. digital asset broker reporting rules, a broker can only report complete cost basis for an asset if it was acquired and held continuously within that same broker account, letting the broker's own system track it from acquisition through disposition. An asset gets bumped into the "noncovered" bucket — and its cost basis field goes blank automatically — the moment any of the following happens: it was acquired before January 1, 2026 (outside the current tracking window); it was moved out of broker custody at some point, whether to a self-custody wallet or to another exchange; it went through a protocol-level change, like bridging across chains or being wrapped into another Token form; or it was staked or lent out, breaking the "continuously held in the same account" chain.
The important part: the rule explicitly states brokers are "not permitted to infer, estimate, or reconstruct historical basis they did not track." That means even a heated phone call to customer support won't help — the broker's system is designed so it simply cannot conjure up a number it never recorded. This isn't a customer-service failure; it's a boundary drawn by the rule itself.
A common and dangerous misconception is that a blank cost basis field means a transaction is untraceable. In practice, the 1099-DA still typically reports gross proceeds in full, and gross proceeds alone are enough to anchor wallet clustering, transaction tracing, and discrepancy analysis against the Forms 8949 and Schedule D you file, plus prior-year filings. In other words, a blank basis field only makes "how much tax you owe" opaque — it does nothing to make "whether you reported this transaction at all" invisible to the matching system.
A Form 1099-DA is fundamentally an information return, not an authoritative tax calculation. Regardless of what the form shows, filers remain responsible for reporting every disposition on Form 8949 using independently determined cost basis and holding period — not simply copying whatever number the 1099-DA happens to show. In practice, that means reconstructing basis for every noncovered transaction going back to 2013 using exchange history, blockchain data, and cost-basis software cross-checked against each other; deliberately segregating assets by wallet or account and keeping that segregation consistent over time, rather than reshuffling lots after the fact — the IRS explicitly does not accept after-the-fact lot selection; and normalizing every transaction timestamp to UTC before reconciling, since the 1099-DA's own timestamps are typically recorded in UTC, and a mismatch with your local time zone can manufacture year-boundary discrepancies that don't actually exist.
If this year's 1099-DA came back with large blank patches in the cost basis column, don't wait around for a "corrected" version from the exchange — in most cases there isn't one coming, because these assets are noncovered by definition, not by mistake. What actually helps is reconstructing that missing basis yourself before filing season's matching systems process the broker's data: pull together exchange history, wallet records, and cost-basis software output into one complete reporting package, and keep every step of that calculation on file, because if the IRS's matching system ever flags a discrepancy, that self-assembled documentation is the only thing you'll have to show for it.
⚠️ This article was researched against the most current regulations and official guidance available at the time of writing, but tax rules change frequently, and the applicable rules can vary by jurisdiction and individual circumstance. This content is intended to help you understand concepts and general direction — it does not constitute formal tax or legal advice. Before filing, please verify current rules directly with the official tax authority in your jurisdiction, or consult a qualified tax professional.