How to Import Bank Statements into TallyPrime, Including PDF Statements

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, and TallyPrime also rejects CSV or Excel files converted from PDF for this purpose. When a PDF is all you have, the working route for bank statement to Tally is different: extract the transactions into a spreadsheet, import them as payment, receipt and contra vouchers through Excel import with a mapping template, then reconcile the bank ledger against the PDF.

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 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 serves the second job: it gives you the transaction rows to bring in as vouchers. 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.
• Vouchers through Excel import: the route most PDF holders need, set out step by step in the next section.
• Bank statement to Tally XML or a connector: TallyPrime also imports vouchers as XML, which converter and connector tools generate. The XML has to carry the voucher, ledger, and master details in Tally's schema, as the guide to what a Tally XML voucher must contain shows for purchase invoices, so changing the file extension is not enough. XML earns its setup at high volume; the Excel route below needs none.
• Manual entry: for a small number of transactions or ambiguous mappings, record the vouchers manually and reconcile them against the PDF.

---

Bank Statement PDF to TallyPrime: Import the Transactions as Vouchers

This route does not bring the statement into Imported Bank Data. It brings in the accounting vouchers the statement's transactions call for, posted against your bank ledger, and you then reconcile that ledger against the PDF. Tally's own pages draw that line. Its Import Data FAQ says TallyPrime does not support importing bank transactions through Import Data from Excel, and sends bank-statement data to Bank Reconciliation's own statement import, the route a PDF cannot use. Its getting-started guide to importing data covers importing payment vouchers from Excel, and says what they need to appear correctly in the Bank Reconciliation report.

Take a backup, or work in a test company, and import a few rows first. Check how they land in the bank ledger and the Bank Reconciliation report before you bring in the full month.

Step 1: Set Up the Ledgers

Every ledger the vouchers will post to must already exist in the company: the bank ledger, and each party, expense, and income ledger on the other side. Names must match character for character, so "M/s Sharma Traders" will not match "Sharma Traders". A mismatched name is a common cause of rejected rows, and the Ledger Not Found fix in the TallyPrime invoice import guide shows how to check your import file against the ledger list.

Step 2: Get the Transactions out of the PDF

Extract one row per transaction with the 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. If the source is a physical book rather than a bank export, you can turn handwritten cash books and ledgers into balance-verified Excel the same way.

Before the rows go any further, 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;
• repeated headers, merged cells, currency symbols, and summary rows are removed from the transaction table; and
• the row count and a sample of rows match the PDF.

Step 3: Turn Each Transaction into a Voucher Row

Each transaction becomes a voucher, and the sheet carries what the voucher needs:

• Voucher Type: Payment for a withdrawal, Receipt for a deposit, and Contra for a transfer between your own bank accounts or to and from cash.
• The ledgers: the bank ledger on one side, and the party, expense, or income ledger on the other.
• Date, amount, and narration, with the reference or UTR carried into the narration so each voucher can be traced back to its statement line.

Tally names Date, Voucher Type, and Debit/Credit Amount as the mandatory fields for vouchers. For payment vouchers to appear correctly in the Bank Reconciliation report, its getting-started guide says to include Bank Date, Ledger Amount, and Bank Name in the Excel file. The simplest way to get the layout right is to start from Tally's sample Excel files ("Vouchers – General" is the one for this job) and keep their column headers as they are, since Tally maps them internally.

Invoice Data Extraction's bank statement converter can give you this sheet straight from the PDF, native or scanned. With a Structured Prompt you name the columns in the order your Tally layout uses, and the spreadsheet comes back with those headers in that order. Any column can carry its own rule: "Voucher Type: Payment if the amount is a withdrawal, Receipt if it is a deposit", or "Ledger: classify as one of Bank Charges, Rent, Electricity Charges, Salary or Suspense". A ledger filled in this way is a suggestion to check, not a posting decision. A Source File column gives the file and page each row came from, and a value or a row the panel of AI agents cannot agree on is flagged in a Review Needed column, with what to check. Keep those two columns while you review against the PDF, then leave them out in Preferences and download the XLSX or CSV for import, so the file carries only your mapped columns. The product does not connect to Tally, write Tally XML, or post vouchers: it hands you the spreadsheet, and TallyPrime imports it.

Step 4: Create the Mapping Template

Tally's guide to importing from any Excel file sets out the steps:

1. Press Alt+O (Import) > Manage > Mapping Templates > TRANSACTIONS > Create.
2. Give the details of the Excel file, a name for the template, and the rows and columns the data occupies.
3. Map each Field (TallyPrime) to its Column Header (Excel).
4. Verify the mapping, then press Ctrl+A to save.

The template is saved in TallyPrime's config > excelmaps folder, so next month's sheet with the same columns imports without re-mapping.

Step 5: Import, Then Clear the Exceptions

1. Press Alt+O (Import) > Transactions.
2. Choose the Excel file and the mapping template.
3. Read the Preview Import Summary. The number of vouchers should match the number of transactions you extracted.
4. Take the backup the import offers if you have not already, then press I to import.

Rows TallyPrime cannot bring in are listed as data exceptions. Fix them at the source (a ledger name, a date, an amount), then import those rows again rather than editing the vouchers piecemeal.

Step 6: Reconcile Against the PDF

Open Bank Reconciliation for the bank ledger and check it against the statement: with every statement line booked, the ledger's closing balance for the period should agree with the PDF's. Any gap points to a transaction missed in extraction, a voucher that failed to import, or one booked twice. The PDF stays the record you check against.

Repeat It Every Month

If you handle bookkeeping for multiple clients or process statements from several banks each month, the same sheet layout and the same mapping template should serve every month. For clients whose books are in BUSY, follow the separate BUSY bank statement import and reconciliation workflow.

The Prompt Library in Invoice Data Extraction keeps one saved prompt per client or statement layout, so each month's sheet comes back with the columns your mapping template expects. Up to 6,000 files can go into one task. Each batch still needs the checks in Step 2 before it reaches TallyPrime.

For a detailed extraction walkthrough, see the guide to converting bank statement PDFs to structured Excel or CSV.