A single transaction can satisfy more than one rule. A payment to a pharmacy might match a rule for medical spending and also a broader rule for anything over a given amount. What happens next depends on the order of the rules and on a switch in the editor that says later rules are skipped once this one matches.
Rules run in order
Rules are evaluated one after another, from the top of the list down. If the rules do not conflict, order is irrelevant: each does its own job. Trouble starts when two rules want to change the same thing, such as the category. In that case the one that acts last, or the one that stops the others, determines the result.
Seeing your rule list as a queue helps. The first rule gets first chance. Later rules get their turn afterwards, unless something stops them.
The stop switch
The editor offers an option which, when enabled, skips later rules once this one matches. It turns the rule into a decisive one. If the specific rule matches, nothing after it can alter the result. Without the switch, later rules may still adjust the transaction.
This is the tool for exceptions. Place the narrow, specific rule near the top and turn on the stop switch. Place the broad, general rule below. Specific cases are handled first and left alone; everything else falls through to the general rule.
A layered example
Suppose you want most payments to a general store filed as household, but purchases of a particular type, identifiable by a keyword, filed as stationery for work.
- Rule one, near the top: the store and the keyword, file under stationery, stop later rules.
- Rule two, below it: the store only, file under household.
A stationery purchase matches rule one and halts. A household purchase does not match rule one, passes through, and is caught by rule two. Reverse the order and every purchase would be filed as household before the specific rule had a chance.
Guidelines for ordering
- Put the most specific rules first.
- Put broad catch-all rules last.
- Use the stop switch on specific rules whose result must not be changed.
- Avoid two rules that fight over the same field without one clearly winning.
If you keep these four habits, most ordering problems vanish.
Diagnosing a stubborn transaction
When a transaction lands in a category you did not expect, work down the list. Which rules could match it? In what order do they run? Does an earlier rule stop the rest? Often, the culprit is a broad rule sitting above a narrower one, or a stop switch on a rule that matches more than you intended.
Another cause is a rule with a loose condition. If a rule's preview shows many more matches than expected, tighten it before worrying about order.
| Symptom | Likely cause |
|---|---|
| Specific rule never fires | A broader rule above it stops processing |
| Wrong category on a few items | Two rules fighting; order unclear |
| Rule seems ignored | Manual category protecting the transaction |
| Rule matches far too much | Condition too loose or logic set to any |
Testing a new arrangement
After reordering, test with real transactions. Pick one that should hit the specific rule and one that should fall through to the general rule, then confirm each lands where expected. If your tools let you re-run rules over a small date range, use that as the experiment. Two minutes of testing is cheaper than discovering a month later that a whole class of payments has been filed in the wrong place.
Keeping the list healthy
Review the rule list a couple of times a year. Remove rules that no longer match anything, merge duplicates, and re-check that specific rules still sit above general ones. A short, ordered, well-named list is easy to reason about. A long, tangled one hides its own mistakes.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


