Bank of America statement PDF to Excel & Tally XML

Convert Bank of America (BoA) 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 America checking PDFs that Indian CAs receive for NRI or US-entity clients are frequently scans. There is no text layer, dates are MM/DD/YY, and credits/debits live in separate sections with one amount column. Jemsky’s Indian Universal Fallback treated right-side amounts as balances and returned empty books — that is why BoA has a dedicated scanned strategy.

The engine renders pages, OCRs word boxes, tracks whether it is in Deposits and other credits or Withdrawals and other debits, anchors on MM/DD/YY, and takes the rightmost money token. Dates are then flipped to DD/MM/YYYY so they sort with Indian banks in the same workbook.

Because BoA often omits running balance, Jemsky builds a synthetic one for the validator. Always compare section totals to the PDF. Zero retention after export; OCR happens in memory.

Statement formats the BoA parser recognizes

• Scanned image-only checking statements: Deposits and other credits vs Withdrawals and other debits sections

Parser quirks specific to BoA

• Often 0 extractable text — generic Indian fallback produced 0 transactions on sample files.
• US MM/DD/YY dates are converted to DD/MM/YYYY for Indian CA Excel (07/16/26 → 16/07/2026).
• Single Amount column; section headers decide credit vs debit — there is no printed running balance.
• Jemsky synthesizes a running balance from 0 for validator continuity on partial section pages.
• Footer marketing / bofa.com / Security Center bleed is dropped.
• Zelle and wire narrations wrap across lines; midpoint banding keeps them on the dated amount.

Example narrations and how they export

• 07/16/26 Zelle payment — US date → 16/07/2026; amount from the deposits section is a credit.
• Image-only 3-page PDF — OCR geometry, not pdfplumber text.

CA workflow on BoA files

Tell the client you will convert the deposits and withdrawals sections, not a PSU-style running ledger. Check Excel totals against the PDF section totals. Tally XML is available after you accept the reconstructed balance column.

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 BoA 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 America statement PDF to Excel?

Upload the BoA e-statement on jemsky.com/app. Auto Detect should pick the BoA 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 America statements into TallyPrime?

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

Does Jemsky store Bank of America statement data?

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

What is unique about the BoA parser versus other banks?

Often 0 extractable text — generic Indian fallback produced 0 transactions on sample files. Tell the client you will convert the deposits and withdrawals sections, not a PSU-style running ledger. Check Excel totals against the PDF section totals. Tally XML is available after you accept the reconstructed balance column.

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