How to Import Bank Statement in Tally Prime: Step-by-Step Guide

Bank reconciliation becomes much easier when you do not have to compare every transaction with a printed statement line by line.

TallyPrime allows you to bring supported bank statements directly into your company data. Once imported, the software can compare transactions in your books with entries reported by the bank, identify matches, highlight transactions that still need attention, and even help create accounting vouchers from bank entries that have not yet been recorded.

If you are searching for how to import bank statement in Tally Prime, the basic route is straightforward:

Gateway of Tally → Alt+O (Import) → Bank Statement → Select Bank Ledger → Choose Statement File → Preview → Import

The important part is preparing the bank ledger and statement correctly before you reach that screen. A PDF statement, for example, cannot simply be converted to Excel and imported through TallyPrime's normal Bank Statement feature. The original bank-supported format matters. Tally's current documentation specifically states that supported CSV or Excel statements should be downloaded from the bank portal rather than converted from PDF.

This guide covers the entire process, including what to do after the import, how automatic reconciliation works, and the most common reasons an import fails.

Quick Steps to Import a Bank Statement in Tally Prime

If your bank ledger is already configured and you have downloaded a supported statement, follow these steps:

Open the required company in TallyPrime.
Press Alt+O (Import).
Select Bank Statement.
Choose the correct Bank Ledger.
Enter or browse to the File Path.
Select the appropriate supported file.
Keep Show Preview set to Yes.
Press Ctrl+A to proceed.
Review the transactions in the Bank Statement Preview.
Press I (Import) to complete the process.
Review the import summary.
Open the Bank Reconciliation Summary to match or reconcile transactions.

TallyPrime displays a summary after the import showing information such as the number of imported entries and identified matches.

What Happens When You Import a Bank Statement?

Importing a bank statement does not simply copy rows from Excel into your books.

TallyPrime uses the statement as bank-side data that can be compared with transactions already recorded in your accounting books.

That distinction matters.

Imagine your books already contain a payment of ₹24,500 to a supplier. The same transaction appears in the bank statement after it clears through the bank.

TallyPrime can compare those two entries and, where the information matches sufficiently, identify them for reconciliation.

Now consider another transaction: your bank statement contains ₹590 as bank charges, but nobody recorded the expense in TallyPrime.

That bank entry has no corresponding book voucher.

Instead of silently ignoring it, TallyPrime can show that it exists only on the bank side. You can then review the transaction and create the appropriate voucher.

This is where statement import becomes much more useful than manually typing bank dates against vouchers.

With the current bank-reconciliation workflow, imported statement data can be used for both automatic reconciliation and voucher creation.

Before You Import: Check These Requirements

Most import problems can be prevented before opening the Import Bank Statement screen.

1. Make Sure Your Bank Is Supported

TallyPrime supports statement import for a large range of banks, but the statement format still needs to be recognised.

A bank being commonly used does not automatically mean every file format downloaded from that bank will work.

If the particular bank or statement format is unsupported, Tally recommends contacting its support team so the format can be reviewed or set up.

2. Download the Statement From Your Bank Portal

This is an easy requirement to miss.

Use the statement file provided directly through your bank's online banking portal whenever possible.

Typically, that means downloading the statement in a supported spreadsheet format such as:

CSV
Excel

Current TallyPrime reconciliation guidance also references MT940 support in relevant workflows, but the exact format available to you depends on the bank and TallyPrime workflow being used.

Avoid editing the original file unnecessarily before import.

3. Do Not Use a PDF Bank Statement

TallyPrime's normal Bank Statement import does not accept PDF statements.

It also specifically warns against taking a PDF bank statement, converting it into CSV or Excel, and then trying to use that converted file as a normal bank statement import.

Why?

Because the Bank Statement feature relies on recognised bank structures. A PDF conversion may visually look like a spreadsheet, but the underlying layout and transaction structure may not match what TallyPrime expects.

If your bank provides only PDF in one part of its portal, look for another download or export option such as CSV or Excel.

4. Close the Statement File Before Importing

If the Excel or CSV file is already open in another application, TallyPrime may be unable to access it correctly.

Close the spreadsheet before starting the import.

This is a small detail, but it is one of the checks Tally lists in its prerequisites.

5. Check Folder Permissions

TallyPrime needs access to the folder containing the bank statement.

If the file is inside a restricted folder or network location where the current user lacks suitable permissions, the import can fail.

Moving the statement temporarily to a normal accessible folder can help determine whether permissions are causing the problem.

Configure the Bank Ledger First

Before importing, make sure the bank ledger itself is properly configured.

If your bank ledger does not appear in the Bank Statement import list, this is one of the first things to check.

