Bandhan Bank statement analyser: Excel in, ITR-ready report out
Bandhan Bank is one of India's newer private banks, and it shows in the statements: narrations tend to be cleaner and more human-readable than the terse, all-caps style of older public-sector banks, with UPI, NEFT and IMPS rows that usually spell the counterparty out. That is good news for a party ledger. The less an engine has to guess, the more rows land against a named party and the shorter your Suspense list gets. Greenote Lite reads the Excel or CSV export, pulls the party from each narration, and hands back an audit-ready workbook.
Works with Excel and CSV statements from netbanking. Got a PDF? That is coming to the full Greenote desktop app.
How to export your Bandhan Bank statement as Excel or CSV
- 1Log in to Bandhan Bank net banking (or the mBandhan app) and open the account statement section for the account you need.
- 2Select the account and set the date range covering the period under audit; in most versions a custom range covers a full financial year in one download.
- 3Choose the Excel or CSV download rather than PDF. Greenote Lite reads .xls, .xlsx and .csv.
- 4Upload the file exactly as downloaded; no cleanup is needed, 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 Bandhan statement
Cleaner input lets the engine go further, so on Bandhan statements the report tends to come out especially tidy:
- Bandhan's narrations are comparatively human-readable, so more UPI, NEFT and IMPS rows resolve to a named party and fewer fall through to Unknown than on older public-sector formats.
- UPI rows usually carry both the counterparty name and the VPA, so fifty payments to one supplier roll up as a single party with one total, with the VPA as a stable anchor when the name is typed differently across months.
- NEFT and IMPS narrations embed a reference number beside the counterparty; the engine keeps the name and strips the reference, so a serial number never turns into a party.
- Debit and credit come straight from the amount columns, so direction never depends on parsing the text and a payment cannot be flipped into a receipt; card and merchant rows are grouped per merchant into a ranked spend list.
- Rows with no readable counterparty, often terse charge, interest or reversal entries, are marked Suspense/Unknown rather than guessed, so the party ledger stays trustworthy.
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.
Bandhan statement questions
Not in Greenote Lite, which reads Excel and CSV only. Export the Excel or CSV statement from Bandhan net banking or the mobile app instead; it typically sits right next to the PDF option. PDF statements are handled by the separate Greenote desktop app, which converts the PDF and exports to Excel or Tally.
Bandhan's NEFT and IMPS rows place a reference number right beside the counterparty; the engine keeps the name and drops the serial, so a reference never masquerades as a party. With names and VPAs spelled out on most rows, more entries resolve to a real party and fewer fall through to Unknown.
Both typically work, as long as you export Excel or CSV rather than PDF. The app and the web portal can differ a little in column order, but the engine detects the transaction table rather than assuming one fixed layout.
Try it on a real Bandhan 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.