A categorisation rule is a simple instruction: if a transaction's description contains certain words, put it in a particular category. If you have never made one, you can ask an AI assistant connected to your expense tracker to make it for you, in plain language. The skill is not in asking, it is in testing the rule before you trust it.
Start with a rule you can picture
Take the word recharge. You might want 'recharge' to mean Mobile and internet. Reasonable. Now look at one month of rows that contain it.
| Description | Amount | Should be |
|---|---|---|
| Mobile recharge | ₹299 | Mobile and internet |
| DTH recharge | ₹350 | Mobile and internet |
| FASTag recharge | ₹500 | Travel |
The rule 'contains recharge, so Mobile and internet' labels all three, a total of 299 + 350 + 500 = ₹1,149. But the real mobile and internet spend is 299 + 350 = ₹649. The FASTag ₹500 is wrongly filed. This is the classic beginner slip, and it is why we test.
How to ask, step by step
- Connect the assistant. In SpendixAI you choose the scope, can start read-only and can disconnect at any time.
- Ask it to list every transaction whose description contains the word, before creating anything.
- Look at the list and notice what does not belong, such as the FASTag row.
- Make your wording more specific, for example 'contains mobile recharge' or 'contains DTH'.
- Ask for one rule per specific wording, naming the category exactly.
- Ask it to read the rule back to you in words.
What if my assistant cannot create a rule?
That usually means it has read-only access, which is a good default. Make the rule in the app yourself. Everything you learned from the listing still applies. You do not need the assistant to benefit from this method.
How rules fit with the rest of the tracker
- Your own rules are applied first.
- Then your history and similar merchants guide the guess.
- Then, only if AI is switched on, a model handles what is left, using the cleaned merchant name and an amount band.
- If AI is off, rows that nothing matched are held for you to review.
- When you correct a row, the correction becomes history.
Common beginner worries
- Will a rule change my past rows? Ask directly. Some tools apply rules only to new imports.
- What if I make a mistake? Edit or delete the rule, and fix the affected rows. Deleted transactions go to a recycle bin for 30 days.
- Do I need a rule for everything? No. A handful for regular payments covers most of the repetitive work.
- Is it safe to chat about my spending? Do not type logins, OTPs or card details. You never need them for this.
Writing rules for the next few payments
Once recharge is sorted, try other everyday wording. Petrol or fuel might be Travel, electricity might be Utilities, and grocer may catch a kirana and a supermarket alike, which is fine if both are Groceries. For each one, run the same listing test. Three or four good rules take about an hour to build and save minutes every month.
- Choose payments that repeat monthly.
- Prefer wording that is part of the description every time.
- Avoid single common words on their own.
- Write each rule down in a note with the reason you made it.
A good first week
- Day one: write down your five most regular payments.
- Day two: make one narrow rule for each, testing as above.
- Day three: import a statement and see how many rows land correctly without your help.
- End of the week: fix the stragglers and add one more rule if a pattern repeats.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

