Support Desk

Submit a ticket My Tickets
Welcome
Login  Sign up

Missing Transactions Report: White Entries (No Match)

In this article, we explain why transactions without matches (white lines) appear in the Missing Transactions Report.


The main reason for entries with white lines are missing deposits and withdrawals.


For example, if 1 BTC was purchased on Kraken and then sent to Binance, both the withdrawal from Kraken and the deposit to Binance must be imported into CoinTracking.


If only the transaction data from Kraken (via API or CSV) is imported, the deposit to Binance is missing.


In this case, the withdrawal of the 1 BTC will appear in the Missing Transactions Report, as the deposit is still missing.


The same applies if only the Binance data is imported.


Now the report will show the deposit of the 1 BTC, but the withdrawal from Kraken is missing.


This is why all exchanges and wallets need to be imported into CoinTracking!


An example of missing transactions with white lines:



Here we see that there were six withdrawals from Kraken. The problem is that no corresponding deposits were imported. To fix the issue, the deposits for the withdrawals shown above need to be imported into CoinTracking.


Keep in mind, a transfer always consists of a withdrawal from Wallet A and a deposit into Wallet B.


Example:


The withdrawals from Kraken were all deposited into the exchange "Binance." Since the user forgot to import their Binance transactions, the withdrawals shown above are listed in the Missing Transactions Report.


Solution:


The user should import the exchange/wallet where these withdrawals were deposited.


In this case, Binance.


Additional reasons why transactions are shown in the Missing Transactions Report:


  • Duplicate Transaction IDs: Rarely, an exchange provides the same transaction ID for two withdrawals or deposits, which causes the software to skip one as a duplicate. In this case, the withdrawal or deposit must be added manually.
  • Combined Withdrawals or Deposits: Withdrawals and deposits have been imported as a single transaction. For example: You withdrew 1 BTC and then 2 BTC later. The deposit is recorded as 3 BTC, which leads to a missing transaction (2 withdrawals and only 1 deposit).
  • Special Transaction Types: Your deposits are actually airdrops, dividends, bonuses, discounts, forks, etc., but were mistakenly imported as a deposit. This automatically leads to a missing transaction because the system assumes there is a missing withdrawal. If it was, for example, an airdrop, then no withdrawal exists. In this case, the incorrectly imported transaction type must be changed to the correct type.
  • Credit/Bank Card Purchases: If a credit or bank card purchase was mistakenly imported as a deposit, the transaction must be entered as a trade with the FIAT investment.
  • Expenses or Lost Withdrawals: Your withdrawals are actually expenses (for goods or services) or a loss (sent to an inaccessible wallet or exchange). For this, use the transaction type "Expense."
  • Time Difference: It is rare, but sometimes withdrawals and deposits are more than 72 hours apart, which causes them to be displayed as missing transactions by the algorithm. Even with correctly imported data, the time gap leads them to be marked as missing (white). This can be ignored if the deposit and withdrawal times actually occurred this way.
  • Incorrectly Calculated Amounts: The fee for a withdrawal or deposit is missing or entered incorrectly, causing the amounts to be incorrect. In this case, please enter the fees correctly: Entering Fees


Important: The software pairs a deposit that is lower (or equal) to the withdrawal + fee.


If the fee was higher or lower, no correct match can be made.


Example:


Withdrawal 1.01 ETH + fee 0.01 ETH and deposit of 1.00 ETH = perfect match.


Withdrawal 1.01 ETH + fee 0.01 ETH and deposit of 1.01 ETH = no perfect match.



We often get asked whether transactions can be marked as related. 


There is no need to manually mark transfers as related, as our software automatically associates them based on matching amounts and timestamps.


However, there is an option to add comments in the comment section to have better oversight for related transfers.


You can go directly to the "Transactions" page and edit your transaction by clicking on this icon for a transfer:



There you can view the transaction history to find and edit the related transaction.


If no related transaction can be found, it must be added to CoinTracking.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.