HDFC Bank statement PDF to Excel & Tally XML

Convert HDFC Bank (HDFC) 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.

HDFC Bank net-banking PDFs mix a dense seven-column grid with a value-date column that generic converters often merge into narration. Jemsky’s HDFC parser reads Chq./Ref.No. and Value Dt as first-class fields so cheque-based audit trails survive Excel and Tally XML.

On 80-page files the table origin shifts: page 1 starts below ~210 pt, later pages below ~40 pt. Header words between 210–260 pt are used to recompute withdrawal, deposit, and balance bands because HDFC slightly retargets those columns across statement generations.

The last page usually prints STATEMENT SUMMARY with OpeningBalance, DrCount, CrCount, Debits, Credits, and ClosingBal. Those labels are not transactions. Jemsky stops extraction above that block.

CA workflow: keep cheque numbers for unmatched payments, use value date when booking, and run the ledger equation before import. Password unlock is RAM-only. Zero statement retention after export.

Statement formats the HDFC parser recognizes

• Net-banking statement: Date, Narration, Chq./Ref.No., Value Dt, Withdrawal Amt., Deposit Amt., Closing Balance
• Long 80+ page retail statements with STATEMENT SUMMARY cutoff on the last page

Parser quirks specific to HDFC

• Column bounds are recomputed from header word coordinates on each page (withdrawal/deposit/balance drift).
• Cheque/reference numbers strip leading zeroes (0000421659621187 → 421659621187) for Excel filters.
• STATEMENT SUMMARY / OpeningBalance / DrCount blocks are cut off so summary labels never become transactions.
• Dates arrive as DD/MM/YY or DD/MM/YYYY and are standardized for Tally.

Example narrations and how they export

• CHQ PAID 000000421659 — Cheque column is isolated; leading zeroes stripped for audit sampling.
• UPI-XXXX@okhdfcbank — Value date stays aligned with debit/credit even when narration wraps.
• STATEMENT SUMMARY — Cutoff — this block is not exported as rows.

CA workflow on HDFC files

HDFC clients often send the full net-banking PDF including the summary page. Convert once, check that DrCount/CrCount are not extra Excel rows, then map cheque payments in Tally using the cleaned reference 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 HDFC 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 HDFC Bank statement PDF to Excel?

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

Can I import HDFC Bank statements into TallyPrime?

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

Does Jemsky store HDFC Bank statement data?

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

What is unique about the HDFC parser versus other banks?

Column bounds are recomputed from header word coordinates on each page (withdrawal/deposit/balance drift). HDFC clients often send the full net-banking PDF including the summary page. Convert once, check that DrCount/CrCount are not extra Excel rows, then map cheque payments in Tally using the cleaned reference column.

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