Yes Bank statement PDF to Excel & Tally XML

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

Yes Bank standard statements are wide portrait pages (~737×935 pt) with right-aligned amount columns. If a converter uses left-edge (x0) bands copied from SBI, Yes Bank withdrawals land in the wrong field. Jemsky classifies withdrawals, deposits, and running balance by x1.

Narration is printed above the date. Attaching those lines to the previous voucher is the classic Yes Bank Excel mess. The parser binds upward description lines to the following date row.

CASA net-banking files are often five quarterly statements concatenated. Each segment has its own opening. Treating the PDF as one table breaks the audit equation; Jemsky handles the CASA plugin separately from the standard wide layout.

Password prompt is collected up front and used only in RAM. Export Excel/CSV/Tally XML; no archive.

Statement formats the Yes Bank parser recognizes

• Wide portrait standard: Transaction Date, Value Date, Cheque No/Reference No, Description, Withdrawals, Deposits, Running Balance (DD-Mon-YYYY)
• CA/SA net-banking CASA: A4 portrait, often 5 quarterly segments merged into one PDF (100+ pages)

Parser quirks specific to Yes Bank

• Standard layout descriptions sit ABOVE the date row — the opposite of many PSU banks.
• Withdrawals/deposits/running balance are classified by right edge (x1), not left edge.
• Dates like 01-Apr-2025 are converted to DD/MM/YYYY.
• CASA merged PDFs contain multiple quarterly opening balances; Jemsky walks each segment.
• YESB0 IFSC plus Yes Bank text; the PNB plugin explicitly refuses Yes Bank files.

Example narrations and how they export

• Description above 01-Apr-2025 — Narration belongs to that dated row, not the previous one.
• 125-page merged CASA — Quarterly segments, not one opening balance for the whole file.

CA workflow on Yes Bank files

If a Yes Bank file is 100+ pages, check whether it is merged quarters before comparing one opening to one closing. For standard 15-page files, confirm descriptions are on the correct dated row 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 Yes Bank 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 Yes Bank statement PDF to Excel?

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

Can I import Yes Bank statements into TallyPrime?

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

Does Jemsky store Yes Bank statement data?

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

What is unique about the Yes Bank parser versus other banks?

Standard layout descriptions sit ABOVE the date row — the opposite of many PSU banks. If a Yes Bank file is 100+ pages, check whether it is merged quarters before comparing one opening to one closing. For standard 15-page files, confirm descriptions are on the correct dated row in Excel.

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