A savings account statement typically carries your name and address, account number, customer ID, branch and IFSC code, the period it covers, opening and closing balances, and a table of dated entries with narrations. Only the dates, amounts and narrations are useful to an expense tracker. The rest is identity data.
Layouts differ by bank and by whether you download a PDF, CSV or Excel version, so use this as a map and check your own statement for exactly what it shows.
What identifies you on the first page?
- Your full name, as registered with the bank
- Your postal address, and sometimes email and mobile number
- Account number, often the whole number rather than a masked one
- Customer ID or a similar identifier
- Account type and sometimes the nominee status or joint holder names
- Branch name and address, and the IFSC code of that branch
- The date the statement was generated
These fields tell anyone who sees them who you are, where you live and exactly which account to refer to. They do not tell a tracker anything it needs.
What describes the period and balances?
There is a statement period, such as 1 July to 30 September, an opening balance at the start and a closing balance at the end. Some statements add a running balance after every row. A balance is personal financial information, so treat the page that shows it as sensitive even when the rest looks routine.
What is in the transaction table?
Each row usually has a date, a narration or description, a reference number, a debit or credit amount and sometimes a balance. The narration is the part most people overlook. It often includes a payee name, a UPI handle, a transfer reference or a merchant string cut short by the bank's system.
| Field | What it shows | Does a tracker need it? |
|---|---|---|
| Date | When the entry posted | Yes |
| Narration | Who or what, in the bank's words | Yes, for categorising |
| Debit or credit amount | Money out or in | Yes |
| Reference number | Bank's internal or UPI reference | Useful for spotting duplicates |
| Running balance | Balance after each row | Not for tracking spend; sensitive |
| Name, address, customer ID | Who you are | No |
| Account number and IFSC | Which account and branch | Only to tell accounts apart, which you can do yourself |
A worked example with three entries
Say your statement shows three rows: a debit of ₹1,240 with a narration starting with a UPI reference and a grocery shop's name, a debit of ₹12,500 labelled as a transfer to a named person, and a credit of ₹55,000 labelled salary. The tracker needs the three dates, amounts and narrations. It does not need your address or customer ID. But the second narration includes another person's name, which is also personal data, so think about that before you share.
Which fields matter if you upload to a tracker?
Dates, amounts, and narrations. In SpendixAI, you pick the account (bank, card or wallet) before importing, so each transaction keeps its account without you needing to expose anything else. The tracker categorises using the normalised merchant name and your own rules, and any AI step receives the merchant name and an amount band, not your name, account numbers, full statement text or balances. That does not make the file itself less sensitive, so keep your own copy safe.
Who else might see these fields?
Anyone you send the file to, any device or backup it is stored on, and anyone you let into the account you uploaded it to. The narrations can also mention other people. Reading the statement as a stranger would, with no context, shows you how much it reveals.
Quick reference
- Identity block: name, address, customer ID, account number, IFSC
- Period and balances: opening, closing and running balances
- Transaction table: date, narration, reference, debit or credit
- Footer: notes from the bank, sometimes branch contact details
- Hide identity and balances when sharing, unless the other party needs them
Useful ideas start with a clearer picture of your own spending.
Explore your reports


