When a categorisation rule does not apply to an imported transaction, the cause is almost always a mismatch between what the rule looks for and what the narration actually says. The text differs, the merchant appears under several spellings, the rule is too narrow or too broad, or the row was already categorised by hand. Compare the rule with the row side by side and the reason usually shows within a minute.
Is the narration different from what my rule expects?
This is the commonest reason. You wrote a rule from one transaction, and the next one is spelt a little differently. How a rule matches, whether on the whole text, on a part of it or on the merchant name, depends on how it was set up, so check the rule itself. Then look at the row.
| Rule looks for | Row says | Why it missed |
|---|---|---|
| SWIGGY INSTAMART | SWIGGY INSTAMART BLR | Match is stricter than you thought, or an extra word is in the way |
| Zomato | ZOMATO LTD | Case or spelling treated differently |
| Fresh Basket | FRESHBASKET | A space is missing in the narration |
| Shree Fuels Petrol Pump | SFPP PUNE | The row uses an abbreviation, not the full name |
Is the merchant spelt several ways?
A shop often appears differently on a bank account and on a credit card, or through UPI and through a card swipe. One rule can only cover what it names. The cleaner fix is a merchant alias that maps the variants to one name, and then a rule on that name. That way a new spelling is a one-line addition rather than a new rule.
Is the rule too narrow or too broad?
- Too narrow: it includes a reference number, a city or a date, which change in every narration, so it can match only once.
- Too broad: a short word such as the name of a common chain inside many narrations, so it fires on things you did not mean and you stop trusting it.
- Conflicting: two rules could both apply to the same row, and the one you expected is not the one that won. Review your rules that mention similar words.
If a rule has stopped working after you edited it, that is often a sign that the edit made it narrower.
Was the row already categorised by hand?
If you set a category on a transaction yourself, treat that as your own decision, and do not assume a rule written afterwards will override it. A rule is meant for rows coming in, so it may not rewrite old ones. If you want an old row to follow the rule, check the transaction and set its category to match.
What order does categorisation follow?
In SpendixAI, your own rules come first. If no rule applies, the tracker looks at your history and similar merchants, and only after that, if AI is turned on, an AI model deals with what is left. If AI is off, those leftovers are held for review. So when a rule misses, the row does not vanish; it falls to the next stage, which may give a different category from the one you wanted.
A fix routine
- Open the uncategorised or wrongly categorised row and read the full narration.
- Open the rule that should have matched it.
- Decide whether the rule needs a shorter, steadier piece of text.
- Add an alias if the merchant shows up under more than one spelling.
- Set the category of the missed row by hand, so it is right today.
- Check the next import to confirm the rule now applies.
Test a changed rule on one real narration before trusting it with a whole year of rows.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

