Cards and UPI

Exporting your UPI transaction history for tracking

How to export your UPI transaction history for tracking: what an app export, a bank statement and an email summary each give you, and which to import.

Editorial illustration for Exporting your UPI transaction history for tracking

For tracking, the most reliable way to export your UPI transaction history is to download the statement of the bank account or card the money came from, in CSV or Excel if offered, otherwise PDF. UPI is only a route for payments, so the account statement is the complete record, while the app history and emailed alerts are useful for filling in who you actually paid.

What do the three sources actually give you?

SourceWhat you usually getBest used forWatch out for
UPI app historyPayee names, your own notes, success or failed statusRecognising who a payment went toHow far back it goes and whether it can be downloaded differs by app, so check yours
Bank statementEvery debit and credit with date, narration and running balanceThe main import, because it is completeNarration is often shortened and full of codes
Emailed summary or alertsOne alert per payment, or a monthly summary if your bank sends oneChecking a single paymentSlow to collect, and not every bank sends them

Which source should you treat as the master record?

Pick the statement of the account that was debited. If you paid from a savings account, that is the bank statement. If you paid from a credit card linked to UPI, it is the card statement. Choosing one master source per account is what stops the same ₹450 grocery payment turning up twice, once from the app and once from the bank.

How do you get a clean statement file?

  1. Decide the period first. Whole months are easier to reconcile than odd date ranges, and many people tidy up by April to March financial year.
  2. Log in to your own bank's net banking or app yourself and use its statement or download option. Choose CSV or Excel if it is offered, because rows come out as separate cells. Use PDF only when nothing else is available.
  3. Open the file and check the first and last dates, and that the debit and credit columns look sensible.
  4. Compare the closing balance in the file with the balance your bank app shows for that day. If they match, nothing is missing.
  5. Save it with a name such as savings-2026-10 so you never import the same month twice by accident.

How do you import it with the least manual cleanup?

If you track in a sheet, paste the rows into one master tab and keep a column called Source so you know which account each row came from. If you use SpendixAI, pick the account first, then upload the PDF, CSV or Excel file and review the rows before saving. Each transaction keeps its account, and a re-uploaded month can be flagged as a possible duplicate. Layouts vary between banks, so glance through the preview rather than assuming every row was read perfectly.

What if the statement names are unreadable?

Narrations often look like a long string with a handle and a code. Say a row reads a payment to a handle that ends in the name of a tea stall. Open your app history for that day, find the payee name you saved, and use it as the clean name in your records. In SpendixAI you can add a merchant alias so the same payee is recognised next time. In a sheet, a small two-column lookup table of ugly name and clean name does the same job.

Is the export complete? A quick check

  • Opening balance plus credits minus debits equals the closing balance.
  • The number of rows looks right for the month; a gap of several days suggests a missing page.
  • Failed payments do not appear as debits, or appear with a matching reversal credit.
  • Cash withdrawals are present as ATM rows even though the spending itself happened later in cash.

Once those four checks pass, the file is safe to import, and the app history can be set aside except for naming payees.

SPENDIXAI JOURNAL

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

Explore your reports