How to Import Bank Statements into TallyPrime (All Formats)

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

TallyPrime cannot import PDF bank statements directly. If your bank issues only PDFs, or is not among the supported institutions, you need to convert the statement into a clean CSV or Excel file before TallyPrime can use it.

The Reserve Bank of India's Digital Payments Index reached 493.22 in March 2025, nearly five times its March 2018 base, which means more digital transactions to classify and reconcile.

---

How Connected Banking Imports Bank Statements into TallyPrime

Connected Banking is TallyPrime's built-in path for bringing external bank statement data into your ledger. It imports transaction files from 145+ Indian banks, using pre-configured templates that map 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

Your import path is determined by what your bank can export and what TallyPrime's template for that bank can read.

The Import Workflow

The actual process is straightforward. From within TallyPrime:

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

TallyPrime's official documentation covers each screen and field in detail. The pre-configured template maps your bank's columns to TallyPrime's expected fields, so you do not have to define the debit, credit, date, or narration columns manually. 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 major names such as SBI, HDFC, ICICI, Axis, Kotak, and PNB, along with many large private and public sector banks. 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 has no template to parse the statement.

---

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 from the transaction data: 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 imported transactions map to voucher types and ledger accounts; for example, a recurring payment to a known vendor can map to the correct expense ledger automatically. You then review the auto-created vouchers, correct exceptions, and post them to the books.

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 before month-end reconciliation. 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

Most failed TallyPrime bank statement imports come down to one of three format problems.

TallyPrime cannot import PDF bank statements. This is the most common blocker. Most Indian banks provide downloadable statements as PDFs, but Connected Banking's import pathway does not read PDFs. There is no setting to enable it and no plugin that adds support.

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. Copy-paste conversion usually carries formatting artifacts: merged cells, split transaction rows, date formats that don't match the expected template, amounts pasted as text, and column orders that differ from what TallyPrime expects. The result is either an outright import rejection or garbled data where transactions are misaligned, amounts land in wrong fields, or rows are silently dropped. For TallyPrime, PDF bank statements need structured conversion, not manual copy-paste.

The third limitation is unsupported banks. Cooperative banks, small finance banks, regional rural banks, payment banks, and some international banks operating in India may fall outside TallyPrime's supported list. Even with a clean CSV or Excel file, Connected Banking needs a bank-specific template that defines where the date, narration, debit, credit, and balance fields sit.

One detail that trips up experienced TallyPrime users: the general-purpose Excel and CSV import feature for masters, stock items, or ledger data does not work for bank transactions. Bank statement import is handled through Connected Banking, not Gateway of Tally's standard import menu.

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 become a clean format that matches your bank's TallyPrime template, or a compatible template.

---

Converting PDF Bank Statements into TallyPrime-Ready Files

For TallyPrime, the converted file needs clean columns for date, narration, debit, credit, and balance, aligned to the bank template you plan to use. 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:

1. Upload the PDF bank statement. The tool ingests the file, whether it is a native digital PDF or a scanned image.
2. 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.
3. 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 the column structure your TallyPrime bank template requires. If you manage books across multiple systems, the same extraction-first logic also applies when getting bank statements ready for Zoho Books, even though Zoho Books uses a different PDF allowlist and CSV import contract.

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 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. The platform supports batch processing of up to 6,000 documents per job, and saved prompts keep the output structure consistent across monthly statement batches.

For a detailed walkthrough, 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.