Bug 463015 - Inactive Payee
Summary: Inactive Payee
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.1.3
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-13 16:27 UTC by Fabiano Caruana
Modified: 2022-12-19 22:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabiano Caruana 2022-12-13 16:27:56 UTC
Hello KMyMoney-Team,

I currently see no way to mark a payee as inactive.
Unfortunately, in the current version, it happens again and again that all payee can be selected for an entry.
If you have a database of 10 years or more, probably 30% to 40% of the payees are no longer "active" for some reason, but can still be selected.

Is there a way to "deactivate" payees in the future?

Greetings
Udo
Comment 1 jesse 2022-12-14 13:09:28 UTC
I am curious, would marking a payee inactive simply avoid showing the payee in the list? 

I am assuming the payee is still there since the system needs it for the integrity of the data. 

Also, what should happen if a payee is marked inactive but a new transaction comes in for that payee? 

I think, it should still hide the payee but when you attempt to enter the payee or transaction, kMyMoney should inform you. 

The message that should show would need to explain how to re-activate the payee.
Comment 2 Jack 2022-12-19 22:08:47 UTC
You are correct that there is no current way to tell KMM not to allow any new transaction for a given Payee, so this is valid wishlist request.  At minimum, marking a Payee as inactive would remove that Payee from any dropdown lists of Payees when entering or editing a transaction.  (Note it might be necessary to reactivate a Payee to add it to an old transaction from prior to the inactivation, but this is similar to the occasional need to reopen a closed account to edit some transaction.)  

What happens when an inactive payee is used in a transaction being imported would need to be decided.  However, since the current default behavior is to create an imported Payee that does not exist, it would create a duplicate Payee unless the import were allowed.  I suppose it would be possible to add "X transactions imported for inactive payee(s)" to the final import report.