When to create a rule
Create a rule only when the target transactions are easy to distinguish from the rest. For example, purchases from one supermarket can be assigned to Groceries by matching its name in the transaction description. Preview the matches before enabling automatic runs and make sure unrelated purchases are not included.
Conditions and actions
Conditions specify which transactions match. Actions specify what the rule will do with them. For example: if the description contains a supermarket name, assign the transaction to Groceries.
Before application
The preview lists matching transactions. Compare that list with the actions stored in the rule. If unrelated transactions appear, narrow the conditions before the run.
Automation run history
The run log records the rule, processed transactions, status, and completed actions. If a transaction changed incorrectly, open its log entry and check the condition and action that ran.