Complete Guide to Bank Statement Import in Tally

Bank reconciliation is one of the most time-consuming tasks in accounting. Every month you download bank statements, open Tally, and start keying in hundreds of transactions — matching each debit and credit to the right ledger, choosing the correct voucher type, and double-checking amounts. For a business with two or three bank accounts and 300 to 500 transactions per month, this process alone can consume an entire working day.

TallyConnects eliminates most of that effort. You upload your bank statement file, the software detects the bank format automatically, matches narrations to Tally ledgers, assigns voucher types, and posts everything to Tally in one go. This guide covers the complete workflow.

Step 1: Download Your Bank Statement

Log in to your bank’s net banking portal and download the statement for the period you want to import. Most banks offer multiple formats:

• Excel (.xlsx / .xls) — the most straightforward format. Columns are already separated.
• CSV (.csv) — works well but watch out for comma-separated amounts that may need cleanup.
• PDF — many banks default to PDF. TallyConnects can parse these directly without converting.

Recommendation: If your bank offers Excel, prefer that. It requires the least processing. If only PDF is available, TallyConnects handles it, but Excel eliminates any chance of parsing ambiguity.

Step 2: Load the Statement into TallyConnects

Open TallyConnects and go to the Bank Statement Import section. Click Select File and choose your downloaded statement. The software immediately analyses the file and attempts to identify the bank.

Auto-Detection of Bank Format

TallyConnects maintains a library of statement formats for major Indian banks. When you load a file, it checks header patterns, column positions, and formatting cues to determine the bank. For example:

• HDFC Bank statements typically have columns: Date, Narration, Chq/Ref No, Value Date, Withdrawal Amt, Deposit Amt, Closing Balance.
• SBI uses: Txn Date, Value Date, Description, Ref No/Cheque No, Debit, Credit, Balance.
• ICICI Bank often includes: Transaction Date, Value Date, Transaction Remarks, Cheque Number, Debit Amount, Credit Amount, Balance.
• Axis Bank and Kotak Mahindra have their own distinct layouts that the engine recognises.

If auto-detection does not identify the bank (for example, a smaller regional bank), you can manually select the bank or map columns yourself using the standard column-mapping interface.

Step 3: Review Narration-to-Ledger Matching

This is the core intelligence of the bank import feature. Every bank transaction has a narration or description field that contains clues about who the money went to or came from. TallyConnects reads these narrations and tries to match them to ledgers that already exist in your Tally company.

The matching logic considers several signals:

• Party name in narration — NEFT, RTGS, and IMPS transactions often include the beneficiary name.
• UPI ID — UPI transactions may contain the merchant or individual name.
• Cheque details — cheque-based payments can be matched if the cheque register is maintained in Tally.
• Historical patterns — if you imported previous months, TallyConnects remembers which narrations you mapped to which ledgers and applies the same mapping.

Each row shows the suggested ledger in a dropdown. Review the suggestions and correct any that are wrong. Over time, the matching accuracy improves as the system learns from your corrections.

Step 4: Auto-Assignment of Voucher Types

TallyConnects assigns voucher types based on the direction of the transaction:

You can override the voucher type for any row. For instance, if a bank charge is categorised as Payment but you want it as a Journal Entry, simply change it in the dropdown.

Step 5: Validate and Import

Click Validate to run the pre-import checks. TallyConnects verifies that every row has a valid date, a mapped ledger, a non-zero amount, and the correct voucher type. Rows with issues are highlighted.

Once validation passes, click Import to Tally. The transactions are posted to Tally Prime as bank vouchers under the bank ledger you selected. A summary shows how many were successful and any that failed.

Handling PDF Bank Statements

PDF statements require an extra parsing step, but TallyConnects handles it transparently. When you select a PDF file, the built-in parser:

1. Extracts text from every page of the PDF.
2. Identifies the table structure (column positions, header row).
3. Separates the data into rows and columns, handling page breaks and wrapped narrations.
4. Presents the extracted data in the same preview grid as Excel imports.

For password-protected PDF statements, you will be prompted to enter the password (usually your account number or a combination of name and date of birth).

Tips for Accurate Bank Imports

• Create ledgers for frequent counterparties before importing. The more ledgers exist in Tally, the better the narration matching works.
• Import month by month in chronological order so that running balances in Tally stay correct.
• Use the same bank ledger name in Tally as the one you select in TallyConnects to avoid mismatches.
• Review contra entries carefully. Transfers between your own bank accounts should not be double-posted if you import statements from both banks.

Frequently Asked Questions