Tally ERP 9 Bank Statement Import

Every way to import a bank statement into Tally ERP 9, and the fastest one when your bank gives you only a PDF: the converter turns it into a clean CSV, Excel or Tally XML file, so you can reconcile or post vouchers without manual entry. Free to try, online, no installation.

PDF (MAX. 10MB)

4.7/5

Tally-Ready File: Tally ERP 9 cannot read a PDF. The converter turns your PDF into a clean CSV or Excel file for Bank Reconciliation, or a Tally XML file for voucher import, one transaction per row, with the dates and amounts Tally expects.
Free & Online, No Install: This tool to prepare a bank statement for Tally ERP 9 runs entirely online, free to try with no account and no card. There is nothing to install and it works the same on Windows, Mac, and Chromebook.
CSV, Excel or Tally XML: Amounts are clean, dates are consistent, and payment modes like NEFT, RTGS, IMPS and UPI are kept in the narration, so reconciliation and voucher posting in Tally ERP 9 run without manual fixes.

PDF to a Tally ERP 9-ready file

Bank statement PDF converted to a clean CSV, Excel or Tally XML file for Tally ERP 9 import — Left: raw PDF Tally ERP 9 cannot read. Right: clean CSV, Excel or Tally XML, ready to reconcile or post.

How it works

Upload a PDF bank statement to import it into Tally ERP 9 — Drag and drop a PDF from SBI, HDFC, ICICI, Axis, Kotak or any bank, scanned files supported.

Transactions converted into a clean CSV, Excel or Tally XML file — Clean columns, consistent dates, debit and credit handled, payment modes kept in narration.

Import the file into Tally ERP 9 for reconciliation or as XML vouchers — Reconciliation: Banking, Bank Reconciliation, Alt+B. Vouchers: Import Data, Transactions.

How Do You Import a Bank Statement into Tally ERP 9?

Tally ERP 9 gives you two import routes. For reconciliation, go to Gateway of Tally then Banking then Bank Reconciliation, select the bank ledger, and press Alt+B to import an Excel, MT940 or CSV file, though this works only for banks pre-configured for auto reconciliation and needs a Tally.NET subscription. For creating vouchers, use Import Data then Transactions with a Tally XML file, which works for any bank and gives full control. The catch: Tally ERP 9 cannot read a PDF at all, and most banks hand you only a PDF. So the first step is always to convert that PDF into a file Tally accepts. This converter does exactly that. It reads your PDF statement and returns a clean CSV or Excel file for reconciliation, or a Tally XML file for voucher import, ready to bring into Tally ERP 9.

Upload any PDF bank or credit-card statement and the converter returns a file Tally ERP 9 accepts. Amounts are written cleanly with debit and credit handled the way Tally expects, dates are consistent, and Indian payment modes like NEFT, RTGS, IMPS and UPI are preserved in the narration so you can identify transaction types. Because everything happens online, there is nothing to install. You can prepare a bank statement for Tally ERP 9 in seconds, free to try, whether your statement is one page or eighty, current or from prior years, typed or scanned, from SBI, HDFC, ICICI, Axis, Kotak or any other bank.

Why Convert the PDF Before Importing into Tally ERP 9?

Tally ERP 9 cannot read a PDF at all
Tally ERP 9 imports Excel, MT940 or CSV for Bank Reconciliation, and XML for vouchers, but not PDF, which is just an image of your numbers. Since most banks hand you only a PDF, this converter produces the clean CSV, Excel or XML file Tally reads, so you skip typing every transaction by hand.

One file for reconciliation or voucher posting
Bank Reconciliation import matches a bank file against existing vouchers, while XML import creates the vouchers themselves. The converter can produce either: a clean CSV or Excel for the Alt+B reconciliation route, or a Tally XML for the Import Data route, so you use whichever your task needs.

Clean columns Tally reads without a format error
Tally ERP 9 shows a Not a valid format error when a file is edited or structured wrong. The converter outputs clean, consistent columns, Date, Narration, Debit and Credit, in the order Tally expects, so the import wizard reads it without that error and the mapping is quick.

Dates and debit-credit the way Tally expects
For XML vouchers Tally needs dates in the correct format and balanced amounts, with debit and credit handled correctly. The converter writes dates consistently and separates debit and credit properly, so vouchers post cleanly instead of failing validation on dates or amounts.

Payment modes kept for transaction types
Indian bank PDFs put the payment mode in the narration, NEFT, RTGS, IMPS, UPI, CR or DR. The converter preserves these in the narration field, so in Tally ERP 9 you can tell payments from receipts and identify transaction types instead of losing that detail.

Works for any bank and historical periods
Tally's built-in reconciliation only supports pre-configured banks, and feeds do not reach old periods. The converter reads any bank's layout, from SBI, HDFC, ICICI, Axis and Kotak to cooperative and overseas banks, across any date range, and scanned statements are handled with OCR, so you can import old statements for year-end or audit.

What This Tool for Tally ERP 9 Bank Statement Import Does

1. CSV or Excel for Bank Reconciliation

The converter produces a clean CSV or Excel file for the Bank Reconciliation route, imported with Alt+B from Gateway of Tally, Banking, Bank Reconciliation. One transaction per row, so Tally can match entries against your vouchers.

