Support Desk

Submit a ticket My Tickets
Welcome
Login  Sign up

Missing Transactions Report

In the missing transactions report, you can check missing transactions, filter by different settings and jump directly to the transactions to fix them.


How to get there:


To find the "Missing Transactions Report" on CoinTracking, go to Reporting- "Missing Transactions".



This article is divided into 4 sections:


1) What is the missing transactions report for?


2) How to search for missing transactions


3) How to solve white lines in the missing transactions report


4) How to solve colored lines in the missing transactions report

 


1) What is the missing transactions report for? 


The "Missing Transactions" report, lets you identify and resolve missing transactions, which can happen due to missing deposits and withdrawals and because of wrong transaction fee entries.


It is important to review your missing transactions because it allows you to ensure the accuracy and completeness of your cryptocurrency transfers.


It is important to solve your missing transactions in order to calculate your assets accurately.


2) How to search for missing transactions

To properly utilize the Missing Transactions Report, please do these three steps:

1) Show all transactions

2) Sort by date

3) If needed, search for a specific coin.



3) How to solve empty/white lines in the missing transactions report


Firstly, we will explain why transactions may appear as unmatched (empty/white) in the missing transactions report.


When you see a white line, you have an incomplete transfer.


A transfer always consists of a withdrawal from source A and a deposit to destination B. 


If, for example, you buy 1 BTC on Kraken and then send it to Binance, you will have to import the withdrawal from Kraken as well as the deposit into Binance!


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


Then, the withdrawal of 1BTC will be shown in the missing transactions report, because the deposit is missing.


The same is the case if you only import your Binance data:


Now you will be shown a deposit of 1BTC into Binance, but the withdrawal from Kraken will be missing.


For this reason, every exchange and wallet needs to be imported into CoinTracking!


Here we have an example of missing transactions, marked as white lines:



We can see, that there were six Bitstamp withdrawals.

The problem is, that no corresponding deposits have been imported.

That is why the lines are being displayed as white.

In order to fix this issue, you need to import where the withdrawals have been sent to (deposited).


We remember that a transfer always consists of a withdrawal from wallet A and a deposit to wallet B.


Example:


Let's assume the withdrawals from the picture above have been sent to the exchange "Binance".

The user, however, forgot to import his Binance transactions into CoinTracking, that is why the withdrawals are being shown as white lines.

They are missing their corresponding deposits!


Solution:


The user imports the exchange/wallet where the coins have been deposited to.


In this case, the exchange is Binance.


After importing the Binance data, the missing transactions should disappear and turn into green (matching) transactions.


There is no option or necessity to manually mark transfers as green or matching.

You can add comments in the comment field of each transfer that belongs together to keep track of their association.


You can jump directly to the transfer on the "Enter Coins" page by clicking on the button/link at the end of each line.


There you can check the transaction history to identify the counterpart transaction and in case it's not there, you could add it here.



Other reasons as to why transactions may appear as unmatched (white) in the missing transactions report:


  • Missing Data: This can occur with manual entries, especially when the transactions appear similar.
  • Duplicate Transaction IDs: The exchange provided the same transaction ID for two deposits or withdrawals, causing the software to skip one as a duplicate.
  • Combined Deposits or Withdrawals: Deposits or withdrawals were imported as a single transaction, where multiple deposits or withdrawals were combined into one entry. For example, if you withdrew 1 BTC and then 2 BTC, the deposit would show as the total of 3 BTC.
  • Special Transaction Types: Your deposits may include airdrops, dividends, bonuses, rebates, forks, etc., which need to be renamed to the particular transaction type on the Enter Coins page via the edit option (for forks, refer to this article: Entering Forked Coins).
  • Credit/Debit Card Purchases: If a credit or debit card purchase is mistakenly recorded as a deposit, it should be edited on the Enter Coins page to reflect a trade with the FIAT currency used for the purchase.
  • Spend or Lost Withdrawals: If you sent funds for goods or services (Spend) or to a no longer existent wallet or exchange (Lost), the withdrawals should be edited on the transactions page to reflect the appropriate transaction type. If you had already manually entered such a transaction, delete the manual entry and keep the edited withdrawal (deleting the withdrawal without renaming it would cause it to be re-imported during the next API check).
  • Time Difference: If there is a time gap of more than 72 hours between a deposit and a withdrawal, and they are not marked as green, you can ignore those transfers.
  • Incorrectly Calculated Amounts: If the fee for a withdrawal or deposit is not included or calculated incorrectly, it can result in incorrect amounts. You can learn how to enter fees correctly by referring to the appropriate guidelines.


           Important: The software for example matches a deposit that is lower (or the same) as the withdrawal + fee.

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


          Examples


Withdrawal 1.01 ETH + Fee 0.01 ETH and Deposit 1.00 ETH - perfect match.

                          

Withdrawal 1.01 ETH + Fee 0.01 ETH and Deposit 1.01 ETH - not a perfect match


  • FIAT Transactions: If you have deposits or withdrawals in FIAT currencies (e.g., USD, AUD, EUR), they do not require a counterpart transfer. Simply set the filter on top to "All currencies but FIAT."



4) How to solve colored lines in the missing transactions report


A transfer always consists of a deposit and a withdrawal.


The probability of a matching transfer pair depends on the time of the withdrawal/deposit and the amount of the transfer pair.


If the time of the deposit is before the withdrawal or the amount of the transfer pair is not matching (for example due to wrong fees) you will see colored lines in the missing transactions report.


The probability of having a correct transfer pair is divided into the following categories:


Exact, high, medium, low and none.


Here is a list of the colored lines and the reasons as to why they appear:



Exact (green):


The transfer matches exactly in terms of amount and time.



High (green):


The transfer matches exactly in terms of amount and time, but the amount is slightly different.

This can happen due to a wrong or missing transaction fee.




Medium (yellow):


The deposit occurs before the withdrawal and or the amount is different.


To fix this, make sure that the withdrawal and deposit have the same time stamp.


You can do this by clicking on the arrow on the right side of the line, which leads you to the Enter Coins page, where you can change the timestamps.



Yellow lines can often be a sign of a forced, not ideal match and have to be checked.


Example: 



Here you can see that a withdrawal of 22 ARDR and a deposit of 23! ARDR have been incorrectly matched (yellow lines)


This happened because the withdrawal of 22 ARDR (first line) is missing a deposit and the software thinks that the deposit of 23 ARDR (last line) was the corresponding deposit to the withdrawal of the 22 ARDR (first line)


In reality, the withdrawal of the 23 ARDR (highlighted in green) and the deposit of the 23 ARDR (last line) should have matched together.


In order to resolve this error, the user needs to add the missing deposit of 22 ARDR to match the withdrawal of 22 ARDR (first line).


Low (orange): The deposit occurs before the withdrawal and the amount is not an exact match (please verify if the match is correct)


Even with a "Medium" or "Low" match, the chances of it being correct are quite high. However, it is recommended to double-check the transactions.


If you are sure that you have a correct match (deposit and withdrawal are matching) you can convert a medium or low match into a "High" or "Exact" match, by either entering the same time for both the deposit and withdrawal entries on the Enter Coins page or include any missing fees so that the amounts match exactly.



Common problems and solutions:

My blockchain transactions are not imported correctly. Why?


Exchange closed or missing data due to wallet inaccessibility



Did you find it helpful? Yes No

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