Informative Guide – CSV Import Guide

This tutorial will guide you through the process of importing your CSV files from exchanges, wallets or other sources into the Blox platform.

Please follow the following instructions, or contact Blox for support.


When working with accounting tools to import/export files to and from Blox, data completeness is essential.


By using the import feature, users will be able to import and insert data for non-supported wallets or exchanges into Blox. Users can easily upload a CSV file (using Blox’s guidelines) in order to integrate and visualise the assets inside the Blox platform.


Please note that only exchanges and wallets supported by CoinMarketCap will be available for this feature (check CMC website for the full list of supported sources). In addition, an exchange that is supported but doesn’t have market data available in CMC or a different token/pair from the list provided will also not be accepted in the CSV Import feature.

How To Import Transactions via CSV File

Before uploading the CSV file:

     1. The first step is to download the full history (Deposits/Withdrawals, Buy/Sell) of transactions from the source (Exchange, Wallet, Other).

     2. To start the import process, click on the ‘+’ button (top right of the screen).

     3. Under the integration cards, please click on the CSV Import button (see the image below). If you are creating a new portfolio, this button can be found on the main screen, under the integration cards.

     4. After clicking the CSV Import button, you will be prompted with the response below.

     5. Click on the ‘template’ button to download the necessary Blox formatting template.


     6. Before uploading your file, please ensure all your data has been properly added to the Blox template file using this instruction guide and following the rules listed below.


     7. Please note there is a file size limit of 10MB (~150K Tx) per-upload at a time. If you exceed the volume/size, users will need to repeat the process until all transactions have been accounted for. Therefore, some users may have to split files manually to ensure they are under the size limit.


     8. Uploading the CSV file to an existing manual account

         a. Select an existing account from the drop-down list that you wish to upload the CSV file.

          b. Click on ‘Upload the CSV file’ to browse and select the CSV file needed.


     9. Uploading the CSV file to a new account.
          a. Select the option to ‘Create New Manual Wallet/Exchange’.

          b. Create a name for the new manual account.

          c. Select the type of the new account (Wallet or Exchange).

          d. Select the name of the transaction source being uploaded (see the image below as reference).

          e. Upload the CSV file.

After Uploading the CSV File:

     10. After selecting or creating a new account press ‘Submit’. The CSV file will be validated before uploading begins.


     11. If the validation fails to process, users will receive an alert, and a CSV with the errors explained in a new column.
         a. Please note, if errors are detected, no transactions will be imported.
         b. Review and/or update your file before uploading again.


     12. After successfully uploading the file, the user will be able to differentiate between ‘Manual’ and ‘Automated’ transactions.
         a. Manually uploaded transactions will contain a ‘CSV’ icon within the transaction table. Automated transactions will have no icon.

     13. Transactions that were imported via CSV can be deleted and edited like regular manual transactions. (Please note: Auto-Sync transactions from exchanges can’t be edited – besides the Unit Price – or deleted).
         a. Users can delete manual transactions but auto-synced transactions can’t be deleted unless the account is deleted.
         b. In manual transactions, users can edit the ‘Unit’ volume of assets, the unit price, etc.

Formatting Validation Rules

