For TallyPrime's built-in bank-statement import, do not assume a PDF is an accepted source file. TallyHelp currently lists bank-portal statements in CSV, Excel, and MT940 formats for that import feature, and says PDF and third-party-converted files are not supported by it. A separate workflow that imports Tally XML is different; check the instructions for your Tally release and test the output in a sample company.
Two workflows that sound similar
Bank Statement import reads a bank statement file in the formats supported by Tally's banking feature. The downloaded statement structure and the bank's format matter.
XML import reads a structured Tally-compatible XML file. A PDF-to-XML tool first extracts transactions from the PDF and then creates that separate import file. The fact that Tally's bank-statement feature rejects a PDF does not by itself establish whether a particular XML file is compatible with your company or release; verify it through the relevant XML import workflow.
Check the official instructions
See Tally's current bank statement import FAQ and bank statement import guide. Tally may update supported formats and menu steps; confirm the instructions against the version installed in your office.
If your source is a PDF
- Keep the bank-issued PDF as the source record.
- Use a workflow that explicitly produces a format your Tally process can accept.
- Compare extracted rows, dates, signs, and balances with the PDF.
- Test the file in a backup or test company and confirm the imported vouchers.
- Reconcile the result before using the process for routine bookkeeping.
Doxify prepares reviewed transaction data and Tally XML from bank statement PDFs. The PDF-to-Tally XML walkthrough explains that workflow; always validate the import in your own Tally setup.