Getting started

How to categorise an SBI statement: UPI, ATM and transfer rows

A practical way to categorise a savings account statement: build a payee map, handle UPI, ATM and transfers, and check that the totals still match.

Editorial illustration for How to categorise an SBI statement: UPI, ATM and transfer rows

To categorise an SBI savings account statement, work from the narration column: group repeated payees first, decide a category for each group once, then handle the awkward rows, such as ATM withdrawals and transfers between your own accounts, separately. Done this way, a month of one hundred and forty rows becomes about twenty decisions.

Why a savings account statement is harder than a card statement

A card statement mostly shows merchants. A savings account statement mixes salary, rent, UPI payments to people and shops, cash withdrawals, EMIs, transfers to your own accounts and refunds. The narration usually carries a payee name or reference, but how it is worded depends on the payment type, so check your own statement for the pattern instead of assuming one. The same shop can appear with different narrations, so group by the name you recognise.

Step by step

  1. Sort the rows by narration so the same payee sits together.
  2. Pick the five largest groups by total and give each a category.
  3. Handle transfers: money moved between your own accounts is not spending. Give it a category called Transfer and leave it out of spending totals.
  4. Handle cash: an ATM withdrawal is a spending event you cannot see inside. Keep it as Cash, then note what cash was spent on if it matters.
  5. Look at what is left, usually one-off UPI payments to individuals, and decide whether to label them by purpose, such as Domestic help or Gift, or leave them as Personal transfers.

A payee map you can copy

Keep a two-column list of text to look for and category. Say these are the examples from one month.

Narration containsCategoryRowsTotal (₹)
Kirana store nameGroceries116,420
Electricity boardUtilities11,980
Landlord's nameRent116,000
Own recurring depositTransfer15,000
ATMCash37,000
Auto and cab payeesTransport142,310

These rows add up to ₹38,710 across 31 rows. If the bank statement shows total debits of ₹41,000, you know ₹2,290 sits in rows not yet categorised, which is a smaller job than reading the whole statement again.

How does an app do this faster?

SpendixAI categorises in stages: your own rules first, then your past choices and similar merchants, and only if you switch AI on, a model for what remains. That model sees a normalised merchant name and an amount band, not your name, account numbers or balances. You can turn AI off per feature or entirely, and unmatched items are then held for review. Corrections become history, and you can add merchant aliases so two spellings of one shop end up together. Upload the statement as PDF, CSV or Excel, choose the account first and review the rows before saving.

What should I do with UPI payments to people?

These are the hardest rows because the narration names a person, not a purpose. Add a short note when you pay, if your UPI app allows it, because the note often travels into the statement narration. For old rows, decide by pattern: a person who gets ₹300 every few days is probably a daily service, while a single large payment is likely a one-off. If you cannot tell, leave it as Personal transfer rather than guess.

Next steps

  • Make your payee map the first sheet in a monthly file and reuse it.
  • Review the Other bucket every month and move anything that appears twice into a named category.
  • Never put net-banking details into a tool that asks for them; a statement file is all a tracker needs.
SPENDIXAI JOURNAL

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

Explore your reports