github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #7319] [Feature] Allow Users to Disable/Deprecrate Payees #9985

New Issue
Closed
opened 2026-04-10 20:19:48 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 20:19:48 -05:00
Owner
Copy Link

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?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

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 Account and a payee of Investment Account one 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_deprecated marked true

Teaching 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"

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? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### 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 Account` and a payee of `Investment Account` one 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_deprecated` marked `true` ### Teaching 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"
GiteaMirror added the feature label 2026-04-10 20:19:48 -05:00
GiteaMirror commented 2026-04-10 20:19:49 -05:00
Author
Owner
Copy Link

@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 👍!

<!-- gh-comment-id:4150478243 --> @github-actions[bot] commented on GitHub (Mar 29, 2026): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-10 20:19:50 -05:00
Author
Owner
Copy Link

@db-src commented on GitHub (Mar 31, 2026):

Likely dupe of https://github.com/actualbudget/actual/issues/6028

<!-- gh-comment-id:4164532490 --> @db-src commented on GitHub (Mar 31, 2026): Likely dupe of https://github.com/actualbudget/actual/issues/6028
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#9985
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?