HSBC Bank statement PDF to Excel & Tally XML

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

HSBC India statements often follow an international ‘Paid out / Paid in’ template rather than Indian PSU debit/credit headers. A converter trained only on SBI/HDFC will leave both amount columns empty. Jemsky maps Paid out → withdrawal and Paid in → deposit.

Brought-forward and carried-forward lines set opening and closing. Missing intermediate balances are recomputed so the audit equation still runs.

This page is for HSBC statement PDFs used by Indian CAs (including clients with HSBC India accounts and hybrid layouts). Export Excel/CSV/Tally XML. Zero retention.

Statement formats the HSBC parser recognizes

• UK/India hybrid layout: Date (DD MMM YY), Payment type and details, Paid out, Paid in, Balance

Parser quirks specific to HSBC

• Headers are Paid out / Paid in, not Withdrawal / Deposit — copied PSU parsers miss both columns.
• Dates like 02 Aug 24 become 02/08/2024.
• Opening from BALANCE BROUGHT FORWARD; closing from BALANCE CARRIED FORWARD; those rows are not transactions.
• Intermediate printed balances are sometimes omitted; Jemsky computes running balance mathematically.
• Detection includes www.hsbc.co.uk style footers as well as HSBC India letterheads.

Example narrations and how they export

• 02 Aug 24 / Paid out 1,200.00 — Named-month date + paid out → Withdrawal in Excel.
• BALANCE BROUGHT FORWARD — Opening metadata, not a voucher.

CA workflow on HSBC files

When reviewing HSBC Excel, look for Paid out as withdrawals. If a row has no printed balance, Jemsky filled it from the running equation — still match the PDF’s carried-forward total.

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 HSBC 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 HSBC Bank statement PDF to Excel?

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

Can I import HSBC Bank statements into TallyPrime?

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

Does Jemsky store HSBC Bank statement data?

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

What is unique about the HSBC parser versus other banks?

Headers are Paid out / Paid in, not Withdrawal / Deposit — copied PSU parsers miss both columns. When reviewing HSBC Excel, look for Paid out as withdrawals. If a row has no printed balance, Jemsky filled it from the running equation — still match the PDF’s carried-forward total.

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