Bank Statement PDF to Tally XML

Tally won’t take a PDF, Excel or CSV of transactions — only XML. This builds that XML straight from your statement, with every entry already typed as a Payment, Receipt or Contra voucher. For TallyPrime and ERP 9, scanned or digital.

No signup to tryAuto vouchers100+ Indian banksFree to start

Click to upload or drag and drop

Supported formats:

PDF

PNG

JPEG

TIFF

Up to 25MB · PDF → Tally

Secure & Encrypted Conversion

All uploads are encrypted for your security

Trouble converting a file? Tell us — we fix issues fast. Report it

How it works

How to convert a bank statement PDF to Tally XML

Upload the statement

Add a bank or credit card PDF from net banking, or a scan of a branch-printed copy. It runs in the browser.

AI builds the vouchers

Each line is read and tagged as a Payment, Receipt or Contra voucher from its debit/credit column, with the narration kept.

Download a Tally XML

A Tally-ready XML — the one format Tally's import engine accepts — built for TallyPrime and Tally ERP 9.

The output

What a Tally XML looks like

Tally import XML wraps each transaction in a VOUCHER with a type and a LEDGERNAME Tally matches on. Toggle from the raw statement to the file.

statement.xml

Messy PDFClean Tally XML

<ENVELOPE>
 <HEADER>
  <TALLYREQUEST>Import Data</TALLYREQUEST>
 </HEADER>
 <BODY><IMPORTDATA>
  <REQUESTDESC><REPORTNAME>Vouchers</REPORTNAME></REQUESTDESC>
  <REQUESTDATA>
   <TALLYMESSAGE>
    <VOUCHER VCHTYPE="Receipt" ACTION="Create">
     <DATE>20240307</DATE>
     <VOUCHERTYPENAME>Receipt</VOUCHERTYPENAME>
     <NARRATION>NEFT - Acme Exports</NARRATION>
     <ALLLEDGERENTRIES.LIST>
      <LEDGERNAME>Bank Account</LEDGERNAME>
      <AMOUNT>-25000.00</AMOUNT>
     </ALLLEDGERENTRIES.LIST>
    </VOUCHER>
   </TALLYMESSAGE>
  </REQUESTDATA>
 </IMPORTDATA></BODY>
</ENVELOPE>

Why Tally XML

Built for Tally's import engine

The work isn't just extracting numbers — it's shaping them into vouchers Tally will accept on the first try.

Auto Payment / Receipt / Contra

Debit and credit columns are read and each voucher is classified the way Tally expects — no manual voucher-type picking.

The only format Tally imports

Tally won't take a PDF, Excel or CSV of transactions — it needs XML. This gives you exactly that, ready to import.

100+ Indian banks

SBI, HDFC, ICICI, Axis, Kotak and more — plus credit-card and overseas statements.

Posts to your bank ledger

Vouchers are written against your bank ledger with the statement narration carried into each one.

Reads scans too

OCR handles scanned and photographed statements — common with branch-printed passbooks and copies.

Tally-friendly dates

Dates are written the way Tally expects, so vouchers aren't rejected on a date-format mismatch.

Three things Tally checks before it posts

Most failed imports come down to these. Ledger name — the bank LEDGERNAME in the XML must match your Tally ledger exactly, so create it first (or let it post to Suspense). Financial year — a voucher dated outside Tally's active period is rejected, so convert a statement within the current FY. Duplicates — Tally doesn't de-dupe, so import one month at a time and back up the company data first.

Why XML, and not a PDF or Excel

Tally's import engine reads XML onlyfor transactions — a PDF or even an Excel of your statement can’t be posted directly. Converting to Tally XML (with the vouchers already typed) is the step that turns a statement into something Tally can record automatically, instead of re-keying every entry.

Importing

Import the XML into Tally

Two clicks from the Gateway — just back up first.

TallyPrime

Gateway of Tally → Import Data → Transactions → choose the .xml and confirm the bank ledger.

Tally ERP 9

Gateway of Tally → Import of Data → Vouchers → select the .xml; vouchers post to the matching ledger.

Private by default. Uploads are encrypted, the XML is built only from the transactions we extract, and the file isn’t kept once you’ve downloaded it — no account needed to try one.

Any bank

Tally XML from any bank's statement

Indian banks are first-class here, but the same extraction reads any institution's layout — so overseas and credit-card statements convert just as cleanly.

SBIHDFCICICIAxis BankKotakYes BankPNBBank of BarodaIDFC FirstIndusIndChaseBank of AmericaHSBCBarclaysNatWestWells FargoCitiANZDBSStandard Chartered+ any bank worldwide

Tally FAQ

Converting to Tally XML — common questions

QWill it import into TallyPrime and Tally ERP 9?

Both. In TallyPrime: Gateway of Tally → Import Data → Transactions → select the XML. In ERP 9: Gateway of Tally → Import of Data → Vouchers → XML. The same file works on either.

QHow are Payment, Receipt and Contra vouchers decided?

From the statement's debit and credit columns — money out becomes a Payment, money in a Receipt, and a bank-to-bank transfer a Contra. The converter sets the voucher type so you don't have to.

QWhy does my Tally import fail or post to the wrong ledger?

Almost always the bank ledger name. The LEDGERNAME in the XML must match your Tally bank ledger exactly — create the ledger first (or post to Suspense) and confirm the spelling matches.

QWhy was a voucher rejected on import?

Usually the voucher date falls outside Tally's active financial year, so Tally won't accept it. Set the right period in Tally, or convert a statement within the current financial year.

QWill re-importing the XML create duplicate vouchers?

Yes — Tally doesn't de-duplicate on import. Bring in one month at a time, use unique references, and back up your company data before importing.

QWhy can't I just import the PDF or Excel straight into Tally?

Tally's import engine only reads XML for transactions; a PDF or Excel of a statement can't be posted directly. Converting to Tally XML is the step that makes the data importable.

QCan I convert a scanned bank statement to Tally XML?

Yes — scanned and photographed statements are read with OCR first, then written to Tally XML, so branch-printed copies convert fine.

QWhich banks are supported?

100+ Indian banks — SBI, HDFC, ICICI, Axis, Kotak, Yes Bank, PNB and more — plus international banks and credit-card statements. Extraction reads each statement's layout rather than a fixed template.

QIs it free to use, and what happens to my statement?

You can convert on the free tier without an account; uploads are encrypted, the XML is built only from the extracted transactions, and the file isn't kept past the job. Locked PDFs prompt for the password to open them.

QHow accurate is the extraction?

Strong on digital and scanned statements, though no converter is perfect on every layout — check the voucher count and tie to the closing balance before you post.

Keep going