2. Tally XML for Voucher Import

Need to create vouchers, not just reconcile? The converter outputs a Tally XML file for the Import Data, Transactions route, structured to Tally's schema, so payments and receipts post as vouchers without manual entry.

3. Clean Columns, No Not-a-Valid-Format Error

Date, Narration, Debit and Credit come out clean and in the order Tally expects, so the import wizard reads the file and you avoid the Not a valid format error that a hand-edited export triggers.

4. Payment Modes in the Narration

NEFT, RTGS, IMPS, UPI and CR or DR markers are preserved in the narration, so you can identify transaction types and classify payments and receipts correctly once the data is in Tally ERP 9.

5. CSV, Excel or XML, Your Choice

Download a CSV or Excel for reconciliation, or a Tally XML for voucher posting, whichever your workflow needs. All carry clean Date, Narration, and amount data, one transaction per row.

Reconciliation vs XML voucher import

Tally ERP 9 import routes compared: Bank Reconciliation with CSV or Excel, and XML voucher import — Reconciliation matches a CSV or Excel; XML import creates vouchers. The converter produces both.

Clean CSV columns mapping into the Tally ERP 9 Bank Reconciliation import wizard — Date, Narration, Debit and Credit in the order Tally expects, so no Not-a-valid-format error.

Tally ERP 9 Bank Statement Import: Reconciliation or XML Vouchers, and Why the File Decides

Most people who want to import a bank statement into Tally ERP 9 discover it offers two very different routes. The first is Bank Reconciliation: from Gateway of Tally then Banking then Bank Reconciliation, you select the bank ledger and press Alt+B to import an Excel, MT940 or CSV file, and Tally matches those rows against vouchers you have already posted. But this route only works for banks pre-configured for auto reconciliation and needs a Tally.NET subscription, and it reconciles rather than creates entries. The second route is XML voucher import through Import Data then Transactions, which posts the transactions as vouchers themselves, works for any bank, and gives full control, but demands a file that follows Tally's schema with ledger names matching your company exactly. Both routes share one hard requirement: Tally ERP 9 cannot read a PDF at all, and your bank almost always gives you a PDF. A bank statement PDF is an image of your numbers, not structured data, so it has to be converted first. This page exists because the file is where Tally imports actually succeed or fail. When the converter turns your PDF into a clean CSV or Excel file, columns in the order Tally expects, you avoid the Not a valid format error and reconcile in minutes. When you need vouchers, it produces Tally XML with dates, debit and credit, and the payment mode kept in the narration, so NEFT, RTGS, IMPS and UPI entries post correctly. For CAs handling many client statements, or anyone bringing in months of history for year-end or audit, that difference compounds. It is the gap between a file that imports on the first try and hours of manual entry. The converter is engineered to produce the former, and it is free to try so you can verify the file on your own statement before importing.

Frequently Asked Questions

1. Is this tool for Tally ERP 9 bank statement import free?

It is free to try: you can convert up to 6 statements with no account and no card to check the Tally file for yourself. Create a free account and you get 10 free pages per month. Paid plans are available only if you need higher volume, and most one-off conversions cost nothing.

2. Can I import a PDF bank statement into Tally ERP 9?

No. Tally ERP 9 imports Excel, MT940 or CSV for reconciliation and XML for vouchers, but not PDF. Since most banks provide only a PDF, you convert it first. This converter turns any bank's PDF into a clean CSV, Excel or Tally XML file, ready to import.

3. How do I import the file for reconciliation in Tally ERP 9?

Go to Gateway of Tally then Banking then Bank Reconciliation, select the bank ledger, and press Alt+B to import. Choose the file format, Excel or CSV, browse to the converted file, and confirm. Tally auto-matches entries by date and amount, and you reconcile the rest manually.

4. How do I import XML vouchers into Tally ERP 9?

Use Import Data then Transactions, select the XML file format, and point to the Tally XML from the converter. Tally posts the transactions as vouchers. Make sure the bank ledger name matches your Tally company exactly, or enable creating ledgers while importing.

5. Why does Tally ERP 9 show Not a valid format on import?

That error appears when the file is edited, has the wrong structure, or the columns are out of order. The converter outputs clean, consistent columns in the order Tally expects, so the import reads without the Not a valid format error.

6. Can it import scanned or old statements for audit?

Yes. Scanned and photographed statements are read with OCR, and there is no date-range limit. This is how accountants import six to twelve months of old statements into Tally ERP 9 for year-end closing, tax filing, or audit preparation.

7. Which is better, reconciliation import or XML vouchers?

Use reconciliation import (CSV or Excel) when you only need to match a bank file against existing vouchers. Use XML voucher import when you need Tally to create the vouchers, or when your bank is not pre-configured for Tally's built-in reconciliation. The converter produces both.

8. Which banks work, and is my Tally data secure?

It detects layouts automatically for SBI, HDFC, ICICI, Axis, Kotak, PNB and hundreds of other Indian and international banks, so it works whatever your bank. Uploads are protected and removed after conversion, and no account is required to try it, so your data is not stored or shared.