The IRS sent a notice for $14,000 in unreported crypto gains. The exchange reported the transactions via 1099-DA, but you didn’t include them on your tax return. This is the most common crypto tax mistake, and it’s easily avoided.
Crypto tax mistakes trigger IRS notices. The 7 most common mistakes are: forgetting exchange-to-exchange transfers, wrong cost basis method, forgetting staking, forgetting crypto-to-crypto trades, and 3 more. This page covers each mistake, the notice it triggers, and how to fix it.
The 7 most common crypto tax mistakes: forgetting exchange-to-exchange transfers, wrong cost basis method, forgetting staking and airdrops, forgetting crypto-to-crypto trades, forgetting DeFi transactions, ignoring the 1099-DA, and skipping the audit archive. The recon cutoff tool’s per-transaction export catches most of these.
Each mistake has a specific IRS notice pattern. The recon cutoff tool’s per-transaction export is the source of truth for the reconciliation. For investors who have already received a notice, the fix is to amend the prior return using Form 1040-X.
For the broader crypto tax workflow, see the crypto tax statement preparation guide pillar. For the 1099-DA, see the 1099-DA reporting guide. For cost basis methods, see the cost basis methods guide.
Mistake 1: Forgetting Exchange-to-Exchange Transfers
Transferring BTC from Coinbase to Kraken is NOT a taxable event. But trading BTC for ETH on either exchange IS a taxable event. The recon cutoff tool’s exchange export marks transfers separately from trades. Forgetting the trades is the most common crypto tax mistake.
The IRS notice: CP2000 (underreported income). The notice shows the unreported trades from the 1099-DA. The fix: amend the prior return using Form 1040-X. The recon cutoff tool’s per-transaction export is the source of truth for the amendment.
How to Avoid Mistake 1
Keep the recon cutoff tool’s per-transaction export for every exchange. Reconcile the 1099-DA against the export. The reconciliation catches missing trades before the IRS does.
Mistake 2: Wrong Cost Basis Method
The IRS default is FIFO, but HIFO often produces a lower tax bill. The catch: HIFO requires specific identification of the lot sold, which means detailed records. The recon cutoff tool’s per-transaction export includes the lot ID, which makes Specific ID possible. Without it, you’re stuck with FIFO.
The IRS notice: CP2000 (underreported income) or a smaller tax bill than expected. The fix: amend the prior return using Form 1040-X with the corrected cost basis method.
How to Avoid Mistake 2
Check the cost basis method every year, not just the first year. The recon cutoff tool’s per-transaction export includes the lot ID. The tax software applies the method to each sale.
Turn any PDF statement into a clean sheet
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.
Convert your statementMistake 3: Forgetting Staking and Airdrops
Staking rewards, airdrops, and mined crypto are income at fair market value on the day received. Forgetting them is the most common cause of IRS notices for crypto investors with staking accounts. The recon cutoff tool’s exchange export marks these with a different category.
The IRS notice: CP2000 (underreported income) for the staking income. The fix: amend the prior return using Form 1040-X with the staking income added to Schedule B or Schedule C.
How to Avoid Mistake 3
The recon cutoff tool’s per-type handling separates staking from capital gains. The tax software applies the income tax rate to staking and the capital gains rate to trades. The recon cutoff tool’s per-type export is the source of truth for the categorization.
Mistake 4: Forgetting Crypto-to-Crypto Trades
Trading BTC for ETH is a taxable event, even if no USD was involved. The IRS treats the BTC as sold at the fair market value of ETH at the time of trade. The recon cutoff tool’s exchange export shows these as two transactions (BTC sold, ETH bought), which the tax software handles correctly.
The IRS notice: CP2000 (underreported income) for the BTC sale. The fix: amend the prior return using Form 1040-X with the BTC sale added to Form 8949.
How to Avoid Mistake 4
The recon cutoff tool’s per-transaction export shows every trade, including crypto-to-crypto. The tax software generates the Form 8949 entries automatically. The recon cutoff tool’s per-trade handling catches crypto-to-crypto trades that are easy to overlook.
Mistake 5: Forgetting DeFi Transactions
DeFi transactions (liquidity pools, yield farming, lending) are taxable events. The 1099-DA does NOT report DeFi transactions. The investor is responsible for tracking them. The recon cutoff tool’s per-DeFi handling reads the DeFi protocol’s transaction history.
The IRS notice: CP2000 (underreported income) for the DeFi gains. The fix: amend the prior return using Form 1040-X with the DeFi transactions added to Form 8949.
How to Avoid Mistake 5
Use a DeFi-specific tax tool (e.g., Koinly, TokenTax) that reads the protocol’s transaction history. The recon cutoff tool’s per-DeFi export is the input to the tax software. The recon cutoff tool’s per-DeFi handling covers Uniswap, Aave, Compound, and others.
Mistake 6: Ignoring the 1099-DA
The 1099-DA is filed with the IRS. Ignoring it triggers an IRS notice. The recon cutoff tool’s archive feature helps you match the 1099-DA against your tax return. The fix: reconcile the 1099-DA before filing.
The IRS notice: CP2000 (underreported income) for the 1099-DA amounts. The fix: amend the prior return using Form 1040-X.
How to Avoid Mistake 6
Reconcile the 1099-DA against your tax return before filing. The recon cutoff tool’s per-transaction export is the source of truth for the reconciliation. The reconciliation takes 30-60 minutes per exchange.
Mistake 7: Skipping the Audit Archive
Crypto audits are increasing. The IRS has a dedicated crypto team since 2021. Skipping the audit archive is the most common cause of audit failure for crypto investors. The recon cutoff tool’s archive feature stores exchange statements, transaction histories, and the converted files.
The IRS notice: audit notice (full audit). The fix: respond within 30 days using the archived records. The recon cutoff tool’s per-archive handling makes the response faster.
How to Avoid Mistake 7
Keep the recon cutoff tool’s archive for at least 7 years. The archive includes the original exchange statement, the converted file, the reconciliation worksheet, and the tax return. The recon cutoff tool’s per-archive handling stores all 4 in a consistent structure.
What to Do If You Got a Notice
If you got a notice, the 3-step response is: read the notice, pull the archive, amend the return. The recon cutoff tool’s per-archive handling makes the response faster.
Step 1: Read the Notice
The IRS notice specifies the tax year, the type of mistake, and the proposed adjustment. Common notices for crypto: CP2000 (underreported income), audit notice (full audit), or a smaller tax bill than expected. The notice tells you which mistake you made.
Step 2: Pull the Archive
The recon cutoff tool’s per-archive handling stores the original exchange statement, the converted file, the reconciliation worksheet, and the tax return. Pull all 4 from the archive. The recon cutoff tool’s per-archive search finds the files in seconds.
Step 3: Amend the Return
Use Form 1040-X to amend the prior return. Attach the corrected Form 8949 and Schedule D. The recon cutoff tool’s per-archive handling provides the corrected amounts. The amendment takes 30-60 minutes per year.
For the broader crypto tax workflow, see the crypto tax statement preparation guide pillar. For the 1099-DA, see the 1099-DA reporting guide . For cost basis methods, see the cost basis methods guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
Related: complete 1099-DA crypto tax guide
This topic is part of the broader 1099-DA and crypto-tax cluster on this site. The consolidated hub for the entire topic, including the form mechanics, broker requirements, cost basis methods, reconciling to bank statements, and state-level differences, now lives in the complete 1099-DA crypto tax reporting guide.
For related reading, the complete US bank payment rails guide covers ACH and wire cash flows from crypto exchanges, and the complete MCC guide covers merchant category codes on credit-card statements. The expanded bank statement anatomy pairs naturally with this hub.
More on the broader cluster
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes.
Decision framework for this topic
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Related reading and broader clusters
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Turn PDF Bank Statements Into Workable Spreadsheets
Your bank statement is a mess of numbers, but your books shouldn't be. Use our converter to get Excel, CSV, or QBO files — ready for QuickBooks.
Try It Free Now
