These are TallyPrime's own import errors. Each one below has a fix that works whichever route you used to get the data in, so you can clear the entry you are stuck on today.
Ledger does not exist
What you see. The import stops, or the voucher is skipped, and the log names a ledger.
What it means. Tally will not create an account on your behalf during an import. If the name in your file is not already a ledger in the company — down to the spelling, the spacing and the ampersand — Tally treats it as unknown and refuses the entry.
How to clear it
- Open the company the import is going into. Gateway of Tally > Chart of Accounts > Ledgers, and check the exact spelling of the name your file uses.
- Watch for the differences that are invisible in a spreadsheet: a trailing space, "and" against "&", "Pvt Ltd" against "Pvt. Ltd.", or two spaces between words.
- Create any genuinely missing ledger first, under the right group, then run the import again.
The import "worked" but nothing appeared
What you see. Tally reports the import as complete. The vouchers are not in the day book.
What it means. Tally writes the reason to a plain text file rather than showing it on screen. The file is named tally.imp and it sits in the Tally program folder, not with your company data. It is the only place the real error is recorded, which is why an import can appear to succeed and do nothing at all.
How to clear it
- Open the folder Tally is installed in and find tally.imp. Open it with Notepad.
- Read from the bottom — the newest run is at the end of the file.
- The line naming a ledger, a date or a voucher number is the actual failure. Fix that one thing and re-run.
Date out of range, or dates land in the wrong month
What you see. Entries are rejected, or they post to a month you did not expect.
What it means. Two separate causes. The date may fall outside the financial year the company is open in, in which case Tally refuses it. Or the day and month have swapped, because a statement written 03-04-2026 is read as 3 April by one system and 4 March by another.
How to clear it
- Check the period the company is open in. Alt+F2 sets it; a date outside that range will not post.
- In the spreadsheet, format the date column explicitly as DD-MM-YYYY before you do anything else. Do not rely on how it looks on screen.
- Spot-check the entries that fall in the first twelve days of a month — those are the only ones a day/month swap can hide in.
Debit and credit do not match
What you see. The voucher is rejected as unbalanced.
What it means. The two sides differ, usually by a rounding fraction or because a row carries a value in both the debit and the credit column. A bank statement exported to Excel often keeps more decimal places than it displays, so a total that looks right on screen is out by a paisa.
How to clear it
- Total the debit column and the credit column separately in the spreadsheet and compare them before importing.
- Round the amount column to two decimal places as a value, not as a display format.
- Check for rows carrying a figure in both columns — those are usually the culprit.
The same entries posted twice
What you see. The bank ledger shows every transaction twice after a second import.
What it means. Nothing in a file-based import knows what you posted last time. Run the same statement again, or a statement whose date range overlaps the previous one, and Tally accepts it as new work.
How to clear it
- Open the bank ledger for the period and sort by date to find the repeats.
- Delete the extra vouchers rather than editing them, so the audit trail stays clean.
- Keep a written note of the date range you posted for each account, and make the next export start the day after it ends.
The pattern behind all five
Four of these five exist because the data travels as a file. A file is prepared outside Tally, Tally reads it in one pass, and anything it cannot match is written to a log you have to go and find. Nothing is checked while you can still do something about it, and nothing remembers what you posted last time.
Posting entries straight into the company you already have open removes the file and the import screen. You see each row with the ledger it is going to, you change what is wrong before anything posts, and there is no log to decode afterwards. That is what this extension does, and it is free.
Skip the file entirely
Import the Excel or CSV your bank already gives you, check every row, and post it into the TallyPrime running on your own computer. No XML file, no import screen, no sign-up.
Add to Chrome — FreeQuestions
Where is the tally.imp file?
In the folder TallyPrime is installed in, not in your company data folder. Open it with Notepad and read from the bottom — the most recent import is written at the end.
Why does Tally not create the missing ledger by itself?
An import is deliberately not allowed to create accounts. If it were, a typo in a narration would silently open a new ledger and your trial balance would grow names nobody recognises. Tally refuses the entry instead, and expects you to create the ledger under the group you intend.
Can I avoid these errors entirely?
Most of them are properties of the file-and-import route: a file is prepared, Tally reads it in one pass, and anything it cannot match is written to a log you have to go and find. Posting entries directly into the open company removes the file and the import screen, so there is nothing to mis-map and no log to decode. You still review every row before it posts.
I fixed the error and re-imported. Now everything is duplicated.
The first run posted some vouchers before it stopped. Open the bank ledger for that period, sort by date, and delete the repeated vouchers rather than editing them so the audit trail stays intact.
Sources
Not affiliated with, endorsed by, or sponsored by Tally Solutions Pvt Ltd. “Tally” and “TallyPrime” are trademarks of Tally Solutions Pvt Ltd, used only to indicate compatibility.