Common Tally import errors and how to fix them

Tally's XML import is well-designed — when your data matches what it expects. When it doesn't, you get errors that range from cryptic to completely silent (the import "succeeds" but data is wrong). Here are the most common issues and how to fix them.

Error: "Date format not recognized"

What's happening: Tally expects dates in a specific format (usually DD-MM-YYYY or DD/MM/YYYY). If your import file has dates in a different format — or dates as text strings — Tally rejects the row or imports it with a wrong date.

The fix: Ensure your export tool formats dates consistently. Lightrr exports dates in Tally's expected format by default. If you're building your own import file, use the date format specified in Tally's import documentation for your version.

Error: "Ledger not found"

What's happening: The XML references a ledger name that doesn't exist in your Tally company data. This happens when the narration from the bank statement doesn't match any ledger in your chart of accounts.

The fix: Either create the missing ledgers in Tally before importing, or configure your import tool to map narrations to existing ledgers. Lightrr maps common narrations to standard ledger names and flags anything ambiguous for your review.

Error: Silent amount errors

What's happening: The import succeeds, but amounts are wrong. This is the most dangerous error because nothing alerts you — you only discover it during reconciliation when the numbers don't add up.

The fix: Always verify a sample of imported transactions against the original statement before processing the full batch. Lightrr shows every extracted amount alongside the source line, so you can verify before exporting.

Error: "Duplicate voucher number"

What's happening: You're importing the same statement twice, or two statements have overlapping transactions. Tally rejects the duplicate to prevent double-counting.

The fix: Check if you've already imported the statement. If you need to re-import, delete the original vouchers first. Lightrr generates unique voucher numbers per export to prevent this.

Error: Credit/debit direction reversed

What's happening: Credits are imported as debits and vice versa. This usually happens when the import tool doesn't correctly interpret the bank statement's credit/debit indicators.

The fix: Verify that your import tool correctly maps the bank's credit/debit indicators to Tally's Dr/Cr fields. Different banks use different conventions (Cr/Dr, +/-, receipt/payment). Lightrr handles this mapping automatically for 690+ Indian bank formats.

The bottom line

Most Tally import errors come from data that doesn't match what Tally expects — not from Tally itself. Using a tool that understands Tally's import schema and your bank's statement format eliminates most of these issues before they happen.