Bug 305019

Summary: Import from Gnucash
Product: [Applications] kmymoney Reporter: Rajesh Ganesan <ca.grajesh>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: CONFIRMED ---    
Severity: wishlist CC: ca.grajesh, mrp, onet.cristian
Priority: NOR    
Version: 5.1.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rajesh Ganesan 2012-08-12 12:11:56 UTC
If I am to download my accounts from gnucash, my description in gnucash is
mapped/imported to payees. Is it possible to map it to description/memo in
kmymoney2 during import? If payee is compulsory during import, we may map account heads to payees. It is easy to modify account heads later than to correct all narrations - which > involves great deal of time!
May I request the developers to consider including such feature (such option need not be default, it may be asked at the time of import in the dialog box) in upcoming versions?

Reproducible: Always

Steps to Reproduce:
1. Import a gnucash file
2. You may see that all your description is imported as payees
3.
Actual Results:  
Payees have all the description given in gnucash

Expected Results:  
1. Payees may be just the name of the accounts in gnucash
2. Description should be imported as description

1. Such an option may be provided to choose in the import dialog
2. User may leave the default import options or map the description of gnucash to description of kmymoney
Comment 1 Cristian OneČ› 2014-07-29 08:29:24 UTC
I'm marking this as a wish. Adding a gnucash testfile that can be used to see the current behavior would be nice.
Comment 2 Nate Graham 2024-06-14 15:10:49 UTC
Migrating "reproducible" keyword to "CONFIRMED" status.
Comment 3 Jack 2024-06-14 15:24:07 UTC
I'm tempted to close this as UNSUPPORTED, but I don't know if the problem is still present with 5.1.3 or master branch.  However, it would help if someone who needed this could could re-write the description of what is actually desired, using more accurate terminology, as PAYEEs have names, and there is a NOTES field, but no DESCRIPTION.
Comment 4 Mark Penner 2024-06-14 18:07:37 UTC
As documented here: https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.impexp.html#idm3078 under "Payees"
> Payee names are generated by the importer from the GnuCash transaction's Description field.

I understand the feature request to be: have an option in the import dialog to not use the GnuCash description field as payee, but rather either leave payee blank if possible or generate payee from the account name. I'm not sure why you would want the payee to be generated from the account name.

In my own GnuCash file, I started out putting a description of what the transaction was for in the description field and the payee name in either memo or notes, I forget what it's called. After I found out about KMyMoney and read how it treated the description as payee, I switched how I entered them. Now my GnuCash file has some payees in the memo field and some in description, so I don't know of a way to cleanly import that. I'll probably either edit it manually sometime or just not bother.

Is the payee field required? Since GnuCash doesn't enforce using the description field as payee, I could see value in having an option to put the GnuCash description in a line in KMyMoney's memo field and leaving payee blank or putting some placeholder in. If I have time, I might look into that, but my time is a finite resource.
Comment 5 Jack 2024-06-14 20:45:36 UTC
Seems to still be a legitimate request, so I'll just update the version to the current release.
The payee field is not required, but it is useful if you want to track all the money you have gotten from or given to some individual or organization.  Some users even enter a payee for transfer transactions (I believe that was mentioned an on old thread on the mailing list.)  I also have several payees such as "Misc restaurant" or "Misc clothing store."  Some might be obvious from the category, but not all, so reports by category and by payee are independently useful for me.
So, the idea of having more control over whether and how payees are created when importing gnucash data seems good.  
I don't know it will get much of a priority for the scarce developers' time, but it's still worth tracking.