Expense categories

Does a shared merchant directory improve categorisation? A plain answer

A forum-style answer on whether a shared merchant directory helps an expense app pick the right default category in India, with steps to test it yourself.

Editorial illustration for Does a shared merchant directory improve categorisation? A plain answer

The question: "Does an expense app with a shared merchant directory pick better default categories, and how would I know?" Short answer: it can help for well-known merchants, it does very little for small local ones, and you can test it in ten minutes with your own statement. Here is how we would go about it.

What a shared directory actually is

Imagine a list of merchants where the same shop is recorded once, under one cleaned-up name, with a default category agreed from how many people file it. When your statement says SHRI GANESH GEN STORE 4471 one month and SHRI GANESH GENERAL STR the next, a directory tries to see they are the same shop and gives both the same category. That is the whole idea: one answer, reused.

The catch is that a directory is built on other people's choices, so it fits big chains well and a small shop poorly. Your neighbourhood tailor will not be in it.

Step 1: look at what the app does first

Read how the app orders its decisions. In SpendixAI, as documented, the order is your own rules first, then your history and similar merchants, and then an AI model for what is left, only if AI is on. we are not going to claim more than that about its internals. When you evaluate any app, ask where a shared list sits in that order, and whether your own corrections beat it.

Step 2: run a ten-minute test

  1. Take one real statement, ideally with 40 or more rows.
  2. Import it and leave every category as the app guessed.
  3. Count how many rows you would change. Call that number W.
  4. Count rows from chain-type merchants and from tiny local ones separately.
  5. Correct a few, import next month's statement, and see whether the same merchants now come out right.

Say the statement has 48 rows and you change 9. That is 9 / 48 = 18.75 percent changed, so about 81 percent were fine. Now split it: of 30 chain rows you changed 2, and of 18 local rows you changed 7. That tells you the app is good at chains (2 of 30 is about 6.7 percent) and weak on local shops (7 of 18 is about 38.9 percent), which is where your own rules matter.

Row typeRowsChangedShare changed
Chains and online brands302about 6.7 percent
Small local shops187about 38.9 percent
All rows48918.75 percent

Step 3: check the spelling drift

The point of a merchant list is to cope with the same business spelled three ways. Search your statement for any merchant you know appears under more than one name, say a cab company's trip receipts and its wallet top-ups. If the app files them differently, add an alias so they are treated as one merchant.

Is my data being shared when a directory is used?

Ask this question of every app, not only this one. In SpendixAI, the AI step, if you switch it on, uses the normalised merchant name and an amount band, and not your name, account numbers, full statement text or balances. You can turn AI off per feature or entirely, and unmatched items are then held for review. Read the privacy page of any tool before you upload a statement.

What we would actually do

  • Let the defaults handle chains and brands.
  • Write rules for your five most frequent local payees.
  • Add aliases where one merchant has two spellings.
  • Recheck every few months, because merchants rename themselves.

If an app cannot show you why it picked a category, or does not let your corrections override its guess, we would be cautious about trusting it with the reporting you depend on.

SPENDIXAI JOURNAL

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

Explore your reports