Open the relevant bank ledger and verify details such as:

Bank Name
Bank Account Number
IFSC, where applicable

Tally's current banking guidance recommends checking these details when a bank ledger is missing from the available import options.

A ledger called simply “HDFC Bank” or “Current Account” is not enough if the required banking information behind the ledger has never been configured.

Set the Reconciliation Beginning Date

If you are beginning the newer bank-reconciliation workflow, the Reconciliation Beginning Date matters.

Think of it as the date from which you want TallyPrime to begin handling transactions through the current reconciliation process.

For businesses using bank reconciliation for the first time, TallyPrime provides an Opening BRS workflow. You can set the reconciliation beginning date and account for earlier unreconciled transactions as opening BRS items.

This keeps old and new reconciliation periods from becoming mixed together.

For example, suppose your accounts were manually reconciled up to:

31 March 2026

You decide to use imported statements from:

1 April 2026

Rather than importing old statements again, complete the old reconciliation first and begin the new process from the clean transition date.

How to Import Bank Statement in Tally Prime Step by Step

Once the bank ledger and statement file are ready, you can perform the import.

Step 1: Open the Correct Company

Start TallyPrime and select the company whose bank statement you want to import.

If several companies are open, confirm the company name before proceeding.

Importing a statement into the wrong company creates unnecessary cleanup work later.

Step 2: Open Bank Statement Import

From Gateway of Tally:

Press Alt+O (Import) → Bank Statement

This opens the Import Bank Statement screen.

Step 3: Select the Bank Ledger

Choose the ledger corresponding to the statement.

For example:

HDFC Bank Current Account

ICICI Bank – Main Account

Be careful if the company maintains several accounts with the same bank.

The bank name alone may not be enough.

Verify the account before importing.

Step 4: Select the File Path

Enter or browse to the folder where the downloaded bank statement has been saved.

Using a simple folder can make this easier.

For example:

Documents > Bank Statements > September 2026

Good file organisation is particularly helpful when you import statements every month.

Step 5: Choose the Supported File

Select the bank statement downloaded from the bank portal.

TallyPrime's official workflow asks you to select the file type as Supported and choose the corresponding statement file.

Step 6: Keep Show Preview Enabled

Set:

Show Preview: Yes

It is tempting to skip the preview when you have imported statements before.

Don't.

The preview gives you an opportunity to see whether TallyPrime is reading the transaction data properly before the statement becomes part of the reconciliation workflow.

Look at:

transaction dates;
withdrawals;
deposits;
descriptions;
number of entries.

A one-minute review can prevent an incorrect statement from creating additional work.

Step 7: Accept the Import Details

Press:

Ctrl+A

TallyPrime processes the selected statement and opens the preview.

Step 8: Review the Bank Statement Preview

Scroll through the imported information.

You do not need to manually verify every line when dealing with hundreds of entries, but check enough transactions to make sure:

the correct period was selected;
debit and credit values appear correctly;
transaction descriptions are readable;
the statement belongs to the expected account.

Step 9: Import the Statement

Once you are satisfied with the preview, press:

I (Import)

The statement is imported into TallyPrime.

What Do You See After the Import?

TallyPrime displays a Summary of Imported Statement.

This helps confirm that the import actually completed.

From there, you can move to the Bank Reconciliation Summary and begin working with the imported entries. Tally's current workflow allows you to press S from the import summary to move to the reconciliation summary.

At this point, the real accounting work begins.

Importing the statement is only the first half of the process.

How Automatic Bank Reconciliation Works

Suppose your books contain:

Payment to ABC Traders – ₹35,000

Your bank statement also contains:

ABC Traders – ₹35,000

If TallyPrime can confidently identify the two records as the same transaction, it can present them as an exact match.

TallyPrime's current automatic reconciliation workflow separates transactions into categories including exact and potential matches.

Exact Matches

An exact match is a bank transaction that aligns sufficiently with a corresponding book transaction.

Instead of entering the bank date manually, you can review the match and reconcile it.

Potential Matches

Real banking data is not always neat.

A description in TallyPrime may say:

Payment to Sharma Traders

while the bank statement says something like:

UPI/SHARMATRADERS/458921

The amount may be correct but other information differs.

TallyPrime can identify potential matches using factors such as transaction amount, instrument date, and party information.

You should review these before accepting them.

Automatic matching is useful, but accounting judgement still matters.

What If the Transaction Exists Only in the Bank Statement?

This is common.

Examples include:

bank charges;
interest received;
payment gateway deductions;
direct customer deposits;
automatic loan deductions;
standing instructions;
payments recorded late by the accounts team.

