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

Bank of India is one of the older public-sector banks, and its statements read that way. The narrations tend to be terse and upper-case, packing the mode and party into a few abbreviated words, and in some versions the Excel download is really an HTML or text table wearing an .xls extension. Greenote Lite is built for exactly this. It reads the file as it actually is, decodes the abbreviated UPI, NEFT and IMPS descriptions into named parties, and refuses to invent a counterparty it cannot read.

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

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

1. 1Log in to Bank of India StarConnect internet banking (or the BOI Mobile app) and open the account statement view.
2. 2Select the account and the date range for the period under audit. Older portals sometimes cap a single download, so a full financial year may need two or three files.
3. 3Download the Excel or CSV version rather than PDF. If the saved .xls shows a format warning when you open it, that is normal for Bank of India and nothing to fix.
4. 4Upload the file exactly as downloaded. There is no need to re-save it as a proper Excel file first, and password-protected files are fine.

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 BoI statement

Bank of India's terseness is the real challenge, so the engine leans on careful decoding and honest labelling in equal measure:

• The .xls files some Bank of India versions produce are HTML or tab-separated text underneath rather than true spreadsheets. The engine detects this and reads them directly, so the format warning your spreadsheet app shows never means the file is unusable.
• Terse, all-caps narrations are parsed for mode keywords such as UPI, NEFT, IMPS and TRF, along with whatever party fragment survives. Truncated names are matched conservatively, so two different parties are never merged into one.
• Direction always comes from the debit and credit columns, not the words, so a transfer row can never flip a payment into a receipt. Whether the export gives you separate debit and credit columns or a single amount with a Dr/Cr indicator, both layouts are read.
• UPI and IMPS descriptions are split on their delimiters, and the party name plus VPA are kept, while long numeric references are recognised by shape and dropped, so a reference number never becomes a party.
• Terse charge, interest and ATM rows are mapped to Bank Charges, Interest and Cash Withdrawal, and any row with no readable counterparty goes to Suspense/Unknown instead of being guessed.

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.

BoI statement questions