Getting started

Teaching a tracker local shop names: kirana, chai and street vendors

Teach your expense tracker local shop names: put one rule or alias on the recurring kirana, milk, vegetable and chai UPI payees so they leave the review pile.

Editorial illustration for Teaching a tracker local shop names: kirana, chai and street vendors

Small vendors rarely look like shops on a statement. They appear as a person's name or a terse UPI handle. The fix is a single rule or alias for each regular one: tell the tracker that this payee is your milk vendor, and every future payment lands in the right category without you touching it. Do it for the five or six you pay every month and most of the review pile disappears.

Why local vendors confuse trackers

A supermarket chain has a recognisable name, and a tracker can guess its category. The man who delivers milk, the vegetable seller on the corner and the tea stall near the office are paid by UPI to an account in someone's name. The statement shows a personal name, a handle or a string of letters, and nothing about what was bought. A tracker cannot tell if a payment to that name was milk or a loan to a friend.

You can, because you know who they are. The skill is to tell the tracker once.

Find your regulars first

Look at one month's statement and list the payees you pay repeatedly in small amounts. Say these appear in a month, with invented figures.

How it appears (example)What it isTypical amountCategory to use
A person's name, dailyMilk vendor₹62 a dayGroceries: dairy
A handle, twice a weekVegetable seller₹150 to ₹300Groceries: vegetables
A person's name, most weekdaysTea stall near office₹20 to ₹40Eating out: tea
A shop name, monthlyNeighbourhood kirana₹1,800 to ₹2,400Groceries
A person's name, fortnightlyLaundry man₹250Household

The milk vendor is ₹62 × 30 = ₹1,860 a month, more than many people would guess, and invisible if it sits in review or lands in Uncategorised.

Rule or alias: which one?

In SpendixAI you have two tools, and they do different jobs.

  • A rule says: when the description matches this text, use this category. It is the firmest instruction and is applied before history and AI.
  • An alias says: this messy name and that messy name are really one merchant. It tidies the name so grouping, history and similar-merchant matching work.

Use an alias when the same vendor appears under two or three spellings or handles, and a rule when you want the category fixed no matter what. For the milk vendor you might do both: alias the variants to one name, then add one rule for the category.

What if the same name is also my friend?

This is the danger. A rule on a personal name will categorise every payment to that name, including the evening you split dinner with someone who shares it, or lent money to a cousin. Before you add a rule, check the history: is every payment to this name a purchase? If not, skip the rule and correct the odd ones by hand, or rely on the aliased name plus your own review.

A ten-minute setup

  1. Open a month's imported transactions and group or sort by description.
  2. Find the vendors you pay at least three times a month.
  3. Pick their category, using a sub-category if it helps, such as dairy or vegetables.
  4. Add an alias if the name varies, then a rule for the category.
  5. Next month, check the review pile. Anything that came back is a new variation to add.

You will not catch every street vendor, and you do not need to. The weekly one-off payments can sit in review or be left as they are. Regulars, which make up most of this spend, are the ones that repay the effort.

SPENDIXAI JOURNAL

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

Explore your reports