Transaction deviation causation
Transaction deviations occur after the calculation algorithm detects a discrepancy between the inflows and outflows of inventory, in this case, crypto coming in and going out. If one wallet with a previous balance of 0 Bitcoin receives 1 Bitcoin and a subsequent transaction is a send event of 1.1 Bitcoin, there is a transaction deviation. The most common reasoning for a transaction deviation to occur are:
- API missing transaction data
- An isolated DeFi interest accrual incident
- A CSV with incomplete data or the CSV timestamps incorrectly assigned.
- Ignoring transactions that should not be ignored.
Step 1: Review the transactions affected by the deviations
When a calculation is complete and deviations exist within the transaction dataset, an orange bar will pop up with the percentage of transactions affected by the deviations. Deviations occur when inflows do not match outflows or when market data is missing. You will be able to review the year and asset type where the transaction deviation took place.
Step 2: Review deviated transactions
Head to the Transactions tab to filter out your deviated transactions.
Step 3: Resolve deviated transactions
Review what caused the transactions to deviate. This occurs when inflows do not match outflows or when market data is missing. In this scenario, market data is missing for two receive type transactions through an Ethereum address. Market data must be present for a calculation to be accurately reported for each transaction.