Central Bank of India statement analyser: Excel in, ITR-ready report out

Central Bank of India is one of the country's oldest public-sector banks, and its statements read like it: terse, upper-case narrations, and an 'Excel' download that in some versions is really an HTML or text table wearing an .xls extension. Greenote Lite is built for exactly this. It reads the older-style export as it comes, decodes the UPI, NEFT and IMPS rows into named parties, and marks anything genuinely unreadable as honest Suspense rather than guessing.

Works with Excel and CSV statements from netbanking. Got a PDF? That is coming to the full Greenote desktop app.

How to export your Central Bank of India statement as Excel or CSV

1. 1Log in to Central Bank of India net banking (or the Cent Mobile app) and open the account statement section for the account you need.
2. 2Select the account and set the from/to dates for the audit period; older portals sometimes cap one download to a few months, so a full financial year may take two or three files.
3. 3Choose the Excel or CSV download rather than PDF. In most versions it sits alongside the PDF option.
4. 4Upload the file exactly as downloaded. If your spreadsheet app warns that the format and extension don't match, that is normal for older public-sector exports and nothing needs fixing.

Menu names shift between netbanking versions, so treat the steps above as a guide — the constant is the format: take the Excel, XLS or CSV download, not the PDF. Greenote Lite does not read PDF statements; the full Greenote desktop app does, and is available now.

What Greenote Lite does with a Central Bank statement

Central Bank's older, compressed format asks more of the parser, and the engine answers with detection plus honesty:

• UPI rows are split on their segments, so the payer or payee name and VPA are lifted out and the same counterparty rolls up as one line in the party ledger instead of scattering across dozens of rows.
• NEFT, IMPS and RTGS narrations typically embed the counterparty name alongside an IFSC and a long reference; the engine strips the codes and the reference number and keeps the name.
• The 'Excel' file some Central Bank portals produce is really an HTML or tab-separated table under an .xls extension. The engine detects and reads these directly, so the format warning your spreadsheet app shows does not mean the file is corrupt.
• Direction is taken from the debit and credit columns, not from wording like TRF TO or TRF FROM, so a terse or mislabelled row can never flip a payment into a receipt; a single amount column with a separate Dr/Cr type is read the same way.
• Terse charge, interest and ATM withdrawal rows are mapped to Bank Charges, Interest and Cash Withdrawal even when the description is only a few characters, and any row with no readable counterparty goes to Suspense rather than a guessed party.

The download is a four-sheet Excel workbook: a party ledger of who paid whom, every transaction categorised and named, a category summary, and an ITR summary with AIS/SFT flags. See why the party ledger comes first or the full statement-to-ITR workflow.

Central Bank statement questions