Automation rules

Rules let you transform transactions automatically as they come in — change the category, rename the merchant, mark it reimbursable, add tags, and more.

Where rules live

Open Settings → Rules. The page lists every rule you've created, in priority order.

Anatomy of a rule

A rule has two parts:

• Conditions — what must be true for the rule to fire (e.g., description contains "UBER", amount is over $20, account is "Chase Checking").
• Actions — what to do when conditions match (set category, set merchant display name, set flag, add tag, set tax category).

Conditions support these fields: description, display_name, amount, account_id. Operators include equals, contains, between, greater than, less than. Actions include set category, set merchant, set display name, set flags (reimbursable / recurring), set tags, and set tax category.

Order matters

Rules run top to bottom. The first rule whose conditions match wins. Drag rules to reorder them — put the most specific rules above more general ones.

Creating a rule

1. Open Settings → Rules.
2. Click New rule.
3. Name the rule, add one or more conditions, and one or more actions.
4. Save.

You can test a rule against existing transactions before locking it in — the editor shows how many transactions it would have matched.

Editing and deleting

Click any rule to edit conditions, actions, or order. Delete from the rule's menu. Deleting a rule does not undo its past effects on already-categorized transactions — those stay until you change them by hand or with another rule.

FAQ

Will a rule re-run on transactions I've already manually categorized? No. Rules only run on incoming transactions. Manual overrides win and are not overwritten on the next sync.

Can a rule fire on multiple actions at once? Yes. A single rule can set the category, set tags, and flag for reimbursement all at once.

What if two rules match the same transaction? The higher-priority rule wins. Reorder rules to control which fires first.