Import transactions: how to deactivate original payee?

Hello,

I have installed the version 5.2.2-843e483 (= kmymoney-5.2-5829-linux-gcc-x86_64.AppImage) a few days ago and since then I have for each imported transaction (import thanks to aqbanking module) the original payee inserted in the transaction memo:

I don’t need this insert there.

I remember having this feature a few months ago and found a setting in the configuration to disable it, it was with the version kmymoney-master-5536-linux-gcc-x86_64.AppImage.
Unfortunately i cannot remember which setting it was.

Where in the settings can I disable the automatic “add original payee into each transaction memo”-feature?

thanks and regards

A picture is worth a thousand words:

Many thanks for the immediate response!

So the parameter is:

  • not located under Settings → configure KMyMoney → Ledger → Import,
  • but under Account → Edit account → “Online Settings” tab → “Memo” tab → include the payee details in memo.

After this, i imported new fresh data into KMyMoney and the original payee is still in the memo but not for all transactions:
see on this screenshot the transactions from July 16th onwards:

Unassigned transactions don’t have the payee information in the memo. → that is good.
The transactions having a category assigned during the data import have the payee information in the memo :thinking: → not good…

That sounds like a copied text from a previous transaction. The code is very clear what to do when the setting is OFF. And that is the only location in the whole code base where this text is created. So it seems to be inherited from existing data.

I have filtered on “original payee: BI” to see if historic data exist and found 4 transactions prior to July 16th 2026

.

I then:

  1. closed the file without saving (to loose the new transactions >= July 16th)
  2. open the file
  3. edited the 4 historic transactions (delete the original payee from the memo).
  4. saved and closed the file
  5. open again and import the new fresh bank transactions

the result is: the original payee comes again :frowning:

are there other historic sources for this specific payee which disturb my wish?
There are still 43 other transactions having in the memo “Original payee : xyz”, but they are not from this payee “BI…”.

I’m not sure this is related to transaction matching, but to Payee matching. If imported the field used to identify the payee contains “Local Bar” and that term is in the matching list for the payee “My Favorite Bar” then the Payee will be “My Favorite Bar” (which might also end up in the Memo) and the memo will also contain “Original Payee: Local Bar”. (The Payee and the Original Payee in the memo may be the same string depending on the payee’s settings for matching. (I have not yet looked at the code.)

this is how the payee matching is defined for this payee in my file:

What i don’t understand is, i have unticked the check box of Account → Edit account → “Online Settings” tab → “Memo” tab → “include the payee details in memo.”
Why is it possible that the original payee details are still written into the memo, independently of how the payee matching is defined…
Payee matching helps when i want several payee names to be federated into one single other payee name. It has nothing to do with the content written into the memo, does it?

Ooops, I don’t know what happened (must have been the heat), but my pointer in Import transactions: how to deactivate original payee? - #2 by ipwizard was the wrong spot where this is controlled. Here we go with the correct option (which btw. matches the code location I referred to earlier):

Here we have the reason why I don’t get it fixed: the option you show doesn’t exist in version 5.2.2-843e483 (= kmymoney-5.2-5829-linux-gcc-x86_64.AppImage) I downloaded on July 8th, 2026 from Download and use the AppImage version | KMyMoney :

on the other hand i tested with a version compiled from the master branch, and it has the option “keep original payee information in memo” you showed.

Strange that is is absent from stable version 5.2.