Convert a Bank Statement PDF for Tally

A bank statement PDF becomes Tally data by reading every posted transaction and writing it as a voucher Tally can import: each debit becomes a Payment voucher and each credit becomes a Receipt voucher, with the date and narration preserved. You upload the PDF above, confirm the preview, download a Tally XML file, and import it through Gateway of Tally so the entries post against your bank ledger. No more typing a hundred lines by hand at month end.

Why hand-keying vouchers is the slowest part of your close

Manual voucher entry is where bank reconciliation goes to die. A single current account can run 80 to 300 lines a month, and each one is a fresh chance to fumble a date, mistype an amount, or pick the wrong voucher type. The converter removes that step entirely: it reads the statement table the bank already printed and turns it into structured vouchers, so you move straight to ledger allocation and reconciliation.

The classifier is built around how Indian statements actually print. A withdrawal column entry, a "Dr" flag, or a debit amount maps to a Payment voucher. A deposit, a "Cr" flag, or a credit amount maps to a Receipt voucher. UPI, NEFT, IMPS, RTGS and cheque references stay attached to the narration so you can still see what each line was when you allocate it to a party or expense ledger inside Tally.

How debits and credits become Tally voucher types

Tally does not have a generic "transaction", every line has to be a specific voucher type posted against specific ledgers. The converter makes that mapping explicit so the import is clean.

The opposite leg of each voucher posts to a holding ledger by default so nothing imports half-formed. You then reclassify lines to the correct expense, income or party ledgers in Tally, far faster than typing every voucher from scratch. For a step-by-step walkthrough with screenshots of the import dialog, see how to import bank statements into Tally.

Tally Prime and Tally ERP 9, both import the same file

The Tally XML voucher format works across both generations of Tally, so the same downloaded file imports whether your office is on the current Tally Prime or still on the older ERP 9. Only the menu path differs.

One prerequisite in both: the bank ledger named in the file has to exist in your company first. Create the ledger under Bank Accounts, then import, Tally posts each voucher against it. .

Allocating UPI, NEFT and cheque entries after import

The import gets the vouchers into Tally; the second half of the job is moving each one off the holding ledger onto its real destination. This is where the preserved narration earns its keep, because the reference codes Indian banks print tell you exactly what each line was.

For a UPI debit, the narration usually carries the payee's VPA, something like a name-at-bank handle, which you can match to a supplier or expense ledger. NEFT and RTGS lines carry a UTR number you can cross-check against the beneficiary's invoice. Cheque payments print the instrument number, so you can tie the voucher to the cheque register. Inside Tally you open each imported voucher, replace the holding ledger leg with the correct party, expense or income ledger, and save. Because the date, amount and voucher type are already correct, you are only choosing a ledger, not re-keying the line.

A practical workflow for a busy account: import the whole month in one pass, then sort the vouchers by narration so all the recurring UPI payees, salary credits, and standing instructions group together. You can reclassify a batch of identical payees far faster than walking the statement top to bottom. Bank charges and the GST levied on them are the lines people miss most often, they import as Payment vouchers against the holding ledger, and you reallocate them to a Bank Charges ledger and an Input GST ledger so your tax credit is captured.

Getting your bank ledger ready before the first import

One setup step makes every future import smoother: have the bank ledger in place and named consistently. Tally posts each voucher against the bank ledger referenced in the file, so the ledger must exist under the Bank Accounts group in your company before you import.

Create the ledger once, for example a current account at HDFC, SBI, ICICI, Axis or Kotak, and keep the name stable month to month so repeated imports always land in the same place. If you keep books for several companies, each company needs its own bank ledger created in its own books; the voucher file itself is company-agnostic and posts wherever you import it. After the first clean import, the routine drops to three actions a month: convert the statement, import the XML, reclassify the holding-ledger legs. That is the difference between a ten-minute reconciliation and an afternoon of data entry.

If you would rather see the columns before they become vouchers, convert the same statement to a spreadsheet first with the Excel converter, eyeball the totals against the statement's closing balance, then come back and export Tally XML once you trust the read.

The fastest path from PDF to posted vouchers

Drop the statement on the tool above, scan the preview to confirm debits and credits read correctly, export Tally XML, and import through Gateway of Tally. Create your bank ledger first if it does not exist, then reclassify the holding-ledger legs to real expense and party ledgers. For accountants closing many clients each month, credit packs keep the per-statement cost low while everything stays in the browser and nothing is stored. Start free with five pages a month on the free converter.