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. If you’re importing data from platforms like Binance or Crypto.com, special attention might be required due to platform-specific quirks and challenges.
Overview of Common Challenges
CSV imports can sometimes result in errors, including:
Small imbalances in transaction records.
Incorrect reward or bonus claims.
Skipped transactions or incomplete data entries.
Dashboard displaying incorrect total values. The core causes of these issues typically revolve around data formatting inconsistencies, platform-specific behaviours, and unintended editing of raw data files.
Transactions not reimporting after deletion
Duplicate transactions appearing in repeated imports
Errors when editing or resubmitting CSV files
Skipped transactions
It is normal to see some skipped transactions after an import. This can happen if Koinly detects rows with the following:
Spam transactions
The row is an internal transfer that doesn't need to be imported.
The row contains a zero amount
The row is blank
The row contains a cancelled/failed transaction
The row contains a transaction that we have deemed unnecessary (e.g. internal transfer to a staking wallet)
Transactions that have already been imported (duplicates). When troubleshooting skipped transactions, you should ensure that your transaction history isn't incomplete by re-fetching the entire historical data from your exchange or wallet.
Check the skipped rows during the import process; these are often irrelevant or empty rows that Koinly automatically omits.
Ensure that the remaining data has imported correctly. If your transaction history seems incomplete, retry fetching your data from the source.
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:
You are sending 1 BTC to Changelly (Deposit)
Changelly is converting this BTC to 5 ETH (Trade)
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)
Common CSV Errors and How to Fix Them
File content type is invalid: Ensure the file adheres to the guidelines provided by the exchange, avoiding any mixing of API and CSV import methods during uploads.
Verify the file type: Double-check that the uploaded file is in CSV format, as Koinly does not support other formats like PDFs or images. To ensure accurate processing, always generate the CSV file directly from your wallet or exchange platform.
Some errors and their solutions that apply broadly to CSV imports include:
Incorrect decimal separators: Ensure there are no mismatched dots or commas as decimal points.
Corrupted formatting: Always keep a backup copy of the raw file and avoid unnecessary edits.
Incorrect column headers: Modify headers to match Koinly's expected format, if required. By applying these troubleshooting tips and best practices, you can ensure accurate data imports and maintain a reliable overview of your Koinly transactions and balances.
Unsupported exchanges or CSV sources: Koinly doesn't support CSV files from all exchanges directly. If using data from an unsupported platform, modify your CSV file to match Koinly's required format using the CSV modification guide.
File format mismatch: Ensure your CSV file has the correct headers (such as "Date" for transaction dates) that Koinly expects. Check that your file's structure matches Koinly's requirements and modify if necessary.
Managing Duplicate Transactions
Duplicate transactions commonly occur when importing from multiple CSV files or the same file multiple times. Here's how to fix this:
Verify if the tokens (or data points) in your file differ from previously imported ones. Discrepancies could trigger duplicates.
Trim your CSV file such that it only starts from the last imported date to ensure no overlapping transactions are added again. When uploading multiple CSV files from the same source (e.g., separate files for trades and deposits from the same exchange), be particularly careful to avoid data duplication:
Identify potential overlap between CSV files before importing.
Consider uploading only specific transaction types (either deposits or trades) depending on your needs.
Review all imported data carefully to identify any duplication that might affect your tax calculations.
Resolving Issues with Reimporting Deleted Transactions
If transactions do not reimport after deletion and reuploading of the CSV file, the issue likely stems from the deletion process:
Ensure the transactions are permanently deleted. Any transactions marked as crossed out in Koinly remain in the system and prevent reimporting.
Refer to the Deleting and Permanently Deleting Transactions article for detailed steps on how to properly delete your transactions.
Manually add missing transactions if issues persist after troubleshooting. This ensures completeness and allows you to bypass upload errors that cannot be resolved through other methods.
Best Practices for Accurate CSV Imports
To minimize errors when importing data from any platform, follow these key practices:
Compare wallet balances as displayed in Koinly with the actual balances on the wallet platform to identify discrepancies.
Avoid opening CSV files in Excel or similar programs after download.
Export unedited, raw CSV files directly from the source platform.
Regularly review your platform settings to ensure correct data export configurations.
Before reimporting, clean your file and remove unnecessary or duplicate rows to avoid processing errors.
Regularly consult Koinly's official resources for updates on CSV formatting requirements or import processes.
Check CSV file compatibility: Ensure your CSV files match Koinly's expected format, particularly regarding column headers and data structure.
Modify incompatible CSV files: If importing from unsupported exchanges or platforms, use Koinly's CSV modification guides to reformat your data appropriately.
Verify no overlapping data: When uploading multiple files from the same source, ensure they don't contain the same transactions to prevent duplication issues.
Platform-Specific CSV Import Troubleshooting
Managing Binance CSV Import Issues
1. Resolving Small Imbalances
Small imbalances may occur due to Binance-specific features, such as Binance Earn bonuses or penalties. Binance doesn’t always provide data for these adjustments directly in CSV files. Here’s how to address these imbalances:
Compare the amounts you’ve sent to Binance Earn versus the amounts received (where applicable).
Be aware that calculations may require approximations if you have ongoing Binance Earn terms for the affected assets.
Note that Binance Support is unlikely to provide this missing data directly.
2. Fixing CSV Misinterpretations
If Koinly misreads a Binance CSV file, resulting in issues like incorrect reward claims:
Use the original Binance CSV: Avoid editing the file in Excel or similar programs, as this can corrupt data.
Verify decimal separators: Ensure the CSV uses consistent decimal separators (dots or commas).
Correct the 'Pair' column: Add a divider if necessary (e.g., modify
BTCUSDtoBTC-USD).Consult support documentation: Refer to Binance CSV Import Issues for additional troubleshooting steps.
Contact Koinly support: Share a problem-causing CSV snippet with the team for deeper analysis.
Managing Crypto.com CSV Import Issues
1. Preventing Skipped Transactions and Incomplete Data
When importing from Crypto.com:
Export all required historical files for every relevant year from Crypto.com.
Create a new wallet in Koinly and select "Import from file."
Use unedited, raw CSV files exported directly from Crypto.com.
Carefully review all transactions to address any discrepancies.
2. Ensuring Accurate Dashboard Balances
Avoid importing duplicates from earlier imports.
Follow guides like the Crypto.com integration guide and Ensuring Your Tax Report is Accurate for step-by-step assistance.
Importing Data from Unsupported Exchanges
Koinly also supports creating custom CSV files from unsupported exchanges. Follow the template provided in the custom CSV guide to reconfigure files for compatibility.
If you need to import data from exchanges or wallets that aren't directly supported by Koinly, you'll need to modify your CSV files to make them compatible:
Export your transaction history from the unsupported platform as a CSV file.
Modify the file structure to match Koinly's required format, ensuring proper headers and data organization.
Use Koinly's CSV modification guide for detailed instructions.
For more comprehensive assistance, refer to the guide on importing from unsupported exchanges.