What to do when seeing duplicated transactions?
If you encounter duplicate transactions where there shouldn't be any, follow the troubleshooting steps first.
1. Refresh the calculations
Navigate to Settings -> Portfolio & Tax and refresh the calculations to ensure the report is up-to-date.
2. Hard-refresh your page.
This clears your browser cache for the specific page, which forces it to load the most recent version of that page. This could include new scripts, styles, or features.
| Windows | Mac |
Google Chrome | Ctrl + F5 | Cmd + Shift + R |
Firefox | Ctrl + F5 | Cmd + Shift + R |
Safari | n/a | Opt + Cmd + E |
Microsoft Edge | Ctrl + F5 | n/a |
3. Remove sync that brought in the duplicates
If the first two steps haven't removed the duplicates, they you might need to use our Sync History feature to remove the import that brought them into the app.
To do this please follow our Sync History Feature article.
Why do I see duplicate transactions?
1. You might have accidentally hard-synced your wallet or API.
Hard syncing might cause duplicated transactions. If you realize that you might have hit the hard sync button instead of the sync button, you can potentially fix it by using the Sync History Feature to remove those transactions.
Read more about hard sync here.
2. You might have imported the same data via different sources.
Transactions from different sources (e.g., API and CSV) are all imported even when they are identical and with the same transaction ID. For example, both transactions in the table below are imported.
Timestamp | Trade Type | Asset | Transaction ID | Import source |
2021-01-01 00:00:00 | Buy | 1 ETH | 123456 | API |
2021-01-01 00:00:00 | Buy | 1 ETH | 123456 | CSV |
If you believe this is the case in your situation, utilize the filter option on the Transactions page to locate the suspected import source. Then, assess whether you want to remove one of these sources.
How does CTC distinguish transactions that are imported through CSV files?
Similar to API syncing, Crypto Tax Calculator recognizes the CSV transactions by their IDs. Unlike on-chain wallet Tx IDs , the ID column CTC abstracts could vary due to different formats provided by exchanges. For example, there could be order ID, trade ID, and transaction ID columns in one exchange CSV. You can check which ID CTC uses by checking the in-app transaction after importing the CSV file.
The same transaction ID might include multiple transactions. Hence, when importing a transaction that is modified, even though it has the same transaction ID as the other one, the transaction will still be imported.
What happens when importing the CSV that might have duplicate data?
If the transaction with the same ID already exists:
Importing another identical transaction, the transaction will not be imported. In the below table, only one transaction is imported.
Timestamp | Trade Type | Asset | ID |
2021-01-01 00:00:00 | Buy | 1 ETH | 0000001 |
2021-01-01 00:00:00 | Buy | 1 ETH | 0000001 |
Importing another transaction with the same ID, the transaction will be imported. In the below table, both transactions are imported.
Timestamp | Trade Type | Asset | ID |
2021-01-01 00:00:00 | Buy | 1 ETH | 0000001 |
2021-01-01 00:00:00 | Sell | 0.078 BTC | 0000001 |
If there is no transaction ID assigned in the CSV:
Importing another identical transaction with or without transaction ID, the transaction will be imported. In the below table, both transactions are imported.
Timestamp | Trade Type | Asset | ID |
2021-01-01 00:00:00 | Buy | 1 ETH |
|
2021-01-01 00:00:00 | Buy | 1 ETH |
|