When TallyPrime does not recognize a bank statement format, start by identifying whether you have a bank-portal export or a PDF. Tally'sofficial import guidedescribes supported bank formats and advises contacting Tally support when a format is not available. Support depends on the bank and its specific file structure.
If you have a native bank export
Check Tally's current bank and format list, select the matching bank ledger, and confirm the export came from the bank's official channel. Do not assume that two CSV files are interchangeable or that renaming an extension changes the underlying format. If the bank should be supported, contact Tally support with the exact file type and Tally release. Keep an unchanged source copy and use a test company for troubleshooting.
If the client only has a PDF
The native statement importer is not the route for a PDF. Extract and review the transactions, then choose an output for the next accounting task: use a supported statement format for reconciliation where available, or Tally XML when the goal is to create vouchers. Excel or CSV may be more suitable for analysis and working papers. Readhow the two Tally import paths differbefore choosing.
Try a reviewed PDF workflow when it fits
Doxify is designed to extract transactions from bank statement PDFs, let you review rows and ledger assignments, and export Tally XML, CSV, or Excel. Try Doxify first with an approved representative PDF if voucher creation is your goal. Check dates, signs, balances, and ledger choices, then test the file in a backup company. This does not add support for an otherwise unsupported native bank-statement file; it gives you a separate PDF-to-voucher workflow to evaluate.
For the broader process, use theTally import guideand transaction review checklist.