TallyPrime vs Tally.ERP 9: how importing bank entries differs

Tally.ERP 9 and TallyPrime look and feel different, but they share the way vouchers are described for import: Tally XML. That's why a well-formed voucher file is the safest way to move bank entries into books, whichever version the client has.

At a glance

The XML route works on both

A voucher file that follows Tally's XML format, with an envelope, an Import Data request and one VOUCHER per entry, imports into Tally.ERP 9 and into every TallyPrime release. The rules don't change between versions:

• Every ledger and voucher type named in the file must already exist in the company, spelled the same way.
• Dates must fall inside the company's books period.
• Debits carry a negative amount, credits a positive one (see Tally XML for bank vouchers).
• Each file should be imported once. A second import duplicates the vouchers in either version.

Importing in Tally.ERP 9

1. Take a backup of the company.
2. Open the company, go to Gateway of Tally › Import Data › Vouchers (shown as Import of Data in some releases).
3. Enter the file name. If the XML isn't in the Tally installation folder, type the full path.
4. Set behaviour for duplicates if asked, and import.
5. Open Tally.imp in the Tally installation folder to see what was imported and what was rejected.
6. Check the bank ledger's closing balance against the statement.

Tally's Tally.ERP 9 help on importing vouchers covers the screen in detail.

Importing in TallyPrime

1. Open the company and take the backup the import screen offers.
2. Press Alt+O (Import) › Transactions.
3. Choose the XML file and import.
4. Read the import summary, then check the Day Book and the bank ledger balance.

Our TallyPrime import guide has the full routine and the common errors.

Excel import in TallyPrime 4.0 and later

From Release 4.0, TallyPrime can import masters and vouchers straight from Excel (release notes). You build a mapping template that tells Tally which column holds the voucher type, date, voucher number, ledger and amount, save it, and reuse it for files with the same layout.

Excel import is convenient when a client hands you a ready voucher sheet. For statements, XML stays simpler: the ledgers and voucher types are already in the file, and the same file works for clients on Tally.ERP 9 and older TallyPrime releases.

Bank reconciliation in each version

Both versions reconcile by bank date, and both can match imported statements automatically for supported banks. Tally.ERP 9 added auto bank reconciliation in its later releases; TallyPrime carries it forward with Alt+O › Bank Statement and newer banking features. The routine is in bank reconciliation in TallyPrime; on Tally.ERP 9 the screens differ, but the idea of entering bank dates and clearing the differences is the same.

Should clients still on Tally.ERP 9 move?

That's the client's decision, but these are the facts to give them:

• Tally says Tally.ERP 9 is not being discontinued and will keep working, but TSS renewal for it ended on 16 August 2026.
• Upgrade terms depend on the licence's TSS history. Tally's upgrade page has an eligibility check by serial number.
• New import and banking features, such as Excel import and Docs by Ira, arrive only in TallyPrime.
• Tally uses the same licensing system for both, so the existing licence works with TallyPrime.

Running a mixed client list

1. Note each client's Tally version in your client list, and the release for TallyPrime clients.
2. Use XML vouchers as the default for bank entries; it works on every version.
3. Keep one test company per version in the office for checking new files.
4. Agree with each client who imports: you, or their accountant on their machine.

One file for both, with FileKey

FileKey's bank statement export produces Tally XML vouchers with balanced debit and credit pairs that import into TallyPrime and Tally.ERP 9. Convert the statement PDF, set ledgers and the bank ledger name, choose Payment & Receipt or Contra vouchers, and download one file. For GSTR-1 sales entries, FileKey's XML settings let you pick each client's Tally version. See the bank statement to Tally converter.

Frequently asked questions

Written by the FileKey Team

FileKey builds the tools CA firms use for e-commerce GSTR-1 and bank statement conversion. We write these guides from the questions accountants and sellers ask us every filing month. Spotted something out of date? Write to [email protected] and we will fix it. More about FileKey.