There is a setting in the rule editor that decides who wins when a rule and a person disagree. It is phrased as whether the rule should override your manual choices, and it is off by default. The default description is plain: a transaction you categorised by hand is never touched. Understanding this single switch prevents most of the surprises people have with rules.
What happens with the switch off
With override off, a rule leaves any transaction you have categorised yourself alone. If you manually filed a payment under gifts, and a rule would have filed it under shopping, the rule respects your decision. This is a protective setting. It means you can write broad rules without fearing they will undo deliberate corrections.
It also means that when you apply a rule to existing transactions, only those you did not touch by hand will change. That is why a rule run sometimes appears to do very little: your own choices are shielding the data.
What happens with the switch on
Turning override on lets the rule replace manual categories. It is the right setting when you want a firm, consistent outcome, such as normalising a tangle of earlier inconsistent decisions. If past you filed the same payee under five different categories, an override rule can bring them all into line in one pass.
It is a stronger tool and deserves care. Because it can overwrite, check the preview of matched transactions carefully, and ask whether any of them were deliberate exceptions.
A way to choose
- **Leave it off** for everyday rules, for rules with broad conditions, and whenever you often make one-off corrections.
- **Turn it on** for a cleanup pass, for a rule with a very precise condition, and when you want consistency across the whole history.
- **Turn it on briefly** to clean up, then switch it off afterwards so future manual choices are respected.
The third approach combines the benefits. Run the rule with override once, review the outcome, then edit the rule and turn the setting off again.
A worked example
A person has paid a local fuel station for years and categorised some payments as transport, others as vehicle and a few as miscellaneous. They write a rule: that merchant, file under vehicle. With override off, only the uncategorised payments change, and the older inconsistent ones remain. With override on, every matching payment becomes vehicle, giving a tidy history. After checking the preview, they run it with override on, then turn it off, so that if a future fuel purchase is a gift card, their manual choice stands.
Interactions to watch
If you ever wonder why a transaction keeps returning to a category you did not choose, check whether a rule with override is responsible. Conversely, if a rule seems to be ignored, a manual category on that transaction may be protecting it. These two observations explain most apparent contradictions.
Also remember that rules do not stand alone. Other rules, merchant defaults and learned behaviour all contribute. When behaviour looks odd, work through them in order rather than assuming a bug.
Documenting the choice
A rule list rarely explains itself. When you switch override on for a cleanup, put it in the rule name or a note, such as one-off cleanup, override on. Months later, when someone wonders why a category keeps changing, the name answers the question. Small labels like this are what keep a collection of rules understandable when you return to it after a long gap.
Summing up
The override switch is about trust. Off says your decisions are final. On says the rule's decision is final. Neither is wrong, but knowing which one is active makes your categorisation predictable.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

