Crypto Tax Records Checklist: Build an Audit-Ready File

A tax report is only as reliable as the evidence behind its acquisitions, disposals, income and transfers. Save original exports, preserve wallet-level links, document USD valuations and reconcile every tax form to the final ledger. Never treat a missing cost as a confirmed zero without trying to reconstruct it.

Reviewed September 1, 2026. This article answers what to preserve and how to organize it. For the separate question of when records can be destroyed, use the IRS crypto record-retention guide.

Minimum data for every crypto transaction

The IRS digital-assets guidance lists asset type, date and time, units, fair market value and basis as core inputs for gain or loss. Your ledger should preserve more detail than the final tax form displays.

Save original exchange and broker evidence

• complete raw CSV or JSON history for trades, deposits, withdrawals and rewards;
• monthly or annual statements and realized-P&L reports;
• order confirmations showing partial fills and fees;
• account profile, legal entity and account identifier;
• API import date, permissions and pagination coverage;
• corrected exports supplied by support;
• emails for delistings, liquidations and account closure;
• Forms 1099-DA and other information returns.

Do not save only a tax-software export. A normalized ledger may merge, split or relabel source rows. Retain the original data so the transformation can be reproduced and challenged if necessary.

Wallet and transfer evidence proves continuity

A transfer between wallets owned by the same taxpayer is generally not a sale, but the fee can have tax consequences. Preserve the sending and receiving addresses, transaction hash, network, units before and after fees, ownership evidence and any exchange withdrawal/deposit IDs.

Public blockchain data does not identify the beneficial owner automatically. Keep a wallet register that records who controlled each address and during which period. Hardware-wallet purchase receipts or signed messages can help establish control without exposing private keys.

Security rule: never include a seed phrase, private key or unencrypted API secret in a tax archive. Public addresses and read-only exports are enough for tax evidence.

Cost basis and lot-identification records

For every acquisition, preserve purchase price, fees, acquisition time, source and prior basis when property was received by gift, inheritance, transfer or nonrecognition transaction. Later adjustments—wash-sale treatment for tokenized securities, return of capital or corrected income—must remain linked to the affected units.

Specific identification requires timely and adequate records. The IRS digital-asset FAQs explain that unhosted-wallet units must be identified no later than disposition and the records must show that those units were removed. Save standing orders, broker instructions and execution confirmations together.

If no valid identification is available, the applicable default method may control. Do not rewrite lot choices after prices are known.

Evidence for staking, mining and crypto compensation

• date control or dominion was obtained;
• units and asset received;
• USD value and price source at that time;
• validator, pool, employer, customer or protocol;
• service agreement, payslip, invoice or reward statement;
• withholding and employment-tax records where applicable;
• basis created by the income inclusion;
• later sale or transfer of the same units.

The same tokens can create two separate records: ordinary income on receipt and gain or loss on later disposition. Link them so the amount included in income becomes traceable basis rather than being taxed twice.

DeFi, loans and derivatives need contract-level context

A transaction hash alone cannot tell whether a protocol interaction was a taxable exchange, collateral deposit, loan, wrapped-asset conversion, liquidity position or claim of income. Save protocol terms, position IDs, pool composition, debt balances, liquidation notices and the rights represented by received tokens.

For futures and perpetuals, keep opening and closing fills, contract type, quantity, entry and exit prices, fees, funding and the broker's realized P&L. Open positions and snapshots are evidence but should not be counted as closed taxable P&L merely because they appear in the import.

The DeFi audit-trail guide provides a protocol review workflow.

Keep tax forms—but do not treat them as a complete ledger

Preserve every original and corrected Form 1099-DA, 1099-MISC, 1099-NEC, W-2 and K-1. For each, create a reconciliation that identifies included ledger rows and explains unmatched amounts. A broker form can omit basis or wallet history, while a ledger can accidentally duplicate broker proceeds.

The IRS Form 1099-DA explainer says taxpayers must report all digital-asset income, gains and losses whether or not they receive the form. If a form is wrong, retain the original, request a correction and keep correspondence.

Four reconciliations make a report defensible

1. Balance reconciliation: opening units + inflows − outflows = closing units by asset and account.
2. Transfer reconciliation: connect owned-wallet withdrawals to deposits without inventing proceeds.
3. Cash reconciliation: match fiat deposits, withdrawals and business receipts to bank records.
4. Tax-form reconciliation: connect Forms 1099-DA and other statements to the return.

Unmatched items should stay visible. A “missing basis” or “classification review” status is more reliable than silently forcing a zero, deleting a duplicate-looking row or treating every deposit as income. The Form 8949 guide shows how the reconciled disposal detail reaches the return.

Recommended yearly archive structure

2026/
 01-source-exports/
 02-wallet-register/
 03-bank-and-fiat/
 04-valuations-and-fx/
 05-normalized-ledger/
 06-reconciliations/
 07-tax-forms/
 08-filed-return/
 09-notices-and-corrections/
 README-methods-and-open-items.txt

Store original files read-only, keep a working copy for transformations and record software version, mappings and accounting method in the README. Use encrypted backups in at least two locations and test restoration annually.

Crypto records FAQ

Disclaimer: This article is for general informational purposes only and does not constitute tax advice. For individual tax advice, consult a licensed tax professional.