Common import errors
R
Written by Robin Singh
Updated over a week 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 detected duplicate transactions, spam transactions, or unnecessary transactions such as internal transfers within a single account.

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.

Did this answer your question?