Tally ERP 9 Bank Statement Import: Essential Checklist

Many clients still keep their books in Tally ERP 9, and their bank statements still need posting every month. Tally's help for Tally.ERP 9 describes importing vouchers from an XML file, so the job is to get the statement into that file and import it once, cleanly.
This guide follows Tally's own help for the import itself, then covers the preparation that keeps the bank ledger in step with the statement.
How Tally ERP 9 Imports Vouchers

Tally's help page on importing vouchers lists three reasons to import vouchers: data corruption or loss, migrating into a later release, and importing data from a third party. A voucher file built from a bank statement is the third case.
- Open the client's company.
- Go to Gateway of Tally, then Import Data, then Vouchers.
- In the Import Vouchers screen, enter the name of the XML file.
- Press Enter to import.
The help notes that the import location is the installation folder by default. If the file sits anywhere else, you must give its exact path, for example C:\Export_Files\XML\DayBook.xml.
Where to find the import log
After the import, open the Tally.imp file in the installation folder. Tally's help points to this file as the import log. Read it every time, even when the import seems to finish without a message.
Prepare the Company Before You Import
The import itself takes a minute. Most problems come from what happens before it. Run these checks first.
| Check | Why it matters |
|---|---|
| The right company is open | Open the client's company before you import, so the vouchers go into the right books. |
| A fresh backup exists | Tally's import FAQ recommends a backup before importing, so the data can be restored after an unintended import. |
| The ledgers the vouchers use exist | Tally's help says the company must hold the masters used in the transaction data. |
| The bank ledger name matches exactly | Every voucher points to the bank ledger by name. A different spelling sends entries to the wrong place or stops them. |
| The file has not been imported before | Tally's import FAQ warns that importing the same XML file again and again duplicates transactions. |
Match the opening balance first
Before importing a new month, compare the bank ledger's balance in the books with the opening balance printed on the statement. If they already differ, the import cannot fix it. The closing balances will still disagree, and the gap will be blamed on the new month.
Find the cause first. It is usually a missing entry from an earlier period, a voucher posted to the wrong bank ledger, or an earlier statement imported twice. Fix it, then import.
Keep a record of each import
For each client, note the file name, the statement period and the date you imported it. When a statement is reissued or corrected, that note stops the same month from going in twice.
A simple sheet per client is enough: one row per import, with the bank ledger name, the period covered, the file name and who imported it. When two people share a client, the sheet shows at a glance which months are already in the books.
Getting the Voucher File From a Bank PDF
The bank gives your client a PDF, and the books need vouchers in XML. Typing the statement into vouchers by hand is the slow route, and a skipped row can hide for weeks.
Leepik builds the file from the PDF. It reads a text-based bank statement and gives every row a suggested ledger. You confirm a party once, and it maps itself on later statements for that client. These rules stay per client, and anything Leepik cannot resolve goes to Suspense.
Before you export, Leepik checks the closing balance against the statement's own summary. It also checks that each debit or credit moves the balance the right way, and flags problems instead of dropping them. You can edit any cell without uploading the file again.
At export, you set the bank ledger name as it reads in the client's company, and pick a date range. The Tally XML voucher file carries the ledger masters inside, so missing ledgers are created on import. The same file works with Tally ERP 9 and TallyPrime. If you prefer a spreadsheet, a CSV file that opens in Excel is also available.
One limit matters: Leepik does not read scanned or photographed statements. Start from the text-based PDF your client downloads from net banking.
After the Import: Confirm the Bank Ledger
A finished import is not the same as a correct month. Before you move on, check three things.
- The log: Tally.imp shows what was imported and what was not. Fix anything it reports before posting more data.
- The closing balance: the bank ledger's closing balance for the period should match the closing balance on the statement.
- Suspense: any row that went to Suspense still needs a decision. Clear it now, while the month is fresh.
When the client moves to TallyPrime
The XML route carries over. In TallyPrime, the same kind of voucher file is imported with Alt+O (Import), then Transactions, as described in Tally's help on importing XML data. Our guide to the bank statement Tally import walks through those steps.
If some clients run TallyPrime and others run ERP 9, a voucher file that works in both keeps one routine for the whole practice.
Conclusion
Tally's help for Tally.ERP 9 describes importing vouchers from an XML file. Build a voucher XML file from the statement, check the company, backup, masters, bank ledger name and opening balance, then import it once through Gateway of Tally, Import Data, Vouchers. Read Tally.imp and confirm the closing balance before you close the month.
For more guides on bank statements, vouchers and Excel, browse the Leepik blog.
Tally and TallyPrime are trademarks of Tally Solutions Private Limited. Leepik is not affiliated with or endorsed by Tally Solutions.