When brokers must issue 1099-DA<\/h2>\n
IRS rules require digital asset brokers to issue 1099-DA when they effect sales of digital assets on behalf of customers and the broker has information sufficient to determine the customer’s basis. The original framework covered custodial brokers only. The 2025 final rules expanded the definition to include non-custodial brokers operating on or after 2025-01-01.<\/p>\n
Custodial brokers (Coinbase, Kraken, Gemini, Binance US) have always been in scope. They track customer wallets and can compute basis because they hold the private keys. Non-custodial platforms (some DEX operators) were initially excluded but the final rules expanded coverage.<\/p>\n
If you used only non-custodial wallets (MetaMask, hardware wallets) and never routed trades through a regulated exchange, you may not receive a 1099-DA. You still need to self-report on Form 8949 based on your own transaction records.<\/p>\n
For deeper reading on whether a specific platform will issue you a 1099-DA, see the broker reporting requirements<\/a> explainer.<\/p>\n Turn any PDF statement into a clean sheet<\/p>\r\n Skip the typos and the hours of copying. Our converter handles any bank statement format and outputs Excel, CSV, or QBO for QuickBooks. No file retention, free to try.<\/p>\r\n Convert your statement<\/a>\r\n<\/div><\/div><\/div> The 1099-DA form has roughly 20 fields. The fields that matter for tax reporting are: gross proceeds (Box 1a), cost basis (Box 1b), date of acquisition (Box 1c), date of sale (Box 1d), proceeds from each transaction, the broker’s name and EIN, and the customer’s name and TIN.<\/p>\n Box 1a lists the gross proceeds from each sale. Box 1b lists the cost basis for each sale. When the broker cannot determine basis, Box 1b may be blank, and you as the taxpayer are responsible for supplying basis using your own records.<\/p>\n Box 1e covers adjustments. This box can hold amounts the IRS needs to know but the broker cannot pre-compute. Most crypto investors leave this box blank, but the broker is required to populate it for certain transaction types.<\/p>\n The complete form-level reading is in the form explainer<\/a>. The differences between 1099-DA and 1099-B are in the comparison article<\/a>.<\/p>\n The IRS allows four cost basis methods for digital assets: First-In-First-Out (FIFO), Last-In-First-Out (LIFO), Highest-In-First-Out (HIFO), and Specific Identification (Spec ID). Each method produces a different gain or loss for the same set of transactions.<\/p>\n FIFO assumes the earliest-acquired units are sold first. This is the IRS default and what most brokers will report. LIFO assumes the most-recently-acquired units are sold first, which can defer gains in a rising market.<\/p>\n HIFO uses the highest-cost units first, which minimizes taxable gain. Spec ID lets you choose which specific lot to apply to each sale, giving you maximum flexibility but requiring detailed records.<\/p>\n For most individual crypto investors, FIFO is correct. Active traders with detailed transaction logs may benefit from Spec ID. The choice method has to be elected consistently and documented. See cost basis methods<\/a> for the full reading.<\/p>\n Reconciling a 1099-DA to your bank statements is the most manual step. The 1099-DA lists each sale or exchange as one line, while your bank statement shows the cash side as one or more lines (typically an ACH debit to a bank account, a wire out, or a card charge to a crypto exchange).<\/p>\n Match each 1099-DA row to the corresponding bank-statement row by date and dollar amount. The match works as follows: a 1099-DA line dated 2025-06-15 for $5,000 will match a bank-statement ACH debit dated 2025-06-15 for $5,000 going to Coinbase Direct.<\/p>\n Bank-statement label differences complicate this. A bank may label the transfer as ACH DEBIT WEB to Coinbase Inc., while the 1099-DA labels it as digital asset sale. The reconciliation must match the underlying event rather than the label.<\/p>\n Easy Statement Sheet reads bank-statement rows into a four-column output and preserves the ACH SEC code in the description column. That makes the rule-based reconciliation scriptable. The 1099-DA-to-bank-statement reconciliation explainer<\/a> walks through this end-to-end.<\/p>\n Three tools dominate the crypto tax software space: CoinTracker, Koinly, and TokenTax. Each handles 1099-DA import, sync with major exchanges and wallets, applies cost basis methods, and exports to Form 8949-ready format.<\/p>\n CoinTracker is the most beginner-friendly. It has direct integrations with Coinbase, Kraken, Gemini, and Binance, plus wallet sync via CSV. Plans start at $49\/year for 100 transactions. The interface is clear and the support is responsive.<\/p>\n Koinly is the next step up in transaction volume. It handles 100,000+ transactions efficiently and supports cost basis methods beyond FIFO. Plans start at $49\/year for 3,000 transactions. Best for active traders.<\/p>\n TokenTax is the highest-volume tool. It supports unlimited transactions on the most expensive plan and has the broadest exchange integration. Plans start at $65\/year for 100 transactions. Best for traders with high transaction counts and complex multi-exchange activity.<\/p>\n The complete comparison of these tools is at CoinTracker vs Koinly vs TokenTax<\/a>. The detailed workflows for bookkeepers are at crypto tax workflow for bookkeepers<\/a>.<\/p>\n Federal tax is the headline concern but state-level treatment varies. Most states follow federal rules for capital gains, including for digital assets. Some states do not have a state income tax (Texas, Florida, Washington). Some states have additional digital-asset-specific rules (New York’s BitLicense-related disclosures, California’s pending digital-asset framework).<\/p>\n States that follow federal pass-through treatment generally let you report the digital-asset gain on the federal Form 8949 and copy the result to the state return. States with no income tax (TX, FL, WA, NV, SD, WY, AK, TN, NH) generally have no state-level capital-gains tax either, but you still file federal.<\/p>\n States with additional digital-asset disclosure (California, New York) may require you to file the federal 1099-DA proceeds on the state return as well, or include a separate disclosure worksheet. The threshold depends on the state, and the requirement changes year over year.<\/p>\n For state-specific 1099-DA treatment, see the dedicated state-by-state guide<\/a>. When in doubt, run your tax situation past a CPA familiar with both federal and state digital-asset rules.<\/p>\n Step one: collect your 1099-DA forms from each broker by January 31 of the filing year. Step two: collect exchange CSV exports for any transactions not covered by 1099-DA. Step three: collect wallet CSV exports for any non-custodial activity.<\/p>\n Step four: import everything into a crypto tax tool (CoinTracker, Koinly, TokenTax). Run cost basis calc using FIFO as the default. Step five: export the Form 8949 PDF the tool produces. Step six: import the PDF into your tax software (TurboTax, H&R Block, TaxAct) or hand it to your CPA.<\/p>\n Step seven: file Form 8949 with the IRS. The form is one row per digital-asset transaction. Schedule D carries the totals. Step eight: reconcile cash flows to your bank statements. Cash inflows from crypto sales should match the proceeds; cash outflows to exchanges should match your purchase history.<\/p>\n Easy Statement Sheet handles bank-statement reading across this workflow. For a deeper DIY walkthrough, see DIY crypto tax reporting<\/a>.<\/p>\n Error one: missing 1099-DA from a broker you used. Most common cause is that the broker has your old address or your tax-ID has changed. Contact the broker directly to request a corrected form. The deadline for the broker to reissue is mid-February of the filing year.<\/p>\n Error two: 1099-DA Box 1b is blank. The broker does not have basis data on file. You must supply basis using your own records. Most tax tools can ingest your exchange CSV to compute basis and produce the missing Box 1b values.<\/p>\n Error three: 1099-DA shows transactions that did not constitute a taxable event. Crypto-to-crypto swaps (BTC to ETH) are taxable events at the time of the swap, but staking rewards and airdrops are also taxable on receipt. The broker may report all of these, requiring you to mark which are taxable events and which are transfers.<\/p>\n Error four: bank statement does not match the 1099-DA cash flow. Most common cause is that the broker removed fees before reporting proceeds. The bank statement may show the full cash transfer while the 1099-DA reflects proceeds after fees. Reconcile by adding fees back to the 1099-DA proceeds for tax purposes.<\/p>\n Do I need to report if my broker didn’t send me a 1099-DA? Yes, you are required to report all taxable digital-asset transactions, regardless of whether the broker sent a form. If you sold more than the IRS-reporting threshold (set per year), include the gain even without a 1099-DA.<\/p>\n What if I moved my coins between wallets, not exchanges? Transfers between wallets you own are not taxable events. Receiving coins in a transfer is not income. The 1099-DA captures only sales or exchanges. Most brokers will not include transfers between your own wallets in their 1099-DA.<\/p>\n Can I use a different cost basis method than FIFO? Yes, but you must elect consistently and document the choice. The IRS accepts FIFO as default and lets you elect LIFO, HIFO, or Spec ID. Make the election on your first return that uses the non-default method.<\/p>\n What about staking and airdrops? Staking rewards and airdrops are taxable as ordinary income at fair market value when received. The 1099-DA is not the right form for these; they go on Schedule 1 and Schedule D. Most tax tools handle this automatically.<\/p>\n 1099-DA is the IRS form digital asset brokers must use to report customer transactions starting in 2025. The form captures gross proceeds, cost basis, dates of acquisition and sale, and adjustments. Reconciling to bank statements is the most manual step in the workflow.<\/p>\n For the form mechanics, see the 1099-DA explainer<\/a> and the form-level read<\/a>. For broker requirements, see broker reporting requirements<\/a>. For cost basis methods, see cost basis methods<\/a>.<\/p>\n For the bank-statement side, the complete US bank payment rails guide<\/a> covers ACH and wire cash flows. The complete MCC guide<\/a> covers merchant category codes on credit-card statements.<\/p>\n Easy Statement Sheet reads bank statements and credit-card statements into a clean four-column output that surfaces cash flows from crypto exchanges via ACH, wire, or card rails. The first three conversions are free, no card required.<\/p>\n For converting supported bank statement or credit-card statement PDFs into the four canonical columns, Easy Statement Sheet is one practical option. Choose the output by what happens next: XLSX for human review or spreadsheet analysis, CSV for software and data pipelines, Google Sheets-compatible for cloud-spreadsheet work, and QBO for QuickBooks import.<\/p>\n The service runs entirely in volatile memory; uploaded statement contents and converted financial data are not persistently retained.<\/p>\n Independent of any specific tool, the workflow is the same: extract, validate against the printed running balance, and route to the format your downstream workflow expects. Tools that preserve the four canonical columns plus the merchant category code label and rail label inline within the merchant description make the rule-based reconciliation layer scriptable across many clients.<\/p>\nReading your 1099-DA form fields<\/h2>\n
Reading the form<\/h3>\n
![\"1099-DA](\"https:\/\/easystatementsheet.com\/blog\/wp-content\/uploads\/2026\/10\/pillar-4211-body-brand-v2.jpg\" "\\"\\"")
Cost basis methods: FIFO, LIFO, HIFO, Spec ID<\/h2>\n
Reconciling 1099-DA to bank statements<\/h2>\n
Crypto tax tools: CoinTracker, Koinly, TokenTax<\/h2>\n
State-level differences<\/h2>\n
Step-by-step DIY workflow<\/h2>\n
Common errors and what to do about them<\/h2>\n
Frequently asked questions<\/h2>\n
The bottom line<\/h2>\n
How this fits the conversion workflow<\/h2>\n