Transactions for transfers are offered when a withdrawal matches a deposit of approximately the same amount (or vice versa).
A warning is displayed if:
The subsequent deposit after a withdrawal on another wallet is missing,
The prior withdrawal before a deposit on another wallet is missing.
More about warnings can be found here.
1. A transfer is only automatically formed if:
The amount difference between deposit and withdrawal is less than 10%,
The time window between deposit and withdrawal is no more than one day,
Deposit and withdrawal do not occur on the same wallet.
If the two transactions exceed the tolerances in 1) and 2), you can still manually form a transfer to a certain extent. To do this, open the deposit or withdrawal with a warning and click on “Form Transfer.” Here, you can select the other part of the transfer to link them.
Additionally, deposits cannot be aggregated to withdrawals, or vice versa.
Example: If you withdraw 3 times 1 DFI (Withdrawal), 3 deposits will arrive on the target wallet, not one aggregated deposit of 3 DFI. Wallets behave like a bank account here. You would also record three separate incoming payments there.
2. Consider defective transactions
If you’ve imported transactions via native integrations, such as the Ethereum blockchain via MetaMask, it’s possible that you tried to import a smart contract. If this smart contract is unknown, it can result in a defective transaction. A transfer is then not possible. Learn more in the Smart Contract article.
3. Use recreation
Exchange APIs can change, as can the implementation and integrations in chain.report. Simply check if the issue persists after performing a recreation (e.g., with the X button).
4. DeFiChain specifics
a) Due to the unfortunately unstable node software of DeFiChain, node detaches can occur, causing transactions to be missing. A recreation can help here as well.
b) Have you used the LightWallet and MetaChain, e.g., with MetaMask? Note that you may need to create up to 3 wallets (1 x DVM, 2 x EVM) to ensure all transactions and transfers are correctly represented. Learn more in the explanatory video for setting up a MetaChain EVM wallet.
c) Note that Account-to-Account or Account-to-UTXO transactions are not supported and require manual rework for defective transactions.
Have you checked these points and still see an error?
If you think the system should have formed a transfer despite checking points 1) to 3)? Then we need a precise error description, identifying the issue with the two specific transactions or other points. Helpful information includes:
Which two transactions are involved? (Date, time, transaction type, token, amount, ...)
Where do you see an error?
Can a screenshot clarify this?
Is there a CSV with the relevant transactions?
What was your actual expectation?
If you can clearly determine that two transactions should have formed a transfer despite checking the above points, 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 for non-Professional users, we cannot perform a portfolio analysis to search for potential errors. This option is available with the Professional Package. A good starting point would be our FAQ – there you’ll find answers to these three points and most other questions.