https://bugs.kde.org/show_bug.cgi?id=340956
--- Comment #3 from Jack <ostrof...@users.sourceforge.net> --- I am assuming that by actualisation you mean download. (I seem to recall someone once using that term for reconciliation, which is a completely different issue.) A downloaded transaction will only ever match a manually entered transaction, not another downloaded one. However, it sound like in your case, it is not that the new transaction should MATCH the previously downloaded transaction, but should be detected as a DUPLICATE, and not imported at all. Duplicate detection is based on a bank ID in the transaction. If that is not there, KMM cannot know it is a duplicate. Can you create a simple sample file which shows the problem? For example - create a new KMM file with one account, do an import, and then repeat the same import. -- 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
