How to Import Bank Statements into TallyPrime (All Formats)

To import bank statements into TallyPrime, your path depends on your bank and your file format. TallyPrime's Connected Banking feature supports native import from 145+ Indian banks, with automatic voucher creation and transaction reconciliation built in.

But TallyPrime cannot import PDF bank statements directly, nor can it accept CSV or Excel files converted from PDFs without proper structure. If your bank issues statements only as PDFs, or your bank is not among the supported institutions, you need to convert that statement into a clean, structured file before TallyPrime can work with it.

The distinction matters more each year. The Reserve Bank of India's Digital Payments Index reached 493.22 in March 2025, nearly five times the base value of 100 set in March 2018. That growth in digital payment volume translates directly into longer bank statements and more transactions to process.

How Connected Banking Imports Bank Statements into TallyPrime

Connected Banking is Tally Solutions' built-in feature in TallyPrime for pulling external bank statement data directly into your ledger. Rather than manual data entry, it gives you a structured interface to import transaction files from 145+ Indian banks, each with a pre-configured template that maps statement columns to TallyPrime's expected fields.

Supported File Formats

The formats TallyPrime accepts through Connected Banking depend on what your bank provides and what the pre-configured template for that bank expects:

CSV and TXT (the most common exports from Indian bank portals)
Excel (XLS/XLSX) for banks that offer spreadsheet downloads
XML for structured data feeds
MT940, the international SWIFT standard for bank statement files, used by banks that follow global messaging formats

Not every bank offers every format. Your import path is determined by the intersection of what your bank's portal can export and what TallyPrime's template for that bank is configured to read.

The Import Workflow

The actual process is straightforward. From within TallyPrime:

Open the Banking menu and select Bank Reconciliation or the import option for Connected Banking.
Select the bank ledger you want to import against.
Choose your bank name from the supported list. This loads the pre-configured template that tells TallyPrime how to parse your statement file.
Set the statement format and date range for the transactions you are importing.
Point TallyPrime to the downloaded statement file and import.

TallyPrime's official documentation covers each screen and field in detail. What matters here is understanding the logic: the pre-configured template does the heavy lifting of mapping your bank's column structure to TallyPrime's internal format, so you do not need to manually define which column is the debit amount, which is the credit, or where the transaction date sits. Once imported, transactions are staged against your chart of accounts and bank ledger for voucher creation and reconciliation, not automatically posted.

Bank Coverage and Its Limits

The 145+ supported banks cover the major names you would expect: SBI, HDFC, ICICI, Axis, Kotak, PNB, and most large private and public sector banks. Each has a tested import template. However, smaller cooperative banks, regional rural banks, and some district-level institutions may not appear in the supported list. If your bank is not listed, Connected Banking will not have a template to parse the statement, and you will need an alternative path to get that data into TallyPrime.

Turning Imported Statements into Vouchers and Reconciled Entries

After import, two TallyPrime features turn raw transaction data into posted accounting entries: auto-create vouchers and bank reconciliation.

Auto-Create Vouchers from Imported Transactions

Once a bank statement is imported, TallyPrime's auto-create vouchers feature can generate accounting entries directly from the transaction data. Instead of manually keying in each payment, receipt, or transfer, TallyPrime reads the imported rows and creates the corresponding voucher types: payment vouchers for debits, receipt vouchers for credits, contra vouchers for inter-bank transfers, and journal vouchers where needed.

This works through configurable rules. You define how TallyPrime should match imported transactions to specific voucher types and ledger accounts. For example, a recurring payment to a known vendor name can be mapped to the correct expense ledger and tagged as a payment voucher automatically. The more precisely you configure these rules, the fewer transactions require manual intervention.

In practice, a well-configured setup handles the bulk of routine transactions without edits. You review the auto-created vouchers, correct any that the rules could not confidently classify, and post them to the books. For firms processing statements with hundreds of monthly transactions, this cuts data entry time significantly.

Bank Reconciliation After Voucher Creation

With vouchers created, TallyPrime's bank reconciliation workflow lets you verify that your books match the bank's records. The reconciliation screen displays your bank ledger vouchers alongside the imported statement entries, allowing you to match them one-to-one.

During reconciliation, TallyPrime flags several conditions:

Matched entries where the voucher amount and date align with a bank statement row
Unmatched entries in your books that have no corresponding bank transaction (potentially erroneous or pending entries)
Outstanding transactions that the bank has recorded but your books have not yet captured
Amount mismatches where a voucher exists but the figures differ from the bank's record

This matching process surfaces discrepancies early, before they compound into month-end headaches. You can reconcile in batches or as statements arrive, depending on your workflow preference.

The accuracy of both auto-created vouchers and reconciliation matches depends directly on the quality of the imported file. Poorly structured data produces misclassified entries, failed matches, and manual cleanup that erases the time savings. The same principle applies whether you are importing bank statements into NetSuite or working in TallyPrime: cleaner source data means more reliable automation.

The Format Gap: Bank Statements TallyPrime Cannot Import

If you have tried to import a bank statement and hit a wall, the issue is almost certainly one of three format problems. Understanding which one applies to your situation will save you from repeated failed attempts.

TallyPrime cannot import PDF bank statements. This is the single most common blocker. Most Indian banks, whether you download statements from net banking portals, request them via email, or receive them from your branch, deliver them as PDF files. SBI, HDFC, ICICI, PNB, and nearly every other major bank defaults to PDF for downloadable statements. Connected Banking's import pathway does not read PDFs at all. There is no setting to enable it and no plugin that adds support. If your file ends in .pdf, TallyPrime will not process it.

