If TallyPrime says “Not a valid format” while importing a bank statement, first check whether the selected bank and statement format are supported. Tally's import guideexplains that bank formats must be supported or configured. The file's extension alone does not prove its contents match the expected format.
Check these items before retrying
- Confirm the workflow. Open the bank-statement import route when your goal is reconciliation; a generic Excel import is a different operation.
- Check the bank and format. Select the matching bank ledger and the file type Tally lists for it. Do not rename a file's extension to make an unsupported format appear valid.
- Close the source file. Tally'sbanking FAQdescribes errors when a statement is already open elsewhere.
- Check access and dates. Make sure the file path is reachable and the statement period fits the reconciliation period.
- Preserve the original. Keep an unchanged copy before editing headers, columns, or dates.
If the error continues
Note the Tally release, bank ledger, selected file type, and exact error. Check whether an earlier attempt imported some rows before trying again. If the bank's native format is unsupported, contact Tally support and ask whether it can be configured. Do not repeatedly import the same file into a live company; use a backup or test company for unfamiliar formats.
When Doxify may help
If your source is a PDF and your goal is to prepare Tally vouchers, rather than import a bank's native reconciliation file, try Doxify's PDF-to-Tally workflow with a representative sample. Review the rows and ledger assignments, export the XML, then validate it in a backup company. Doxify does not turn an unsupported native bank format into a supported Tally statement format; these are different workflows. Read the PDF-versus-XML explanationand import checklistbefore changing your process.