Most retail discussion of "crypto audits" treats the topic as binary: either the IRS audits you (catastrophic) or it does not (fine). The reality is that an IRS examination is a structured process with specific documentary requests, and the difference between a quick close and a multi-year ordeal is almost entirely determined by what the taxpayer can produce on the first information document request (the IDR).
This article is the practitioner-level version of "what records to keep". It walks through the four records the IRS will, in order, ask for in a crypto-related examination, drawing on the digital assets compliance pages and the cryptocurrency examination guidance the IRS has released through its Large Business and International division.
How the IRS picks crypto returns for examination
The IRS uses several signals to identify crypto-related returns worth examining. Reading the Treasury Inspector General for Tax Administration’s 2023 audit report on virtual currency compliance, the most important are:
- A "Yes" answer to the digital asset question on Form 1040 with no Form 8949 attached.
- 1099-MISC or 1099-K issued by a centralised exchange that does not match the income reported on the return.
- Wallet addresses associated with on-chain activity that the IRS’s contracted blockchain analytics provider can attribute to the taxpayer.
- From 2026 onward, mismatches against the data reported under the OECD’s Crypto Asset Reporting Framework.
None of these is a guarantee of examination, and most discrepancies are resolved by automated correspondence (a CP2000 letter) rather than a full examination. But the four records below are what the auditor or revenue agent will ask for if it does escalate.
Record 1: complete transaction history per wallet and per exchange
The first IDR in any crypto examination asks for the complete transaction history of every wallet and exchange account the taxpayer controlled during the tax years under examination. "Complete" means every event, including transfers between the taxpayer’s own wallets, with timestamps, asset symbols, quantities, and the prices used.
The format the IRS prefers, based on practitioner reports of recent examinations, is a CSV per source with consistent columns: timestamp, action (buy / sell / send / receive / reward), asset, quantity, fiat value, fee, counterparty (where known). The taxpayer is expected to be able to produce this on demand for any year still within the statute of limitations (three years from filing for most returns; six years for substantial omissions per section 6501).
The single most common reason taxpayers cannot produce this record is that they have switched exchanges and lost the historical exports. The defensive habit is to download and retain every available export at the end of each calendar year, regardless of whether you intend to file. Storage is essentially free; the cost of reconstructing a year of trades from chain data five years later is high.
Record 2: per-disposal cost basis substantiation
For every disposal reported on Form 8949, the IRS will request the cost basis substantiation. Per Publication 551, the taxpayer must be able to show:
- The date the disposed unit was originally acquired.
- The cost basis on that acquisition date, in USD.
- The cost basis method applied to identify the disposed unit (FIFO, or specific identification with the four-piece record from Revenue Procedure 2024-28).
- The fair market value at disposal, in USD.
The four-piece record matters because under the per-wallet rule from 2025, taxpayers using anything other than FIFO must have specifically identified the lot at the time of the disposal. After-the-fact reconstruction does not satisfy the rule. A tax tool that just produces FIFO numbers without keeping the lot identification per disposal cannot demonstrate specific identification, and the IRS will fall back to FIFO.
Record 3: income event substantiation
For staking rewards, lending interest, airdrops and hard-fork receipts reported as ordinary income on Schedule 1, the IRS will request:
- Date of receipt of each event.
- Quantity received.
- Fair market value at receipt, in USD.
- Source of the price used (the IRS prefers a third-party price feed, not the platform’s internal price).
The most common deficiency in this record set is bulk reporting: a taxpayer who received daily ETH staking rewards across 365 days and reported the total as a single line item, valued at the year-average price. Per Revenue Ruling 2023-14, each event is its own income recognition at the spot price on the day. Tools that export a single line item are not producing a substantiated record.
Record 4: same-owner transfer log
The fourth record is the one most taxpayers do not realise they need. Transfers between wallets controlled by the same taxpayer are not taxable events, but they look identical, on the source chain or in an exchange CSV, to a transfer to a third party. The taxpayer must be able to demonstrate that the destination wallet was their own.
The acceptable evidence in practice is a list of every wallet address the taxpayer controls, plus, for each transfer flagged as same-owner, the source address, destination address, timestamp and transaction hash. The auditor verifies the destination address against the taxpayer’s control list.
The defensive habit is to maintain a single document - a spreadsheet, a JSON file, anything that will survive the years - listing every wallet address the taxpayer has ever controlled, with the date it was created, the platform it was created on, and (if applicable) the date it was abandoned. Hardware wallets and software wallets the taxpayer set up themselves both go on this list.
How the four records fit together
A correctly run crypto tax workflow produces all four records as a side effect of the calculation. The tax tool ingests the per-wallet transaction histories (Record 1), applies a cost-basis method with per-lot identification (Record 2), records every income event with a third-party price source (Record 3), and lets the user flag same-owner transfers (Record 4).
This is the architecture the SafeFinance Crypto Tax Calculator is designed around. Every disposal in the report has an audit trail back to the original acquisition lot, every income event has the price source and timestamp, and the user can mark transfers as same-owner before the report is run. The exported PDF and CSV are the four records, in the format the IRS asks for.
The point of mentioning the tool is not the upsell; it is that the four records above are the actual deliverable of any compliant crypto tax process. A taxpayer who can produce them in the first response to an IDR closes the examination quickly. A taxpayer who cannot is in for a much longer process. The tool you use is less important than whether the tool you use produces all four.