Charter AI

7 Days Money Back Guarantee - Limited Time Offer before 31 October, 2026

Where do I find the Tally.imp log file and how do I read it?

When an import doesn't fully succeed, Tally's own documentation points to Tally.imp for the details behind a rejection — for example, a date-range error during import. TallyPrime's data-exchange documentation groups import problems into error messages (mapping/template issues), master-related exceptions, and voucher-related exceptions, so the fastest way to resolve a failed import is to work through whichever of those three categories the rejected rows fall into.

What Tally's documentation covers

TallyPrime's own "Import Data Errors and Resolutions" documentation splits import problems into three groups: error messages from mapping or template configuration (for example, a "from" value in a mapping range that isn't less than or equal to the "to" value, or a file Tally can't read at all — "Unable to read the file. Select a valid Excel file and try again"), master-related exceptions affecting ledgers, stock items and other masters, and voucher-related exceptions specific to individual transactions.

For a date-range problem specifically, the documentation directs you to "Check Tally.imp for details" — Tally.imp is where the specifics of what went wrong live, rather than trying to diagnose a failed import from the on-screen message alone.

How to work through a rejected import

Resolve failures by category rather than row by row where possible:

  1. Check whether the error is a mapping/template problem — fix the mapping template and re-try before touching the source data.
  2. If it's a master-related exception, create or correct the missing/mismatched ledger, stock item or other master, then re-import.
  3. If it's a voucher-related exception, correct the specific voucher rows named in the error before re-running the import for just those rows.
  4. Where Tally points to Tally.imp for details (for example on a date-range error), check it for the specifics rather than guessing from the summary message.
How Charter AI does this

Charter AI runs the equivalent checks before export, not after: an unbalanced voucher, an unresolved ledger, or a GSTIN that fails its checksum is flagged in the review queue, so the Tally Import XML you download only contains vouchers that have already passed. There's no separate import log to read because the checks happen before the file reaches Tally.

Start free 7-day trial

FAQs

Does a failed import undo the rows that did succeed?

Tally's documentation groups errors by category (mapping, masters, vouchers) rather than describing an all-or-nothing rollback, so check which specific rows or masters are named in the error before assuming the whole batch failed.

What's the difference between a master-related and a voucher-related exception?

A master-related exception is about the ledgers/stock items/other masters themselves (missing or mismatched), while a voucher-related exception is about an individual transaction row — the fix is different depending on which one you're looking at.

Related guides

Sources checked

Last reviewed 2026-09-23

Tally, Vyapar and other product names are trademarks of their respective owners. Charter AI is not affiliated with them.