Bug 440800

Summary:	Import of credit card transaction with invalid Payee
Product:	[Applications] kmymoney	Reporter:	George <hexdump>
Component:	importer	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	ostroffjh
Priority:	NOR
Version:	5.0.8
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description George 2021-08-09 17:34:54 UTC

I think that the import of credit card transactions is not working correctly when the Merchant Name is not already in KMyMoney. It appears that it is using the last known merchant Name instead of leaving it blank.
Here is a recent example:
<STMTTRN>
<TRNTYPE>PAYMENT
<DTPOSTED>20210806160000[0:UTC]
<TRNAMT>-1.07
<FITID>202108061
<CORRECTFITID>202108061
<CORRECTACTION>REPLACE
<NAME>Kindle Svcs*2P8C792O1 866-321-88
<MEMO>Kindle Svcs*2P8C792O1 866-321-88
</STMTTRN>


This imported with a Merchant name of
Zelle Transfer Conf# T0BN438LM;
and there is no such a name anywhere in the file being imported.

Not good.
Is there a setting within KMyMoney to tell it to make it a blank or some such ?
Help !!!

Comment 1 George 2021-08-12 15:01:42 UTC

Merchant should say Payee

Comment 2 Jack 2021-08-12 15:24:53 UTC

5.0.8 was released January 2020.  Is it possible for you to upgrade to a newer version?  You can also try using an AppImage (https://kmymoney.org/appimage.html)

I am not aware off any way to tell KMM to leave the Payee blank, but there are settings reagarding which OFX filed to use as the source for the Payee.  However, you are correct that it should not create a payee from data unlrelated to the transaction.

One additional thought - please look at the payee info for "Zelle Transfer Conf# T0BN438LM" and see if it has matching enabled, and if anything in the new transaction happens to meet the matching criteria.

Comment 3 George 2021-08-13 13:46:51 UTC

I tried 5.1.2.1e with the same result. I tried messing with the which OFX field to use for PAYID with no change. I tried NAME.(In reply to Jack from comment #2)
> 5.0.8 was released January 2020.  Is it possible for you to upgrade to a
> newer version?  You can also try using an AppImage
> (https://kmymoney.org/appimage.html)
> 
> I am not aware off any way to tell KMM to leave the Payee blank, but there
> are settings reagarding which OFX filed to use as the source for the Payee. 
> However, you are correct that it should not create a payee from data
> unlrelated to the transaction.
> 
> One additional thought - please look at the payee info for "Zelle Transfer
> Conf# T0BN438LM" and see if it has matching enabled, and if anything in the
> new transaction happens to meet the matching criteria.

The payee matching was the answer. when I took it off, the import worked as intended.
thanks

Comment 4 Jack 2021-08-15 17:37:51 UTC

I'm going to close this as NOT A BUG, since KMM is behaving as designed.  
The team is definitely aware of this type of problem, and if there isn't already one, I may file a separate bug about giving the user better control of the automatic creation of new payees on data import.