No transfer is formed

Transactions for transfers are offered when a matching deposit of roughly the same amount exists for a withdrawal (or vice versa).

A warning is displayed when

1) The later deposit after a withdrawal on another wallet is missing,

2) The previous withdrawal before a deposit on another wallet is missing,

You can find more about warnings here.

1. A transfer is only formed automatically if:

1) The difference in amount between the deposit and the withdrawal is less than 10%
2) The time window between the deposit and the withdrawal is no more than one day
3) The deposit and the withdrawal do not take place on the same wallet

If the two transactions exceed the tolerance from 1) and 2), there is still, to a certain extent, the option to form the transfer manually. To do this, you open the deposit or withdrawal with the warning and click "Form transfer". Here you can select the other part of the transfer in order to link them into a transfer.

In addition, deposits explicitly cannot be summed up into withdrawals or vice versa.
Example: If you withdraw 1 DFI three times (Withdrawal), then 3 deposits (Deposits) will arrive on the destination wallet and not one aggregated deposit of 3 DFI. Wallets behave here like a bank account. There, too, you would record three individual incoming payments.

2. Note broken transactions

If you have imported transactions via native integrations, such as the Ethereum blockchain via MetaMask, it is possible that you tried to import a smart contract. If this smart contract is not known, this can result in a broken transaction. A transfer is then likewise not possible. You can learn more in the smart contract article.

3. Use a new setup

Interfaces of exchanges can change, just like the implementation and integrations in chain.report. Simply check whether the problem still exists after you have carried out a new setup (e.g. with the X button).

4. DeFiChain specifics

a) Due to the unfortunately unstable node software of DeFiChain, node detaches can occur. As a result, transactions can be missing. A new setup helps here as well.

b) Have you used the LightWallet and the MetaChain and, for example, MetaMask? Keep in mind that you have to create up to 3 wallets here (1 x DVM, 2 x EVM) so that all transactions and transfers are mapped correctly. You can learn more about this in the explanation video on creating a MetaChain EVM wallet.

c) Note that account-to-account or account-to-UTXO transactions are not supported and, in the case of broken transactions, require manual follow-up.

You have checked these points and still see an error?

If you think that the system has not formed a transfer here despite points 1) - 3)? Then we need a precise error description in which the error can be identified on the two specific transactions or on other points. Information would include, for example:

1) Which two transactions are involved? (date, time, transaction type, token, amount, ...)

2) Where do you see an error?

3) Can a screenshot illustrate this?

4) Is there a CSV with the relevant transactions?

5) What would your actual expectation have been?

If, however, you can clearly tell that 2 transactions should have been formed into a transfer despite checking the points above, 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 do not know exactly why?
Example: You cannot resolve warnings?
Example: There are balance discrepancies in the wallets.
Please understand here that we cannot take on a portfolio analysis for Non-Professional_User here in order to look for potential errors. This option exists for the Professional package. A good starting point would be our FAQ - there you will find answers to these three points and to most other questions.