How to Import Bank Statements into TallyPrime: Supported Paths

To import bank statements into TallyPrime's Bank Statement workflow, use a supported bank's CSV, Excel, or MT940 file downloaded from the bank portal. Where your account is eligible, Connected Banking is a separate option that fetches the statement inside TallyPrime.

You cannot upload a PDF bank statement through the Bank Statement workflow. TallyPrime also rejects CSV or Excel files converted from PDF for this purpose. If PDF is your only source, converting the bank statement to a spreadsheet can create review or staging data, but moving that bank statement to TallyPrime requires a separate mapped transaction import, Tally-compatible XML, or connector workflow.

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.

Source you have	Correct TallyPrime path	What it produces
Original CSV, Excel, or MT940 from a supported bank portal	Import Bank Statement	Imported Bank Data for voucher creation and reconciliation
Eligible account connected within TallyPrime	Connected Banking	A statement fetched into the banking and reconciliation workflow
PDF or a spreadsheet converted from PDF	Not accepted as a Bank Statement file	Extract and review as staging data, then use a separately mapped transaction import or specialist Tally XML/connector tool
Unsupported bank or statement format	Ask Tally support to configure it	A supported statement setup; do not imitate another bank's template

---

How to Import a Supported Bank Statement into TallyPrime

TallyPrime supports Bank Statement import for 145+ banks. This coverage figure applies to downloaded statement files; it should not be read as the availability list for Connected Banking. Tally's current Bank Statement instructions treat file import and fetching a statement through Connected Banking as two distinct routes.

Supported File Formats

For Bank Statement import, the supported files are:

• CSV downloaded from the bank portal
• Excel downloaded from the bank portal
• MT940 downloaded from the bank portal

PDF, PDF-derived CSV/Excel, TXT, and XML are not Bank Statement import formats. Tally's Banking FAQ states this file boundary explicitly. XML belongs to a separate generic data-import route, not the statement workflow described here.

The Import Workflow

For an original supported statement file:

1. From Gateway of Tally, press Alt+O (Import) > Bank Statement.
2. Select the bank ledger, enter the file path, and choose the supported file.
3. Turn on the preview and review the statement before importing it.
4. Complete the import, then open Bank Reconciliation Summary.

The imported rows appear in Imported Bank Data. They are available for voucher creation and matching against book transactions; importing the statement does not silently turn every row into a final accounting entry.

Bank Coverage and Its Limits

The supported list includes many Indian public- and private-sector banks, but a particular bank or statement layout may still be unavailable. If TallyPrime does not support your bank or its current format, Tally instructs users to email its support team so it can configure the statement. Reshaping the data to resemble another bank's template is not a supported workaround.

---

Turning Imported Statements into Vouchers and Reconciled Entries

After a statement has entered Imported Bank Data through a supported route, TallyPrime can help create book vouchers and reconcile them with bank transactions. These steps still require review.

Auto-Create Vouchers from Imported Transactions

TallyPrime can create payment or receipt vouchers from imported bank entries. You can create a voucher for one entry, create several at once, or consolidate selected entries into one voucher. Newly created vouchers are optional so you can check the ledger, bank allocation, cost centre, narration, and other details before regularising them.

Do not treat auto-create as automatic classification of every transaction. The relevant ledger and voucher details still need to be selected and verified, especially for unfamiliar payees, transfers, fees, refunds, and combined settlements.

Bank Reconciliation After Voucher Creation

TallyPrime's bank reconciliation workflow compares book vouchers with bank entries. Exact matches can be reconciled, while exceptions remain visible for action.

The reconciliation review focuses on several conditions:

• entries present in both the books and bank data;
• book entries with no corresponding bank row;
• bank rows for which no book voucher exists; and
• likely matches that still need a date, amount, or ledger detail checked.

This review surfaces missing vouchers, timing differences, duplicate entries, and genuine mismatches before period-end close. A voucher created from a bank row can be reviewed and regularised before it is reconciled.

