Federal Bank / Bank of India statement PDF to Excel & Tally XML

Convert Federal Bank / Bank of India (Federal / BoI) 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.

This Jemsky page covers Federal Bank (FDRL0) statement geometry and Bank of India structured debit/credit tables that CA firms often convert in the same workflow. Federal files are the ones with Freedom Current headers, SWIFT FDRL, and the frequent filename spelling FEDRAL.

Long Federal PDFs move amount columns slightly each page. Static bounds copied from page 1 fail on page 18. Jemsky recalculates debit, credit, and balance bands per page and reads CR/DR on balance.

Cheque / Tran ID stays in its own field for voucher matching. Excel and Tally XML export from RAM; the PDF is not kept.

Statement formats the Federal / BoI parser recognizes

• Federal Bank FDRL0 / Freedom Current: Date (DD-MM-YYYY or DD-MON-YYYY), Particulars, Cheque/Tran ID, Debit, Credit, Balance CR/DR
• Bank of India operating statements sharing structured debit/credit tables on this combined page

Parser quirks specific to Federal / BoI

• Federal detection includes the common misspelling fedral bank and SWIFT FDRL.
• Debit/credit/balance bands are recomputed per page because Federal shifts them on long files.
• Dates may be 11-04-2025 or 29-APR-2025 in the same client relationship.
• Sampled Federal files include 616-transaction password PDFs with 100% audit.

Example narrations and how they export

• 29-APR-2025 — Named-month dates standardized with DD-MM-YYYY rows in the same file.
• FEDRAL BANK.pdf filename — Misspelling still matches Federal, not a fallback unknown bank.

CA workflow on Federal / BoI files

Federal password PDFs are common (sample pattern: truncated PAN-like tokens). Unlock on Jemsky in RAM. For Bank of India vs Federal, trust Auto Detect plus the letterhead, then review Tran IDs in Excel.

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 Federal / BoI 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 Federal Bank / Bank of India statement PDF to Excel?

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

Can I import Federal Bank / Bank of India statements into TallyPrime?

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

Does Jemsky store Federal Bank / Bank of India statement data?

No. Federal Bank / Bank of India PDFs are not archived. Passwords unlock in memory only.

What is unique about the Federal / BoI parser versus other banks?

Federal detection includes the common misspelling fedral bank and SWIFT FDRL. Federal password PDFs are common (sample pattern: truncated PAN-like tokens). Unlock on Jemsky in RAM. For Bank of India vs Federal, trust Auto Detect plus the letterhead, then review Tran IDs in Excel.

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