Form 1099-DA represents a fundamental shift in how the IRS enforces crypto tax compliance. For years, crypto reporting relied largely on self-reporting, inconsistent software outputs, and incomplete data. That era is ending. With Form 1099-DA, the IRS is now receiving third-party transaction data directly from registered crypto brokers.
In theory, tax software should be able to ingest this information, reconcile it with a taxpayer’s records, and produce compliant reporting. In reality, the structure of Form 1099-DA creates legal and practical problems that most software platforms are not equipped to solve.
What Form 1099-DA Actually Requires
Each registered broker is required to report gross proceeds from digital asset dispositions that occurred on its platform. These forms are issued per exchange, not per taxpayer. A taxpayer using multiple exchanges will receive multiple 1099-DAs, each reflecting only a slice of their activity.
Critically, most 1099-DAs do not include reliable cost basis. Some include partial or estimated basis, others explicitly state that basis is not reported to the IRS. The IRS matching systems, however, treat proceeds as authoritative.
This creates an immediate compliance problem. The IRS has numbers. If the taxpayer’s return does not match those numbers, the system assumes underreporting.
Why Software Cannot Simply “Match the 1099”
Most tax software was designed around a single consolidated dataset. Import transactions, calculate gains, generate one Form 8949, and move on. Form 1099-DA breaks that model.
Each 1099-DA requires its own Form 8949 grouping. In addition, taxpayers must separately report all digital asset activity not covered by a 1099-DA, including DeFi trades, self-custody wallet activity, protocol interactions, and transactions on non-reporting platforms.
That means a compliant return may require multiple 8949s, each tied to a specific reporting source, plus an additional 8949 for everything else.
Most software does not enforce this separation. Some will attempt to blend transactions. Others will overwrite internal calculations to force proceeds to match reported totals. Either approach creates legal risk.
The Mismatch Problem Is Built In
Even when a taxpayer reports correctly, mismatch notices are likely. The IRS matching system does not understand context. It does not know that cost basis came from another exchange, a wallet transfer, or an early acquisition.
If Coinbase reports $300,000 in proceeds and the taxpayer reports $40,000 in net gains, the system flags the difference. Software cannot fix that. Legal framing and documentation are required to resolve it.
We are already seeing cases where taxpayers receive proposed assessments based entirely on gross proceeds.
Why This Becomes a Legal Issue
Once a return is filed, incorrect structuring is not a software issue. It is a legal exposure. Statements made on a return become part of the taxpayer’s record. Automated notices escalate. Penalties accrue. Audits follow.
Relying on software to reconcile incomplete third-party reporting without understanding enforcement mechanics is a mistake. At a certain point, professional judgment is required to determine how to report defensibly.
The Bottom Line
Form 1099-DA assumes a level of data completeness and consistency that does not exist in crypto markets. Tax software is not designed to resolve legal mismatches between partial third-party reporting and full economic reality.
When reporting becomes fragmented, software stops being a solution and starts being a risk amplifier.
At Gordon Law, we work with taxpayers facing crypto audits, mismatch notices, and enforcement actions tied to Form 1099-DA reporting. If your reporting involves multiple exchanges, self-custody, or DeFi activity, relying solely on software may expose you to unnecessary legal risk. This is where strategy matters.
