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

[Feature] Archival of payees #2579

New Issue
Closed
opened 2026-02-28 20:19:49 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:19:49 -06:00
Owner
Copy Link

Originally created by @kpoppel on GitHub (Oct 29, 2025).

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?

The payee list quickly grows very long, even after merging those which can be merged. For instance after a holiday, many new payees appear which are never relevant again.

I suggest a feature which can achieve an 'archival' function of Payees.

Option 1 is more than adequate, Option 2 a great convenience, Option 3 not the best of ideas, just honorable mention.

Describe your ideal solution to this problem

This can be done in several ways or stages:

  1. Select and mark all payees which should be archived. In the drop down menu select "archive", which effectively just hides them from view. Add a button to show/hide archived Payees. Make an indication like the category learning for archived Payees.
  2. Hide Payees which are not active automatically. Make a configuration setting to select auto-archive of Payees not active since "X days/months". No need to bother with Payees which are not active. Same mechanism to show/hide archived Payees as above.
  3. Suggest real clean-up of Payees for really old or selected transactions by aggregating them to their Category. Basically taking all "Travel" Category Payees and setting the Payee to "Travel" and be done with it.

Teaching and learning

No response

Originally created by @kpoppel on GitHub (Oct 29, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? The payee list quickly grows very long, even after merging those which can be merged. For instance after a holiday, many new payees appear which are never relevant again. I suggest a feature which can achieve an 'archival' function of Payees. Option 1 is more than adequate, Option 2 a great convenience, Option 3 not the best of ideas, just honorable mention. ### Describe your ideal solution to this problem This can be done in several ways or stages: 1. Select and mark all payees which should be archived. In the drop down menu select "archive", which effectively just hides them from view. Add a button to show/hide archived Payees. Make an indication like the category learning for archived Payees. 2. Hide Payees which are not active automatically. Make a configuration setting to select auto-archive of Payees not active since "X days/months". No need to bother with Payees which are not active. Same mechanism to show/hide archived Payees as above. 3. Suggest real clean-up of Payees for really old or selected transactions by aggregating them to their Category. Basically taking all "Travel" Category Payees and setting the Payee to "Travel" and be done with it. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:19:49 -06:00
GiteaMirror commented 2026-02-28 20:19:50 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 29, 2025):

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

@github-actions[bot] commented on GitHub (Oct 29, 2025): :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 -->
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 needs votes
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#2579
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?