If the transaction appears in the bank but not in the books, TallyPrime can help you create a voucher from the imported bank data rather than entering the transaction again from scratch.

Current TallyPrime documentation specifically describes the ability to auto-create vouchers from bank statement entries.

This can save considerable time for businesses with a high number of bank transactions.

Auto-Creating Vouchers From Bank Statements

Consider this example.

Your bank statement contains:

Bank Charges: ₹885

No corresponding entry exists in TallyPrime.

You can review the bank entry and create the appropriate accounting voucher from it.

Similarly, if a customer has transferred money directly into your bank account but the receipt was not recorded, the bank entry can become the starting point for creating the Receipt voucher.

TallyPrime supports creating:

individual vouchers;
multiple vouchers;
consolidated vouchers

from suitable bank-statement entries.

You should still review the ledger allocation carefully.

The software knows money entered or left the bank. It cannot automatically know the business reason behind every transaction without sufficient information.

How to View Imported Bank Data Later

You do not lose access to the statement after leaving the import screen.

To view imported transactions:

Press Alt+G (Go To) → Search for “Imported Bank Data” → Enter

Alternatively:

Gateway of Tally → Banking → Imported Bank Data

You can then select the relevant bank and period.

The Imported Bank Data report shows the bank-side entries along with deposit and withdrawal information.

From this report, current TallyPrime also provides actions for:

creating vouchers;
reconciling or modifying matches;
unlinking incorrect matches;
setting transaction status;
checking potential matches.

This makes it a useful working report rather than simply an archive of imported files.

What If You Imported the Wrong Bank Statement?

It happens.

Perhaps you selected:

the wrong month;
the wrong account;
a duplicate statement;
the wrong file.

Do not begin deleting accounting vouchers randomly.

TallyPrime provides the ability to reset imported bank-statement data where necessary. Its current documentation specifically notes that statement data can be reset when the wrong period has been imported or when reconciliation needs to be reset.

Before resetting anything, check which transactions have already been reconciled or used to create vouchers.

The later you notice the mistake, the more carefully you should review the effect before resetting the data.

Common Bank Statement Import Errors in TallyPrime

Bank Ledger Is Not Visible

Open the bank ledger and check:

Bank Name
Account Number
IFSC

Incomplete bank details are a common reason the ledger does not appear in the import list.

CSV Statement Is Not Importing

The file may technically be a CSV but still use an unsupported CSV encoding or variation.

Tally recommends resaving problematic CSV files specifically as CSV (Comma delimited) when another CSV format is causing trouble.

Do this only with a statement originally downloaded in the appropriate bank-supported format—not with a spreadsheet created from a PDF.

Excel Statement Is Not Importing

Older or specialised Excel formats may cause problems.

Tally's troubleshooting guidance recommends resaving older files such as .xls, .xlsb, or .xlsm as a standard Excel Workbook (.xlsx) where relevant.

“Bank Statement Is Already Open” Error

First close Excel or any program using the file.

If the error continues, Tally's FAQ suggests renaming the file by adding -imp to the filename and trying again.

For example:

statement.csv

becomes:

statement-imp.csv

Statement Format Is Not Supported

A statement can come from the right bank and still have an unsupported structure.

Banks sometimes offer multiple export layouts.

Try downloading another supported format directly from the bank portal.

If TallyPrime still does not recognise it, Tally advises contacting its support team regarding the bank or statement format.

PDF Converted to Excel Still Does Not Work

This is expected.

A converted PDF spreadsheet is not treated as the same thing as an original supported bank statement.

Download the CSV or Excel statement directly from online banking instead.

Import Bank Statement vs Connected Banking

Downloading a statement manually is not the only way to bring bank information into TallyPrime.

For supported accounts, Connected Banking can fetch bank statements through the banking connection.

The workflow is broadly:

Alt+Z (Exchange) → All Banking Options → Get Statement

You choose the bank ledger and statement period, request the statement, and import it once the request is ready.

Manual Statement Import	Connected Banking
Download file from bank portal	Retrieve statement through connected workflow
Requires supported statement file	Requires supported connected bank/account
Works well for monthly import routines	Reduces manual downloading
Useful without connected banking setup	Requires connection and internet access
You choose local CSV/Excel file	Statement is requested through TallyPrime

If your bank is available through Connected Banking and your organisation is comfortable using it, the second method can remove another manual step.

If not, regular statement import remains perfectly practical.

Bank Statement Import vs Manual Reconciliation

Manual reconciliation is still available.

With manual reconciliation, you compare your books against the bank statement and enter the relevant bank dates yourself.

This can work for a business with very few transactions.

