The IRS is auditing your 2022 return. You need 5 years of crypto exchange statements, organized by exchange and year, and the audit response is due in 30 days.
Crypto audits are increasing. The IRS has a dedicated crypto team since 2021. The audit window is 3 years (standard) or 6 years (substantial understatement). This page covers the IRS-ready archive, the 30-day audit response, and how the recon cutoff tool’s archive feature handles crypto.
Crypto audits are increasing. The IRS has a dedicated crypto team since 2021. The audit window is 3 years (standard) or 6 years (substantial understatement) for crypto. The recon cutoff tool’s archive feature stores exchange statements, wallet addresses, transaction hashes, and cost basis records.
Audit-ready crypto records need 4 things: exchange statements, wallet addresses, transaction hashes, and cost basis records. Missing any of the 4 is the most common cause of audit failure for crypto investors. The recon cutoff tool’s per-archive handling stores all 4 in a consistent structure.
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 IRS Crypto Audit Team
The IRS has had a dedicated crypto team since 2021. The team focuses on high-income crypto investors (>$10K in transactions per year) and on-chain analysis. The team has issued thousands of notices and conducted hundreds of full audits since 2021.
The IRS crypto team uses on-chain analysis to find unreported transactions. They trace wallet addresses, identify exchange accounts, and match the on-chain activity to the 1099-DA filings. The team also matches the 1099-DA against the tax return. Mismatches trigger notices.
The 3 Audit Triggers
3 things trigger a crypto audit.
Trigger 1: 1099-DA Mismatch. The 1099-DA shows a different amount than the tax return. The fix: reconcile the 1099-DA before filing. The recon cutoff tool’s per-transaction export is the source of truth for the reconciliation.
Trigger 2: On-Chain Analysis. The IRS traces wallet addresses to find exchange accounts. If the on-chain activity is higher than the reported activity, the IRS sends a notice. The fix: track on-chain activity in the archive. The recon cutoff tool’s per-wallet handling reads the wallet’s transaction history.
Trigger 3: Third-Party Reporting. Banks, brokers, and crypto exchanges report to the IRS. The matching is automated. The fix: keep the archive current. The recon cutoff tool’s per-archive handling updates the archive automatically.
The 4 Audit-Ready Records
Audit-ready crypto records need 4 things. Each is a separate file in the archive.
Record 1: Exchange Statements
Exchange statements are the PDFs or CSVs from the exchange. Coinbase issues a Tax Report CSV. Kraken issues a Ledger CSV. Gemini issues an Account Statement CSV. Robinhood issues a Tax Document PDF. The recon cutoff tool’s per-exchange handling reads each format and normalizes the output.
Record 2: Wallet Addresses
Wallet addresses are the public addresses of self-custody wallets. The recon cutoff tool’s per-wallet handling reads the wallet’s transaction history. The archive stores the wallet address and the corresponding transactions.
Record 3: Transaction Hashes
Transaction hashes are the on-chain identifiers for each transaction. The recon cutoff tool’s per-blockchain handling reads the blockchain’s transaction history. The archive stores the transaction hash and the corresponding on-chain activity.
Record 4: Cost Basis Records
Cost basis records are the lot ID and the original price for each purchase. The recon cutoff tool’s per-transaction export includes the lot ID. The archive stores the cost basis records alongside the exchange statements.
From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start ConvertingThe 30-Day Audit Response
When the IRS sends an audit notice, the response is due in 30 days. The 5-step response uses the archive.
Step 1: Read the Notice
The notice specifies the tax year, the type of mistake, and the proposed adjustment. The recon cutoff tool’s per-archive handling identifies which year and which mistake the IRS is auditing. The response addresses the specific year and mistake.
Step 2: Pull the Archive
The recon cutoff tool’s per-archive handling retrieves the 4 records (exchange statements, wallet addresses, transaction hashes, cost basis records) for the affected year. The archive search takes 2-3 minutes.
Step 3: Reconcile the Affected Transactions
The reconciliation worksheet shows which transactions match the IRS’s records and which don’t. The recon cutoff tool’s per-reconciliation handling generates the worksheet from the 4 records. The reconciliation takes 30-60 minutes.
Step 4: Prepare the Response
The response includes the 4 records, the reconciliation worksheet, and any additional documentation. The recon cutoff tool’s per-response handling generates the response document. The response is filed via the IRS audit portal or by mail.
Step 5: Follow Up
The IRS might ask follow-up questions. The recon cutoff tool’s per-archive handling makes the follow-up faster because all the documents are already organized. The follow-up response is due within 30 days.
The 7-Year Archive Rule
The standard 3-year audit window closes fast. The 6-year window for substantial understatement closes slower. The 7-year archive rule covers both windows plus a buffer for late-filed returns. The recon cutoff tool’s archive feature defaults to 7 years of retention.
The archive is in cloud storage (Google Drive, Dropbox, or Box). The folder structure is: client name (or self) / year / record type. The recon cutoff tool’s per-folder handling creates the folder structure automatically.
A common failure mode bookkeepers report is treating this as a single operation rather than a chain of dependent steps. The temptation is to find a tool that ‘just works’ and stop investigating the mechanism.
The result is a wrong-fix cycle: the tool gives partial output, the bookkeeper spends 30+ minutes troubleshooting, the fix is for the wrong step, and the same error recurs on the next statement. The fix: identify which step failed and apply the right intervention to that step.
Common Crypto Audit Mistakes
3 mistakes crypto investors make on audit prep.
Archiving only the exchange statements. The exchange statements are 1 of the 4 records. The fix: archive all 4 (exchange statements, wallet addresses, transaction hashes, cost basis records). The recon cutoff tool’s per-archive handling covers all 4.
Not keeping 7 years. The 6-year window for substantial understatement is the long pole. The fix: keep 7 years. The recon cutoff tool’s per-archive handling defaults to 7 years.
Storing archives in personal accounts. The archive should be in a business or personal account that’s accessible. Personal accounts might be inaccessible. The fix: store the archive in a stable, accessible location.
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 the tax software, see the crypto tax software comparison 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
