Exporting Transaction History for Taxes

Overview

If you hold cryptocurrency on a hardware wallet and you're preparing taxes, exporting transaction history is a necessary step. This guide explains practical ways to get a usable CSV of on-chain activity (incoming, outgoing, swaps, staking rewards) so your tax software or accountant can process gains and income. I’ve worked with multiple wallets since 2018 and, in my testing, the process usually takes less than 30 minutes for a single account — and longer if you have many addresses or DeFi activity.

Why export as CSV? Because CSV files are a portable, human-readable format that most tax tools accept. They let you keep a record that matches on-chain transactions (tx hashes), timestamps, amounts, and destination addresses — which is what tax preparers ask for. But not all exports are identical. Token swaps, DeFi interactions, and multi-hop trades can look messy without cleanup.

Before you export: prep & security

Confirm device firmware is authentic and up to date (see firmware update & verify).
Use a trusted computer or a clean profile on your browser when connecting the device.
Never enter or export your seed phrase or private keys. Exports are read-only and should never require revealing private keys.
Prefer wired USB connections for desktop exports. Bluetooth is convenient for mobile but has a larger attack surface (see connections: USB / Bluetooth / NFC).

And make a mental checklist: which accounts do you need (BTC, ETH, other chains), date range for the tax year, and whether you need raw transaction CSVs or an aggregated gains report.

How to: Step-by-step export (companion app CSV)

This section describes the typical flow in a hardware wallet's companion app when exporting a CSV. UI labels vary by app, but the high-level steps are consistent.

Connect your hardware wallet by cable (recommended) and unlock it.
Open the desktop companion app and allow the app to access accounts (this is read-only; you are not sharing private keys).
Navigate to Accounts (or Activity/Transactions) and choose the account you want to export.
Look for an Export or Download button and choose CSV (or Export transactions).
Select the date range if available (use the full tax year to avoid missing entries).
Save the CSV to a secure location and give it a clear filename (e.g., 2025_crypto_wallet_accountA.csv).

Notes from my testing:

Some apps export one account at a time. If you have multiple accounts (e.g., separate BTC and ETH accounts), repeat the process and then merge CSVs in a spreadsheet.
CSV rows typically include: date/time (UTC), transaction hash, incoming/outgoing amount, token symbol, and counterparty address. DeFi interactions may appear as multiple rows for a single logical trade.

Other methods: block explorers & third-party tax tools

If the companion app misses an on-chain event (some wallets don't index every token or contract interaction), you can export transaction history from a block explorer by address. This is slower but raw and authoritative (on-chain data by tx hash).

Third-party tax tools accept either (a) CSV uploads or (b) read-only address/xpub imports. Read-only imports are safer because you never hand over private keys. But check compatibility — some tools need specific CSV column names or an import template. See third-party compatibility for integration tips.

But which route is right? If you have simple send/receive history, the companion-app CSV plus a quick verify on-chain is enough. If you have active DeFi, staking, or many token swaps, a tax tool that can parse contract logs will save hours.

Reconciling and verifying exported CSVs

Export, then verify. Always.

Match transaction counts and balances against a block explorer for sample tx hashes.
Check for duplicates. If you import exchange and wallet records into the same tax tool, you might double-count transfers.
Look for missing token decimals or incorrectly formatted quantities (common with low-liquidity tokens).

Simple reconciliation checklist:

Total number of transactions per account matches the app and explorer.
Beginning and ending balances for the tax year line up.
Major transfers between your own addresses are marked as transfers (not taxable disposals in many jurisdictions).

If something doesn’t match, export again and sample 5–10 tx hashes on a block explorer.

Multi-account, multisig and advanced setups

Multisig (multi-signature) wallets and aggregated setups complicate exports. With multisig you may need to gather signed transaction records or collect transaction history from each cosigner's compatible interface. Some multisig configurations require a specialized explorer or aggregator to reconstruct the precise flow of funds.

For multi-account single-sig setups, export each account separately and merge CSVs. Label columns clearly (account name / address) so your tax tool can track cost basis per address.

For step-by-step multisig guidance see multisig setup.

Privacy and security considerations

Never upload private keys or seed phrases to any cloud service or tax site. Period.
Upload CSVs only to reputable, read-only tax tools or hand the CSV to your accountant via encrypted email or secure file share.
If you must allow a third-party to read transactions, prefer address/xpub import over uploading device-backed files.
Confirm the companion app and tax tool are genuine (link to firmware verification and third-party-compatibility).

But remember: CSVs include addresses and transaction history, which reveal on-chain balances. Treat them like sensitive financial documents.

Common mistakes to avoid

Importing exchange CSVs and wallet CSVs without deduplicating internal transfers.
Assuming token swaps are single trades; DeFi swaps can show as multiple on-chain actions (approval, swap, liquidity moves).
Forgetting to export staking rewards or airdrops that may be reported separately.
Using an unverified third-party tool without checking read-only options.

FAQ

Q: Can I recover my crypto if the device breaks and I still have a CSV? A: The CSV is a record only. Recovery requires your seed phrase or backed-up private keys. See restore & recover.

Q: Will the CSV include every token and DeFi action? A: Not always. Token transfers and contract-level events can be omitted or shown in raw form. If you use DeFi heavily, expect some manual reconciliation.

Q: Is it safe to connect my hardware wallet to a tax tool? A: Only if the tool uses read-only address imports or watch-only keys. Never provide private keys or seed phrases.

Q: Which method is best: companion app, block explorer, or tax tool? A: It depends. Companion app exports are fastest for basic history. Block explorers are authoritative for spot checks. Tax tools help map trades and compute gains automatically. Choose based on complexity.

Summary & next steps

Exporting your hardware wallet transaction history into CSV for taxes is straightforward if you follow security habits and verify the data. Start by updating and verifying your device firmware (firmware update & verify), then export per-account CSVs from the companion app and reconcile with on-chain explorers. Use a trusted tax tool for heavy DeFi activity or hand a clean CSV to your CPA.

Ready to export? Check the app first (see Ledger Live download & install for setup) and then follow the step-by-step above. If you have questions about passphrases, backups, or multisig exports, see passphrase usage & risks, backup & SLIP-39, and multisig setup.

If you found this helpful, keep this CSV safe and consult a tax professional for specific filing guidance. And if something still doesn’t match, export again and compare a handful of tx hashes on-chain — that simple check solves more problems than you’d expect.