Rule purpose
The name should state the condition and change, for example "Groceries from Market" instead of "Rule 1."
Transactions checked by the rule
Wallets, transaction type, and date can limit which records the rule checks. Leave a filter empty only when the rule should process every value in that field.
Match conditions
Conditions can check the transaction direction, amount, currency, wallet, category, tag, description, or date. The rule can require every condition or accept any one of them.
Actions the rule will perform
A rule can set a category, add or remove a tag, replace or extend the description, or send a notification. Separate unrelated actions into different rules so each one is easier to check.
Priority for overlapping rules
When several rules match one transaction, the higher-priority rule runs first. For example, put a rule for one supermarket above a general rule for all expenses.
Automatic or manual trigger
Start with a manual trigger and preview several matches. Enable automatic runs on transaction creation or update only after unrelated transactions no longer appear in the preview.
Save, preview, and run
Saving stores the rule but does not change transactions. Preview finds the current matches. Only a run applies the proposed field changes.