How to Download Bank Statements as Excel or CSV from 12 Major Indian Banks (2026)

A PDF statement is a picture of data. An Excel or CSV statement is the data.

Working from PDFs means one of three things: manual re-typing (slow, error-prone), OCR conversion (fast, differently error-prone), or paying for a converter tool that does the OCR for you (fast, still error-prone, now also costing money). Every one of these introduces a step where 8 can become 3, and a lakh can lose a zero.

The Excel export from netbanking has none of these problems. The amounts arrive as numbers. The narrations arrive as complete strings, which matters enormously if you build party ledgers from narrations. And the file is analysable the moment it downloads, by your own pivot tables or by tools like Greenote Lite that take Excel and CSV directly.

Netbanking portals differ in menus but agree on the flow:

The twelve banks with dedicated parsing support in Greenote Lite, and where to find the detailed export walkthrough for each:

Client banks with someone else? The full supported-banks list covers 120+ Indian banks, and statements from any bank work in generic mode.

Not every "Excel" download is the same file type, and a few quirks repeat across banks:

.xls vs .xlsx. Several banks still export the older .xls format. It opens fine in modern Excel and processes fine in analysis tools; just do not be surprised by the extension.

"Delimited" means text. Some banks offer a Delimited option: a plain-text file with a separator character. It is effectively a CSV and any decent tool ingests it, but if you open it directly in Excel, use the import wizard so amounts do not lose formatting.

Header rows and footers. Bank exports wrap the transaction table in letterhead rows above and disclaimers below. Analysis tools handle this automatically; if you are pivoting manually, delete them first so the table detects cleanly.

Encoding oddities. Occasionally a CSV arrives with characters that render as junk (usually the rupee symbol). Harmless to amounts, but re-exporting as Excel avoids it.

The export is easy; the logistics are where statements go wrong. Clients forward PDFs because the bank emails them PDFs, and the netbanking export never occurs to them.

What works in practice:

Send instructions, not requests. Instead of "please send bank statements", send "please log in to netbanking and download the statement in Excel format" with the steps for their bank. The per-bank pages above are written to be forwarded as-is.

Ask for the full financial year in one go. Piecemeal statements create gaps and overlaps. Specify the date range explicitly: 1 April to 31 March.

Ask for every account. The savings account the client forgot to mention is a classic source of surprises at finalisation. Ask for all accounts held during the year, including ones closed mid-year.

Sometimes there is genuinely no Excel: an account closed years ago, a cooperative bank with no netbanking, a client who only has the printed statement the branch gave them.

Honest options, in order of preference: ask the branch for a soft copy in Excel (many can generate one on request), re-type just the rows that matter for the question at hand rather than the whole statement, or OCR the PDF and then verify every amount against the source before relying on it.

What we do not recommend is treating OCR output as trustworthy without verification. And to be transparent about our own tool: Greenote Lite takes Excel and CSV only, precisely because we are not willing to hand back working papers built on unverified OCR. PDF input is planned for the full Greenote desktop app, where the verification workflow around it can be done properly.