Bank of Baroda statement PDF to Excel & Tally XML

Convert Bank of Baroda (BoB) 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.

Bank of Baroda PDFs split into portrait BOB World / mobile statements and landscape borderless tables. Jemsky isolates both with BARB0 and BoB header keywords, and explicitly ignores Varachha locality text so a BoB customer in Mota Varachha is not sent to the Varachha co-op plugin.

Portrait files may be English-only or bilingual. The Hindi labels नामे, जमा, and शेष mark debit, credit, and balance. Coordinate bands still apply: date, value date, narration, cheque, debit, credit, balance.

Wrapped UPI/IMPS/RTGS lines are joined in vertical reading order inside the date–balance Y band. That is the usual BoB month-end mess when CAs copy from the PDF viewer.

Export Excel for the working paper and Tally XML for Day Book. Zero retention.

Statement formats the BoB parser recognizes

• Portrait / BOB World mobile: Cheque Debit / Debit Credit / Hindi नामे जमा शेष headers
• Landscape borderless corporate-style tables

Parser quirks specific to BoB

• Identity is BARB0 IFSC or bank of baroda / bob world — not the words MOTA VARACHHA in an address.
• Bilingual Hindi/English portrait files (नामे / जमा / शेष) are first-class, not an afterthought.
• Row bands are sliced from transaction-date and balance Y coordinates so footer noise stays out.
• Password-protected BOB World downloads unlock in RAM (sample pattern: registered mobile).

Example narrations and how they export

• UPI wrap on bilingual portrait — Hindi headers do not become extra Excel columns.
• MOTA VARACHHA in address — Does not route to Varachha Co-Op; BARB0 wins.
• BOB World 18-page file — 306-txn class files still audit to the printed close.

CA workflow on BoB files

BoB World passwords are often the registered mobile. Enter it on Jemsky; it never hits logs. If Auto Detect ever picks Varachha on a BARB0 file, that is a bug — Contact us with the PDF.

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 BoB 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 Bank of Baroda statement PDF to Excel?

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

Can I import Bank of Baroda statements into TallyPrime?

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

Does Jemsky store Bank of Baroda statement data?

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

What is unique about the BoB parser versus other banks?

Identity is BARB0 IFSC or bank of baroda / bob world — not the words MOTA VARACHHA in an address. BoB World passwords are often the registered mobile. Enter it on Jemsky; it never hits logs. If Auto Detect ever picks Varachha on a BARB0 file, that is a bug — Contact us with the PDF.

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