MyTaxFlow — Convert Bank Statement to Tally XML

Tally Bank Statement Import Excel Format (Free Template)

Which Excel file Tally actually accepts, the exact columns for your own file, and a free template you can fill and import today.

Updated November 2026 · 8 min read
Short answer: Tally Prime has two different Excel imports for bank data. The Bank Statement screen only accepts a file the bank itself produced in its supported format. If you want to import your own spreadsheet, you must use Alt+O → Transactions and map the columns — and that is what the free template on this page is for.

Most of the confusion around “Tally bank statement import Excel format” comes from mixing those two routes. They have different menus, different files and different error messages. Once you know which one your file belongs to, the import either works immediately or fails for a reason you can fix in a minute.

The Two Excel Imports in Tally Prime

Bank Statement screenTransactions (Excel import)
MenuGateway of Tally → Alt+O → Bank StatementGateway of Tally → Alt+O → Transactions
File it acceptsStatement file produced by a supported bankAny spreadsheet you create yourself
Column namesMust match the bank's layoutYou map each column to a Tally field
What it createsImported bank data used for reconciliationPayment, Receipt and Contra vouchers
Works with a PDF?NoNo — convert the PDF to XML instead

If your file came from the bank's net banking export, use the first row. If you cleaned up or built the data yourself, use the second row.

What the Bank Statement Screen Actually Accepts

The Bank Statement import is a reconciliation feature, not a generic importer. Tally defines a supported file layout for each bank it works with, and it expects the bank's own download, not a file that has passed through another tool.

This is the most common failed import. Someone converts a PDF to Excel, opens Alt+O → Bank Statement, picks the file, and Tally rejects it as an invalid format. The file is fine — the route is wrong. PDF statements belong on the voucher XML route, not this screen.

When to Use Your Own Excel Instead

The Transactions import is the practical choice when the data does not come from a bank layout at all:

The Template Columns

One row per ledger leg, two rows per voucher. The voucher number is what keeps the legs together, so repeat it on both rows.

ColumnRequiredWhat Tally needs from it
DateYesA date Tally can read, and one that falls inside the company's financial period. DD-MM-YYYY is safest.
Voucher NoRecommendedGroups rows into one voucher. Repeat the same value on both legs. Without it, Tally may create one voucher per row.
Voucher TypeYesPayment, Receipt or Contra. It must already exist in the company.
LedgerYesExact ledger name as spelled in Tally. A mismatch skips the row.
DebitOne of the twoAmount debited to that ledger. Money leaving the bank appears as a debit on the expense or party leg.
CreditOne of the twoAmount credited to that ledger. Money coming into the bank appears as a credit on the bank leg.
NarrationRecommendedCheque number, UTR, UPI reference. This is what makes the entry auditable later.

Download the template

Two example vouchers are included, with a second sheet explaining the columns. Delete the examples before you import.

The example rows show the sign convention clearly. A payment of ₹1,250 debits the expense or suspense leg and credits the bank:

Date,Voucher No,Voucher Type,Ledger,Debit,Credit,Narration
01-04-2026,BNK-001,Payment,Suspense Account,1250.00,,UPI/DR/123456/ABC ENTERPRISES
01-04-2026,BNK-001,Payment,HDFC Bank - Current A/c,,1250.00,UPI/DR/123456/ABC ENTERPRISES

Column names are a convenience, not a rule: Tally asks you to map each column during import, so a sheet that says Txn Date and Withdrawal still works if you map them to Date and Debit.

How to Import the Filled Template

Tally Prime

  1. Confirm the bank ledger exists under Bank Accounts, and that every opposite ledger name in the sheet exists too.
  2. Close the Excel file. Tally cannot read a file that is still open in another program on some setups.
  3. Open the company that should receive the vouchers.
  4. Press Alt+O (Import) and choose Transactions. In some releases the label is Vouchers.
  5. Select the Excel file. Tally shows the sheet, the header row and a mapping screen.
  6. Map each column to the matching Tally field, then choose Add as the behaviour for existing vouchers.
  7. Accept the backup prompt on a first import, then press Enter. Tally reports imported and skipped counts.

