https://bugs.kde.org/show_bug.cgi?id=315072
--- Comment #49 from Cristian Oneț <onet.crist...@gmail.com> --- (In reply to Jack from comment #47) > Are we mixing up matching an imported transaction to a payee with noting an > imported transaction is a duplicate of an existing transaction? Does it > matter whether an imported transaction is checked for being a duplicate > before or after it is matched to a payee? No we are not mixing up this. AFAIK before the imported transaction is created payee matching is performed and after that the imported transaction is matched to existing transactions. The second match considers the payee as a match criteria so in order for it to work correctly the first match must work as expected. I'll check the code to make sure that this is actually true but as I recall this is the way it's done. -- 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
