The Categorization rules builder is available on the Bank and Expected pages, in the Categorization rules builder tab.
How to Create and Customize a Categorization Rule
Review Automatic Suggestions
The builder displays groups of similar uncategorized transactions along with prefilled conditions.
Refine Transaction Groups
Observe the list of transactions matching the suggested conditions on the side.
Add or adjust conditions (e.g., amounts, keywords) as needed. The list will update dynamically with every change.
By default the rule will apply to both paid and expected transactions, if your rule only apply to one or the other, just select the correct option for the condition Type. This means that by default, if accessing the categorization rules builder on the Bank page, it can also categorize expected transactions not displayed in the categorization rules builder.
Note: When navigating suggestions, any manual changes are discarded.
Adjust Rule Consequences
By default, the suggested category is pre-selected.
Change the category if needed, or add the Ignore consequence.
Optionally, select an inflow (for debit) or outflow (for credit) category to reverse transactions.
Remember: You cannot reverse and ignore transactions at the same time.
Process and Apply the Rule
If youâre satisfied with the group and conditions, click to create the categorization rule.
Alternatively, you can apply the selected consequences directly, but similar future transactions will have to be categorized by hand or reprocessed via the categorization rules builder.
đĄ Tips
Use keyboard shortcuts (Ctrl + â / Ctrl + â) to navigate faster between suggestions.
Reset modifications anytime to reload the default suggested conditions.
For targeted rules, adjust the Type condition so that the rule applies only to paid or expected transactions.
â FAQ
Can I reverse a transaction using this tool?
Yes. You can choose a reverse consequence by selecting an inflow category for debit transactions or an outflow category for credit transactions. Note that reversing and ignoring transactions simultaneously is not supported.
Why is there a spinner on the number of suggestions ?
The algorithm delivers a first version of the suggestions in a matter of seconds, even if the entity has a large number of transactions to be categorized. This first pass is less refined (especially the conditions) but it allows to start processing groups of transactions right away.
The second pass is slower and aims at:
diminishing the number of groups of transactions by merging similar groups
refining the conditions of each group to create better categorization rules, to reduce the need to clean the conditions found by the algorithm
While the second pass is running, the total number of suggestions can still change and therefore is replaced by a spinner, a visual clue that the algorithm is still doing its magic in the background.
The categorization rules builder creates too many rules, help !
As long as you take time to review (and adjust if needed) each suggestion, you should not encounter any collision between rules, as the categorization rules builder only process uncategorized transactions, and put the rules created at the bottom of the list (low priority). If problem arises :
Use the search bar in the Settings > Rules management to locate the categorization rules that are not working on a given category, and remove them.
Remove the category of the transactions with the issue.
Check that they are not categorized to another category via another categorization rules. If itâs the case and itâs not the good category, repeat step 1 and 2.
Then, launch again the categorization rules builder, adjust the suggested categorization rule, and youâre done !
I selected the types Paid & Expected, but I only see one type in the transaction table
When youâre working from the Bank page, only the bank transactions will be displayed, but the rule will also apply on the expected transactions.