Thanks for the report. This is a known issue with Plaid, where some banks don't give Kualia a clear understanding that a transaction is being updated. Just for your knowledge: every day or so, Plaid sends me data about a sync for a bank account. The data includes a list of NEW transactions and a list of UPDATED transactions. For most banks, when a transaction moves from pending to cleared, it comes in as an UPDATED transaction. However, a few banks put it in the NEW list. Meaning Kualia can't tell that it should update an existing transaction, causing it to just create a brand new transaction with the same information. There is something I can do about this, though. I can be try to be smart about it where a transaction coming in with the same amount and cleared should check first if a similar transaction already exists, and to just update it. The hard part is making sure we don't have any false positives. Meaning, if you actually did make two transactions of the same amount, we should not just update the first one. I'll see what I can do!
Ahhhh that makes sense, would a feature that marks potential duplicate help? That way it wouldn’t automatically combine the two things together but could alert the user and allow them to investigate it further. And make proper adjustments or even allow them to combine or ignore. Not sure if that would work or make things more complicated but thought it might be a helpful solution.
I made some changes for this. Let me know if it happens again. If not for a week or so, I'll consider my fix good and complete this request 🤝