Please make sure to upload the correct CSV or XLSX. In the crypto.com app, for example, different types of transactions can be exported:
So, for each wallet, ensure you export the right file and then select the correct version before uploading it. Naturally, you should only upload Binance CSVs to a Binance wallet, crypto.com (App) CSVs to a crypto.com (App) wallet, and so on.
Example: You want to upload the CSV file with trades for the Binance exchange. To do this, create a Binance wallet, click on "Import Data," and then select "Trade." Before uploading, you can often expand a guide here. For this example, it looks like this:
Additionally: In every created wallet, you also have the option to upload the chain.report template. Please ensure you upload the correct file to the correct wallet with the correct CSV selection.
Make sure the files are not reformatted. Microsoft Excel, in particular, saves files in a different format after opening (e.g., with date formatting). This makes the file unreadable. Please try again with a "fresh" file.
Check the file with a different editor, e.g., Notepad. Are there any anomalies? Reformatting? Inserted blank lines? Please do not save after opening here either.
Can't upload your trades on KuCoin?
Then you probably uploaded the wrong file, namely the orders as XLSX. You can find the correct file here:
https://www.kucoin.com/order/trade/detail
The ANYCOIN XLSX format is unfortunately defective after export and cannot be read by chain.report. As a workaround, you can open and save the file with MS Excel - then the file can be read again.
With Plutus, the Dex Enhancer Tool unfortunately delivers inconsistent formats. Therefore, some files cannot be read. Note: Import is only possible via the Dex Enhancer.
With bake.io, make sure to use the correct upload format and please follow the explanatory video when setting up the wallet. The currency must explicitly be selected as Euro, and the tax report should not be exported.
When using the template, ensure that you have filled in the columns correctly. For example, the deposit value with currency must not be missing in the type and should not be swapped with the withdrawal column. Support does not check a template that is not filled out correctly.
If these points have not helped,
Contact us after careful review via the contact form on the website, and we will check the format of the file. If any point from the above list applies, we unfortunately cannot process the bug report further.
Have you checked these points and still see an error on chain.report?
Then we need a precise error description where the error can be identified in specific transactions or other points. Information would include:
1) Which transaction(s) are involved? (Date, time, transaction type, token, amount, ...). Please provide a single example if possible.
2) Where do you see an error?
3) Can a screenshot clarify this?
4) Is there a suitable CSV file? Then please upload it as well.
If you were able to identify errors so clearly, please send us the data via the support chat on the website.
If you cannot clearly identify the error or its cause:
Example: The tax burden is too high, but you don't know exactly why?
Example: You can't resolve warnings?
Example: There are balance discrepancies in the wallets.
Please understand that we cannot perform a portfolio analysis for non-professional users to search for potential errors. This option is available for the Professional package. A good starting point would be our FAQ - there you will find answers to these three points and most other questions.