Reconstruct Exchange History
Binance, Kraken & Co.
MEXC, Bybit, Kucoin or a closed exchange? Retrieving historical data retroactively is the real challenge. TX-Partner combines API, CSV and manual processing.
30 min · Free · No commitment
Robert & Johannes · personally review your data
Most exchange connections fail not because of the tool, but because of the data:
Why CSV Exports Alone Are Not Enough
Reconstructing exchange history retroactively requires more than a CSV export. API limits, deleted accounts and missing time periods make professional reconstruction necessary.
API Doesn't Cover All Products
For exchanges like Binance, the API doesn't cover all products: Spot, Earn, Staking and Futures run on different endpoints and often have gaps in historical data. CSV exports fill those gaps, but need to be correctly merged with API data to avoid duplicates.
Exchanges Closed, Accounts Gone
FTX, Bittrex, Cryptopia, Celsius, MT.GOX: Closed exchanges no longer provide CSV exports. Coinbase Pro (legacy) and Bitpanda Pro also no longer exist in their original form.
Missing Cost Basis = Phantom Gains
Without complete exchange history, the tax tool sets the acquisition cost to 0 EUR. The result: phantom gains, negative balances, and an inflated tax liability.
Not Every Exchange Is the Same
Different exchanges require different strategies. Some deliver clean data, others require significant manual post-processing.
Important: This overview refers to historical data. For ongoing tracking, most exchanges work well. Problems arise when transaction data needs to be retrieved retroactively.
Historically Often Problematic
Historical data often requires matching API and CSV or completely manual processing.
Closed
No login, no export. Reconstruction via on-chain analysis, archived data and memory protocols.
Usually Works Well
API connection delivers complete historical data as well. CSV as backup recommended.
Record Retention Requirements
In Austria, § 132 BAO requires a 7-year retention period for tax-relevant documents. In Germany, § 147 AO mandates a 10-year retention period for accounting records. Missing exchange histories can become a problem during a tax audit or information request.
Binance Tax Report: Exporting All Years Completely
Binance is the most widely used exchange and one of the most challenging for complete historical documentation. The API doesn't cover all Binance products, and historical data is often incomplete. Relying on the API alone leaves gaps.
The Problem with Binance
- The API doesn't cover all products: Spot, Earn, Staking, Futures and transfers run on different endpoints
- Historical data via API is often incomplete, especially for older transactions and less-used products
- CSV exports fill the gaps but must be correctly merged with API data, otherwise duplicates occur
Exporting Wallet History
- On-chain wallets (Ethereum, Solana, BNB Chain) are accessible via blockchain explorers at any time – no login required
- Exchange-internal wallets (Binance, Coinbase) are only accessible through account exports
- Multi-chain wallets require a separate export or API call per chain
8 Exchanges, 1 Tax Tool, 0 Complete Imports
A recent case: 8 exchanges with incomplete or missing imports — despite API connections where available.
5 Exchanges connected via API — with gaps
Binance, Gate.io, Kucoin, Bybit, MEXC
3 Exchanges only importable via CSV
FTX, eToro, OKX: No API available or exchange no longer exists. Import only via CSV exports.
5 API insufficient for 5 exchanges
MEXC, Bybit, Kucoin, Gate.io, Binance: CSV exports needed as supplement, or import entirely via CSV then synchronize with API.
5 Manual import for 5 exchanges
FTX, OKX, Kucoin, MEXC and Gate.io: The client's tax tool was unable to correctly read the raw data. Every exchange has different data formats and transaction types. The raw data had to be manually processed and converted into a readable format.
The biggest challenge: every exchange has its own raw data formats and transaction types. Without experience with these formats, it is nearly impossible to get the data correctly into the tax tool.
How TX-Partner Reconstructs Your Exchange History
TX-Partner knows the specifics of every exchange: API limits, CSV formats, raw data structures. That saves weeks of research on your own.
Inventory
Record all exchanges, wallets and time periods used. Which access still exists? Which exchanges have closed? Where is data missing?
Data Acquisition
Set up API connections, pull CSV exports, submit support requests to exchanges. For closed exchanges: use on-chain analysis and archived data.
Process Raw Data
Read CSV files, correctly assign transaction types, standardize formats. Every exchange has its own data structures. TX-Partner knows them all.
Tax Tool Import
Import cleaned data into Blockpit or CoinTracking. Synchronize API + CSV. Cost basis correct, transfers assigned, no negative balances.
Exchange History definitively complete.
30 minutes that make the difference.
Book Data Check 30 min · Free · No commitment500+ documented cases · 15+ years crypto experience
You might also like
Reconstruct DeFi History
LP tokens, yield farming, cross-chain bridges: retroactively document on-chain data.
Learn more
Reconstruct Crypto History
Restore missing transaction data step by step.
Read article
CoinTracking Errors Overview
Common CoinTracking issues and how to fix them systematically.
Learn more
When Exchange Data Is Missing
What to do when an exchange API or CSV export doesn't deliver a complete history and transactions are patchy.
Read article