Preparing Hardware Wallet Exports Before Tax Season

Tax season assembly starts with what you can export today — not what you wish you had exported two years ago. Hardware wallet manufacturers provide different export paths, and knowing which files to pull saves weeks of gap resolution later.

Ledger devices

Ledger Live exports transaction history per account. Pull CSV exports for every account you have used, including archived accounts you no longer display in the default view. Note the export date in your file name — Ledger timestamps reflect sync time, not always block confirmation time.

Check for hidden accounts: if you created accounts beyond the default BTC and ETH slots, each needs its own export. Internal transfers between Ledger accounts appear as separate transactions and must not be filtered out before assembly.

Trezor devices

Trezor Suite offers CSV and PDF export options. CSV is preferred for assembly because fee fields remain machine-readable. If you used Trezor with third-party interfaces in past years, gather those interface exports separately — Suite may not include pre-migration history.

Common gaps to flag early

• Exports pulled after a device wipe without prior backup
• Accounts created on deprecated software versions
• Transfers where only the receiving address is documented
• Fee payments on secondary chains omitted from primary export

Before intake

Store exports in a single folder with a simple inventory document listing wallet brand, approximate first-use year, and chains used. Send this inventory with your intake request so scope estimation is accurate.

Assembly teams work faster when exports arrive labeled. Unlabeled files force manual identification and extend timelines during peak season.