AI and MCP

Can you create a categorisation rule just by chatting?

Forum question answered: can you create a categorisation rule by chatting with an assistant? Numbered steps, a tested example, and the limits to know about.

Editorial illustration for Can you create a categorisation rule just by chatting?

The question: 'Instead of clicking through settings, can I just tell an assistant to create a rule that files my society maintenance payments under Housing?' Often yes, if the assistant is connected to your tracker with permission to write. What matters more than how you create the rule is whether the rule is narrow enough to be right and whether you tested it on old data.

What a rule is, in one paragraph

A rule says: when a transaction looks like this, give it this category. In SpendixAI your own rules are applied first, before your history, similar merchants and any AI, so a rule is the most predictable layer. That is why a sloppy rule does more damage than a missing one: it will confidently mislabel.

Steps we would follow

  1. Connect the assistant. SpendixAI supports Claude or ChatGPT through MCP, with a scope you choose, an option to start read-only, and a way to disconnect at any time.
  2. Start by asking it to show every transaction that would match your pattern, without changing anything.
  3. Read the matches. If anything looks wrong, make the pattern more specific.
  4. Only then ask for the rule to be created, and name the category exactly as it appears in your tracker.
  5. If your connection is read-only, create the rule in the app yourself using what you learned.
  6. Check the next import to see the rule fire.

An example you can copy the shape of

Say you pay society maintenance by UPI each month and the narration contains the words SOCIETY MAINT. Over six months you see six matches of ₹3,500 each, which is 6 × 3,500 = ₹21,000. That is a clean set: same words, same amount, same month day. A rule on that wording, filed under Housing, is safe.

Now suppose you wrote the rule as simply 'contains MAINT'. It would also catch a vehicle maintenance bill for ₹2,800 and push it into Housing. Narrow patterns beat short ones.

PatternMatchesRisk
contains SOCIETY MAINT6 rows of ₹3,500Low
contains MAINTThe 6 rows plus a ₹2,800 vehicle billMislabels the vehicle bill
amount equals ₹3,500Society rows and any other ₹3,500 paymentHigh, amounts repeat

What can go wrong

  • Rules built on a word that appears in many narrations.
  • A rule that makes sense this year but not after you move house or change your society.
  • Two rules that both match one transaction. Check how your tracker settles that before relying on it.
  • Assuming the rule will rewrite old rows. Ask whether it applies only to future imports or to existing ones as well.

Testing a rule on old rows first

If your tracker lets you filter old transactions by a word, do that before creating the rule. Filter for SOCIETY MAINT, count six rows, add them up to ₹21,000, and compare with your own record of what you paid. If the filter shows seven rows, find the seventh before the rule does it for you. A rule is only as good as the list it would have matched last year.

  • Count the rows the wording would match.
  • Add up the amounts and compare with your records.
  • Read three of the descriptions in full.
  • Only then create the rule.

Keep the rule tidy over time

Once a quarter, read your rules like a list. Delete the ones that no longer fire. If you correct a row by hand, remember the correction becomes history, which helps similar merchants, but a rule for a regular payee is still cleaner. You can also add a merchant alias when one payee appears under several names.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports