🏦 Tally Prime · XML Import · BSI Feature · HDFC · SBI · ICICI · Free

How to Import Bank Statement in Tally Prime

Tally Prime cannot open PDF files directly. This guide covers both methods: XML voucher import (works in all versions) and Tally Prime's built-in Bank Statement Import (BSI) for reconciliation. Free converter included.

🏦 Convert for Tally Prime →
📄→🏦

Convert Bank Statement PDF to Tally XML

Free · No signup · Tally Prime compatible output

Choose PDF File

Two Methods to Import Bank Statement in Tally Prime

Choose the method based on your goal: creating vouchers (Method 1) or bank reconciliation (Method 2).

Method 1: XML Voucher Import (All Tally Prime Versions)

  1. Convert bank statement PDF to Tally XML using our free converter above
  2. Open your Tally Prime company
  3. Ensure bank ledger (e.g. HDFC Bank A/C) exists under Bank Accounts group
  4. Press Alt+O or go to Import from the menu
  5. Select Vouchers
  6. Navigate to and select the downloaded .xml file
  7. Review the import preview and press Import
  8. Verify: number of vouchers imported = number of statement rows
Creates Bank Payment and Bank Receipt vouchers in Tally. Best for recording transactions in your books.

Method 2: Bank Statement Import / BSI (Tally Prime 3.0+)

  1. Convert bank statement PDF to Excel using our free converter
  2. Save as CSV with columns: Date, Description, Debit, Credit
  3. In Tally Prime: GatewayBanking
  4. Select Bank Reconciliation
  5. Select the bank account ledger
  6. Press Alt+B (Import Bank Statement)
  7. Select your CSV file
  8. Tally matches bank transactions against existing ledger entries
Used for reconciliation — matches bank transactions to existing Tally entries. Does not create new vouchers. Requires Tally Prime 3.0 or later.

Troubleshooting: Why Import Fails in Tally Prime

Common reasons an XML import shows zero vouchers or an error in Tally Prime.

ProblemLikely CauseFix
Zero vouchers importedBank ledger name in XML doesn't match Tally ledger exactlyCheck ledger name in Tally (Gateway → Chart of Accounts) and ensure it matches exactly, including capitalization
"Invalid data" errorXML encoding issue (non-UTF-8 characters in narration)Check the bank statement narrations for special characters. Our converter handles this — if using another tool, ensure UTF-8 encoding
Wrong financial yearStatement dates fall outside the active Tally company yearChange the active period in Tally to match the statement date range (Alt+F2 to change period)
Vouchers created but wrong amountsIndian comma-formatting not removed (1,23,456 treated as 1.23)Our converter removes Indian formatting automatically. If using another method, ensure amounts are plain numbers before converting to XML
BSI (CSV) import not availableTally Prime version older than 3.0Update Tally Prime to version 3.0 or later, or use Method 1 (XML voucher import) instead

Frequently Asked Questions

Method 1 (XML, all versions): Convert your bank statement PDF to Tally XML using our free converter → Gateway → Alt+O (Import) → Vouchers → select XML file → confirm. Method 2 (BSI, Tally Prime 3.0+): Banking → Bank Reconciliation → Alt+B (Import Bank Statement) → select CSV file in Tally's required format.
Tally Prime accepts XML files (TALLYMESSAGE/VOUCHER format) for voucher import via Gateway → Import → Vouchers. Tally Prime 3.0+ also accepts CSV files with Date, Description, Debit, Credit columns via the Bank Statement Import (BSI) feature in Bank Reconciliation.
No — Tally Prime cannot import PDF files. You must first convert the PDF to XML (using our free converter for Method 1) or to CSV (for Method 2 / BSI), then import the converted file into Tally Prime.
XML voucher import (Method 1) creates actual vouchers in Tally from bank transactions — used when you want to record bank activity in your books as payment/receipt entries. BSI (Bank Statement Import, Method 2) is for bank reconciliation — it matches imported bank transactions against existing Tally ledger entries without creating new vouchers. Method 1 is for bookkeeping; Method 2 is for reconciliation.
The most common cause is a ledger name mismatch — the bank ledger name referenced in the XML must match exactly the ledger name in your Tally company, including capitalization and spacing. Other causes: the financial year active in Tally does not include the statement dates (press Alt+F2 to change period), or the XML file has an encoding issue.
Yes — completely free. No signup, no credit card, no daily limits. The converter produces Tally-compatible XML from your bank statement PDF at zero cost.

Related Tally Tools