Skip to main content
Common import errors
Carl avatar
Written by Carl
Updated over 2 months ago

When importing a CSV file or syncing an API, you may sometimes notice that some transactions failed to sync. This can be due to a number of different reasons, with the most common ones being listed here below. If you want to check whether a recent import encountered any errors, then you can check the Import History page. Any issues will be listed on the right side on the page.

Skipped transactions

It is normal to see some skipped transactions after an import. This can happen if Koinly detects rows with the following:

  1. Spam transactions

  2. The row is an internal transfer that doesn't need to be imported.

  3. The row contains a zero amount

  4. The row is blank

  5. The row contains a cancelled/failed transaction

  6. The row contains a transaction that we have deemed unnecessary (ex. internal transfer to a staking wallet)

  7. Transactions that have already been imported (duplicates)

Date is before lock date or portfolio lock date

This error occurs when a setting is preventing a transaction from importing. This could be due to a portfolio lock, which can be adjusted in your settings, or it could be due to a starting sync date in your wallet's API settings.

Amount must be greater than 0

This error occurs when a transaction is too small for Koinly. Koinly tracks your balances with 10 digits of precision, but if a transaction has a lower amount of crypto than this, then Koinly will not import it. This issue can generally be ignored since the transaction is too small to affect your balances or gains.

Currency not found

If Koinly encountered a currency that is not recognized, then the transaction will be skipped. You can click on the error to check which currency is causing the issue. If it not a currency that you recognize, then it is likely not a real currency and the error can be safely ignored. If you do recognize the currency, then you can add the transaction manually or contact our support team to fix the issue.

Very few imported transactions compared to total rows in file

Koinly groups certain rows into the same transaction which can result in a lot less transactions being created from your file. Ex.

  • If your file contains a trade spread on multiple rows - Koinly will create a single transaction for these

  • If your file contains both order and trade ids then Koinly will group multiple trades for the same order into the same transaction

  • If your file contains a lot of "futures" transactions (realized profit/loss) then Koinly will group these into a single transaction for each day

Number of imported transactions is much higher than the number of rows in the file

Koinly creates up to 3 transactions for swap services like Changelly, Safello etc (one deposit, one trade, and one withdrawal). This allows Koinly's transfer matching engine to work seamlessly with such transactions.

๐Ÿ”ตExample: A trade of 1 BTC to 5 ETH:

  1. You are sending 1 BTC to Changelly (Deposit)

  2. Changelly is converting this BTC to 5 ETH (Trade)

  3. Changelly is sending the 5 ETH back to your wallet (Withdrawal)

There are also other cases where you may see more transactions ex.

  • If fees are being paid in multiple currencies for a trade (Koinly will add one of the fees to the trade itself and the other fee will be added as a separate transaction).

  • If you are importing a file with your margin borrowing history (if this file also contains the repayment dates and the interest paid, you will see 3 transactions being created for each row)

Did this answer your question?