Merchant names on statements change from month to month, so a tool that matches exact text will treat the same shop as several different ones. A merchant directory, whether it is built from your own history, from similar merchants or from a wider list, helps by mapping many spellings to one name and one default category. Your own corrections must still beat any default.
How the same shop gets four names
A statement may show a full business name one month, a shortened version the next and a payment gateway's name after that. UPI adds a handle, card machines add a location code and online sellers pass through intermediaries. If each spelling is a separate merchant, you correct the same shop again and again.
A worked example with made-up numbers
Say you buy milk and groceries from one online grocer. Across three months the narrations look different:
| Month | Narration on statement | Amount in rupees |
|---|---|---|
| January | GROCERMART ONLINE BLR | 2,340 |
| February | GROCERMART*ORDER 8812 | 1,980 |
| March | GM ONLINE RETAIL | 2,410 |
Without a directory, you categorise three merchants. With one name mapped to all three, the total for the quarter reads 2,340 + 1,980 + 2,410 = ₹6,730 under Groceries. The more spellings a tool can fold into one, the less you correct by hand.
Order of authority
A sensible design puts your own choices first, then defaults. That means an alias or rule you create overrides anything the directory suggests, because the directory cannot know that for you a particular chemist is a business expense or that a pharmacy chain is Health.
- Your own rules: highest priority.
- Your history: what you corrected before.
- Similar merchants and shared defaults: a starting point for unfamiliar names.
- A model, if you allow one: used for what remains.
What does SpendixAI do?
SpendixAI categorises in stages: your own rules, then your history and similar merchants, then, only if AI is on, an AI 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, set a monthly AI budget, or turn it off entirely, in which case unmatched items are held for review. You can add merchant aliases to tell it two spellings are the same shop.
What to look at in any app
- Does it let you merge two spellings into one merchant?
- Does your correction beat the default?
- Can you see which rows are unmatched?
- Is it clear what data is used to suggest a category, and can you switch that off?
- Do the totals change when you merge, or only the labels?
Why spelling changes happen so often
Merchants change payment providers, open new branches and rename products. A seller who was paid through one gateway last month may use another this month, so the text on your statement changes even though you bought from the same place. Festival seasons bring extra sellers and one-off campaign names. Because of this, any approach that relies on matching exact text will always trail behind, and the sensible response is to keep a small list of aliases for the merchants you use most.
Limits to expect
A directory cannot know every small seller, so local shops, individuals and one-off payees will always need your input. Treat it as a way to shrink the pile to a manageable size rather than an end to reviewing.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
