Implement duplicate transaction flag and suggested rule to delete CSV or API version of transaction.

Describe the problem:
example: when importing transactions via CSV and API from binance you will receive a lot of duplicates. Kojnly should implement a solution to flag potential duplicate transactions by comparing the amount and time of transaction. Not that the API imported and CSV imported is rounded differently and time is also usually off by a few minutes.

Which exchange/wallet is this regarding?
Binance as an example but probably applies to most if not all exchanges where its possible to combine CSV and API imported transactions.

How did you import data into this wallet?
CSV and API

What have you tried to fix this so far?
No fix available other than manually cleaning up transactions one by one.

Hi @alexandernordbo

While this is a requested feature on our feedback portal which you can upvote to receive updates on the case, we do not suggest mixing API and CSV in the same wallet covering the same period as it results in duplicate transactions.

When it comes to Binance, if you have issues with the API, I suggest you use the CSV import method to create your wallet following the instructions in the guide below:

https://koinly.io/integrations/binance/