https://bugs.kde.org/show_bug.cgi?id=326100
--- Comment #2 from Matthew Schultz <matt...@gmail.com> --- (In reply to comment #1) > I believe that matching is based on a transaction id provided by the > bank/credit card. Is there any chance your institution made any changes to > their system in the past month? Also, does each transaction duplicate just > once, or does it create a new one each time you update the account? > > Additional question - how do you have your online settings for that account > set? You can set how far back it tries to update each time it connects. > Setting it to the last time you updated might at least eliminate some of the > duplication. I'm not aware of any changes my bank has made with transactions. What I do recall is as soon as I upgraded from 4.6.2 to 4.6.3, I immediately started getting duplicate transactions every time I click update. This occurs every time on the same transactions assuming I do it again the same day and there hasn't been any new transactions. It doesn't even matter if I previously accepted it, they will be marked as duplicates again on a subsequent update. I changed the setting so it checks the last 30 days instead of 60 days which has limited the number of duplicate transactions but this is still rather annoying since I still have to accept the last 30 days of duplicate transactions every time I update. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