In order to successfully import CSV files, they must follow the format and rules set forth by the Blox platform and guidelines. CSV files will only be imported after the validation. All validated CSV files must meet the requirements below:

  • File Format – Only CSV files will be accepted.
  • Size – Maximum file size is 10MB (~150K Tx).
  • Date Column: Please use the correct timestamp format: E.g. 2019-04-01 08:13 AM (yyyy-mm-dd HH:MM AM/PM) or 03-21-2019 03:25 PM (mm-dd-yyyy HH:MM AM/PM). The date separator can be “/” or “-”.
    • If the hour is not provided the validation will fail.
    • Time Zone – the date provided will be considered in UTC+0.
  • Mandatory fields were filled:
    • Trades – Date, Transaction Type, Traded Units & Currency, Received Amount & Currency.
    • Deposit – Date, Transaction Type, Received Units & Currency, ‘From Address’ (Recommended).
    • Withdraw – Date, Transaction Type, Traded Units & Currency, ‘To Address’ (Recommended).
  • Field Editing Rules:
    • Numeric columns (e.g. Received/Sent Amount, Value, Fee) must only use numbers and no letters.
    • Text columns (e.g. Received/Sent Currency and Currency Fee) must only use text and no numbers, besides notes that may contain both.
    • Currency pairs should be separated into different columns (E.g. BTC/CDT won’t be accepted).
    • Coins or tokens can be written in exchange acronyms or full name (Ex: Bitcoin = BTC, ETH = Ethereum).
    • No negative numbers or special characters (e.g. #±~’: > < ?) can be inserted in any of the fields.
    • Please make sure that the name of the token is written correctly otherwise it will appear as an unknown asset in the Blox platform.
  • Column header validation. In case that the user changed the header of the columns, the CSV will fail the validation.

Example of Blox template for CSV import.

  • Please find one example for each transaction type (trade, deposit and withdraw). The different transaction types were divided in this example to make the visualization easier.
    • Deposit and Buy have the same format
    • Withdraw and Sell have the same format
    • There should be one file for all the transaction types. The headers should appear only once
    • The numbers below are just an example and don’t represent real data.

Short explanation about the fields in the Blox Template

  • Date – Timestamp of the transaction (yyyy-mm-dd HH:MM AM/PM or mm-dd-yyyy HH:MM AM/PM) – UTC+0.
  • Transaction Type – Deposit, Withdraw and Trades.
  • To – Account that received the amount
  • From – Account from which the amount was received
  • Sent Amount – The quantity of amount sent
  • Sent Currency – The currency of the amount sent
  • Received Amount – The quantity of the amount received
  • Received Currency – The currency of the amount received
  • Value – The value of the transaction in $ according to the user’s source
  • Fee – The number of units
  • Currency Fee – The currency of the fee

FAQ and Troubleshooting

How is the balance calculated from CSV imported transactions?

When importing data into Blox there are two main areas that are affected.

  1. Unit balance – After summing up all of the assets units according to the imported file, Blox will set the final unit balance for each token. According to this final unit balance, Blox uses CMC in order to define the portfolio value at any specific moment.
  2. Imported transactions – All the imported transactions will be recorded with the price provided in the CSV file. In case the CSV does not contain a value for all the transactions, Blox will use CMC to set the price for those transactions. Please note that the value of the transaction will not affect the value of the portfolio.
  3. The only way to manually change the value of the portfolio is by changing the number of the Units of a manual transaction or adding more units via a CSV import.

How to delete incorrect data via imported CSV?

The user can easily delete any manual account from the Accounts Tab. If the imported data is not correct, the user can simply delete the account that contains the imported data. In cases where the user wishes to delete a small number of manually imported transactions, it can also be done within the transaction detail’s side panel.


How to add transactions to a new or existing account?

Please review points #7 and #8 in the guide above.

What is the file size limit that can be imported?

File size limit of 10MB (~150K Tx) per-upload at a time. If you exceed the volume/size, users will need to repeat the process until all transactions have been accounted for.

Can we import the transaction notes?

Notes that were added to the transactions and follow Blox’s template guidelines will also be imported. Please follow Blox’s CSV import format template.


Is it important to choose the account type when creating a new account when importing a CSV file?

When creating a new manual account and importing a CSV file, it is very important to choose if the account is an Exchange or Wallet and select the correct name of the source being imported.


Can I differentiate transactions that were imported via CSV?

Every transaction that was uploaded via CSV Import feature will have a small “CSV” icon to differentiate from transactions that have been auto-synced.


What is the supported time zone?

The timezone should be provided in the date (using the ISO 8601 format). In cases where time zones are omitted, Blox will consider the dates provided as UTC+0.


What happens if there is an error while importing the CSV file?

If there is an error in the validation process, the entire CSV file will not be imported and the user will receive a CSV with an additional column. This column will identify and display all of the errors found in the failed validation process.


What happens if there is an invalid asset/wallet/exchange while importing the CSV file?

The CSV Import feature is only valid for exchanges and blockchains supported by CoinMarketCap.

For example, Uniswap exchange is a supported exchange, but there is no available data in CMC, therefore uploading will not be possible.

On the other hand, itBit exchange is supported by CMC but only has two pairs of tokens with available data (BTC/USD and ETH/USD as shown in the image below).

If a user selects to use itBit exchange for the CSV import, and wishes to upload tokens LTC/USD, the system will return with an error. This is because that specific token pair is not available on CMC and the system is unable to retrieve the information.

You might also enjoy

Ready to stake with Blox?

Introducing Blox Staking, a new service offering non-custodial staking for Ethereum 2.0.
Visit us today to join our Beta waitlist!