Tally Prime XML Purchase Voucher Format: Sample Schema & Alt+O Import Guide

Why Tally XML is the Industry Standard for Automated Bookkeeping

Unlike third-party ODBC desktop drivers or unverified TDL plugins that crash whenever Tally Solutions releases an update (such as Tally Prime 3.0 or 4.0), Tally's native XML transaction import engine has remained 100% backward compatible for over two decades.

By pressing Alt + O (Import) → Transactions, accountants can feed standard XML files containing hundreds of purchase vouchers in a single operation.

Key XML Tags for Tally Prime Purchase Vouchers

• <VOUCHER VCHTYPE="Purchase" ACTION="Create">: Defines a new purchase voucher entry.
• <PARTYLEDGERNAME>: Must match or create the Sundry Creditor ledger name.
• <ALLLEDGERENTRIES.LIST>: Defines debit (Purchase Account, CGST, SGST, IGST) and credit (Supplier) ledgers.
• <ISDEEMEDPOSITIVE>: Set to Yes for debits (purchases & taxes) and No for credits (vendor liability).

Common XML Import Errors in Tally and How EntryFlow Solves Them

1. "Date out of range": Invoices dated outside the current financial year or before books beginning date. EntryFlow validates invoice dates against Indian fiscal calendars.
2. "Ledger does not balance by 1 paisa": Rounding errors across multiple line items. EntryFlow applies automatic round-off ledgers to guarantee zero-paisa variance.
3. "Invalid HSN code": Tally Prime 4.0 requires mandatory 6/8 digit HSN codes for B2B transactions. EntryFlow verifies HSN codes against the GST tariff schedule.