Arjun stared at the blinking cursor on his laptop screen. The coffee beside him had gone cold two hours ago. Outside his small office in Ahmedabad, the city slept, but for him, the nightmare had just begun.
It was 1:17 AM. His client, Shanti Enterprises, had audited their books in TallyPrime (Release 11). The problem? Their new investor, a grumpy traditionalist named Mr. Mehta, refused to upgrade his ancient Tally.ERP 9 (Release 10). “If it isn’t broken, don’t fix it,” Mehta had barked over the phone. “Convert the data to Version 10 by morning, or the deal is off.”
But there was a ghost: The opening balance for “Prepaid Insurance” was off by ₹12. He traced it to a journal entry in v11 that used an “Adjustment Period” field—a feature v10 ignored. He manually entered that ₹12 correction via a journal voucher in v10. how to convert tally data version 11 to 10
Arjun opened TallyPrime (v11) and began a systematic extraction.
On a separate folder, he installed Tally.ERP 9 (Release 10) – the target version. He created a new, empty company named “Shanti_Converted_v10.” Then he opened the Excel files. The v11 export had extra columns: Is GST Registered? , Bill-wise expiry dates , and a weird UDIMasterType that v10 would vomit on. Arjun stared at the blinking cursor on his laptop screen
Arjun groaned. He was losing the war.
At 5:58 AM, he exported the final Company Data Backup from Tally v10 as a .900 file (the old format). He emailed it to Mr. Mehta with a single line: It was 1:17 AM
Of course. v11 had enhanced date handling for e-invoicing. v10 used a simpler calendar.