Rules are the part of Spendix that turns repetition into automation. If you keep filing the same kind of transaction into the same category, a rule can do it for you. The first one is the most instructive, because it teaches the shape of every rule that follows: a name, one or more conditions, and one or more actions.
Pick a pattern worth automating
Start by looking at the transactions you categorise most often by hand. Maybe it is your daily commute payments, or the monthly payment to a particular utility. The best first rule targets something frequent, predictable and unambiguous. Avoid anything where the right category depends on mood or context.
A good test is whether you could explain the rule to a friend in one sentence. If the sentence needs an if or a but, wait; build the simple rules first.
Name it and set the condition
Open the rule editor and give the rule a name that tells you what it does, such as Metro travel to Transport. Plain names matter because rules accumulate, and a list of ten cryptically named rules is hard to maintain.
Next, add a condition. A condition says which transactions the rule applies to. Typical ones test the merchant, the amount or the direction of money, and one condition is enough to begin. As you build it, the editor shows what it would match, which is the best sanity check available. If the screen asks you to finish the condition above to see a match, the condition is not complete yet.
Choose the action
The action is what the rule does when a transaction matches. The simplest is to file under a category. Others are available, such as marking spending as business or personal, flagging it reimbursable, renaming the merchant or excluding it from reports. For a first rule, filing under one category is plenty.
Pick a category from your own list. If the right category does not exist yet, create it first, so the rule is not left waiting.
Decide about the past
The editor includes an option to also apply the rule to transactions you already have. Turning it on cleans up history as well as the future. It is usually a good idea for a first rule, provided the preview looks right. If you leave it off, the rule affects only new arrivals.
There is one more setting worth understanding, which controls whether rules override choices you made by hand. By default, a transaction you categorised yourself is never touched. That protects your decisions and is the safer starting point.
Save and verify
Save the rule. The app confirms with a message that the rule was created. When a rule is applied to existing transactions and finds nothing to change, you may instead see a note that it was saved and nothing needed changing, which just means the data already fit.
Afterwards, open a few transactions that the rule touched. Confirm that the category is right, and look for any that should not have been caught. If a false match appears, tighten the condition rather than deleting the rule.
| Step | What to decide |
|---|---|
| Name | What the rule does, in plain words |
| Condition | Which transactions it should catch |
| Action | Category or other change |
| Past data | Apply to existing transactions or not |
| Manual choices | Keep protected unless you have a reason |
What to build next
After a first success, look at your next three most repetitive corrections and build rules for them in turn. Resist the urge to write dozens at once. Rules interact, and a small, well-understood set is easier to trust than a large pile.
Only some roles can create rules in a shared workspace. If you cannot find the option, check your role with the workspace owner.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


