Yes. TallyPrime imports bank statements in Excel, CSV and MT940 format, and Tally lists well over a hundred banks whose statement files it recognises. There are two formats it will not take: a PDF, and an Excel or CSV file that was made from a PDF.
That second one catches most people out, because it is exactly the file a PDF bank statement converter hands you. This page covers what TallyPrime accepts, how the import works, and what to do when the statement you have is a PDF.
The short answer, in one table
| What you have | Will TallyPrime import it? |
|---|---|
| Excel or CSV downloaded from your bank’s net banking portal | Yes |
| An MT940 file from your bank | Yes |
| A PDF statement, emailed or downloaded | No |
| An Excel or CSV you converted from a PDF | No — Tally names this case explicitly |
| A scanned or photographed statement | No |
| A statement your client sent you as a PDF | No |
If your row is one of the first two, stop reading and use Tally’s built-in import. It is free, it is already installed, and nothing you buy will do that job better.
What Tally’s own documentation says
This is worth quoting directly, because a lot of advice on this topic contradicts it. From TallyHelp’s page on importing bank statements:
You can import bank statements that are CSV/Excel format, download from the bank portal.
You cannot import bank statements in the following format: PDF. CSV/Excel converted from PDF.
TallyHelp, Import Bank Statements in TallyPrime
Read the second line twice. Plenty of guides tell you to convert your PDF into Excel and then import it. Tally’s own documentation says that file is not accepted.
Why a tidy spreadsheet still gets rejected
TallyPrime’s Bank Statement import is not a generic spreadsheet reader. It holds a format definition per bank, which is why the File Type list you pick from is bank-specific, and why Tally asks you to write to their support when your bank is missing rather than telling you to reshape the file yourself.
A spreadsheet you built yourself matches none of those definitions, however clean it looks. The columns are in your order, not the bank’s. That is the whole reason the restriction exists, and it is why reshaping the file usually turns into an afternoon.
How to import a bank statement in TallyPrime
Assuming you have the file your bank’s portal produced:
- Download the statement in Excel or CSV from net banking. Look for the format dropdown next to the download button — most portals default to PDF.
- Close the file. Tally will not read a statement that is open in Excel.
- From the Gateway of Tally, press Alt+O for Import, then choose Bank Statement.
- Fill in the Bank Ledger, the File Path and the File Type, and pick the file.
- Press Ctrl+A to import, then I to confirm on the preview screen.
- The Summary of Imported Statement tells you how many entries came in and how many matched existing vouchers exactly. Press S for the Bank Reconciliation Summary.
Two things stop this import for reasons that have nothing to do with your file. The bank ledger has to be set up under Bank Accounts, or the banking menus stay empty. And the statement dates have to fall after the ledger’s Reconciliation Beginning Date — anything earlier is ignored without much explanation.
Importing a statement is not the same as creating entries
These are two different outcomes and people ask for one while meaning the other.
- Reconciliation. You already passed the entries. The imported statement is matched against them so you can see what agrees and what does not.
- Auto-creating vouchers. You have no entries yet. TallyPrime reads the imported rows and fills in the payment or receipt details for you, as single, multiple or consolidated vouchers.
The second is the one most accountants actually want, and TallyPrime does it — from a statement file it accepts. What it does not do, in either mode, is decide that a UPI payment to a fuel pump belongs in Vehicle Running Expenses. That decision is still yours, whichever route the data takes.
So what do you do when all you have is a PDF?
This is the normal situation for anyone handling other people’s books. Clients forward the PDF their bank emailed them. Nobody hands over net banking credentials so you can re-download it as Excel.
Four routes, honestly ranked by effort:
If you take the first or second route, entering a bank statement in Tally step by step covers which voucher type each row needs and the checks that catch a bad month.
| Route | What it involves | Use it when |
|---|---|---|
| Ask for the Excel | Get whoever owns the account to re-download in Excel or CSV | Always try this first. It is free and it ends the problem |
| Type it in | Manual receipt and payment vouchers | Under roughly thirty lines. Do not over-engineer a small job |
| Convert, then build a Tally XML voucher file | Get the rows into a spreadsheet, add a ledger column, run it through an Excel-to-XML template, import under Vouchers | You already have a template that works and you are comfortable maintaining it |
| A connector that creates the vouchers | Something else reads the statement and posts the vouchers into Tally for you | PDF statements arrive every month, across several clients |
The detail that explains the whole confusion
Tally has two separate import doors, and they have different rules.
- Import > Bank Statement expects your bank’s own file, in your bank’s own layout. This is the door that refuses anything made from a PDF.
- Import > Vouchers expects Tally XML. It does not care where the data came from, because by that point it is already shaped as vouchers with ledgers attached.
That is why “convert your PDF to Excel and import it” fails, while “convert your PDF and build a voucher file” works. Same source file, different door. If you want the long version, we wrote a separate guide on what a Tally XML file actually contains and when you still need one.
The part that actually takes the time
Not the import. The ledger mapping.
A month of bank rows is a list of narrations: UPI/DR/4159/RELIANCE, NEFT-AXISCN00123-ACME TRADERS, ATW-4587-CASH WDL. Every one has to become a named ledger before it is a voucher. No file format does that for you, and neither Excel nor XML nor MT940 changes the size of the job.
When you are comparing tools, this is the thing worth comparing. Anything that only converts a PDF into a spreadsheet has done the easy half.
One check that catches a bad conversion in a minute
If you do convert a PDF, whatever tool you use, do this before anything reaches your books. Your statement has a running balance column. Compare the closing balance on the converted sheet against the closing balance printed on the statement. If they do not match, a row was misread, and you have found it before it is in the ledgers rather than at the trial balance.
Four failures that check reliably catches, all of them common in Indian statements:
- Column headings print on page one only. Pages two onward arrive as a bare grid. A converter that re-guesses the columns per page can shift the narration into the date column, and page one looks perfect. Always check page two, never page one.
- Direction shown by sign, not by words. Some banks never print Cr or Dr; they put a plus or minus on the amount. A tool looking for the letters gets every entry’s direction wrong.
- Wrapped narrations. A long narration spills onto a second line and one transaction becomes two rows, one of them with no amount.
- A CSV wearing an .XLS name. Some Indian banks hand you comma-separated text with a spreadsheet extension. Excel opens it; most import tools refuse it. If a tool calls your file corrupt, open it in Notepad and look.
There is more on how the formats differ in our comparison of PDF, Excel and CSV statements for Tally.
Where SmartXtract fits, and where it does not
If your bank gives you Excel and TallyPrime supports that bank, use Tally’s built-in import. It is free and it is already on your machine. We are not a better version of something you already have.
SmartXtract is for the other case: the statement is a PDF, or a scan of a branch printout, or from a bank that is not on Tally’s list. You upload it — password-protected files are handled by typing the password at upload. Every row is read and checked against the statement’s own running balance, so a misread figure shows up as a break in the chain instead of sitting quietly in your books. You get a clean Excel file out of it.
That Excel then goes into Tally through Tally Connector, a free Windows app that runs beside TallyPrime on the same PC. Its AI Assistance suggests a ledger for each narration; you adjust what it got wrong, apply, and it creates the receipt, payment and contra vouchers. Nothing posts until you approve it. There is no XML file to build, Undo Import reverses a whole batch if the mapping was wrong, and a payee you map once is remembered on the next statement.
Start free with 20 pages, no card. Or read the full walkthrough of importing a bank statement PDF into Tally.
Frequently asked questions
Can we import bank statement in Tally ERP 9?
Yes. Tally.ERP 9 has bank statement import too, reached through Banking rather than the Import menu, and it is aimed at reconciliation. The format rule is the same: it reads the file your bank produced, in a layout it recognises, and it cannot read a PDF. Auto-creating vouchers from imported bank rows is a TallyPrime feature, so on ERP 9 the entries are still yours to pass.
Can TallyPrime import a PDF bank statement?
No, and converting the PDF into Excel does not fix it. Tally’s documentation names both cases: PDF, and CSV or Excel converted from PDF. The Bank Statement import expects your bank’s own file in your bank’s own layout, so a spreadsheet you assembled yourself will not be accepted no matter how tidy it is. A Tally XML voucher file is a different import and is accepted.
Which banks does TallyPrime support for statement import?
Tally’s own pages give two different figures — the bank statement page says 145+ banks, the reconciliation page says more than 200. Either way it is a list, not a guarantee, and the practical answer is to check whether your bank’s format appears in the File Type dropdown when you run the import. Tally invites you to write to their support if yours is missing.
Why does Tally say my bank statement format is wrong?
Four causes cover almost every case. The file was converted from a PDF rather than downloaded from the bank. The file is still open in Excel. The statement dates fall before the bank ledger’s Reconciliation Beginning Date. Or Tally does not have write permission on the folder the file sits in. Work through those before you go looking for a different tool.
Do I need to make a Tally XML file?
Only if you choose that route. XML is one way to get vouchers into Tally, not the only one, and it is the one that costs you a template to build and maintain. A connector that creates the vouchers directly skips the file entirely. If you already have an XML template that works, there is no reason to abandon it.
Is there a free way to import a bank statement into Tally?
Yes, and it is the first thing to try. Download the statement as Excel or CSV from net banking and use TallyPrime’s built-in Bank Statement import. That costs nothing and it is the right answer whenever your bank is supported. Paid tools become worth it when the statement only exists as a PDF or a scan, or when you are doing this across many clients every month.
Can I import a scanned bank statement into Tally?
Not directly. A scanned statement is an image, so there is no text to read until something has run it through OCR, and the figures it produces need checking against the statement’s own running balance before they become vouchers. Once the rows have been read and turned into vouchers they go into Tally like any others, but the reading step has to happen outside Tally. Scans are also the format most likely to be misread, so the closing-balance check matters more here than anywhere else.
In short
Tally imports bank statements, and does it well, as long as the file came from your bank. The moment the statement is a PDF — which is how most of them arrive — Tally’s own import is closed to you, and converting the file does not open it. What you need at that point is not a converter but something that produces vouchers.
If that is your monthly reality, try it on your own statement — 20 pages free, no card.
