IDBI Bank statement PDF to Excel & Tally XML

Convert IDBI Bank (IDBI) bank statement PDFs with Jemsky’s dedicated parser — not a renamed homepage and not generic OCR. This page documents the layouts we actually ship, the quirks that break other converters, and examples CAs see in the wild.

IDBI Bank has two geometries that must not share code: a portrait retail statement and a landscape REP31 Customer Account Ledger used on large CA books. The ledger plugin requires IDBI identity plus Customer Account Ledger / REP31 / Ledger Print. The retail plugin returns 0.0 on those markers so you never parse a 580-row ledger with retail A4 bounds.

REP31 amounts use Indian grouping and Cr/Dr suffixes. Instrument digits become cheque/ref. Particulars are joined left-to-right for NEFT/CLG/ATM.

This is why IDBI is its own Jemsky page: swapping in the Indian Bank or generic OCR path destroys lakh amounts. Excel and Tally XML; PDF discarded.

Statement formats the IDBI parser recognizes

• Portrait retail statement (idbi_standard_v1)
• Landscape REP31 Customer Account Ledger (idbi_ledger_v1) with GL Date + Value Date + Cr/Dr balance suffix

Parser quirks specific to IDBI

• REP31 / Customer Account Ledger / Ledger Print forces the landscape plugin; standard returns 0.0 on those markers.
• Indian lakh grouping (2,39,63,421.14) parses to 23963421.14.
• Cover/param pages and ‘IDBI BANK … Page N’ run-dates are skipped.
• A row must have both GL Date and Value Date plus a Cr/Dr balance token.
• Not Indian Bank (IDIB) and not IDFC FIRST (IDFB).

Example narrations and how they export

• REP31 landscape 580 txs — Sample closing 647,920.90 with 100% audit vs printed totals.
• 2,39,63,421.14 — Lakh grouping, not European thousands.

CA workflow on IDBI files

If the PDF header says Customer Account Ledger or REP31, expect landscape parsing and lakh amounts. Retail IDBI PDFs are the shorter portrait path. Always Auto Detect rather than forcing Indian Bank.

Exports and privacy

Every successful convert can download Excel (.xlsx), CSV, and TallyPrime / Tally.ERP 9 Payment and Receipt XML. Customer statement bytes never land in Jemsky’s database. Optional Tally Party Ledger Masters store ledger names you import — not this bank’s PDF.

1. Open the converter and upload the IDBI PDF.
2. Leave Auto Detect on unless you know the exact layout name.
3. Confirm the financial audit equation matches the printed closing balance.
4. Export Excel for the working paper and/or Tally XML.

Frequently asked questions

How do I convert a IDBI Bank statement PDF to Excel?

Upload the IDBI e-statement on jemsky.com/app. Auto Detect should pick the IDBI plugin. Review Opening + Deposits − Withdrawals = Closing, then download Excel, CSV, or Tally XML. The PDF is parsed in RAM and discarded.

Can I import IDBI Bank statements into TallyPrime?

Yes. Export Tally XML and use Import → Transactions. Optional: import Master.json/xml and enable ledger suggest so IDBI UPI/NEFT rows map to party ledgers instead of Suspense A/c.

Does Jemsky store IDBI Bank statement data?

No. IDBI Bank PDFs are not archived. Passwords unlock in memory only.

What is unique about the IDBI parser versus other banks?

REP31 / Customer Account Ledger / Ledger Print forces the landscape plugin; standard returns 0.0 on those markers. If the PDF header says Customer Account Ledger or REP31, expect landscape parsing and lakh amounts. Retail IDBI PDFs are the shorter portrait path. Always Auto Detect rather than forcing Indian Bank.

Related: All banks · User Guide · Security · Free Excel · Tally