To categorise UPI payments automatically, write rules that match the payee name or UPI handle and assign a category: for example, anything to your milk vendor goes to Groceries. Start with the five or ten payees you pay most, then review whatever is left once a month.
A few well-chosen rules cover most of your rows, because UPI spending is repetitive. The unmatched rest is a short list that you can sort in minutes.
Which payees should get rules first?
Sort a month of UPI rows by payee and count how often each appears. Rules pay off where the payee repeats and the category never changes.
| Payee | Rule text to match | Category |
|---|---|---|
| Milk vendor | Part of the vendor's name or ID | Groceries |
| Auto or cab driver you use often | The driver's name or ID | Transport |
| Electricity or water bill payee | The utility's name in the narration | Utilities |
| Society office | The society's name | Rent and housing |
| Neighbourhood pharmacy | The shop's name | Health |
Match on the stable part of the name. A name that includes a date, a number or a random code will not match next time, so choose a word that stays the same.
How do I write a rule that does not misfire?
- Look at three or four past rows for the payee and find what they share.
- Match on that shared word, not on the amount, unless the amount never changes.
- Apply the rule to past rows, if your tool allows, and read the result.
- Check that no unrelated payee is caught, for example a person whose name shares a word with a shop.
- Keep the rule list short and clear.
Say a rule matches the word Fresh and assigns Groceries. It will also catch a laundry called Fresh Wash. Making the rule more specific, with the full vendor name, solves that.
What happens to the leftovers?
Whatever no rule catches stays uncategorised or lands in a catch-all category such as Needs review. Set aside ten minutes each month to go through that list. For every payee that appears twice or more, add a rule, so the list shrinks.
SpendixAI applies your own rules first, then your history and similar merchants, and only then, if you have switched AI on, a model for what is left. The model sees the normalised merchant name and an amount band, not your name, account numbers, full statement text or balances. You can switch AI off per feature, set a monthly AI budget, or turn it off completely, in which case unmatched items are held for review. Corrections become history.
What should I check each month?
- The uncategorised or review list, sorted by amount, largest first.
- Any category that jumped from last month, in case a rule is catching the wrong rows.
- New payees that appeared three or more times.
- Rules that no longer match anything, which can be removed.
Keep a one-line note of why
Next to each rule, jot a few words about why it exists, such as matches the milk vendor, or rent to landlord. Months later, when a rule seems to be catching the wrong rows, that note tells you what it was meant to do and whether to narrow it or delete it. Review the list every quarter and remove rules for payees you no longer use.
A simple starting set
If you want a first set of rules without overthinking it, make one for each of these: your milk or grocery vendor, your regular transport, rent, utilities, phone and broadband, and any monthly service payee. That is usually enough to categorise most of a typical month's UPI rows, and the rest can be handled as they appear.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


