Money tips

Why transactions end up uncategorised, and how to stop it

Why transactions end up uncategorised: unknown merchants, UPI payments to people, brand-new shops. Learn the causes and fix them with rules and aliases.

Editorial illustration for Why transactions end up uncategorised, and how to stop it

Transactions stay uncategorised when the tool has nothing to match them against: a merchant name it has never seen, a UPI payment to a person, or a cryptic bank narration. You stop it by teaching the tool once, with a rule or an alias, so the same line never needs a decision again.

What does "uncategorised" actually mean?

It means no rule, past decision or similar merchant gave a confident answer. The transaction is not lost or wrong; it is waiting for a label. A handful at the end of each month is normal. A growing pile means the same few causes are repeating, and each of them has a fix.

What are the usual causes?

CauseWhat it looks likeFix
Unknown merchantA narration like a string of letters and a city codeAdd a rule for that text
UPI payment to a personPaid to a name, no shop in sightDecide by purpose, then make a rule for that person
Different names for one merchantThe same shop shows up in three spellingsAdd an alias that maps them to one name
Brand-new shopFirst time you have ever paid itCategorise once, so history takes over
Cash withdrawalsJust an ATM lineAdd hand entries for what the cash bought
Mixed-use merchantsA large store sells groceries and electronicsChoose a default, and edit exceptions

Look at your own list of uncategorised rows and tick off which cause each one belongs to. You will often find that three or four merchants account for most of them.

Why are UPI payments to people so hard?

A payment to "Ramesh K" carries no category. It might be the vegetable seller, a friend repaying a loan or the plumber. No tool can guess that from the name, and a guess would often be wrong. This is a case where your knowledge beats any matching.

The practical route is to decide once per person. If Ramesh is your regular milkman, make a rule that sends payments to him to Groceries. If a friend is someone you split dinners with, leave those rows for a manual look. For one-off payments, categorise them on the spot and move on.

How do you fix it for good?

  1. Open the uncategorised list and sort it by merchant text, so the repeats sit together.
  2. Pick the merchant with the most rows and categorise one of them.
  3. Turn that choice into a rule, so future rows land in the same place.
  4. Where one merchant appears under several spellings, add an alias so they are treated as one.
  5. Repeat until the list is short. Two or three sessions usually clear most of the backlog.

How does SpendixAI handle the leftovers?

SpendixAI categorises in stages: your own rules first, then your history and similar merchants, and only if AI is switched on, an AI model for what is left. The model sees the cleaned-up merchant name and an amount range, not your name, account numbers, full statement text or balances. If you turn AI off, unmatched items are held for your review instead. Your corrections become history, and you can add merchant aliases.

That staged design is why the backlog shrinks over time: each correction teaches the next import.

A monthly routine that keeps the pile small

  • Import or enter the month's transactions in one sitting.
  • Clear the uncategorised list the same day, while you still remember what the payments were.
  • For every UPI payment to a person, write down the purpose in the transaction note if your tool allows it.
  • Add one or two new rules each month rather than twenty at once.
  • At quarter end, scan your rules for any that no longer make sense.

If a particular merchant is genuinely confusing even to you, ask for the invoice or check the bill in your email, and keep it with the transaction for later.

SPENDIXAI JOURNAL

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

Explore your reports