Rules for Transaction Categorization
It would be extremely beneficial and would definitely make the app much more automated if we can have rules for automatically categorizing transactions based on specific criteria such as Notes, Payee etc.
This would help in two scenarios:
1. it would allow bulk importing the entire history of our accounts and automatically have all the transactions categorized using the currently added rules.
2. when using Shortcuts to add transactions, it would apply these rules to categorize them automatically. (you should allow adding a transaction without a category through the shortcuts similar to what you can do through the app)
Additionally and very importantly, the app should learn these rules automatically when categorizing previously uncategorized transactions, so it can apply them directly during future imports or when using shortcuts. Similar features are already implemented in apps like Gem, FireflyIII, and Emerald.
check this out for example:
https://shelftwo.com/gem/faq/import-and-shortcuts/#import-rules
Consolidated requirements
Support both user-defined categorization rules and assignments learned from previous transactions; distinguish explicit rules from learned behavior.
During CSV imports and transaction creation through Shortcuts, reuse relevant payee/history-based assignments for account, category, tags and notes, not only category.
Reduce the need to configure every payee manually while preserving the ability to define rules explicitly. A separate merchant/branch hierarchy is outside this request.

Log in to comment and vote
Comments3
Sog77
Oct 29
•Merged request
•5 votes
Add support to "automatically" detect Category, Tag, and other relevant fields for future transactions.
I believe this will require a significant amount of work, but since some base work has already been done, it might be beneficial for the service to support such functionality.
Currently, you can manually link transactions by payee, which automatically categorizes them for future transactions. However, this requires manual configuration at least once for each payee to be linked to a category, Account etc…
See screenshot
This can be problematic when you have a large list of payees. (+200). The feature should be able to detect transactions for the same payee and automatically link at least the account, category, tag, and note when a future transaction occurs.
Currently, I’m using a custom CSV file with some automation using Vlookup to link folders, categories, and tags for transactions. It would be ideal if I could simply import the generated transactions without having to create a custom CSV file or perform any manual operations. In this way, the system would already know where to link these transactions.
josealv97-netizen
Oct 29
•Merged request
•3 votes
Feature Request: Automatic Category Assignment Based on Merchant History
When an expense is automatically created through an iOS Automation (Apple Pay transaction), Budget Flow currently imports the amount and merchant name, but the category field remains empty.
I would like Budget Flow to automatically suggest or assign a category based on previous transactions from the same merchant.
Use Case
Example:
● Transaction 1:
● Merchant: Carrefour
● Amount: €45.20
● Category: Groceries
● Transaction 2 (imported automatically later):
● Merchant: Carrefour
● Amount: €18.50
ALEJANDRO LÓPEZ ALBERTOS
Feb 23, 2025
Strongly agree.
Right now I have an “if” in the apple pay transaction shortcut that automatically categorizes the expense based on merchant name. It works well but your proposal where the app learns patterns is much better.