mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-10 23:54:00 -05:00
[GH-ISSUE #6511] [Feature] Import Categories from File #80184
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#80184
Reference in New Issue
Block a user
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?
Originally created by @balthanon on GitHub (Dec 29, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6511
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
When importing data from files-- whether CSV or QSV/OSV, if the category doesn't match exactly, it is impossible to map the category into Actual Budget. This results in losing that information which could be useful in mapping the transaction to your actual categories. It is possible to use the Notes field as a workaround for this, but that only works if you're using a CSV file (which I've found to have issues with matching transfers and recognizing positive and minus signs) and you then potentially lose out on storing something else from the import there like extended description or the original payee names from the credit card or bank.
While this is most useful when you're initially setting up Actual Budget and are importing a year or more of data potentially, I think it's likely to be an ongoing problem if you run across new categories from a credit card company or bank. Plus, if you use multiple suppliers, this is one of the only ways you could actually standardize the data from all of those companies.
It is possible to implement some of this manually, but that is a decent amount of work copying and pasting categories out of spreadsheets and if the data changes, you might not realize that the payment processor is using new categories when they just don't import later on when updating your data.
This has come up in previous issues as well, but as far as I can see there hasn't been any resolution to them beyond an explanation of how it currently works and then closing the other feature request. (https://github.com/actualbudget/actual/issues/3446 and https://github.com/actualbudget/actual/issues/3428#issue-2525372326 - the former is a feature request, but as far as I can tell, seems to have been closed based upon the fact that it referenced the bug report unless it the user found another issue that I haven't been able to find. That bug was then closed with an explanation why the issue exists and how it can be worked around manually.)
Describe your ideal solution to this problem
It should be possible to automatically create categories based upon a file import. Whether that is through importing transactions via a stand alone CSV file or better yet as part of the transaction import process it would be beneficial to keep as much data as possible from imports. (Or both.)
My ideal solution for this would be to have a check mark that users can enable in the import process that says "Create Categories that Don't Exist" or something. If that is checked, then it would create and place all the new categories in an "Imported" group. Users could then generate rules off of that data to recategorize the transactions as they wish or just move the categories to a group if they want to keep them as is.
The ability to import categories from a basic CSV file would actually be useful as well, since that could allow people to import a budget structure from file or just generate a list out of a downloaded CSV file. That could be helpful for people to get a running start on creating a solid budget structure for themselves that they could then modify or for just importing a list of categories that certain payment processors or banks use (i.e. here's a list of all of the categories that American Express or Mastercard or Visa use so you can import category data from them.)
Teaching and learning
The import doc should definitely be updated to mention this (and there are actually a few other features in the file import process that aren't well documented there.)
https://actualbudget.org/docs/transactions/importing/
It would also be useful to update Starting Fresh and getting started, particularly if the stand alone file import of categories is implemented-- having a few basic configurations for a budget that maybe community members could provide would be really helpful for people just getting started with this process.
https://actualbudget.org/docs/getting-started/starting-fresh
(It probably depends on if I stick with using the application, but I might be willing to help with creating the PR later-- want to focus first on actually implementing a budget for myself and someone else first.)
@github-actions[bot] commented on GitHub (Dec 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 👍!
@db-src commented on GitHub (Dec 31, 2025):
Dupe of
https://github.com/actualbudget/actual/issues/2226
I think
@balthanon commented on GitHub (Jan 2, 2026):
Yeah, #2226 probably covers importing them directly as a file and #557 mostly covers importing them as part of the transaction process. Missed those when I was searching for similar issues and feature requests.