The transactions might not be listed correctly
Some transactions should not be imported because they are, for example, not relevant for tax purposes. It's also possible that parts of some CSVs should not be read because they are redundant transactions from other CSVs or are only internal exchange transactions. Additionally, some lines in a CSV file cannot be extracted as individual transactions because they could be combined with other lines into a single transaction.
Another possibility is that certain products from some exchanges are not offered as data.
If you are missing transactions, for example, after an API sync, this is often correct because APIs often do not deliver all data and products. For instance, an API might only provide data from the last 3 months. Or it might be that an exchange API does not deliver transactions for Earn products or similar. chain.report then has no way to read these transactions.
Tip: Pay attention to the note when setting up the wallet, where you can find some information about limitations:
You see the transactions in CSV, on the website, but not in your API (or vice versa)?
Unfortunately, the data from exchanges often differs fundamentally between different output formats, including supported products. Therefore, we cannot accept the other source as evidence for a missing transaction in a bug report.
Transactions with wrapped assets like WBTC or WETH (or similar) are not listed?
We follow the tax argumentation of our partner tax advisor and assess these assets as the same economic goods, meaning that, for example, the exchange of WBTC for BTC (or vice versa) does not constitute a disposal. Accordingly, we standardize all WBTC and replace them with BTC. Since a trade from WBTC to BTC would thus become a trade from BTC to BTC, transactions of this type are no longer imported. This also means that arbitrage trading between wrapped assets and native assets cannot be captured (as well as its fees), and a strategy for capturing is needed, especially with frequent arbitrage trading.
Are staking transactions missing in your Bittrex or Bitget wallet?
As of December 2023, Bittrex unfortunately does not provide staking transactions via the API interface. Therefore, we currently have no way to capture these in chain.report.
Once Bittrex provides this data, we will connect the corresponding interface.
Our recommendation for a quick fix: Expand the deposits with a warning, edit the transaction, and change it to a staking transaction.
Also, with Bitget, the API does not deliver all rewards, even if they are listed on the web or in the CSV.Are transactions for staking and referral rewards missing in your Bitvavo wallet?
If you synced Bitvavo via the API interface, unfortunately, this information is not provided by Bitvavo. We recommend using the CSV import here to cover these transaction types as well.Are transactions missing in your KuCoin wallet?
Unfortunately, transactions are only delivered up to a certain point via the KuCoin interfaces. For some transaction types, this is 9 months, for others, only 30 days.
Have you engaged in liquidity mining on the DeFiChain?
Liquidity mining earnings are recorded in chain.report only once at the end of the day, aggregated as a single transaction for the day's total distribution. Due to this later recording, there may be a discrepancy in the amount of earnings for a day within a single day.Are account-to-UTXO or account-to-account transactions missing on the DeFiChain?
It may be correct that these are not displayed. If you view the transaction in the DeFiScan Explorer, you will see that your wallet is both the recipient and the sender of the funds. The remaining fees are often so negligible that the transaction is not listed in chain.report.
Are transactions missing in your DeFiChain wallet? Node disconnects could be the reason:
Unfortunately, the DeFiChain node software remains unstable up to version 4.0.9. As a result, our nodes occasionally lose connection. This can lead to missing transactions that cannot be reloaded. Consequently, there are also differing balances.
We hope for a stability update of the DeFiChain node software soon. For you, the only solution is to create a new setup, for example, with the X button. Therefore, you should also plan for new setups in the future.Are transfer domain transactions missing in your MetaChain wallet?
These are not really missing here, because for every transfer domain deposit, there is also, for example, a native deposit. If the transfer domain deposit were recorded, the deposit would end up being recorded twice.
Edit: Before 31.03.2024, this native accompanying deposit is unfortunately not always present, so a transfer domain deposit before this date may be missing.Have you exchanged DFI for WDFI? Or dBTC for BTC or csETH for ETH?
These tokens are standardized with us, and a corresponding trade would thus be ineffective - and therefore not read.
Are transactions missing in your crypto.com exchange wallet?
Unfortunately, the crypto.com API provides very incomplete data. You can upload the spot_trades.csv here. However, you must ensure that no transactions are redundantly imported. You should prepare for manual post-processing to correctly and completely represent your crypto.com exchange in the end. We recommend sending a request to crypto.com support to resolve the issue of missing data.
How to generate an API key for KuCoin can be seen here:
Therefore, our recommendation:
It's best to use the CSV export from KuCoin. Please make sure to use the correct path to the Trades CSV. If you download an XLSX file here, you've got the wrong file. The CSVs can then be uploaded in the wallet using the "Import Data" button. However, there are also data limitations with KuCoin. If transactions are missing here as well, you can request all your data via email from KuCoin Support. You will then receive an Excel sheet, which you can also upload in the wallet import on chain.report. But be cautious: KuCoin has recently been sending data that you could download yourself, which is limited to 2 years. Therefore, it's crucial that you specify in the email to KuCoin that you also need data older than 2 years.
Have you used the Margin Trading section of KuCoin?
This section is not yet supported by chain.report and can therefore lead to missing transactions and incorrect balances.
Do you have other missing transactions or are your wallet balances incorrect?
Then be sure to check this article.
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 could 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 relevant CSV file? Then please upload it as well.
But: A CSV file is generally not proof of missing data in the API connection. The data from CSV exports and APIs often differ from the exchanges.
If you were able to identify errors this 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're not sure 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.