Rajkot Nagrik Sahakari Bank statement PDF to Excel & Tally XML

Convert Rajkot Nagrik Sahakari Bank (RNSB) 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.

Rajkot Nagrik Sahakari Bank (RNSB) is three converters pretending to be one brand. E-Passbook splits dates across lines. Statement of Account uses TRAN/VALUE DATE with Indian-grouped amounts and Cr/Dr on total balance. Compact files drop Tran/Value and are frequently locked with the mobile number.

Jemsky’s plugins are mutually exclusive on purpose. Feeding an E-Passbook into the compact DATE parser loses the year. Feeding compact into E-Passbook invents instrument columns.

Sampled files: 156-txn E-Passbook and 59-txn statement-of-account both at 100% audit vs printed Dr/Cr counts. Particulars that start above the date row are assigned by midpoint between anchors.

Excel/CSV/Tally XML. Mobile passwords unlock in RAM only. No statement archive.

Statement formats the RNSB parser recognizes

• E-Passbook / Statement of Operative Account: Date split DD-MM- / YYYY, Instrument No, Debit, Credit, Closing Balance
• Statement of Account with TRAN DATE + VALUE DATE + TOTAL BALANCE (Cr/Dr suffix, Indian grouping)
• Compact DATE-only statement (no Tran/Value Date); often password = 10-digit mobile

Parser quirks specific to RNSB

• Three exclusive plugins; E-Passbook returns 0.0 on TRAN DATE+VALUE DATE headers and vice versa.
• E-Passbook prints year on the next visual line, including across page breaks.
• Debit and credit are mutually exclusive — no 0.00 filler on the empty side.
• Compact statements stop at STATEMENT SUMMARY and prefer printed opening/closing from that table.
• IFSC RNSB0000 / Rajkot Nagrik identity.

Example narrations and how they export

• E-Passbook 156 txs, open 71,354.03 close 320,536.53 — Year-on-next-line dates still audit 100%.
• Compact PDF password = mobile — Unlock in RAM; DATE-only header.
• TRAN DATE / VALUE DATE statement — Particulars may start above the amount row.

CA workflow on RNSB files

Ask the RNSB client: E-Passbook, Statement of Account, or compact mobile PDF? If they only have a password hint, it is often the registered mobile on compact files. Auto Detect still preferred.

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 RNSB 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 Rajkot Nagrik Sahakari Bank statement PDF to Excel?

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

Can I import Rajkot Nagrik Sahakari Bank statements into TallyPrime?

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

Does Jemsky store Rajkot Nagrik Sahakari Bank statement data?

No. Rajkot Nagrik Sahakari Bank PDFs are not archived. Passwords unlock in memory only.

What is unique about the RNSB parser versus other banks?

Three exclusive plugins; E-Passbook returns 0.0 on TRAN DATE+VALUE DATE headers and vice versa. Ask the RNSB client: E-Passbook, Statement of Account, or compact mobile PDF? If they only have a password hint, it is often the registered mobile on compact files. Auto Detect still preferred.

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