Punjab National Bank statement PDF to Excel & Tally XML

Convert Punjab National Bank (PNB) 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.

Punjab National Bank still produces both modern e-statements and passbook-style PDFs. CA firms in smaller cities see both in the same week. Jemsky routes PNB identity carefully because the letters PNB appear inside other banks’ narrations.

The PNB plugin refuses files that already match Yes Bank (YESB0), Kotak, IndusInd, ICICI, HDFC, Axis, or SBI. That isolation is why a Yes Bank PDF will not be mislabelled as PNB.

Passbook-style files reprint headers mid-document. Jemsky continues the ledger instead of starting a second opening balance. Digital files export typed debit/credit for month-end Excel.

Tally XML and CSV are available from the same in-memory parse. No PNB statement archive is kept.

Statement formats the PNB parser recognizes

• Digital e-statement tables with PUNB / Punjab National headers
• Passbook-style continuation pages still used by many PNB retail clients

Parser quirks specific to PNB

• Detector returns 0.0 if the PDF is actually Yes Bank, Kotak, IndusInd, ICICI, HDFC, Axis, or SBI — PNB is a short token that false-positives.
• Passbook-style pages need continuity of running balance across ‘carry forward’ headers.
• IFSC prefix PUNB0 is a stronger identity signal than the letters PNB alone.

Example narrations and how they export

• Passbook print PDF — Continuation pages stitched; opening on page 2 is not a new account.
• Digital e-statement — Standard debit/credit columns typed for Excel.

CA workflow on PNB files

If Auto Detect says Universal Fallback on a PNB passbook scan, send the PDF via Contact — some image-only passbooks need a different path. Digital PUNB e-statements should hit the PNB plugin.

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 PNB 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 Punjab National Bank statement PDF to Excel?

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

Can I import Punjab National Bank statements into TallyPrime?

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

Does Jemsky store Punjab National Bank statement data?

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

What is unique about the PNB parser versus other banks?

Detector returns 0.0 if the PDF is actually Yes Bank, Kotak, IndusInd, ICICI, HDFC, Axis, or SBI — PNB is a short token that false-positives. If Auto Detect says Universal Fallback on a PNB passbook scan, send the PDF via Contact — some image-only passbooks need a different path. Digital PUNB e-statements should hit the PNB plugin.

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