The natural next step most users try is manual conversion: opening the PDF, copying the transaction table into Excel or a CSV file, and importing that. This does not work either. When you copy-paste from a PDF into a spreadsheet, the output carries formatting artifacts: merged cells, split rows where a single transaction spans two lines, date formats that don't match the expected template, amounts that paste as text rather than numbers, and column orders that differ from what TallyPrime expects. The result is either an outright import rejection or, worse, garbled data where transactions are misaligned, amounts land in wrong fields, or rows are silently dropped. A PDF bank statement to TallyPrime pipeline requires structured, clean conversion, not manual copy-paste.

The third limitation is unsupported banks. Connected Banking ships with pre-configured templates for 145+ banks, but India's banking system includes far more institutions than that. Cooperative banks, small finance banks, regional rural banks, payment banks, and international banks operating in India frequently fall outside the supported list. Even if you have a perfectly formatted CSV or Excel file from one of these banks, TallyPrime will not import it through Connected Banking. The import relies on bank-specific column mappings that define where the date, narration, debit, credit, and balance fields sit in the file. Without a matching template, the data has nowhere to go.

One detail that trips up experienced TallyPrime users: the general-purpose Excel and CSV import feature you may have used to bring in masters, stock items, or ledger data does not work for bank transactions. Bank statement import is handled exclusively through the Connected Banking pathway. There is no workaround through Gateway of Tally's standard import menu. Attempting it will either produce errors or import the data as something other than bankable voucher entries.

So the diagnostic is straightforward. You need an alternative conversion step before TallyPrime can use your data if any of these apply:

Your statement is a PDF (regardless of which bank issued it)
Your statement comes from a bank not on TallyPrime's supported list
Your file is a CSV or Excel sheet created by manually copying from a PDF

In each case, the raw file must be transformed into a clean, correctly structured format that matches the column mapping TallyPrime expects for your specific bank, or for a compatible bank template.

Converting PDF Bank Statements into TallyPrime-Ready Files

The PDF bank statement needs to become a structured CSV or Excel file before TallyPrime's Connected Banking import will accept it. The conversion must accurately separate transaction dates, descriptions, debit amounts, credit amounts, and running balances into clean, individual columns. Get that right, and TallyPrime treats the file no differently than one downloaded directly from a supported bank portal.

What Makes a Converted File TallyPrime-Ready

Not every CSV or Excel file will import cleanly. TallyPrime expects specific structural qualities:

Column alignment with a bank template. The columns in your converted file must match what TallyPrime's pre-configured template expects for the bank you select during import. If your bank is not in the supported list, structuring the output to match a similar bank's template format is often the best workaround. At minimum, you need date, transaction description, and amount columns.
Consistent date formatting. Every date in the file should follow a single format (e.g., DD-MM-YYYY). Mixed formats cause mapping failures or silently misparse transactions.
Separated debit and credit columns. TallyPrime distinguishes between withdrawals and deposits. If your source PDF shows a single "Amount" column with positive/negative signs, the conversion must split these into distinct debit and credit columns.
No formatting artifacts. Merged cells, embedded headers mid-file, currency symbols inside amount fields, and trailing whitespace are common leftovers from PDF extraction done poorly. Any of these will break the import or produce incorrect voucher entries.

The Extraction Workflow

A document extraction tool handles the conversion by reading the PDF and outputting structured data. The general workflow looks like this:

Upload the PDF bank statement. The tool ingests the file, whether it is a native digital PDF or a scanned image.
Specify what to extract. You define the target fields: transaction date, narration/description, debit, credit, and closing balance. Some tools can auto-detect the structure of a bank statement and suggest the extraction layout without manual configuration.
Download the structured output. The result is a CSV or Excel file with each transaction on its own row and each data point in its own column, ready for TallyPrime's import.

Invoice Data Extraction handles this conversion. Bank statements are a core supported document type, and the output formats (Excel .xlsx and CSV) are the same formats TallyPrime's Connected Banking expects. You upload the PDF, provide a prompt specifying the columns you need (transaction date, description, debit, credit, balance), and the platform returns a clean spreadsheet. Because extraction is prompt-driven, you can tailor the output to match whatever column structure your specific TallyPrime bank template requires. There is no need to manually reformat the file after extraction.

Building a Repeatable Workflow for Multiple Statements

If you handle bookkeeping for multiple clients or process statements from several banks each month, a one-off manual conversion is not sustainable. You need a process that works the same way every time.

The prompt library feature in Invoice Data Extraction addresses this directly. You can save your extraction instructions for each bank's statement format, name them (e.g., "SBI Savings Statement" or "HDFC Current Account"), and reuse them month after month. When a new batch of PDF statements arrives, you select the saved prompt and run the extraction. The platform supports batch processing of up to 6,000 documents per job, so even firms reconciling dozens of client accounts can process an entire month's statements in a single run. The output stays consistent across every batch because the same extraction logic applies each time. A free tier covers 50 pages per month, with pay-as-you-go pricing for higher volumes.

For a detailed walkthrough of the full PDF-to-spreadsheet process, see our guide on converting bank statement PDFs to structured Excel or CSV. The platform can extract data from PDF bank statements from all major Indian banks and international institutions.