How to Import a Bank Statement into Tally Prime

It is the last week of the month. You have a folder of client bank statements, each one a PDF, and a deadline. Most of the work is not thinking. It is typing. Date, narration, amount, ledger, repeat, for a few hundred rows. This guide walks through how to get a bank statement into Tally the right way, where people usually go wrong, and how to cut the typing out of the job completely.

Two ways to get a bank statement into Tally

There are really only two options, and the right one depends on how many transactions you are dealing with.

1. Manual voucher entry

You open the bank statement on one screen and Tally on the other, then create a Payment or Receipt voucher for each line. It works, and for a statement with ten or fifteen transactions it is perfectly fine. For a busy current account with three hundred rows, it is a few hours you will not get back, and every row is a chance to fat finger an amount.

2. XML import

Tally reads a standard XML file and creates all the vouchers in one pass. The catch is that Tally does not read a PDF. You need the statement converted into Tally's XML format first, with the debits and credits already mapped. Once you have that file, the import itself takes seconds. This is the route that scales, and it is what the rest of this guide focuses on.

Before you start: get your ledgers right

Most failed imports are not import problems. They are ledger problems. Five minutes of setup here saves a lot of cleanup later. Check that you have:

• The correct bank ledger created under Bank Accounts, matching the account the statement belongs to.
• Party ledgers for the vendors and customers that show up often, so postings land in the right place instead of a Suspense account.
• The right company and financial year open, so vouchers do not post to the wrong period.
• A backup, taken before any bulk import. This is the one habit that turns a bad import from a disaster into a five minute redo.

Step by step: importing a bank statement as XML

These steps assume you already have a Tally compatible XML file for the statement. If you do not, skip to the section on converting the PDF below, then come back here.

1. Open Tally Prime and load the company the statement belongs to. Confirm the financial year is correct.
2. Go to Gateway of Tally, then Import, then Vouchers. In Tally ERP 9 the path is Gateway of Tally, then Import Data, then Vouchers.
3. Browse to your XML file and select it. Tally shows the file path and asks you to confirm the behaviour for existing entries.
4. Choose how to handle duplicates. For a fresh statement, you usually want to add new vouchers. If you are re-importing a corrected file, remove the earlier batch first so you do not double up.
5. Run the import. Tally posts every Payment and Receipt voucher and shows a count of what came in.
6. Open the Bank Book and scan the imported vouchers against the statement. Check the opening and closing balance line up.

The debit and credit mapping that trips people up

This is where good conversions earn their keep. A bank statement is written from the bank's point of view, not yours. When the bank says debit, money left your account. When it says credit, money came in. In Tally the posting has to reflect your books, which means:

• A withdrawal on the statement becomes a Payment voucher, crediting the bank ledger.
• A deposit on the statement becomes a Receipt voucher, debiting the bank ledger.
• The other side of each entry needs a sensible ledger, not a catch all, or your reports will be useless at review time.

If a converter gets this backwards, every figure in the bank account flips sign, and you will spend longer fixing it than you would have spent typing. So when you evaluate any tool, the debit and credit mapping is the first thing to test, not the file formats it claims to support.

Common import errors and how to fix them

Ledger not found

Tally refuses an entry because a ledger named in the XML does not exist in the company. Create the missing ledger, or adjust the file to point at a ledger you already have, then re-import.

Date out of range

The voucher date falls outside the open financial year. Either the year is set wrong in Tally, or the statement spans a year end. Open the correct period and try again.

Duplicate vouchers

You imported the same statement twice. Filter the Bank Book by the import date, delete the duplicate batch, and reconcile. This is exactly why the pre import backup matters.

For the official reference on the import behaviour and any version specific differences, see Tally's help documentation.

Reconciling after import

Importing vouchers is not the same as reconciling. Once the entries are in, open the bank reconciliation, set the bank dates against each voucher, and confirm the reconciled balance matches the closing balance on the statement. If the two agree, the import was clean. If they do not, the difference usually points you straight to a missed or doubled row.

Doing it in minutes instead of hours

The slow part of all of this is turning a PDF into a correctly mapped XML file. That is the step worth automating. StmtSnap reads the bank statement PDF and produces a bank statement to Tally XML file with the Payment and Receipt vouchers already mapped, so the only thing left for you to do is the import and the reconcile. It handles Indian statement quirks like UPI narrations and multi line rows, and it generates an Excel copy at the same time if you want to eyeball the data first.

If you work across banks, the bank specific guides walk through the exact columns each one uses, for example HDFC, SBI and ICICI.