Bug 235967 - Incorrect Matching on Import
Summary: Incorrect Matching on Import
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-02 01:00 UTC by allan
Modified: 2011-09-28 18:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description allan 2010-05-02 01:00:58 UTC
Version:           Version 3.97.2-svn1121075 (using KDE 4.3.5)
Compiler:          gcc 
OS:                Linux
Installed from:    Compiled From Sources

Two entries in an OFX import should have matched with their corresponding schedules, but one imported transaction was matched against the wrong schedule entry.

I downloaded my bank statement via OFX including these two lines -
28 Apr  payee1  £149.88
28 Apr  payee2  £161.00

Result
28 Apr  payee1  £161    Scheduled entry matched with payee2 entry for £161.
                                  Bank entry payee2 £161
                                  Your entry payee1 £161
28 Apr  payee1 £149.88 not matched

So, the payee2 download of £161 has been matched with the payee1 schedule of 
£149.88.  The payee1 download has not been matched with the schedule for the 
same value.  The payee2 schedule is shown in grey for 1 May.

In brief, the match occurred on different amounts for different payees.  I 
created a fresh file and set up the two schedules and downloaded the OFX file and reproduced the problem.

In Kmm 1.03, on loading the same .kmy file, the schedule entries were displayed and accepted, then the OFX was imported and matched correctly.  In KMM 3/97, the scheduled items were not first displayed, but the payee1 schedule was matched, (incorrectly) during import.
Comment 1 allan 2010-05-02 01:03:36 UTC
The problem occurs also in the initial 3/97.2 svn release, not just the more recent.
Comment 2 allan 2010-05-10 22:59:03 UTC
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.
Comment 3 Thomas Baumgart 2010-08-02 10:10:03 UTC
Do the schedules have the 'This is an estimate' option turned on? Just want to make sure to have all the details.
Comment 4 allan 2010-08-02 12:23:37 UTC
(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.
Comment 5 Thomas Baumgart 2011-06-04 09:51:45 UTC
Does this still occur with more recent versions of KMyMoney?