Skip to content
Crypto Bulletin

Markets, protocols and policy news

ID d0f0e3

DEX Trade Imports: Wallet Sync or CSV

To import DEX trades into tax software, start with wallet sync; use CSV for missing history, then reconcile each trade once and explain balances by chain.

Crypto Bulletin Newsroom 3 min read

DEX Trade Imports: Wallet Sync or CSV

List every public address, chain and available trade-history date range first; wallet sync and CSV coverage both depend on that inventory. For completed cowswap trades, start with supported wallet sync; use CSV only to fill history the sync omits or a documented gap. Import each chain, reconcile a sample trade and balances, then correct exceptions until each trade appears once and the remaining balance is explained.

  1. Start with completed DEX trades and gather the public addresses that made them, the chains used and the history you can access. Koinly’s blockchain import instructions say to add a separate wallet for each chain, even when the same address is used across chains. As background, cowswap fees adds the fee context for cowswap trades; keep the task here to importing and reconciling records.

  2. Choose wallet sync when the tax software supports the chain and address. Koinly says its blockchain sync uses a public address and imports that chain’s history, including token transfers and DeFi transactions. Coverage varies by software, chain and available history, so check the imported date range before treating sync as complete.

  3. Use CSV when sync does not cover the history or the software documents a CSV remedy for the gap. Follow that software’s supported CSV schema and export instructions; Koinly advises keeping files unedited and says explorer CSVs may lack complete or accurate transaction data. Avoid mixing CSV and API data for overlapping periods: Koinly warns duplicate detection may fail when the sources record the same activity differently.

  4. Import each chain separately, then set clear boundaries between sources. The tricky part is the cutoff: give each source a start and end date, and record the timezone used. A shared cutoff day can put the same trade in both imports, especially if one file uses local time while the sync timestamps in UTC. Set the CSV to end before the sync begins, or the reverse, and inspect trades around the boundary.

  5. Reconcile a sample from each chain against the trade history: compare dates in UTC, tokens, amounts and transaction references where available. Then review wallet balances and transfers for unexplained differences; a routed DEX trade can create several on-chain entries, so confirm the tax software has recognized the completed trade rather than counting its component activity twice. Correct exceptions by removing a duplicate or importing a documented missing period.

  6. Finish when each completed trade appears once and the wallet balances are explained by the imported history. If a balance still differs, trace the affected chain and date range back to the source before adding more data.