IDBI Bank statement analyser: Excel in, ITR-ready report out
IDBI Bank has the feel of an older public-sector portal: narrations arrive terse and upper-case, party names sometimes truncate mid-word, and in some versions the "Excel" download is really a text or HTML table wearing an .xls extension. Greenote Lite is built for exactly this. It reads the file for whatever it actually is underneath, pulls the mode and the counterparty out of each cramped narration, and hands back a party ledger, categorised transactions and an ITR summary written in plain language.
Works with Excel and CSV statements from netbanking. Got a PDF? That is coming to the full Greenote desktop app.
How to export your IDBI Bank statement as Excel or CSV
- 1Log in to IDBI Bank internet banking (or the GO Mobile+ app) and open the account statement section. In most versions it sits under the Accounts or Operative Account Statement menu.
- 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 more than one file.
- 3Choose the Excel or CSV download rather than PDF. Greenote Lite reads .xls, .xlsx and .csv.
- 4Upload the file exactly as downloaded, even if opening it shows a format-mismatch warning. That is normal for these exports, and nothing needs re-saving first.
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 an IDBI statement
IDBI's older, public-sector-style format is the kind that trips up naive parsers, so the engine leans on a few specific habits:
- Terse, upper-case narrations are parsed for mode keywords such as UPI, NEFT, IMPS and TRF, plus whatever party fragment survives. Truncated names are matched conservatively, so two different parties are never merged into one.
- UPI descriptions are typically slash-separated and carry a reference, the payer or payee and a VPA. The engine keeps the human name and the VPA for the party ledger and drops the long reference, so repeated payments to one counterparty roll up as a single line.
- NEFT and IMPS rows usually embed an IFSC and the counterparty name mid-string. The codes and reference numbers are stripped and the name is kept.
- In some versions the .xls IDBI produces is a text or HTML table wearing an Excel extension. The engine detects and reads these directly, so the format-mismatch warning your spreadsheet shows does not mean the file is corrupt.
- Direction is taken from the debit and credit columns as the source of truth, so a word inside the narration can never flip a payment into a receipt. Terse charge, interest and ATM rows are mapped to Bank Charges, Interest and Cash Withdrawal even when the description is only a few characters long.
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.
IDBI statement questions
No, and re-saving can actually drop rows. The older IDBI portal exports a text or HTML table under an .xls name, so your spreadsheet app flags the mismatch. Greenote Lite reads that raw table as it is, so upload the original file untouched.
The engine pulls the mode and whatever name survives, and rolls repeat payments to the same counterparty into one line. A fragment too short to trust is never force-matched to another party; it stays in Suspense/Unknown for you to settle from the voucher.
Yes, if you export it as Excel or CSV. GO Mobile+ and the netbanking site can lay columns out differently, and the engine detects both. Skip the PDF option; PDF statements are handled by the separate Greenote desktop app.
Try it on a real IDBI statement
Your first statement is free — the trial processes the first 300 transactions so you can judge the quality end to end. Verify your email with a one-time code (no password, no card), and the file is deleted the moment your report is ready.