Charter AI

7 Days Money Back Guarantee - Limited Time Offer before 31 October, 2026

Tally Prime bank statement import says "NOT A VALID FORMAT" — how do I fix it?

"NOT A VALID FORMAT" almost always means the file doesn't match what Tally's Bank Reconciliation importer expects, not that the file is corrupt. The two most common causes are: the statement was converted from PDF and picked up extra rows, missing headers or the wrong separators along the way, or the downloaded file was edited/re-saved after the fact — Tally's own documentation says an altered statement will trigger this exact message. Clean the file to a single plain sheet with the right date format and re-import.

What causes it

On a CAclubindia expert thread about this exact error in TallyPrime, the expert reply is specific: any extra rows, missing headers, or wrong separators in a converted file will cause "the 'not a valid format' error," and PDF-to-spreadsheet conversions are the usual source of that mess.

Tally's own Bank Reconciliation documentation gives a second, separate cause: importing a statement that's been edited or re-saved after download. It states that if the bank statement being imported has been edited or altered, "the error message 'Not a valid format' will be displayed while importing the statement" — so re-download a fresh copy rather than fixing an already-opened-and-saved file.

How to fix it

Work from a fresh, unedited download from your bank where possible, and clean it to Tally's expected layout before importing.

  1. Re-download the statement from net banking rather than reusing a file you've already opened and saved.
  2. Remove merged cells, blank rows and any extra columns so the sheet is one clean table: header row, then transaction rows only.
  3. Format dates as DD/MM/YYYY and remove currency symbols from the amount columns.
  4. Save as CSV or a plain Excel file with no formulas or filters applied.
  5. Re-import via Gateway of Tally > Banking > Bank Reconciliation > select the bank ledger > B: Import.
How Charter AI does this

Charter AI reads the bank statement — PDF, Excel or CSV — directly, so there's no manual reformatting step to get wrong. Every transaction is checked deterministically (voucher balance, GSTIN on the counterparty, duplicates) before it's marked ready, and the reviewed set exports as a Tally Import XML file you bring in through Tally's Import option.

Start free 7-day trial

FAQs

Does this error only happen on TallyPrime?

The exact wording was reported on TallyPrime 6.x, but Tally's own Bank Reconciliation documentation (written for Tally.ERP 9) describes the same message for an altered statement file, so the cause and fix apply to both.

I converted the PDF myself and the file looks fine — why does it still fail?

PDF-to-Excel conversions often add invisible formatting — extra blank rows, merged header cells, or numbers stored as text — that isn't obvious when you open the file but still breaks Tally's strict layout check.

Where do I get Tally's expected column layout?

Open the Bank Reconciliation import screen for the bank ledger — Tally shows the expected format there before you select a file.

Related guides

Sources checked

Last reviewed 2026-09-23

Tally, Vyapar and other product names are trademarks of their respective owners. Charter AI is not affiliated with them.