mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #7319] [Feature] Allow Users to Disable/Deprecrate Payees #100460
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#100460
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iaewing on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7319
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Like many other users; I migrated years of transactions from YNAB.
In some cases; I have thousands of transactions with a YNAB style transfer payee. I have also been making new transactions with the Actual transfer payee conventions.
This can lead to duplication of payees that leads to confusion. As a result personally, I have thousands of investment contributions with the old YNAB style payee and now hundreds of new transactions that are actually marked properly as transfers within Actual.
Rather than having a payee of
Payee: Investment Accountand a payee ofInvestment Accountone which maps to a regular payee and one that maps to a transfer we can allow users to "Disable" a payee preventing further transactions using it while maintaining historical data.Describe your ideal solution to this problem
We could implement the ability for a user to mark a payee as deprecated or disabled. This would prevent the payee from displaying as an option when a user is selecting a payee for a new transaction or when creating a new schedule. The payee would still display on existing transactions associated with it.
This maintains historical data preventing a painful back-filling/data correction process while preventing it from being confused as the correct payee in future transactions.
This could be tracked on the payees table as a boolean value. When a select populates the options for payee it could filter out any with
is_deprecatedmarkedtrueTeaching and learning
The ability to control this could be in the manage payees interface, either through the rules modal, or a new CTA.
If the rules modal, a simple subheading along the lines of "Marking a Payee as deprecated prevents it from being used for new transactions but still allows you to see existing transactions using the deprecated payee"
@github-actions[bot] commented on GitHub (Mar 29, 2026):
✨ Thanks for sharing your idea! ✨
This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don't forget to upvote the top comment with 👍!
@db-src commented on GitHub (Mar 31, 2026):
Likely dupe of https://github.com/actualbudget/actual/issues/6028