All Collections
Platform Guides
Why do the in-app transactions look different from the transactions on the CSV?
Why do the in-app transactions look different from the transactions on the CSV?
Layla Huang avatar
Written by Layla Huang
Updated over a week ago

You may encounter situations where the data within the application appears different from the CSVs you imported, or the transaction count differs from your expectations. We have provided a list of potential explanations below.

1. There might be missing files

To provide more accurate data, we sometimes have to import the data from multiple CSVs. You can find this stated in the instructions or additional notes. If this is the case, ensure you follow the instructions and download and import all the required CSVs so the data will be complete.

2. The transactions are aggregated

We aggregate the transactions with the same timestamp for the same asset. If you have multiple transactions that happened at the same time, they might be aggregated in-app. For example, if you have these transactions in the CSV:

  • 01-01-2023 00:00:00 Buy 1 ETH

  • 01-01-2023 00:00:00 Buy 1.3 ETH

  • 01-01-2023 00:00:00 Buy 2.5 ETH

They might be aggregated into one transaction in the app:

  • 01-01-2023 00:00:00 Buy 4.8 ETH

3. The transactions are auto-grouped

We auto-group the transactions when they match our grouping logic. For example, a ‘buy’ and a ‘sell’ in the CSV might be grouped into a ‘trade’ in the app when the time and value match. We currently have below transactions that might be auto-grouped:

  • Transfer - Send and Receive

  • Trade - Buy and Sell

Note: Bridge does not auto-group.

4. The CSV format has been updated

Occasionally, exchanges may modify their CSV format or introduce changes to transaction types. As a result, CryptoTaxCalculator may not be able to recognize these transactions. If you notice missing transactions that are not a result of the aforementioned reasons, please contact our support team through the in-app chat. We will be happy to assist you by updating the transactions accordingly.

Did this answer your question?