[Kmymoney-devel] KMyMoney - Matching priority

[aga]

On Saturday 01 May 2010 17:10:12 Thomas Baumgart wrote:
> Hi,
> 
> on Saturday 01 May 2010 aga wrote:
> > On doing an OFX download, two entries were matched that were unrelated.
> >  The payees were different, but the amounts were the same.  One of them
> >  should have matched against the correct payee, although the amount was
> >  different.
> >
> > Is that what should happen?  I would have thought that the same payee
> > would take precedence, rather that the amount.  If the amount has to be
> > identical for matching, a completely different payee should not be
> > accepted, should it?
> 
> Yes, it should. I have seen it lately too many times, that the payee
>  changes its name on the transaction.  The matcher can use some improvement
>  though.  I will be working in this area after the 4.x release.
> 

This is getting worse!  And I don't think it's me.  It's these same two items.

Item 1)  Sefton - council tax
			- scheduled monthly payment £149
			- next due date 28 April
Item 2) NPower - gas
			- scheduled monthly payment £55 (current value, should now have been £161)
			- next due date 28 April

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

Result
28 Apr	Sefton	£161	Scheduled entry matched with NPower D/L entry for £161.
						Bank entry NPower £161
						Your entry Sefton    £161
28 Apr	Sefton	£149.88	not matched

So, the NPower download of £161 has been matched with the Sefton schedule of 
£149.88.  The Sefton download has not been matched with the schedule for the 
same value.  The NPower 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.

Something's amiss, I think.

Allan