Exporting Exchange Trade History Into a Personal Ledger You Can Reconcile

Raw trade history exports from an exchange are rarely ready to use. They arrive with timestamps in one format, fees in another, and rows that mix spot fills, futures fills, transfers, and funding payments. If you have ever opened a CSV and closed it again because nothing lined up, this routine is for you. The goal is not to build an accounting system, but to create a personal ledger you can actually reconcile: one file per month, one consistent column layout, and a short set of checks you repeat each time you export. The routine below applies to Binance, OKX, Bybit, and Bitget, and it assumes you are working from the official help centre pages for each platform rather than from memory. Before you start, decide where your records will live: a spreadsheet you control, a folder on your own drive, or a simple local database. What matters is that the ledger is yours, that you can open it without the exchange, and that each row traces back to a specific export file. Treat the exchange as the source of raw data and your ledger as the source of truth for your own review. Nothing here is tax, legal, or investment advice; it is a recordkeeping habit.

Choose the export window and download the raw files

Start by opening the help centre for the exchange you use and searching for the trade history or transaction history export article. Each platform labels the feature slightly differently, and the export window is often limited, so you may need to request several files to cover a full year. Do not assume the default range is the one you want. Set the start and end dates explicitly, and if the interface offers a choice between spot, futures, or all products, export each product type separately so the columns stay consistent. Save the files with a name that includes the exchange, the product, and the date range, for example a folder named by year and month with subfolders per product. Keep the original download untouched in a raw folder and work on a copy. This matters because the export format can change between platform updates, and you want to be able to re-check what the original file contained. If a download fails or the file is empty, note the date and try a narrower range rather than assuming there is no data.

Map the columns and normalise timestamps and fees

Open the raw file and identify the columns before you delete anything. Typical exports include a timestamp, a pair or instrument, a side, a price, an executed quantity, a fee amount, and a fee currency. Write down the exact column names for each platform in a small mapping note, because the same concept may be called different things across exchanges. Convert every timestamp to one time zone and one format in your ledger, and keep the original timestamp in a separate column so you can trace back. Fees deserve their own columns: separate the fee amount from the fee currency, and if the fee was paid in a token rather than the quote currency, do not silently convert it at an arbitrary rate. Record it as it appears and mark it for later review. The same applies to futures fills, where fee handling and contract specifications differ from spot. Check the official fee page for the exchange to understand how fees are described, and check the futures documentation if you trade derivatives, so you know which fields the export is meant to contain. If a column is missing that you expected, that is a signal to re-read the help article rather than to guess.

Build the ledger and reconcile it against balances

With clean columns, append each month's rows to a single ledger sheet or table, keeping a source file column so every row points back to its raw export. Then reconcile: for each asset, sum the quantities in your ledger and compare against the balance shown in the exchange interface at the same point in time. Differences usually come from transfers, deposits, withdrawals, staking or funding entries that are not in the trade export. Export those separately from the transaction history section of the help centre and add them as their own row types. Do not force a match by editing trade rows; add a clearly labelled adjustment row instead, with a note explaining what it represents. If the gap persists after adding transfers and funding, write down the discrepancy, the date, and the asset, and stop trying to resolve it that day. A small unresolved difference that is documented is more useful than a ledger that has been quietly altered to balance. Repeat this reconciliation monthly so the gaps stay small and easy to trace.

Keep the routine repeatable and auditable

A ledger is only useful if you can rebuild it. Store the raw exports, the mapping note, and the ledger together, and record the date you downloaded each file and the export range it covers. Once a month, set a short block of time to download the new period, run the same column mapping, append the rows, and reconcile. If the exchange changes its export layout, update the mapping note and re-process only the affected files, keeping the old versions. Before you rely on any figure, spot-check a few rows against the exchange interface: pick a trade, find it in the raw file, and confirm the price, quantity, and fee match. Use the help centre when something does not appear where you expect, and use the fee and futures pages to confirm what a field is supposed to mean. Never treat the ledger as a substitute for official statements; treat it as your own working record. If you share records with anyone, share the ledger plus the raw files so the numbers can be checked independently.

Risk boundary: Russia Crypto Guide

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.

Scenario checkpoint

• Export each product type separately with explicit start and end dates, and keep the untouched raw files in a dated folder.
• Write a column mapping note for each exchange before you rename or delete anything.
• Normalise timestamps to one time zone and keep the original timestamp in its own column.
• Record fees with their original currency and do not convert them at an assumed rate.
• Add transfers, deposits, withdrawals, and funding entries as separate row types during reconciliation.
• Reconcile monthly and document any unresolved difference instead of editing trade rows to force a match.