Getting started

Categorising Paytm Payments Bank transactions without the mess

Wallet and UPI narrations are cryptic. Learn to sort Paytm Payments Bank transactions into categories with rules, merchant names and a monthly review.

Editorial illustration for Categorising Paytm Payments Bank transactions without the mess

To categorise Paytm Payments Bank transactions, group them by merchant first, then by the purpose of that merchant, and write a rule for every merchant that repeats. Narrations on wallet and UPI statements are terse, so the work is in turning each name into a category once and letting that rule do the next hundred. This method works in a sheet or an app.

What do the narrations look like?

The exact wording varies, so look at your own statement. The pattern is usually a payment type, a payee name or handle and a reference number. Here are some made-up examples of the kind of line you will see, not real merchant entries.

Narration (made up)What it probably isCategory to assign
UPI to GREEN BASKET STORENeighbourhood groceryGroceries
UPI to R SHARMAA person's nameCheck: rent, help or friend?
Wallet payment METRO TICKETLocal transportTransport
Recharge MOBILEPhone top-upBills
Transfer to SELFYour own other accountTransfer, not spending

Which lines need a human?

Payments to individuals are the hard ones. A name alone does not say whether it was rent, a domestic helper, a loan to a friend or a split dinner. Decide once for each regular name: say 'R SHARMA' is your landlord, and every ₹14,000 to that name becomes Rent. For one-off names, look at the amount and the date, and when in doubt add a note while the memory is fresh.

Wallet top-ups and refunds also confuse totals. A top-up from your bank to the wallet is a transfer, and money coming back from a cancelled order is a refund, so net it against the original category instead of listing it as income.

Build your rules in four steps

  1. Sort the month by payee name, so that repeat merchants sit together.
  2. Pick the top ten payees by number of payments or total.
  3. Write one rule per payee: name contains this text, category is that.
  4. Run the rules, then fix what is left by hand.

Ten rules typically cover most of the rows you see, because a few shops, apps and people account for most payments. The first month is slow, the second much faster.

A worked example with made-up numbers

Say November has 64 payments totalling ₹41,800. After the ten rules, 49 payments are sorted, and 15 remain unmatched. Of those, 9 turn out to be small food items, 4 are transfers to yourself and 2 are friends. Your Transfer rows should not count as spending, so remove them from the total: if they come to ₹6,000, spending becomes 41,800 minus 6,000, which is ₹35,800. That correction alone changes the picture.

Can software do this for me?

SpendixAI sorts transactions in stages: your own rules, then your history and similar merchants, then an AI model only if AI is on and something is left. When AI is used it sees the normalised merchant name and an amount band, not your name, account numbers, full statement text or balances. You can turn AI off per feature or entirely, in which case unmatched items wait for your review. A correction you make becomes history, and you can add merchant aliases so several spellings count as one.

It reads statements uploaded as PDF, CSV or Excel; it does not read SMS or connect to your bank. Check that the Paytm statement you have imports as expected before relying on it.

Monthly review

  • Check unmatched rows and fix them.
  • Confirm transfers between your own accounts are not counted as spending.
  • Look for the same amount paid to the same merchant twice in two days.
  • Add a rule for any new payee that appeared three times.
SPENDIXAI JOURNAL

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

Explore your reports