When importing a CSV file or syncing using API, you may notice errors when importing some of your files:
These will usually be caused by:
😶🌫️ Skipped transactions
😵💫 Failed transactions (rows)
🙅 Rejected file (for CSVs)
👮 Access denied (for APIs)
🥷 Unrecognized file (for CSVs)
🤷 Invalid file
This article explains what each of those messages mean and how to fix them (if needed)
Common errors
😶🌫️ Skipped transactions
Koinly will often skip (won't import) some of the provided data on purpose as the particular transaction is not needed/relevant. The reason for skipping the transaction is usually provided in the import summary.
Most common reasons for skipping transactions include:
Internal transfer within the exchange
E.g. sending funds from your funding to spot accountDuplicate
The transaction is already imported to KoinlyImported from another file
Transaction is relevant but we skip it because it will be imported using a different file from the exchangeStaking/unstaking
Skipped just like internal transfersDate is before lock date
If you set a lock date in your Settings, transactions prior to this lock date will be skippedStatus cancelled
Transaction was submitted but never processed (didn't happen) - e.g. reverted withdrawal, cancelled limit order
How to fix skipped transactions
There is no need to fix this - the transactions are skipped on purpose. If you believe Koinly misinterprets the file and some of the data shouldn't have been skipped, then please reach out to our Support team.
😵💫 Failed transactions
It's possible that some rows were not imported not because they were skipped on purpose but because of some error, usually with the data in the file:
This is usually due to:
Wrong date format
Usually happens if the file was open in Excel before importing - reformat the dates back toYYYY-MM-DDbefore saving (best - import file without opening it)Currency not found
A token must exist in Koinly to import it - check the Markets page if the correct symbol is in the file. If the symbol doesn't exist, you can use placeholders NULL1, NULL2, NULL3, etc
How to fix failed transactions
In most cases, downloading a new file from the exchange and importing it to Koinly without ever opening it in Excel solves the problem.
🙅 Rejected file (for CSVs)
Some files will fail to import and throw a message This file is not needed
These files are rejected on purpose because:
The file contains only irrelevant information (e.g. internal transfers)
The same data will be imported using another file from the exchange
How to fix rejected files
There's no need to fix this - the file is rejected on purpose, usually because the same data will be imported from another file our instructions require. If you believe Koinly misinterprets the file and it shouldn't be rejected, then please reach out to our Support team.
👮 Access denied (for APIs)
Access denied (and other red errors) after syncing usually mean that that the API key was not created correctly.
For more information on how to deal with this error, see:
🥷 Unrecognized file
Unknown file usually shows when trying to import the wrong file or if the files comes from an unsupported exchange.
For details, see:
🤷 Invalid file
Invalid file error means that the file imported is in the wrong format.
Koinly supports CSV, XLSX and zip files. We do not support PDF, NUMBERS or XLS (old Excel) files.
How to fix invalid files
Invalid files need to be converted to CSV (or XLSX) before importing using any spreadsheet software (Excel, Google Sheets).
☝️ Converting a PDF to CSV
Converting a PDF file to CSV using some online converter rarely works as PDF is not a well structured file so the resulting CSV is usually broken. Most of the time, this means that the only way to import the data from PDF is by creating a new CSV file from scratch and copy-pasting the data by hand.
How to avoid issues when importing CSVs
Integration instructions
Follow Koinly's integration instructions precisely and import only the files required
Don't open the files in Excel
Import exactly the files downloaded from the exchange without ever opening them in Excel or Google Sheets
Unsupported exchanges
For unsupported exchanges, be sure to follow How to modify CSV files to transform the file to a Koinly-readable format
Other issues
Few transactions imported
Often a file will contain more rows than what Koinly imports, even though no rows are skipped. It's common if a single trade spans multiple rows in the file but results in one transaction in Koinly.
Often a file will have a separate row for:
Sold token (Out)
Bought token (In)
Fee paid
But those 3 rows result in only one trade imported.
Koinly will also usually aggregate your PNL transactions (futures, perpetuals) into one daily gain and one daily loss transaction.
Deleted transactions can't be reimported
If you deleted transactions and try to import them again but they are skipped as duplicates, it means you didn't delete the transactions permanently.
Check how to view deleted transactions and how to delete them permanently in:
Too many transactions imported
This will be specific to "gateway exchanges" like Changelly, Safello, etc.
When importing a file from this exchange, every trade (1 row) will result in 3 transactions:
Deposit
Actual trade
Withdrawal
This is expected due to the nature of this exchange - the deposit and withdrawal, after importing, will merge into transfers to/from your other respective wallets, because this is what actually happened - you sent assets to Changelly (transfer), trade happened on Changelly (exchange) and the acquired asset was sent to your target wallet (transfer).