Kotak Mahindra Bank statement PDF to Excel & Tally XML

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

Kotak Mahindra Bank net-banking PDFs collapse debit and credit into one amount column labelled Withdrawal(Dr)/Deposit(Cr). Converters that assume two amount columns will put every Kotak row in the wrong Excel field or duplicate it.

Jemsky’s Kotak parser reads the (Dr) and (Cr) suffix on each amount token, including on running balances for OD accounts. Dates like 01-04-2025 are standardized. Cheque/ref lives in its own band.

A subtle bug we already fixed: narration that starts slightly left of 115 pt (common on UPI) used to export as empty remarks. Bounds now start at 100, while stray De/Cr/Dr wraps are ignored.

Use Excel to review OD interest lines, then Tally XML for Payment/Receipt posting. Zero retention.

Statement formats the Kotak parser recognizes

• Combined Withdrawal(Dr)/Deposit(Cr) column with explicit (Dr)/(Cr) suffixes
• Overdraft and savings variants sharing Cust Reln No / KOTAK MAHINDRA BANK headers

Parser quirks specific to Kotak

• There is no separate debit and credit column — 30,288.00(Dr) vs 112,814.00(Cr) decide the side.
• Running balances may also carry (Dr)/(Cr); suffixes are stripped for the numeric balance.
• Narration bounds start at x0=100 so UPI lines that begin ~112 pt are not dropped.
• Lone wrap fragments De / Cr / Dr are ignored so they do not pollute remarks.

Example narrations and how they export

• 30,288.00(Dr) — Mapped to Withdrawal, not a negative deposit.
• 3,923,053.00(Dr) balance — OD running balance with suffix, numeric in Excel.
• UPI particulars at x≈112 — Earlier bound of 115 dropped these; current bound keeps them.

CA workflow on Kotak files

When a Kotak OD statement shows a huge (Dr) balance, that is not a parse error — confirm it against the PDF before mapping to a bank ledger in Tally. Empty remarks on UPI usually meant an old bound; current Jemsky keeps those particulars.

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

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

Can I import Kotak Mahindra Bank statements into TallyPrime?

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

Does Jemsky store Kotak Mahindra Bank statement data?

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

What is unique about the Kotak parser versus other banks?

There is no separate debit and credit column — 30,288.00(Dr) vs 112,814.00(Cr) decide the side. When a Kotak OD statement shows a huge (Dr) balance, that is not a parse error — confirm it against the PDF before mapping to a bank ledger in Tally. Empty remarks on UPI usually meant an old bound; current Jemsky keeps those particulars.

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