The short version
Importing the bank statement is the step that turns bank reconciliation from typing dates into reviewing exceptions, which is why it is usually the first piece of Tally automation a finance team sets up. On TallyPrime Release 6.0 or later the whole flow takes a few minutes per bank account.
- Enable auto reconciliation on the bank ledger. Alter the ledger, set Enable Auto Bank Reconciliation to Yes, and set the Reconciliation Beginning Date. This is a one-time setting per bank account.
- Download the statement in Excel, CSV, or MT940. Use the same date range as the period you are reconciling. One file per bank account.
- Open the Bank Reconciliation report and press Alt+O. Select the file. TallyPrime reads the bank's format and flags duplicate lines.
- Reconcile exact matches with F8, review potential matches with Alt+S. Exact matches agree on amount, date, and instrument number. Potential matches are suggested on instrument date, amount, and party.
- Create entries for missing lines with F7 or Alt+F7. F7 creates one voucher from a bank line; Alt+F7 combines several lines, such as a month of bank charges, into one entry.
Prepare the file so the import works first time
Most failed imports are file problems, not Tally problems. Check these before pressing Alt+O.
- Use the bank's Excel, CSV, or MT940 download. TallyPrime does not import PDF statements. If you only have a PDF, download the Excel or CSV version from net banking instead of converting by hand.
- Keep the bank's original columns. Do not merge cells, delete header rows, or re-sort the sheet. Tally recognises the bank's own layout.
- Match the date range to the period. Overlapping ranges are caught as duplicates, but a clean range keeps the review short.
- Record instrument numbers in your vouchers. Cheque and UTR numbers on payment and receipt vouchers are what turn potential matches into exact matches.
Common import errors and how to fix them
| Problem | Likely cause | Fix |
|---|---|---|
| Import option not available | Release older than 6.0, or auto reconciliation is off for the ledger | Upgrade to Release 6.0 or later and enable auto reconciliation on the bank ledger |
| Format not recognised | Edited sheet, merged cells, or a converted PDF | Download a fresh Excel or CSV file from net banking and import it unedited |
| Many lines land in potential matches | Vouchers missing cheque or UTR numbers | Add instrument numbers on vouchers going forward; confirm current pairs with F8 |
| Closing balances still differ | Opening BRS not entered, or a line was imported twice | Enter the opening BRS (Alt+H) and check the duplicates Tally flagged |
| Customer receipts stay unmatched | UPI or NEFT credits never booked in Tally | Create the receipt from the bank line (F7) and settle it against the party's bills |
After the import: dealing with what does not match
A clean import usually reconciles 97 to 99 percent of lines on its own. The rest, bank charges, interest, unrecorded customer receipts, and uncleared cheques, are the lines that take time. Our full guide to bank reconciliation in Tally Prime walks through manual BRS, auto reconciliation, and a fix for every type of unmatched line.
Where AI takes over after the import
TallyPrime tells you which lines did not match. It does not tell you why, or what to post. KolossusAI reads each unmatched line, gives the likely reason, prepares the entry, and posts it to Tally only when you approve, alongside bulk purchase bill import, one-click entries, and chat with your Tally. See Tally automation with AI for how it works; it is ₹10,000 a year for web and mobile with a 14-day free trial.