Convert a Bank Statement to Tally (PDF to Excel/CSV Import)

The short version

Convert to Tally XML, not to Excel.

Tally Prime's Bank Statement import — the one built for reconciliation — does not accept Excel or CSV that was converted from a PDF. That is stated in Tally's own documentation, and it is a property of how the feature works rather than a bug you can format around.

Tally's voucher import does accept your data, because Tally XML carries its own meaning. That is the route to use.

Why Excel is refused and XML isn't

Tally's bank statement importer isn't a general spreadsheet reader. It matches your file against a stored layout for your specific bank — column order, header wording, the date format that bank uses in its own downloads. That is how it knows which column holds the debit without asking you. It supports 200+ banks this way.

A file converted from a PDF carries the right figures in a different shape. Columns in another order, headers worded differently, dates formatted differently. Tally checks the shape, doesn't recognise it, and declines. No converter can solve this, ours included — matching one bank's exact download layout would break the moment that bank changed it, and would have to be redone for every bank separately.

Tally XML sidesteps the problem completely. The XML says *this is a Receipt, this is the bank ledger, this is the amount, this is the date*. There is no layout to recognise because nothing has to be inferred.

Converting the statement

1. Upload your statement PDF to the Tally XML converter. Scanned statements and password-protected files both work — locked statements are unlocked in your browser, so the password never reaches a server, which matters because Indian banks usually build it from your PAN or date of birth.
2. Check the reconciliation result before you download. Opening balance plus credits minus debits has to equal the closing balance the bank printed. If it doesn't, you get told, and you can correct the figure in the table before exporting.
3. Download the Tally XML.

That check earns its keep here more than anywhere else. A dropped transaction in a spreadsheet is an annoyance. The same dropped transaction inside Tally is a wrong ledger balance you find weeks later during reconciliation.

Importing into Tally

Create any ledgers the statement references first — Gateway of Tally → Create → Ledger. A voucher naming a ledger that doesn't exist is skipped, and Tally will not create it for you.

Then:

1. Gateway of Tally → Alt+O (Import) → Vouchers
2. Give the path to the XML file
3. Choose Add rather than Overwrite
4. Check the imported and skipped counts

In Tally ERP 9 the same route is Gateway of Tally → Import Data → Vouchers. The XML schema is identical.

The full walkthrough, including what to do when vouchers are skipped, is in how to import a bank statement in Tally Prime.

When you should use Excel instead

If your bank's own portal offers Excel, CSV or MT940 downloads, use those with Tally's Bank Statement import (`Alt+O` → Bank Statement). It auto-creates vouchers *and* auto-reconciles them, which the voucher import doesn't do. It is the better route whenever it is available to you.

The XML route exists for the situation most Indian account holders are actually in: a PDF in your inbox and no portal download.

You can still reconcile afterwards — import the vouchers, then run Bank Reconciliation inside Tally against them.

Other formats

The converter also exports Excel, CSV, QBO, OFX, QIF, JSON and Xero/QuickBooks CSV from the same statement. If you need the figures for a CA, a loan file or a GST working alongside the Tally import, export both — the conversion is done once and every format comes from the same checked data.