-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-categorization #98
Comments
Imported from https://trello.com/c/fi1WLdoc |
Some would like automatic categorization and some would like explicit rules (and some would like a combination) |
+1 to the topic |
@AAverin Yeah, I could allow regex for advanced users. When I get to this I'm going to use:
|
Any update on the issue? |
The best I can do is point to the roadmap: https://github.com/buckets/application/projects/2 After bug fixes, this is pretty high up on the list. |
This is my script to automatical add transactions to categories:
And configuration auto_categorize.yml:
|
Coming from nYNAB I have to say that I'm actually quite relaxed not having auto categorization. Why? If the categorization has sufficient usability (like just typing a few letters that appear somewhere in the category than having to scroll and click and maybe having multi-select) then I have to fight less against an incorrect auto categorization. nYNAB tended to incorrectly assign a number of particular cases that I have a lot of (like 30% of all new transactions that I import via CSV). I move money for my house (separate account and budget) a lot and I get income payments and expenditures from my and my wife's work all the time and stuff like Amazon and Paypal typically get mis-classified. So, making an auto-categorization feature, I'd recommend considering how much auto-categorization causes one to having to watch very closely whether a given category is correct and also making the rules easy to edit. nYNAB makes this really hard, so it's been a problem all the time that I just had to live with (papercuts and such). |
I agree that while I miss the auto categorization a little, it's not all that different than having to correct half of the entries. I do think ultimately some kind of auto categorization is helpful -- maybe with options to ignore various payees (ie. Amazon). I'm not minding the manual exercise, but there are some pain points:
I see at lest #2 is being addressed, so that's great! While I'm at it -- it would be wonderful to see the bucket balance next to the bucket name when I'm selecting it for the transaction. Just to serve as a reminder, and so I can see right away if I've overspent and need to make adjustments. |
Another comment describing what people want:
|
I love the concept of this app, but this missing feature is quite big. I would love to have something like auto categorization with a rule based approach similar to what Tiller Money does on Google Sheet: a table of rules that each user can specify to match a transaction with a category. This however seems very low of a priority in the roadmap here ... it's very unfortunate... |
Allow the categorization rules to be detailed, specific. For example "if the merchant contains this phrase" or "if the amount is X" for the exact same amount for recurring transactions. |
Any news regarding this issue? |
No description provided.
The text was updated successfully, but these errors were encountered: