Cards and UPI

How to track UPI spending from your bank statement

How to track UPI spending from your bank statement: why it is the complete record, how to import it, and how to categorise payees on the first pass.

Editorial illustration for How to track UPI spending from your bank statement

To track UPI spending, use your bank statement as the main record. Every UPI payment you make from an account appears there as a debit with a payee name or ID and a reference, whichever app you used. Download the statement as PDF, CSV or Excel, import it into your tracker, and categorise the payees once.

App histories are useful, but the statement is the one place where all your UPI payments from that account sit together with your card payments, EMIs and cash withdrawals.

Why is the bank statement the better record?

  • It lists payments from every UPI app linked to that account, so nothing hides inside one app.
  • It shows the debit that actually left your account, not a pending or failed attempt.
  • It puts UPI beside other debits, so your total spending is not split across several apps.
  • It is something your bank provides in a downloadable form, so you do not need any app's permission.

If you have more than one bank account linked to UPI, you need the statement for each, because a payment is recorded in the account it was paid from.

How do I import it?

  1. Download the statement for a month, or for several months, as PDF, CSV or Excel from your bank's official site or app.
  2. Open your tracker and choose the account the statement belongs to before importing.
  3. Upload the file. You can upload several files in a batch.
  4. Review the rows before saving. Check dates, amounts and the debit or credit direction.
  5. Save, then check the import history for status and any failure notice.

SpendixAI works this way: you pick the account first, upload PDF, CSV or Excel, and review rows before they are saved. It has no bank connection and does not ask for net-banking logins. Layouts differ between banks, so look at the preview rather than assuming every row has read correctly.

How should I categorise payees the first time?

The first import is the most work, because every payee is new. Sort the rows by payee name and handle the repeated ones first, since one decision covers many rows. Start with the payees you pay most often: milk and vegetables, an auto or cab driver, a pharmacy, a canteen, utilities, rent.

Payee typeExample categoryHow often it repeats
Milk or vegetable vendorGroceriesWeekly or daily
Auto or cab driverTransportSeveral times a month
Landlord or society accountRent and housingMonthly
PharmacyHealthOccasional
A person with no clue in the noteUnsorted person paymentsVaries

Leave payments to individuals in a catch-all category if the purpose is unclear, and sort them later, as the article on paying a person on UPI describes. The goal on the first pass is to categorise the big repeats, not to be perfect.

What about categorising automatically?

SpendixAI categorises in stages: your own rules first, then your history and similar merchants, and only after that, if you have switched it on, an AI model for what is left. You can turn the AI step off, set a monthly AI budget, or hold unmatched items for review. Your corrections become history, so the second month should need far less work than the first.

A word on reading the rows: narration text on UPI debits tends to be short and a little cryptic, with a payee name, an ID and a reference run together. Do not worry about decoding every line. Categorise the ones you recognise, leave the rest in a review pile, and come back to them with the payment app open.

Monthly routine

  • Download the statement for each account on the same day each month.
  • Import, review rows and save.
  • Sort any new payees, then add a rule for the ones that will repeat.
  • Glance at totals by category and at the largest single payments.
SPENDIXAI JOURNAL

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

Explore your reports