Bug 236388

Summary: QIF Import Matching Problem
Product: [Applications] kmymoney Reporter: allan <agander93>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: CLOSED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description allan 2010-05-05 01:53:38 UTC 
Version:           3.97.2-svn1121075 (using 4.3.5 (KDE 4.3.5) "release 0", openSUSE 11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.12-0.2-desktop

This problem is I believe also present in v1.03.

I imported a QIF bank statement file including the following item - 

D22/04/2010
Ppayeename 
T-£xxx.xx
Mmemo
^

The payee name imported was correctly matched against an existing configured name.  However, the detail was instead shown as an investment transaction to an unconnected security.  It also showed under that security with both quantity and value numerically identical to the value of the transaction and with a price of £1.57 obtained from heaven knows where.

Looking at that payee, the previous transaction, six months earlier, also was a withdrawal, which was used to fund a purchase of the security in question.  So, the payee name was correctly matched, but the matching has gone a bit overboard.

I hope that's fairly clear.

I think I recollect reporting something similar to this at the time of the qif import rework.
Comment 1 allan 2010-05-05 01:56:34 UTC 
Also, the entry in the security is numerically invalid.
Comment 2 Cristian Oneț 2011-08-12 13:14:37 UTC 
Allan could you resurrect this report? We've come a long way since 3.97.2-svn1121075 and who knows... maybe you'll even find the problem since you've become more familiar with the QIF importer :).
Comment 3 allan 2011-10-28 16:19:08 UTC 
(In reply to comment #2)
> Allan could you resurrect this report? We've come a long way since
> 3.97.2-svn1121075 and who knows... maybe you'll even find the problem since
> you've become more familiar with the QIF importer :).

I know I saw this happen several times, but not recently.

I think it's best closed, and I'll investigate more should it happen again.