Troubleshooting

Common Tally XML import errors, and how to fix them

Gateway of Tally → Import → Vouchers is strict about what it accepts. Here are the errors that come up most often, and what actually causes each one.

Error "Ledger does not exist" — the XML references a ledger name that isn't created in this company yet. Tally does not auto-create ledgers on import. Fix: create the ledger first (exact spelling matters), then re-import.
Error Voucher amount doesn't balance — total debit doesn't equal total credit in a voucher. Every voucher bank2tally generates is balanced by construction (one bank leg, one ledger leg, equal amounts); this error usually means a hand-edited or third-party XML file.
Error Vouchers silently skipped, dates outside the period — if a voucher's date falls outside the company's current financial year (or before its Books Beginning date), Tally won't post it. Check Gateway of Tally → F11/Company features for the active period before importing a statement that spans a year-end.
Risk Duplicate vouchers from importing the same file twice — Tally's XML import doesn't detect duplicates on its own; importing the same statement export twice creates two sets of vouchers. Keep track of which statement periods you've already imported.
Error "Nothing to import" / import completes with 0 vouchers — usually a malformed XML (wrong root tag, broken encoding) rather than a data problem. Re-download or re-generate the file rather than hand-editing it.

Prevention

Avoiding these before they happen

Most of these errors trace back to one of two habits: importing before every referenced ledger exists, or importing the same period twice without checking first. Before any XML import, it's worth creating (or confirming) the bank ledger and a Suspense ledger, checking Gateway of Tally → F11 for the active financial year against the statement's date range, and keeping a simple log of which statement periods have already been imported for each company. None of that is Tally-specific caution — it's the same discipline any bulk data import needs, accounting software or not.

When the error isn't listed here

Read the exact wording before assuming

Tally's import log is usually specific about which voucher failed and why, even when the wording is terse. If an error doesn't match anything above, the log entry itself — not a general troubleshooting guide — is the fastest way to the actual cause. If the XML came from bank2tally and something looks wrong in it, the file is plain text; opening it in a text editor to check the voucher in question usually clarifies whether the issue is in the file or in Tally's current company setup.

Questions

Why does Tally say a ledger does not exist during import?

Tally's XML import never creates ledgers automatically — every ledger name in the file must already exist in the company, spelled exactly the same way, before you import.

Can importing the same Tally XML file twice cause duplicate vouchers?

Yes. Tally does not check whether a voucher was already imported, so re-importing the same file creates a second, duplicate set of vouchers.

Will bank2tally's XML output ever import unbalanced?

No — every voucher it produces has an equal debit and credit leg by construction. An unbalanced-voucher error points to a hand-edited or different tool's XML file.

Try it on your own statement

One free conversion, no signup needed.

Convert a statement free