Summary: | Incorrect Matching on Import | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | allan <agander93> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
allan
2010-05-02 01:00:58 UTC
The problem occurs also in the initial 3/97.2 svn release, not just the more recent. This really boils down to two issues. 1) Outstanding schedules were not being entered. Because of this the other issue emerged. This first problem, of schedules not being entered, appears now to have been resolved. However.... 2) matching against schedules. a) On opening KMM, now, outstanding schedules are flagged. If all are now entered, and then the import is performed, all works as expected. b) On opening KMM, skip the outstanding schedules. During import, it is found that imported items appear to match scheduled items. If this matching is not accepted, import continues and there is no problem, apart from now needing to do manual schedule entry and matching. c) As for b) except during import, accept the items found possibly to match. This is where the incorrect items got matched. So, if the schedules are entered before import, all is OK. If they are entered during import, mismatching occurs. Do the schedules have the 'This is an estimate' option turned on? Just want to make sure to have all the details. (In reply to comment #3) > Do the schedules have the 'This is an estimate' option turned on? Just want to > make sure to have all the details. In this case (with the example quoted), and currently, both payees have that option turned on. I can't be sure what might have been the case originally. I've just now loaded a kmy file from about six weeks ago with lots of overdue schedules, which initially I skipped. When during import the possible matches against schedules were flagged, I accepted them. The result is a bit of a mess. One payee has been allocated to four unrelated items. Three were for deposits of £37.85, £3.84, £3.84 and a cheque payment of £622.75. The payee allocated is for my car tax, last paid in March at £215. Neither it nor the 'matched' entries are schedules. Also, the two payees originally reported on (and above) show up again. One is correctly matched against its schedule, but the other is incorrectly matched against the first payee, ignoring the payee shown in the detail. Does this still occur with more recent versions of KMyMoney? |