Importing from Binance

Download your Binance Transaction History as a CSV file and import it to build your crypto holdings records.

Last reviewed

Downloading your history from Binance

Download the account-wide Transaction history as a CSV file. It lists trades, converts, staking and earn rewards, deposits and withdrawals across your wallets. A spot order history export is a different file and is not read.

What to look for

  1. Sign in to Binance in a web browser
  2. Open your Wallet and look for Transaction history
  3. Look for an option to export or generate a statement of all transactions
  4. Choose the dates you want; you may need more than one export to cover your full history
  5. Download the CSV file when it is ready
Steps written on 23 October 2026 and not checked against a live Binance account, so they say what to look for rather than which button to press. The CSV is read without AI, and your financial documents never leave our servers without your approval.

Supported formats and columns

The import wizard recognises Binance exports in CSV format by these column headings: change, coin, operation, utc_time. A row with a blank currency cell is recorded in USD.

Costs

This export has no per-trade cost column, so no dealing charges are read from it.

Rows set aside

Some rows are recognised but not imported. The review step lists each one and why:

  • Unrecognised action — not imported
  • Cash transaction — not currently imported
  • Date could not be read — not imported
  • A number on this row could not be read — check it and add it by hand

Step-by-step import

  1. Open Import statements in the sidebar, under Estate & assets → Portfolio
  2. Drag and drop your Binance CSV, or click to browse
  3. The Binance Transaction History layout is recognised from its column headings
  4. Review the parsed transactions: rows that need attention carry a confidence badge
  5. Confirm the import to create your transaction records

Screenshot, for illustration only

The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The importer on its first step, upload, where you say what kind of statement it is, whose it is and which account it belongs to.

Cost line-item extraction

A trading fee charged in the asset you received is netted off the quantity that moved. A fee charged in a third asset, such as BNB on a USDT trade, is set aside in the review step with the reason.

See Understanding investment costs (opens in a new tab) for how each cost affects cost basis in each supported jurisdiction.

Common issues

Crypto-to-crypto trades and converts

A trade or Convert between two crypto assets, including stablecoins such as USDT or USDC, is recorded as a swap: one asset out and the other in, linked together.

Rows that are set aside

Margin, futures and P2P lines, and other operation types the reader does not cover, are listed in the review step with the reason rather than dropped, so you can see everything the file contained.

Before you import

Dedicated reader: Binance files are read by a reader built for their layout, without AI.

These parts of the Statement import guide apply to every broker:

Related pages

Can’t find what you’re looking for?

Our support team is here to help. Contact us and we’ll get back to you as soon as possible.

Contact us

We use cookies to improve your experience. See our Cookie policy (opens in a new tab) for details.