Bank Statement to Tally XML Converter

Tally ERP 9 and its successor Tally Prime are the dominant accounting software platforms in India, used by millions of businesses ranging from sole proprietors to mid-size enterprises. Tally handles statutory compliance for GST, TDS, and Income Tax, making it the backbone of Indian bookkeeping.

Tally uses a proprietary XML format for bulk data import. This XML structure is built around the concept of vouchers, which are the fundamental unit of accounting in Tally. Every financial transaction in Tally is recorded as a voucher: Receipt vouchers for money coming in, Payment vouchers for money going out, Journal vouchers for internal transfers, and Contra vouchers for bank-to-cash movements.

The challenge Indian accountants face is that bank statements come as PDF files, but Tally requires structured XML vouchers for import. Manually entering hundreds of bank transactions into Tally is a time-consuming process that consumes hours of billable time during busy periods like GST filing deadlines and year-end closing. Converting PDF bank statements directly into Tally-compatible XML eliminates this manual data entry entirely.

Tally XML import files follow a specific hierarchical structure that the software expects. Understanding this structure helps accountants verify that the converted output will import correctly.

The outermost element is ENVELOPE, which wraps the entire import payload. Inside it, the HEADER section specifies the import type (IMPORTDATA) and the version. The BODY section contains IMPORTDATA with one or more REQUESTDATA blocks.

Each REQUESTDATA block contains a TALLYMESSAGE element, which in turn holds individual VOUCHER entries. A voucher entry includes the date (formatted as YYYYMMDD), the voucher type (Receipt or Payment), the voucher number, and a NARRATION field that carries the transaction description from the bank statement.

The critical part of each voucher is the ALLLEDGERENTRIES section. Tally uses double-entry accounting, so every voucher must have at least two ledger lines that balance to zero. For a bank payment of 5,000 rupees, one ALLLEDGERENTRIES line debits the expense ledger (e.g., Office Expenses) for 5,000, and the other credits the bank ledger (e.g., HDFC Bank Current Account) for 5,000. The ISDEEMEDPOSITIVE flag tells Tally which side is the debit and which is the credit.

FinanceConvert generates this exact structure from your PDF bank statement. Each transaction becomes a balanced voucher with the bank account as one leg and a configurable default ledger as the other leg.

Step 1: Download your bank statement as a digital PDF from your online banking portal. Indian banks like SBI, HDFC, ICICI, Axis, Kotak, and PNB all provide monthly statements in PDF format from their net banking platforms.

Step 2: Navigate to the Bank Statement to Tally converter on FinanceConvert and drop your PDF file into the upload zone.

Step 3: The AI-powered extraction engine identifies the transaction table within your PDF, detecting columns for date, narration, debit (withdrawal), credit (deposit), and closing balance. It handles the specific formats used by Indian banks, including DD/MM/YYYY dates and INR amount formatting.

Step 4: Each transaction is mapped into a Tally XML voucher. Withdrawals become Payment vouchers and deposits become Receipt vouchers. The bank narration from the statement populates the NARRATION field in each voucher.

Step 5: Download the generated XML file. The output is a complete Tally ENVELOPE document with properly structured IMPORTDATA, TALLYMESSAGE, and VOUCHER elements.

Step 6: Import into Tally. Open Tally Prime or Tally ERP 9, press Alt+H for Help, select Import Data, and point to the downloaded XML file. Tally will process each voucher and add it to your company data. Review the Day Book after import to verify all transactions are correctly recorded.

Tally enforces strict double-entry accounting. Every rupee that enters or leaves an account must be balanced by an equal and opposite entry in another account. This is the fundamental principle that makes Tally reliable for statutory compliance and audit.

When FinanceConvert generates a Payment voucher from a bank withdrawal, it creates two ALLLEDGERENTRIES lines. The first line debits the expense or payee ledger (the account where money is going) and the second line credits the bank ledger (the account where money is coming from). Both lines carry the same amount, ensuring the voucher is balanced.

For Receipt vouchers generated from bank deposits, the polarity is reversed: the bank ledger is debited (money coming in) and the income or party ledger is credited (the source of the money).

The ISDEEMEDPOSITIVE flag in each ALLLEDGERENTRIES line tells Tally how to interpret the amount. When ISDEEMEDPOSITIVE is Yes, the amount is treated as a debit in the context of the voucher type. When it is No, the amount is treated as a credit. This flag is essential for Tally to correctly post the entry to the right side of each ledger account.

After import, accountants can review each voucher in the Day Book and reassign the default contra ledger to the correct expense category, vendor account, or income head. This post-import categorization is a standard workflow in Indian accounting practices and is significantly faster than manual data entry of the original transactions.