Hi,

I'm running into an issue where the same real-world transaction is downloading repeatedly through Moneydance+ (Plaid) instead of being recognized as already-accepted.

I compared the raw transaction details for the original (already accepted) transaction and the newly downloaded duplicate, and found that the ol_fitid values are different between the two, even though it's the same transaction (same date, amount, and payee).

Details:
- Financial institution: Bank of America - Connection method: Moneydance+ (Plaid) - Moneydance version/build: 2024.4 (5253)

-Original transaction ol_fitid: mdplus:E9mgVNb6aDcLDnx8NXBBTaRQr7yyOMTnoLwKY -Duplicate Transaction ol_fitid: mdplus:JdK8eEmxQBCZB0LDgyQNT5mmd419bOf0qvjn3

• Original transaction ol_fitid_1: gQЗeoz8nVХumgQLANnJvtZqeJВxd8kUayp4mv

• Duplicate transaction ol_fitid_1: 4MYdoKrQAeS1mebZrK0bUM4k6Aba41TzVgpj7n

• Transaction date/amount/payee: [e.g. 07/312026, -$0.07, Bank of America Interest]

This is happening on multiple accounts.

Since the FITID is different each time this transaction downloads, Moneydance has no way to recognize it as already seen, and it keeps reappearing after I accept or merge it. This looks like an upstream issue with how Plaid is generating transaction IDs for this institution rather than something I can fix on my end.

Could you look into this and/or escalate to Plaid if needed? Happy to provide a console log or additional examples if that would help.

Thanks,