The difficulty appears when an account contains hundreds or thousands of monthly entries.

Imported bank statements allow TallyPrime to compare book and bank transactions automatically and identify matches, reducing repetitive manual work.

For most businesses already using a supported bank statement format, the imported-statement workflow is worth considering.

Practical Example

Suppose your April bank statement contains 120 transactions.

Your accountant has already entered 105 of them in TallyPrime.

After importing the statement:

92 are identified as exact matches;
10 appear as potential matches;
3 book transactions remain unmatched;
18 bank transactions have no corresponding voucher.

Instead of comparing all 120 entries manually, the accountant can focus on the exceptions.

Those 18 unmatched bank entries might include:

bank charges;
customer deposits;
direct debits;
interest;
transactions that were simply missed.

This is the real advantage of importing statements.

It shifts the accountant's time away from searching for obvious matches and toward reviewing the transactions that actually need attention.

Best Practices for Bank Statement Import

Import Statements Regularly

Do not wait six months and import everything at once unless there is a specific reason.

Monthly—or more frequent—reconciliation keeps discrepancies easier to understand.

Use a Consistent File Structure

A folder such as:

Bank Statements → 2026-27 → HDFC → September

is much easier to manage than dozens of files sitting in Downloads.

Preview Before Importing

The extra minute is worth it.

Reconcile Before Importing the Next Large Period

Keeping the workflow current prevents a backlog of unidentified transactions.

Investigate Unmatched Entries

Do not simply force every transaction to reconcile.

A mismatch may reveal:

duplicate entry;
wrong amount;
wrong date;
missing voucher;
bank charge;
incorrect party.

Review Auto-Created Vouchers

Automatic voucher creation saves data-entry time, but ledger selection and accounting treatment still need to make business sense.

Frequently Asked Questions

How do I import a bank statement in Tally Prime?

From Gateway of Tally, press Alt+O → Bank Statement, select the bank ledger, choose the supported statement file, keep Preview enabled, press Ctrl+A, review the statement, and press I to import it.

Which bank statement formats does TallyPrime support?

TallyPrime's current statement-import documentation supports bank-provided CSV and Excel files, while current bank-reconciliation guidance also refers to MT940 for relevant supported workflows. Availability depends on the bank and statement format.

Can I import a PDF bank statement into TallyPrime?

Not through the standard Bank Statement import feature. Tally specifically states that PDF statements and CSV/Excel files converted from PDF are not supported in that workflow.

Why is my bank ledger not showing during import?

Check whether the bank ledger contains the Bank Name, Account Number and IFSC details. Tally recommends verifying these fields when the ledger is missing from the import list.

Can TallyPrime automatically reconcile bank transactions?

Yes. After statement import, TallyPrime can identify exact and potential matches between book entries and bank transactions for reconciliation.

Can TallyPrime create vouchers from a bank statement?

Yes. Imported bank transactions can be used to create vouchers, including multiple or consolidated voucher workflows where appropriate.

Where can I see an imported bank statement later?

Open Alt+G → Imported Bank Data, or go through Gateway of Tally → Banking → Imported Bank Data.

What should I do if I imported the wrong statement?

Use the bank-statement reset facility after reviewing whether any imported entries have already been reconciled or used. TallyPrime supports resetting imported bank data when necessary.

Do I need to import a file if I use Connected Banking?

Not necessarily. With supported Connected Banking accounts, TallyPrime can request the bank statement through the connected workflow and then bring it into the reconciliation process.

Does importing a statement automatically change my accounting books?

Think of the imported statement primarily as bank-side data used for matching and reconciliation. Where a bank transaction has no book entry, TallyPrime can help create the required voucher, but those transactions should still be reviewed and accounted for appropriately.

Make Bank Reconciliation a Review Task, Not a Data-Entry Task

The biggest benefit of importing a bank statement is not the import itself.

It is what happens afterward.

Without imported bank data, an accountant may spend a large part of the reconciliation process simply comparing one line with another.

With the statement inside TallyPrime, the software can do much of that comparison first.

Exact matches can be dealt with quickly.

Potential matches can be reviewed.

Missing book entries stand out.

Bank charges and direct transactions become easier to spot.

The accountant spends more time asking, “Why doesn't this transaction match?” and less time asking, “Where is this transaction?”

That is a much better use of a reconciliation process.

Start with a properly configured bank ledger, download the statement directly from the bank rather than converting a PDF, use the preview before importing, and then work through the Bank Reconciliation Summary instead of treating the import as the final step.

Once this becomes a regular routine, bank reconciliation stops feeling like a month-end clean-up exercise and becomes a much more manageable part of everyday accounting.