Manually entering bank transactions into Tally Prime or Tally ERP is one of the most time-consuming tasks in a CA's workflow. A single client with 300 transactions a month means hours of repetitive data entry — and hours of opportunity for errors.
The good news: Tally Prime and Tally ERP support XML import, which lets you bypass manual entry entirely. Upload a properly formatted XML file and Tally creates the vouchers automatically. This guide walks through exactly how to do it.
What you need before you start
- Tally Prime or Tally ERP (supported versions with XML import)
- Your client's bank statement in PDF format
- A way to convert the PDF to Tally-compatible XML (covered below)
The key step most guides skip is the conversion. Tally Prime and Tally ERP cannot read a PDF directly — they need an XML file in a specific format called TallyXML. Getting from PDF to that XML is where most CAs get stuck.
Step 1: Download the bank statement as a PDF
Log in to your client's bank's internet banking portal and download the account statement as a PDF. Most banks offer this under Accounts → Account Statement → Download as PDF.
A few things to keep in mind:
- Format: Always download the native PDF (not an Excel or CSV) — the native PDF gives the AI more reliable layout information to work with.
- Date range: Keep it to one quarter or one month at a time if the statement is very long. Most banks limit downloads to 12–24 months.
- Password protection: Some banks email password-protected PDFs. Remove the password first using Adobe Acrobat or a PDF unlocker before the next step.
Once you have the PDF, you're ready to convert it.
Step 2: Convert the PDF to Tally Prime and Tally ERP XML
This is the step that used to require either expensive software or painful manual work in Excel. AI tools like Doxify handle it in seconds.
Here's how:
- Go to doxify.in and sign in (or create a free account — your first 100 pages are free).
- Click Convert in the top navigation and upload your bank statement PDF.
- Click Convert. Doxify's AI reads the statement and extracts every transaction — date, narration, debit amount, credit amount.
- Review the extracted transactions in the preview screen. You can edit any line if needed.
- Click Download XML to save the Tally Prime and Tally ERP-compatible XML file.
The entire process takes under 30 seconds for a typical 10–15 page statement. The AI works with any Indian bank — HDFC, SBI, ICICI, Axis, Kotak, Union Bank, Canara, PNB, Bank of Baroda, and more — without needing bank-specific templates.
Step 3: Import the XML into Tally Prime or Tally ERP
Now that you have the XML file, importing it into Tally Prime or Tally ERP is straightforward.
- Open Tally Prime or Tally ERP and select the company you want to import into.
- Go to Gateway of Tally → Import.
- Click Vouchers (or select XML if you see that option).
- Browse to the XML file you downloaded from Doxify and select it.
- Click Import. Tally Prime or Tally ERP will process the file and create the vouchers automatically.
When the import is complete, Tally Prime or Tally ERP shows an import summary. A typical 300-transaction statement imports in under 10 seconds.
Step 4: Verify the imported vouchers
After import, always do a quick verification:
- Day Book: Go to Gateway of Tally → Display More Reports → Day Book and check that all transactions appear for the correct date range.
- Closing balance check: Compare the closing balance in Tally against the closing balance on the bank statement. They should match exactly.
- Narration spot-check: Open 5–10 random vouchers and confirm the narration and amount match the original PDF.
If the closing balance doesn't match, the most common causes are: a missed transaction on a page break in the original PDF, a password-protected PDF that wasn't fully unlocked, or a statement that spans two separate accounts.
Common issues and how to fix them
Tally shows "Invalid XML" on import
This usually means the XML file was generated for a different version of Tally or was corrupted during download. Re-download from Doxify and try again. Make sure you're using the XML file exactly as downloaded — don't open and re-save it in a text editor.
Some transactions appear as "Unknown" ledger
Tally maps each voucher to a ledger account. If Doxify's XML references a ledger that doesn't exist in your Tally company, Tally will flag those vouchers. Solution: check the import summary, find the unmapped entries, and either create the missing ledger or reclassify those vouchers manually.
The PDF won't upload — "Invalid file"
Check that the PDF isn't password-protected or corrupted. Try opening the PDF in Adobe Reader first. If it opens correctly there, re-download from the bank portal and try again.
How much time does this save?
A 300-transaction bank statement typically takes an experienced accountant 3–5 hours to enter manually in Tally. With the PDF → XML → Import workflow, the same statement takes under 3 minutes — from downloading the PDF to having all vouchers in Tally.
For a CA firm handling 20 clients a month, each with one bank account, that's a saving of 60–100 hours of data entry per month. At that scale, the economics of a tool like Doxify become obvious.
Does this work with Tally ERP as well?
Yes. The XML import feature exists in both Tally Prime and Tally ERP. The steps are nearly identical — open the import option in your Tally ERP version and choose Gateway of Tally → Import Data → XML where applicable. The XML file Doxify generates is compatible with both versions.
Summary
Importing a bank statement into Tally Prime or Tally ERP is a 4-step process:
- Download the statement as a PDF from the bank portal
- Convert the PDF to Tally XML using Doxify
- Import the XML via Gateway of Tally → Import → Vouchers
- Verify the closing balance and spot-check vouchers
The entire workflow takes under 3 minutes per statement. If your firm processes bank statements regularly, this is the single highest-ROI change you can make to your Tally workflow this year.