Convert any bank statement PDF to Tally XML

Re-typing a bank statement into Tally voucher by voucher is the slowest job in any Indian accounting practice. StmtSnap converts a bank statement PDF straight into a Tally ERP 9 / Tally Prime XML file, so the whole statement imports in a single step instead of hundreds of manual entries.

Tally XML is included on the Starter, Pro and Enterprise plans. There is no Tally plugin to install and no intermediate Excel clean-up. The free tier gives you Excel and CSV from the same PDF.

Convert now

Text PDFs are converted in this browser and never uploaded. Scanned PDFs are read by Google Gemini, and we ask first.

Before you convert: a text PDF stays on your device. If the PDF is a scan, we show a notice before any page is sent to Google Gemini, and scanned pages need a free account. Excel and CSV are free; Tally XML, QuickBooks QBO and Zoho CSV are on paid plans (pricing).

What StmtSnap creates in Tally

  • A Payment voucher for every debit (withdrawal) line
  • A Receipt voucher for every credit (deposit) line
  • Both sides of each voucher: the bank ledger and the other ledger
  • Transaction date and narration (first 200 characters) on each voucher
  • Vouchers numbered in statement order, in one importable XML

How to import the XML into Tally

  1. Convert your bank statement PDF in StmtSnap and download the _tally.xml file.
  2. Make sure the ledgers named in the file exist in your Tally company (see below).
  3. Open Tally Prime (or Tally ERP 9) on the correct company.
  4. Go to Gateway of Tally → Import → Transactions (in ERP 9: Import of Data → Vouchers).
  5. Select the _tally.xml file. Tally posts every Payment and Receipt voucher for the period.

Tally rejects a voucher whose ledger name does not exist in the company. The file uses "Bank Account" for the bank side and "Suspense Account" for the other side unless a ledger rule matches, so either create those two ledgers or rename them in the file before importing. Clearing Suspense entries to the right ledgers afterwards is the usual month-end step.

Long narrations that wrap onto two or three lines in the PDF are joined back into one before the voucher is written, so UPI and NEFT strings printed inside the narration survive. A separate cheque/reference column is not carried into the voucher in this version.

Because the export is deterministic, the same PDF always produces the same vouchers, which helps when a practice splits data entry and review between two people.

Questions

Does StmtSnap support Tally Prime and Tally ERP 9?
Yes. The file is standard Tally import XML (an ENVELOPE with Payment and Receipt vouchers) and imports through the normal import screen in both.
Do I need a Tally plugin or TDL?
No. You import the file directly from Gateway of Tally. No plugin, add-on or TDL is required.
Are debits and credits mapped correctly?
Withdrawals become Payment vouchers that debit the other ledger and credit the bank; deposits become Receipt vouchers that debit the bank and credit the other ledger.
Is the Tally export available on the free plan?
No. Tally XML is on the Starter, Pro and Enterprise plans. The free tier gives you Excel and CSV.
Which banks can I export to Tally?
Any bank whose statement is a text PDF with a column header naming a date column and at least one money column (Debit/Credit, Withdrawal/Deposit, a single Amount, or Balance). A scanned PDF has no text to read, so it goes through the scanned-page path instead: you see a notice first, and it needs a free account.

Reference: TallyPrime — banks supported for statement import

Comparing converters?

Related converters