To turn a Standard Chartered India statement into a CSV, first look for a spreadsheet or CSV option in your own statement download screen. If there is none, convert the PDF to rows in Excel or Google Sheets and save as CSV UTF-8. The file only works for import if the dates, amounts and narration survive the trip, so most of this guide is about the small details that break a CSV.
Why do CSV files break when the data looks fine?
A CSV is plain text with commas between fields. Anything that contains a comma, a quotation mark or a line break must be wrapped in quotation marks, or it spills into the wrong column. Spreadsheet programs add that wrapping for you when you save, but a hand-edited file often does not have it.
Take a made-up narration: Rent, Jan, flat 4B. Written naively, the comma after "Rent" makes one description into two columns, and every amount shifts right by one. The correct line looks like 05/01/2026,"Rent, Jan, flat 4B",18000.00,.
What should the finished file look like?
- One header row only, with plain names such as Date, Description, Debit, Credit or Amount.
- One transaction per row, with no blank rows, totals or page headers in the middle.
- Dates in one consistent order, day first for Indian statements, and not mixed with text months.
- Amounts as plain numbers: no rupee sign, no spaces, no Dr or Cr letters inside the number.
- Either separate debit and credit columns, or one signed column. Not a mix.
- UTF-8 encoding so symbols and accents in narration do not turn into question marks.
How do I save it properly from Excel or Sheets?
- Finish cleaning the sheet and delete empty columns on the right.
- In Excel, choose Save As and pick CSV UTF-8 (Comma delimited). Plain CSV (Comma delimited) also works but may damage non-English characters.
- In Google Sheets, use File, Download, Comma-separated values.
- Reopen the file in a plain text editor such as Notepad. You should see commas and, where needed, quotation marks. If the layout looks scrambled there, fix it before importing.
- Check the last line: a trailing row of commas means a stray empty row.
What if my regional settings use semicolons?
Some computers set a list separator other than the comma, so Excel writes semicolons into the CSV. An importer that expects commas will read each row as one long field. Look at the file in Notepad: if you see semicolons between fields, change the list separator in your system region settings or save from Google Sheets, which always writes commas.
| Check | What a wrong result looks like | Fix |
|---|---|---|
| Leading zeros | A cheque or reference number such as 000482 becomes 482 | Format that column as Text before saving |
| Long numbers | A 16-digit reference shows as 1.23E+15 | Format as Text, then re-enter or re-paste |
| Dates | 05/01 turns into a different day or month | Set the column format to a fixed date before saving |
| Negative amounts | Brackets or trailing minus signs | Convert to a leading minus sign |
Can I skip the CSV step?
Often, yes. SpendixAI takes statement files in PDF, CSV or Excel, so you do not have to build a CSV unless your statement is only available that way. Choose the bank or card account first, upload, then review the rows before saving. If a layout does not parse cleanly, a tidy CSV in the shape above is the dependable fallback.
Before you hand the file over
- Keep a copy of the original statement with the same month in its name.
- Do not include card numbers, passwords or login details in any column or file name.
- Import one month first, check it, and only then load older months.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

