CSV to Tally XML Converter — TallyPrime & ERP 9 (FREE)
A month of bank rows, arriving in TallyPrime as finished Payment and Receipt vouchers instead of being typed one at a time. Upload a statement above to convert CSV to Tally XML, free: the ledgers are written into the file itself, and each voucher is numbered from its own contents so next month's statement can never collide with this one. Tally ERP 9 reads exactly the same file.
Not the file you need?
Why Use Our CSV to Tally XML Converter Tool?
The ledgers are written into the file
"Ledger does not exist!" stops most Tally XML imports, because Tally matches names exactly and will not invent one. This file declares its ledgers first, under the right parents — a ledger filed in the wrong group imports cleanly, then misreports in every statement Tally prints afterwards.
Voucher numbers that survive a second import
Most converters number vouchers PAY-001, RCT-001 and restart at 1 next month, so statement two collides with statement one and Tally either duplicates everything or refuses the rows. Each number here comes from the transaction's own content, so a genuine re-import is caught and two different statements never are.
Nothing to map, nothing to configure
No mapping template, no field-matching screen, no company name to type — SVCURRENTCOMPANY is deliberately omitted, so the vouchers land in whichever company you have open. A CSV to XML converter online with no signup, no install and no cap on vouchers.
How to convert CSV to Tally XML in three steps
Start with your bank's CSV
Downloaded from net banking, a card issuer, a payment gateway, or exported from a worksheet. Headers are optional and the column order makes no difference.
Upload the CSV
Use the box above, up to 10MB. Dates, narrations and amounts are located in the data itself, so there is no mapping template to build first.
Download the XML and import
There is nothing to set — download the .xml and import it in Tally. Money out becomes a Payment voucher, money in becomes a Receipt.
Why a Tally XML import stops before it starts
"Ledger does not exist!" halts the file
Tally looks up ledger names exactly. A trailing space, a different spelling or a ledger that was simply never created stops the import, and the vouchers referencing it are skipped. Setting "Ignore errors during data import" to Yes lets the rest through and writes the failures to the tally.imp log, but the missing ledgers still have to be made.
Native import will not take a converted file
Tally Prime does import bank statements directly, at Gateway of Tally → Alt+O → Bank Statement, and it will create vouchers from them. What it will not accept is a PDF, or any CSV or Excel file that was produced from a PDF — which is precisely the file most people are holding.
The second statement imports twice
A voucher number is Tally's only duplicate checkpoint on an XML import. Converters that number sequentially per file hand Tally the same numbers again next month, so it either duplicates the lot or, with Prevent Duplicates set, refuses genuine transactions.
Dates and company names fail quietly
Tally XML dates are YYYYMMDD and are validated against the open company's financial year, so a date outside it is rejected. Naming a company that does not match the open one produces "Could not set SVCURRENTCOMPANY" and the import never begins.
Who converts a statement into Tally vouchers
Indian SMEs on TallyPrime
A month of bank entries typed by hand is an afternoon gone. A bank statement to Tally XML converter turns that same statement into every Payment and Receipt voucher in one import.
Statements Tally won't accept
Tally's own bank statement import rejects PDFs and any CSV or Excel produced from one. The XML voucher route has no such restriction.
Banks outside Tally's list
Native import only understands specific bank layouts. If your bank, card issuer or payment gateway is not among them, the file is refused outright.
Accountants with many clients
Ledger names differ in every company file. Convert per client, rename the three declared ledgers once, and the vouchers land where they belong.
Re-importing a corrected file
Voucher numbers come from the row content, so re-importing the same statement is caught as a duplicate while a genuinely different one is not.
Tally ERP 9 users
The XML voucher format predates TallyPrime and is read by ERP 9 just as well, so an older installation is not left out.
Frequently Asked Questions — CSV to Tally XML Converter
QHow do I import a bank statement into TallyPrime from a CSV?
QCan TallyPrime import a bank statement without converting it?
QWhy does my import fail with "Ledger does not exist"?
QWhat is Tally XML?
QDoes this work with Tally ERP 9 as well as TallyPrime?
QWill importing the same statement twice create duplicate vouchers?
QWhat voucher types does the XML create?
QWhat does "Could not set SVCURRENTCOMPANY" mean?
QCan I convert Excel to Tally XML as well?
QIs this a general CSV to XML converter?
QIs there a CSV to Tally XML converter free download?
QMy dates were rejected. What went wrong?
QDoes my bank statement leave my browser?
Other Conversion Formats
Turn a CSV statement into Tally vouchers, not typing
Your bank sends CSV. TallyPrime wants vouchers. Convert CSV to Tally XML here in about ten seconds, then run the bank statement to Tally import at Gateway of Tally → Import Data → Vouchers. Free, no account needed, and there is nothing to install.