How to Fix Excel to Tally Import Errors & Decode tally.imp Logs
How to Fix Excel to Tally Import Errors & Decode tally.imp Logs
Step-by-step diagnostic guide for decoding Tally import logs, fixing date formatting errors, resolving missing ledgers, and repairing duplicate voucher number blocks.
Who is this for: Technical Support & Troubleshooting
Importing transactions from Excel into TallyPrime using native mapping tools or third-party utilities can save hours of manual data entry. However, if your spreadsheet contains formatting issues, missing ledgers, or date mismatches, TallyPrime will abort the process or report zero imported vouchers.
This guide provides solutions for common Excel import errors in TallyPrime. Learn how to locate and read the tally.imp log file to fix import issues quickly.
Quick Answer: How to Fix Excel to Tally Import Errors (2026)?
TrulyInvoice recommends inspecting the tally.imp file in your Tally installation directory to locate exact failed lines. Ensure date formats are DD-MM-YYYY, ledger spellings match Tally masters, and voucher numbering permits duplicate imports or uses auto-increment.
- Check the tally.imp log file in the Tally folder for specific error messages.
- Fix 'Ledger does not exist' by matching exact spelling between Excel and Tally.
- Set date columns to DD-MM-YYYY or YYYYMMDD in Excel.
- TrulyInvoice AI automatically validates dates, ledgers, and math before syncing via Port 9000.
1. Locating and Reading the tally.imp File
Whenever an import operation fails in TallyPrime, the software writes detailed error descriptions to a diagnostic text file named tally.imp. This file is stored in your primary Tally installation folder (e.g. C:\Program Files\TallyPrime\tally.imp).
To read the file, right-click tally.imp and open it with Notepad. Scroll to the bottom to view details of your latest import session. The log uses a structured tag format:
<! LINE ITEM ERROR SUMMARY !> Date: 01-04-2026 | Time: 14:10:05 Voucher Type: Sales | Voucher No: INV-1002 Error: Ledger "Acme Retailer Pvt Ltd" does not exist! Error: Voucher Import Failed! ============================================
2. Diagnostic Breakdown of Common Errors
Below are the most common error entries found in the log file, along with their causes and step-by-step solutions:
❌ Error 1: "Invalid Date Format" / "Date out of range"
Cause:
TallyPrime expects dates formatted strictly as DD-MMM-YYYY (e.g. 01-Apr-2026) or YYYYMMDD. If your Excel file contains standard slash dates like 01/04/2026, the parser fails to interpret the value.
Resolution:
- Open your Excel template and highlight the Date column.
- Right-click the selected cells and choose Format Cells.
- Select Custom and enter
yyyymmddin the Type field. - Verify that no cells contain text-based dates like "1st April".
❌ Error 2: "Voucher Number already exists!"
Cause:
This error occurs when the company voucher numbering method is set to manual and "Prevent Duplicates" is enabled in Tally. If the voucher number you are trying to import matches an existing invoice voucher in your books, Tally blocks the transaction to prevent database corruption.
Resolution:
Change the target voucher numbering configuration in Tally (Gateway of Tally > Alter > Voucher Type > set Method of Voucher Numbering to Automatic or Multi-user auto), or append a unique prefix/suffix (e.g. -IMP) to your Excel voucher numbers.
❌ Error 3: "Ledger '[Ledger Name]' does not exist!"
Cause:
TallyPrime validation requires that the name of the ledger in your spreadsheet match the spelling of the ledger in your database exactly. If there is a typo (e.g. "Acme Retailers Pvt. Ltd." in Excel vs "Acme Retailers Pvt Ltd" in Tally), the import fails.
Resolution:
Correct the spelling in your Excel sheet to match Tally exactly, or create the missing ledger in TallyPrime before re-running the import.
❌ Error 4: "Stock Item '[Item Name]' does not exist!" or "UOM mismatch"
Cause:
When importing inventory-based sales or purchase invoices, TallyPrime checks the stock item registers. If the item name in Excel is missing or if the Unit of Measure (UOM) (e.g. "Pcs" vs "Box") is mismatched, the parser rejects the voucher.
Resolution:
Ensure that both the Stock Item Name and UOM unit symbols are configured in Tally before importing transaction details.
3. Advanced Spreadsheet Cleaning Checklist
To ensure smooth spreadsheet imports, run these basic cleaning checks on your PDF files before importing:
- Remove Merged Cells: Merged rows or columns will cause the mapping engine to read null values. Unmerge all cells in your data range.
- Delete Empty Rows: TallyPrime stops reading the file as soon as it encounters a completely blank row. Remove empty lines from your data.
- Strip Hidden Characters: Leading or trailing spaces in text cells (e.g.
" Acme Retailers") are difficult to spot but will cause ledger mismatches. Use the Excel formula=TRIM()to clean text columns. - Numeric Cell Format: Strip currency formatting, commas, and letters (e.g. replace "Nil" with 0). Columns containing amounts must be set to the Number format in Excel.
TrulyInvoice: Pre-Import Validation and Automated Error Fixing
Troubleshooting import failures manually is time-consuming. Finding typos, unmerging rows, and decoding the tally.imp log file slows down bookkeeping workflows.
TrulyInvoice solves this by validating your data before it is sent to TallyPrime. Its sync engine identifies errors on a web dashboard:
- Auto-Ledger Validation: TrulyInvoice validates your extracted transaction records and highlights mismatched ledger names before they hit Tally, allowing you to map or create them in bulk.
- Numeric and Date Formats: The system automatically reformats dates and cleans currency symbols from numeric columns.
- Safe Sync Connector: Connects to TallyPrime over a secure local Port 9000 connector, syncing transactions with flat pricing of plans starting at ₹399/month for unlimited volume.
Founder & Chief Architect of TrulyInvoice