Tally.ERP 9

  1. Place the file in a folder Tally can access.
  2. Go to Gateway of Tally → Import of Data → Vouchers.
  3. Enter the full file path, choose the file type, and map the columns.
  4. Check the Day Book afterwards against the row count.

“Not a Valid Format” and Other Excel Errors

Message or symptomCauseFix
Not a valid formatUsing the Bank Statement screen for your own file, or for a PDF converted to ExcelImport through Alt+O → Transactions instead
Zero vouchers imported, no errorColumn mapping did not include date or amount, or the company period excludes those datesRemap the columns and check F2 (Period) in the company
Vouchers land in SuspenseThe opposite ledger name does not match an existing ledgerCreate the ledger, or correct the spelling in the sheet
One voucher per rowVoucher number column missing or not mappedAdd and map the Voucher No column
Import stops partwayRows with blank dates, merged cells, subtotal rows or text in amount columnsRemove totals rows, unmerge cells, format amounts as numbers
File not visible in the pickerFile still open, wrong filter, or saved as .xls while Tally expects .xlsxClose Excel, choose All Files, re-save in the expected format

For a batch that keeps failing, set Alt+O → Configuration → Ignore errors during import to Yes. Tally then imports the valid rows and lists the rest as exceptions, which is far easier to debug than a silent failure.

Excel or XML for Bank Statements?

Excel voucher importTally XML import
Best forData you already have in a spreadsheetStatements that arrive as PDF
Manual workEvery row typed or cleaned by handNone — the statement is read for you
Column mappingRequired on every importNot needed, the file already carries the structure
Error surfaceTypos, merged cells, wrong ledger namesLedger names and company period
Repeat importsYou must avoid duplicating rows yourselfAlso duplicates unless you check the Day Book first

Why a PDF Statement Still Needs Conversion

If the source is a net banking PDF, neither Excel route helps until the data is out of the PDF. Converting PDF to CSV with a generic tool usually breaks the narration and balance columns, and Tally rejects the result anyway. The reliable path is PDF to Tally XML: the voucher type, ledger and debit/credit direction are written into the file, so the import has nothing to guess.

Related: the full import guide covers both routes step by step, and the Tally XML format guide explains the file structure if Tally reports a tag or date error.

How this guide was checked

The column mapping, menu paths and error behaviour were tested in TallyPrime and cross-checked against Tally's documentation for Excel import and for the bank statement (reconciliation) import. Read the editorial policy for how we handle corrections.

Last reviewed: 4 November 2026

Sources

Frequently Asked Questions

Can I import my own Excel file into Tally Prime as bank entries?

Yes, but not through the Bank Statement screen. Use Alt+O (Import) and choose Transactions, then select your Excel file and map each column. The Bank Statement screen only accepts statement files produced by supported banks.

What columns does the Tally bank statement import Excel format need?

Date, Voucher No, Voucher Type, Ledger, Debit, Credit and Narration. Use one row per ledger leg and repeat the voucher number so Tally groups the two legs into one voucher. Header names are a convenience, because Tally asks you to map each column during import.

Why does Tally say not a valid format when I import my Excel file?

The usual causes are choosing the Bank Statement screen for a file the bank did not produce, a date column Tally cannot read, merged cells or totals rows, an open file, or a .xls/.xlsx mismatch. Import the file through Transactions and map the columns instead.

Does the Tally bank statement import screen accept a PDF or an Excel converted from a PDF?

No. Tally documentation states that PDF statements, and CSV or Excel files converted from a PDF, cannot be used with the bank statement import feature. For a PDF, convert it to Tally XML and import the vouchers instead.

Is the free template the same as MyTaxFlow's exported XML?

No. The template is a plain spreadsheet you fill in yourself for Tally's Excel voucher import. MyTaxFlow reads the PDF statement for you and produces Tally XML with the same voucher structure, so there is nothing to type.

How many rows can Tally Prime import from Excel at once?

There is no documented row limit, but practical limits come from voucher grouping and file size. Import a few hundred rows at a time, keep one voucher number per voucher, and check the imported count against the row count before moving on.

Skip the Spreadsheet Entirely

Upload a digital bank statement PDF and get reviewable Tally XML — voucher type, ledgers and debit/credit already in place.

Convert Bank Statement to Tally XML

Related Guides