https://bugs.kde.org/show_bug.cgi?id=315072
--- Comment #37 from Cristian Oneț <onet.crist...@gmail.com> --- (In reply to Florian from comment #36) > Today I imported my transactions from my bank account and the algorithm was > neither able to match the imported transactions nor did it recognize > duplikates. It worked pretty much better with release 4.6. OK, I get that, but the above statement isn't really helpful to figure out why matching does not work. Duplicate detection works the following way: - amounts must match (considering variation for schedules) - bankids must match or the existing transaction must have an empty bankid The payee was added as a matching criteria to avoid a wrong match scenario described here https://git.reviewboard.kde.org/r/107759/. Could you apply these conditions to your data and report back why is the matching and duplicate detection failing? -- 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