The same control principle applies when importing bank statements into NetSuite: source provenance and a review step matter as much as file structure. For TallyPrime's Bank Statement route, provenance includes downloading the supported file from the bank portal rather than reconstructing it from a PDF.

---

Can You Import a PDF Bank Statement in TallyPrime?

No. You cannot directly import or upload a PDF bank statement in TallyPrime's Bank Statement workflow. Converting that PDF bank statement to Excel or CSV does not make it eligible: TallyPrime's current instructions also reject spreadsheets converted from PDF or third-party software.

That distinction matters because two different jobs are often described as “bank statement to Tally Prime”:

1. Bank Statement import brings an original supported statement into Imported Bank Data for voucher creation and reconciliation.
2. Transaction import creates Tally transactions from mapped Excel data or appropriately structured XML/JSON. It is a separate data-import process.

If you only have a PDF, extraction can help with the second job by producing clean staging data. It cannot make the file acceptable to the first workflow.

Choose the PDF Route by Your Actual Outcome

If the statement remains locked in PDF, choose among these outcomes:

• Review, audit, or analysis: extract the transactions into XLSX or CSV, validate the totals, and work with the spreadsheet outside TallyPrime.
• Mapped Excel transaction import: map spreadsheet columns to the corresponding TallyPrime fields and import the resulting transactions. Tally's Import Data documentation explains this separate route.
• Bank statement to Tally XML or a connector: use a specialist workflow that performs the required voucher, ledger, master, and schema mapping before posting or importing. Changing the file extension is not enough.
• Manual entry: for a small number of transactions or ambiguous mappings, record the vouchers manually and reconcile them against the PDF.

Generic transaction import should not be described as Bank Statement import. It moves mapped accounting data into TallyPrime; the PDF-derived sheet is not accepted as Imported Bank Data merely because its columns look like a bank export.

---

Prepare PDF Bank Statement Data for Mapping and Review

For a PDF-only route, extraction quality still matters even though the spreadsheet is staging data rather than a TallyPrime Bank Statement file. A practical table includes transaction date, narration, reference or UTR number, debit, credit, and balance. That is also the useful structure when you turn Indian bank statement PDFs and UPI records into Excel rows.

Before downstream mapping, check that:

• dates use one unambiguous format;
• debit and credit are separated or the amount-sign convention is documented;
• multi-line narrations remain attached to the correct transaction;
• opening balance plus credits minus debits agrees with the closing balance, allowing for the bank's sign convention; and
• repeated headers, merged cells, currency symbols, and summary rows are removed from the transaction table.

These are review controls, not a claim that the resulting spreadsheet matches TallyPrime's Bank Statement template. Any transaction-import or connector stage must still map the rows to the correct voucher types, ledgers, masters, and Tally fields.

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. The same extraction approach also covers manual records, so you can turn handwritten cash books and ledgers into balance-verified Excel when your source is a physical book rather than a bank export.
2. Specify what to extract. Define the transaction date, narration, reference, debit, credit, and balance fields, plus the date and number formats you need.
3. Download and validate the structured output. Check row counts, balance movement, signs, and a sample against the source PDF before using the data in any downstream mapping process.

Invoice Data Extraction's bank statement converter turns native or scanned bank-statement PDFs into structured XLSX, CSV, or JSON. You describe the fields and formatting you need, then review the output as staging data. It does not generate Tally XML, map Tally ledgers or vouchers, connect to TallyPrime, or post transactions; those are separate downstream steps.

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. For clients whose books are in BUSY, follow the separate BUSY bank statement import and reconciliation workflow.

The prompt library in Invoice Data Extraction lets you save and reuse extraction instructions for recurring statement layouts. The platform accepts mixed batches of up to 6,000 files per job, and the same saved prompt can keep requested columns and formats consistent from one run to the next. Each batch still needs validation before its output enters a mapped accounting workflow.

For a detailed extraction walkthrough, see the guide to converting bank statement PDFs to structured Excel or CSV. The result is a reviewable spreadsheet—not, by itself, a supported Bank Statement import file or a finished Tally transaction payload.