How to Import Excel to Tally: Step-by-Step Guide (Without Errors)
How to Import Excel to Tally: Step-by-Step Guide (Without Errors)
Troubleshoot Excel to Tally purchase import errors. Learn how to parse tally.imp log logs, resolve XML errors, and validate ledger mapping fields.
Who is this for: Tally Automation
Importing transactions from PDF file sheets into Tally Prime is a standard bookkeeping workflow for companies and CA firms in India. However, the import gateway can be sensitive. One incorrect cell value, date format discrepancy, or misspelled ledger name will block the import, leaving you with cryptic logs or silent failures. This guide covers how to debug and resolve invoice-to-Tally purchase import errors.
Table of Contents
1. Reading and Understanding the tally.imp Error Log
When an Excel or XML import fails, Tally Prime does not display the exact error message on the main screen. Instead, it logs the failure details in a local file named tally.imp.
To view this file, go to your TallyPrime installation folder (usually located at C:\Program Files\TallyPrime or C:\TallyPrime) and open tally.imp with Notepad. Scroll to the bottom of the document to see details of the most recent import attempt.
Example tally.imp Log Entries:
LINE 45: <Line Number>: Ledger "Aurobindo Pharma" does not exist!
LINE 82: <Line Number>: Date "25/05/2026" is out of range or invalid format!
LINE 110: <Line Number>: Stock Item "Paracetamol 650" has missing UOM "STRIP"!
2. Five Most Common Excel Import Errors & Fixes
1. Date Format Mismatch
Problem: PDF files often format dates as '25/05/26' or '25-05-2026', which Tally's import parser rejects.
Fix: Format the Date column in Excel as a Custom type: YYYYMMDD or DD-MMM-YYYY.
2. Ledger Spelling & Case Differences
Problem: A party ledger spelled as 'Jindal Steel' in Excel won't match a ledger named 'Jindal Steel & Power Ltd' in Tally.
Fix: Match Excel cell names to Tally ledger names exactly, including spaces and symbols, or use an utility that supports ledger aliasing.
3. Missing Stock Item or UoM Masters
Problem: The import fails if the stock item name or its Unit of Measurement (e.g. PCS, KGS) doesn't exist in Tally's database.
Fix: Pre-create missing stock masters in Tally before running imports, or configure your import tool to auto-create them.
4. Tax Math Inconsistencies
Problem: Discrepancies of even a few paise in CGST/SGST/IGST calculations between Excel totals and Tally's expectations will block the import.
Fix: Ensure Excel tax formulas use standard rounding rules: ROUND(Value, 2).
3. Dealing with XML Compilation Codes & Tags
If you are converting PDF files to XML format using third-party templates, syntax issues can prevent imports. Ensure that:
- XML tags are closed correctly (e.g.,
<VOUCHER>must have a matching</VOUCHER>). - No illegal characters (like raw ampersands
&) are used. Use&in XML strings to avoid parsing errors.
4. Troubleshooting Tally Prime Release 4/5 Native Mapper
TallyPrime Release 4.0 and 5.0 include a built-in Excel import mapping tool. If you encounter issues while using this module:
- Check the active company file: Confirm the correct client profile is loaded before starting imports.
- Review the column mapping profile: Go to Import > Manage > Mapping Templates and verify that headers like 'Voucher Date' are mapped to the correct columns.
- Clear duplicate rows: Ensure that row groupings (linking item rows to a single voucher header) are configured correctly to prevent duplicate voucher creation.
5. Tally Native Mapping Errors vs. TrulyInvoice Zero-Spreadsheet Automation
TallyPrime's native Excel import mapper is notoriously sensitive. Users regularly face native mapping errors such as unmapped date formats, unaligned ledger names, column type mismatches, and multi-line item structure errors. Resolving these issues requires painstaking PDF formatting, formula checks, and constant manual template adjustments.
Instead of wasting hours troubleshooting spreadsheet structures, TrulyInvoice provides a PDF-based, zero-spreadsheet alternative. Rather than compiling complex templates, you simply drag and drop your invoice PDFs. The AI OCR engine extracts invoice data, performs pre-flight ledger validation, and syncs everything directly into Tally without touching an Excel sheet.
Skip the Spreadsheets: PDF-to-Tally Automation
Eliminate Excel template mapping issues entirely. Try TrulyInvoice to sync purchase invoices from PDF files directly.
Get Started for FreeFrequently Asked Questions
Where is the import error log file (tally.imp) located?
The 'tally.imp' log file is located in the local directory where your TallyPrime application is installed (e.g., C:\Program Files\TallyPrime). Open it with Notepad or any text editor to view detailed logs of the failed import.
What does 'Ledger does not exist' mean during import?
This error occurs when a supplier ledger name or tax ledger name in your Excel sheet doesn't match Tally's ledger names exactly. Tally is case-sensitive and spacing-sensitive. Ensure ledgers exist in Tally or toggle 'Auto-Create Ledgers' in your import utility.
Why does my date format trigger an import error?
Tally requires a specific date format: DD-MMM-YYYY (e.g., 25-May-2026) or YYYYMMDD (e.g., 20260525). If your Excel sheet uses formats like DD/MM/YY, Tally will fail to parse it and skip the voucher.
How can TrulyInvoice validate my Excel sheet before importing to Tally?
TrulyInvoice provides a free Excel template validator page to check date formats and verify that GSTIN structures are valid locally before importing.
Chartered Accountant & Accounting Automation Specialist