Bug 243669

Summary: Payee automatism gives strange results (Part 1)
Product: [Applications] kmymoney Reporter: andreas.grupe
Component: generalAssignee: 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:
Sentry Crash Report:

Description andreas.grupe 2010-07-05 17:39:29 UTC
Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

I do it in two parts as the payee assignment ends up in two different scenarios. Maybe you will put part 1 and part 2 together.

Part 1: A payee already exists and former transactions with a category happened on this payee. An other payee with a similar name is treated exactly the same way, what is totally wrong.

Reproducible: Always

Steps to Reproduce:
Payee PAYPAL => the first transaction via aqbanking was assigned to a category
Today a new payee:
Payee PAYSAGE (this is a customers company name) via aqbanking => Is handled as if the customer name was PAYPAL. Transaction is assigned a wrong category (the one PAYPAL had)

Actual Results:  
Wrong category assigned

Expected Results:  
See that the customer is new; don't assign a category

Another one: Old customer "KIRSTE" new customer "Kirsten" is treated like the old one.
Comment 1 Alvaro Soliverez 2010-07-05 17:54:28 UTC
What version of KMyMoney are you using? Where did you install it from?
Comment 2 andreas.grupe 2010-07-05 18:03:19 UTC
I'm using 3.98.1 and downloaded it from http://kmymoney2.sourceforge.net/index2.html

Sorry that I missed that.

Andreas
Comment 3 Thomas Baumgart 2010-08-02 10:42:37 UTC
What are the option settings on PAYPAL on the "Matching" tab of the payee?

Does the transaction of PAYSAGE show that name or is it attached to PAYPAL?

The "Kirsten/KIRSTE" case is by design. This is to allow matching the payee name with any addition provided by some stores. This might not happen with HBCI but is common using QIF or OFX. You can avoid it by adding "^KIRSTE$" to the list of matching names.
Comment 4 andreas.grupe 2010-08-02 15:27:39 UTC
The options for Paypal are "Nach Zahlungsempfänger zuordnen" (the middle
one, don't know the english text) as are all payees automatically
assigned to.

The transaction PAYSAGE is treated as if it was a PAYPAL transaction.
The name shown was correct but the category assigned was wrong.
Paypal is assigned to transactions comming from a (manual) bank account
(as Paypal does not provide an online account) matching my normal online
bank account. Paysage is a payment from a customer comming to my normal
online bank account.
If it's still unclear I can only give more details in German ;-(

To touch every single payee to avoid the Kirsten/Kirste case is not
possible. I would have to touch hundreds of payees. And all new payees
every day (between 10 and 20 per day) , too.

And there are other cases like Kaufhof (expense category) is treated the
same as Hof (income) and so on and so on.

I'm working with HBCI.

Hope that helps. I'm happy to provide more details. The only thing I'd
like to have is a simple way to stop the automatism to assign
transactions to customers.

Thanks for your help.

Andreas

Am 02.08.2010 10:42, schrieb Thomas Baumgart:
> https://bugs.kde.org/show_bug.cgi?id=243669
>
>
>
>
>
> --- Comment #3 from Thomas Baumgart <ipwizard users sourceforge net>  2010-08-02 10:42:37 ---
> What are the option settings on PAYPAL on the "Matching" tab of the payee?
>
> Does the transaction of PAYSAGE show that name or is it attached to PAYPAL?
>
> The "Kirsten/KIRSTE" case is by design. This is to allow matching the payee
> name with any addition provided by some stores. This might not happen with HBCI
> but is common using QIF or OFX. You can avoid it by adding "^KIRSTE$" to the
> list of matching names.
>
>
Comment 5 andreas.grupe 2010-08-02 15:46:09 UTC
Sorry for writing a 2nd mail.

I recognised an other case. It happens that customer names are
misinterpreted and they are displayed wrongly, too (like Meyer is
correkt but Meiner is displayed). And often the payee names are not
recognized at all. Even if the text is more or less the same as with
other transactions where the names are read correctly.

I'll post you an example for the first case here, as soon as it happens
again.

Cheers

Andreas

Am 02.08.2010 10:42, schrieb Thomas Baumgart:
> https://bugs.kde.org/show_bug.cgi?id=243669
>
>
>
>
>
> --- Comment #3 from Thomas Baumgart <ipwizard users sourceforge net>  2010-08-02 10:42:37 ---
> What are the option settings on PAYPAL on the "Matching" tab of the payee?
>
> Does the transaction of PAYSAGE show that name or is it attached to PAYPAL?
>
> The "Kirsten/KIRSTE" case is by design. This is to allow matching the payee
> name with any addition provided by some stores. This might not happen with HBCI
> but is common using QIF or OFX. You can avoid it by adding "^KIRSTE$" to the
> list of matching names.
>
>
Comment 6 Thomas Baumgart 2011-09-28 19:02:28 UTC
Did it happen again in the meantime?
Comment 7 Thomas Baumgart 2012-01-03 09:13:21 UTC
Changing state due to missing feedback