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

[GH-ISSUE #502] [RFC] Auto Categorisation Behaviours #7114

New Issue
Closed
opened 2026-04-10 16:47:28 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 16:47:28 -05:00
Owner
Copy Link

Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/502

Discussed in https://github.com/actualbudget/actual/discussions/461

Originally posted by winklevos January 14, 2023

Description

Add setting to configure the auto categorization mode and add additional modes of auto categorization.

Currently Actual will automatically create a rule to categorize a payee, I will call this Automatic Learning. It functions as described under Automatic Learning.

I would like to add the below additional options, configurable in the settings page.

Auto Categorization Mode:

  • Automatic Learning (default)
  • User Directed
  • Always Prompt

Automatic Learning

Actual will automatically create a rule once you have categorized a payee enough times.

Logic

  1. You categorized the latest transaction for that payee.
  2. You have manually categorized that payee to that category 3 or more times
  3. This is scoped to the last 6 months and 180s forward.
    https://github.com/actualbudget/actual/discussions/246

User Directed

This option would be my personal preference

Logic

  1. If you categorize a transaction and the payee does not have a rule setting a category. Create a rule and update any other matching uncategorized transactions.
  2. If you re-categorize a transaction with a rule setting another category prompt to update rule. (edit-rule modal)

Always Prompt

Whenever a category is set or changed on a transaction ask for action.

  • Just this transaction
  • This and future transactions
  • This, uncategorized, and future transactions
  • All matching transactions (re-categorize if required)

Parting thoughts

Please let me know what you think, or if you have another bit of logic to suggest

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/502 ### Discussed in https://github.com/actualbudget/actual/discussions/461 <div type='discussions-op-text'> <sup>Originally posted by **winklevos** January 14, 2023</sup> ## Description Add setting to configure the auto categorization mode and add additional modes of auto categorization. Currently Actual will automatically create a rule to categorize a payee, I will call this `Automatic Learning`. It functions as described under Automatic Learning. --- I would like to add the below additional options, configurable in the settings page. Auto Categorization Mode: - `Automatic Learning` (default) - `User Directed` - `Always Prompt` ### Automatic Learning Actual will automatically create a rule once you have categorized a payee enough times. #### Logic 1. You categorized the latest transaction for that payee. 2. You have manually categorized that payee to that category 3 or more times 3. This is scoped to the last 6 months and 180s forward. https://github.com/actualbudget/actual/discussions/246 ### User Directed This option would be my personal preference #### Logic 1. If you categorize a transaction and the payee does not have a rule setting a category. Create a rule and update any other matching uncategorized transactions. 2. If you re-categorize a transaction with a rule setting another category prompt to update rule. (edit-rule modal) ### Always Prompt Whenever a category is set or changed on a transaction ask for action. - Just this transaction - This and future transactions - This, uncategorized, and future transactions - All matching transactions (re-categorize if required) ## Parting thoughts Please let me know what you think, or if you have another bit of logic to suggest</div>
GiteaMirror added the feature label 2026-04-10 16:47:28 -05:00
GiteaMirror commented 2026-04-10 16:47:30 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Feb 16, 2023):

👋 Hi @winklevos !

Before I dive deep into the proposal here: if it is approved - will you be interested to implement it? What would be your best-case outcome scenario from this RFC?

<personal rant>IMO an RFC with no concrete action points is just a blog post. It's good.., but not really moving things forward.</personal rant>

Cheers!

<!-- gh-comment-id:1433519886 --> @MatissJanis commented on GitHub (Feb 16, 2023): 👋 Hi @winklevos ! Before I dive deep into the proposal here: if it is approved - will you be interested to implement it? What would be your best-case outcome scenario from this RFC? \<personal rant>IMO an RFC with no concrete action points is just a blog post. It's good.., but not really moving things forward.</personal rant> Cheers!
GiteaMirror commented 2026-04-10 16:47:31 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 6, 2023):

👋 Closing this off due to inactivity.

<!-- gh-comment-id:1499528886 --> @MatissJanis commented on GitHub (Apr 6, 2023): 👋 Closing this off due to inactivity.
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#7114
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?