Skip to main content
All CollectionsCSV files
Guide to Compiling the CryptoBooks CSV
Guide to Compiling the CryptoBooks CSV

Follow these instructions to make your CSV compatible with our format.

Diego Lorenzetti avatar
Written by Diego Lorenzetti
Updated over 4 months ago

Follow this guide to correctly fill in the rows of the CSV file in CryptoBooks format.

If you are unsure how to edit and save a CSV file, read this article:

Below you will find detailed instructions on the allowed values that can be used to fill in each field/column of the CSV file.

  • Field/Column 1: TYPE - mandatory field

    indicates the type of transaction (deposit, withdrawal, or trade).

    • If you are creating the line for a deposit transaction, you must enter one of the following allowed values:

      • Incoming

      • Deposito (Deposit in Italian)

      • Deposit

      • Ingoing

    • If you are creating the line for a withdrawal transaction, you must enter one of the following allowed values:

      • Outgoing

      • Withdrawal

      • Prelievo (Withdrawal in Italian)

    • If you are creating the line for a trade transaction, you must enter one of the following allowed values:

      • Trade

      • Scambi (Trades in Italian)

      • Scambio (Exchange in Italian)

  • Field/Column 2: CATEGORY - mandatory field

    indicates the category to which the imported transaction belongs. The allowed values are as follows:

    • Transfer

    • Trasferimento

    • Trading

    • Staking

    • Mining

    • Payments

    • Lending

    • Pool

    • Borrowing

    • Farming

    • Fees

    • Salary

    • General_Income

    • Settlement

    • Airdrop

    • Bank&Card

    • Lost

    • Delisted

    • Gift

If you don't know which category to assign to the transaction, read the article you can find at the link below for more details on the categories:

  • Field/Column 3: TRANSACTION DATE - mandatory field

    indicates the date of the transaction you are importing. The allowed formats are:

    1. yyyy-MM-dd HH:mm:ss (example: 2023-07-14 12:34:56)

    2. yyyy-MM-dd HH:mm (example: 2023-07-14 12:34)

    3. dd/MM/yyyy HH:mm:ss (example: 14/07/2023 12:34:56)

    4. dd/MM/yyyy HH:mm (example: 14/07/2023 12:34)

    where yyyy is the year, MM is the month, dd is the day, hh is the hour, mm is the minutes, and ss is the seconds.

  • Field/Column 4: FROM CURRENCY - mandatory field

    depending on the type of transaction, indicates:

    • In withdrawal transactions, it is the code of the currency that was withdrawn/sold.

    • In deposit transactions, it is the code of the currency that was deposited/purchased.

    • In trade transactions, it is the code of the currency that was sold in the exchange.

!!!! Please Note !!!!

If you use a comma as a decimal separator, you must enclose the amounts in quotation marks ("xxxx.xx").

This rule must be applied to every field where you input numerical values that use a comma to indicate decimal amounts.

Example of an incorrect line not accepted by the software:

Trade,Trading,13/04/2022 19:04,EUR,2999,85,BNB,7,6368,,,

Example of a correct line accepted by the software:

Trade,Trading,13/04/2022 19:04,EUR,"2999,85",BNB,"7,6368",,,

  • Field/Column 5: FROM AMOUNT - mandatory field

    depending on the type of transaction, indicates:

    • In withdrawal transactions, it is the amount of the currency that was withdrawn/sold.

    • In deposit transactions, it is the amount of the currency that was deposited/purchased.

    • In trade transactions, it is the amount of the currency that was sold in the exchange.

  • Field/Column 6: TO CURRENCY - mandatory only for TRADE transactions:

    • It is the code of the currency that was purchased in the exchange.

    • In withdrawal transactions

      • it should be left empty if you want to use the market conversion rate at the transaction date

      • filled with the symbol of the FIAT currency of the account (i.e. EUR or GBP) if wanting to indicate a price different than the market price

    • In deposit transactions

      • it should be left empty if you want to use the market conversion rate at the transaction date

      • filled with the symbol of the FIAT currency of the account (i.e. EUR or GBP) if wanting to indicate a price different than the market price

  • Field/Column 7: TO AMOUNT - mandatory only for TRADE transactions:

    • In trade transactions, it is the amount of the currency that was purchased in the exchange.

    • In withdrawal transactions

      • it should be left empty if you want to use the market conversion rate at the transaction date

      • filled with the sale price expressed in FIAT of the account if wanting to indicate a price different than the market price

    • In deposit transactions

      • it should be left empty if you want to use the market conversion rate at the transaction date

      • filled with the purchase price expressed in FIAT of the account if wanting to indicate a price different than the market price

!!!!Please note!!!!

If you use a comma as the decimal separator, you must enclose the amounts in quotation marks ("xxxx,xx").

This rule applies to each field where you enter numeric values using a comma to indicate decimal amounts.

Incorrect and not accepted by the software:

Trade,Trading,13/04/2022 19:04,EUR,2,999,BNB,7,6368,,,

Correct and accepted by the software:

Trade,Trading,13/04/2022 19:04,EUR,"2,999",BNB,7,6368,,,

  • Field/Column 8: FEE CURRENCY - optional field

    indicates the code of the currency used to pay the transaction fees.

    Fill in this field only if a fee was paid for that transaction.

  • Field/Column 9: FEE AMOUNT - optional field

    indicates the amount paid in fees for the transaction.

    Fill in this field only if a fee was paid for that transaction.

  • NOTES - optional field

    Limited to 200 characters, it is a field to enter your own notes/comments within the transaction.

  • ORIGINAL ID - optional field

    Here you can enter the original ID of the transaction, useful if you want to do a quick search for one or more transactions within the CSV file.

Below is an example of a correctly compiled file with some rows of transactions of different types:

Excel view

Text editor view

Did this answer your question?