[Feature] Turn on category learning for ynab importers #748

New Issue

GiteaMirror · 2026-02-28T19:17:19-06:00

GiteaMirror commented

2026-02-28 19:17:19 -06:00

Originally created by @twk3 on GitHub (Nov 20, 2023).

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?

When importing from ynab4 or ynab web, there are no category rules created after import. Typically rules are only created when categories are manually set by the user. (Or brought in from an acutal import).

I think having them for the ynab importers would be an improvement, as the outcome would likely more closely match the ynab experience they were having with auto-categorisation.

Describe your ideal solution to this problem

Expose the already existing learnCategories up through addTransaction and the api so importers can make use of it
Turn on learnCategories for the importers

Teaching and learning

API changes should be documented in the API reference, but I don't think there is existing references that have boolean flags like this that have default values.

Originally created by @twk3 on GitHub (Nov 20, 2023). ### 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? When importing from ynab4 or ynab web, there are no category rules created after import. Typically rules are only created when categories are manually set by the user. (Or brought in from an acutal import). I think having them for the ynab importers would be an improvement, as the outcome would likely more closely match the ynab experience they were having with auto-categorisation. ### Describe your ideal solution to this problem 1. Expose the already existing `learnCategories` up through addTransaction and the api so importers can make use of it 2. Turn on learnCategories for the importers ### Teaching and learning API changes should be documented in the API reference, but I don't think there is existing references that have boolean flags like this that have default values.

GiteaMirror added the feature label 2026-02-28 19:17:19 -06:00

GiteaMirror closed this issue

2026-02-28 19:17:20 -06:00

GiteaMirror commented

2026-02-28 19:17:20 -06:00

@github-actions[bot] commented on GitHub (Nov 20, 2023):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 (Nov 20, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!

GiteaMirror commented

2026-02-28 19:17:21 -06:00

@twk3 commented on GitHub (Nov 23, 2023):

This was completed in https://github.com/actualbudget/actual/pull/1944

@twk3 commented on GitHub (Nov 23, 2023): This was completed in https://github.com/actualbudget/actual/pull/1944