Convert a Bank Statement PDF to Tally XML

A bank statement converts to Tally XML by wrapping each transaction in the structured XML envelope Tally imports natively: an outer ENVELOPE, a TALLYMESSAGE for each entry, and a VOUCHER element typed as Payment for debits or Receipt for credits, with the date written as YYYYMMDD and the narration carried across. Upload the PDF above, confirm the preview, and download a ready-to-import .xml file. No third-party add-on, TDL, or Excel template is needed, Tally reads the file directly.

What is inside a Tally XML voucher file

Tally XML is not a spreadsheet with an .xml extension, it is a specific request document Tally's import engine understands. Each transaction becomes a VOUCHER node, and each voucher carries its own ledger entries so the import posts as real accounting, not raw rows.

Because each voucher is self-contained and typed, Tally validates and posts it the same way it would a voucher you keyed by hand. If a date or voucher type were malformed, Tally would reject the line, which is exactly why the converter normalises both before writing the file. The full import walkthrough lives in how to import bank statements into Tally.

Tally XML versus TDL, Excel templates, and ODBC

Tally XML is the most portable way to get transactions in because it needs nothing installed. The alternatives each carry friction that XML import avoids.

For a single statement or a monthly batch, XML import wins on simplicity: download the file, open the import dialog, done. If you would rather have plain rows to manipulate before posting, the Excel converter gives you a spreadsheet instead, and the main Tally converter covers the end-to-end voucher workflow including ledger mapping.

How the import dialog reads the file, step by step

It helps to know what Tally does with the file once you point the import dialog at it, because that explains why each formatting rule matters. Tally treats the XML as a request: it reads the action in the header, walks each TALLYMESSAGE in order, and tries to create the VOUCHER it finds inside.

For each voucher, Tally checks that the voucher type exists, that the date parses, and that the ledger entries balance and reference real ledgers. If all three hold, it posts the voucher; if any fail, that line is rejected and Tally reports it in the import log. This is why the converter is strict about three things up front, valid Payment and Receipt types, YYYYMMDD dates, and balanced legs, so the import log comes back clean instead of listing skipped lines. After import, Tally shows a count of vouchers added; that number should match the transaction count you saw in the preview, which is your fastest sanity check that nothing was dropped.

Because the file is processed top to bottom, the vouchers post in statement order, so your day book reads in the same sequence as the original statement. That ordering also means the running balance you reconcile against lines up date by date, making it easy to spot a single missing or duplicated entry.

Why the XML route beats retyping or copy-paste

The alternative to a structured XML file is either re-keying every voucher or pasting rows into a template, and both lose information the XML keeps. Retyping discards nothing technically but costs time and introduces errors; template paste is faster but flattens the data.

A spreadsheet template typically captures date, amount and a description, then relies on a macro to guess the voucher type and ledger. The XML file the converter builds instead encodes the voucher type explicitly per line, escapes the narration so special characters survive, and formats the date so Tally never rejects it. The result is that an XML import is reproducible: the same statement always produces the same vouchers, which matters when an auditor asks how a figure got into the books. If you do prefer a manual review pass, convert to a sheet with the CSV converter first, check it, then export Tally XML for the actual posting, you get the review step without giving up the clean import.

Handling several statements, banks or companies

The XML file is portable, which makes multi-account and multi-company work straightforward. One file imports into whichever company you open the import dialog from, so the same workflow scales from a single account to a full client roster.

If you keep more than one bank account, convert each statement separately and import each file against its matching bank ledger, keeping one file per account avoids mixing transactions and makes the per-account reconciliation clean. For a practice handling several companies, the routine is identical per company: open the company in Tally, import that company's statement file, reclassify. Because the converter names the bank ledger in the file, you can tell at a glance which account a file belongs to before importing it into the wrong books. Across HDFC, SBI, ICICI, Axis and Kotak the column layouts differ, but the converter detects each and still emits the same standard voucher structure, so your downstream import process never changes from one bank to the next.

For a busy close, convert the whole month for every account in a batch, then import them in sequence. Each import posts in statement order and reports its own voucher count, so you can verify each account independently rather than untangling one giant file. The walkthrough at how to import bank statements into Tally covers the dialog options that matter when you import file after file.

From statement to a clean import file in seconds

Upload the PDF above, confirm the preview reads your debits and credits correctly, choose Tally XML, and download a well-formed voucher file. Create the bank ledger in your company if it is not there yet, then import through Gateway of Tally and reclassify the holding-ledger legs to your real ledgers. The voucher count Tally reports after import should match the preview, which is your one-glance confirmation that nothing was dropped. For ongoing or multi-client work, credit packs keep the per-file cost low; the first five pages each month are free on the free converter.