Bug 365023 - Payee listing
Summary: Payee listing
Status: CONFIRMED
Alias: None
Product: kmymoney
Classification: Applications
Component: onlinebanking (show other bugs)
Version: git (master)
Platform: Mint (Ubuntu based) Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL: https://www1.royalbank.com
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-07-02 21:52 UTC by binky
Modified: 2018-10-29 20:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description binky 2016-07-02 21:52:43 UTC
program keeps assigning bank transaction info as payee; requiring regular deletion of them from payee list

Reproducible: Always

Steps to Reproduce:
1. download transaction from Royal bank of Canada
2.
3.
Comment 1 allan 2016-07-02 23:18:39 UTC
A bit more information might help us.  It sounds like you may be importing?  If so, by what method?
What revision of KMyMoney are you using? (Help>About KMM).  Distro package or compiled from source?
Have you considered setting up matching for the payee name you wish to use?
Comment 2 Thomas Baumgart 2018-10-13 16:20:31 UTC
status change was not performed
Comment 3 Jack 2018-10-13 19:08:30 UTC
I don't know what the situation was for the original poster, but when I import OFX (I'll have to review my settiongs) if KMM doesn't match the payee to an existing one, it creates a new payee with the exact name.  If the original poster does not respond, I might consider changing this to a wishlist for there to be a user option for KMM to never create a new payee on import.  For me, it is much more common that I need to adjust the matching criteria for an existing payee than that I really need a new payee.
Comment 4 Andrew Crouthamel 2018-10-29 03:33:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Jack 2018-10-29 20:56:26 UTC
I'm reopening, but changing to a wishlist.  The issue is that if payee matching does not recognize the imported field designated to hold the payee, it creates a new payee.  Most of the time, what is needed is not a new payee, but to modify the matching for some existing payee.  I would like a setting so that either no payee is created (creating a transaction which must be edited before accepting) or there is a popup asking whether to create a new payee or allow the user to choose an existing one.

In addition (but probably should be files as a separate wishlist) whether the transaction matches or creates a new payee, the field used to indicate the payee is NOT included in the memo field of the new transaction, often losing information (for example, the particular branch of a store).