Many accountants, Chartered Accountants (CAs), GST practitioners, and businesses using TallyPrime Edit Log encounter a situation where the GSTR-1 Excel export works perfectly, but the JSON export either fails, freezes, or does not generate the file.

This issue can be frustrating because:

• There are no GST exceptions.
• All vouchers appear valid.
• Excel export completes successfully.
• The latest version of TallyPrime is already installed.
• Yet JSON export refuses to work.

Since GST Portal accepts only JSON files for offline uploads (or APIs through GSPs), resolving this issue becomes critical before filing returns.

This article explains every possible technical reason, diagnostic procedure, and solution.

Understanding the Difference Between Excel and JSON Export

Although both exports originate from the same GSTR-1 report, internally they work differently.

Excel Export

Excel export is primarily a reporting function.

It simply extracts transaction data into spreadsheet format.

Excel export generally tolerates:

• Minor formatting inconsistencies
• Transactions not required for filing
• Certain incomplete optional fields

Hence Excel export is relatively forgiving.

JSON Export

JSON export is much stricter.

Before generating JSON, Tally validates numerous GST rules including:

• GSTIN format
• Invoice structure
• Tax breakup
• HSN data
• GST Return schema
• Document summary
• Voucher mapping
• GST classifications
• State codes
• Transaction consistency

If any internal validation fails, JSON generation may stop.

Common Symptoms

Users generally experience one of the following:

• JSON export does nothing
• JSON file is never created
• Export freezes
• Export window closes
• Tally hangs
• Empty (0 KB) JSON generated
• JSON export fails while Excel export succeeds

Scenario Covered

In this case:

• Latest TallyPrime Edit Log installed
• Excel export working
• No GST Exceptions
• No Uncertain Transactions
• Company data appears correct

This usually indicates that the issue is not basic GST data entry.

Possible Reasons

1. One Voucher Causes JSON Validation Failure

Even though Exception Report is clean,

one voucher may contain:

• hidden formatting issue
• incorrect GST classification
• corrupted GST object
• old migrated voucher
• invalid internal mapping

Excel ignores it.

JSON does not.

2. Section-wise GST Data Problem

Sometimes only one section fails.

Examples:

• B2B
• B2CL
• B2CS
• CDNR
• CDNUR
• Exports
• HSN Summary
• Document Summary

Recommendation:

Export individual sections separately.

This immediately identifies the problematic section.

3. HSN Summary Issues

Recent GSTN schema updates have made HSN validation stricter.

Possible issues:

• Missing HSN
• Invalid HSN length
• Incorrect UQC
• Wrong Quantity

Excel may still export.

JSON may reject.

4. Document Summary Issues

Recent GST schema revisions require proper document summary generation.

Incorrect:

• Invoice numbering
• Credit Notes
• Debit Notes
• Cancelled invoices

can interrupt JSON generation.

5. Transactions Marked for Deletion

If vouchers are:

Marked for Deletion on GST Portal

they may interfere with JSON generation in some releases.

Verify these transactions.

6. Company Data Corruption

Internal database corruption may affect:

• GST Objects
• Voucher indexes
• Internal collections

Even if vouchers appear normal.

Run:

Verify Company Data

and repair if required.

7. Old Migrated Data

Companies upgraded across multiple Tally versions may contain legacy GST objects.

Especially if migrated from:

• ERP 9
• Prime Release 1
• Prime Release 2
• Prime Release 3

These objects sometimes fail newer JSON schema validation.

8. Installed TDL

Custom TDL may interfere with:

• Export Collections
• Voucher Objects
• GST Functions
• XML Objects

Disable all TDLs temporarily.

Test JSON export again.

9. Antivirus Blocking JSON Creation

Some endpoint security software monitors:

• JSON files
• Temporary files
• GST folders

Temporarily disable antivirus.

Retry export.

10. Windows Folder Permissions

Export only to:

C:\GST\

Avoid:

• Desktop
• OneDrive
• Network folders
• Long folder names
• Special characters

11. Windows Security

Try:

Run TallyPrime as Administrator.

Sometimes Controlled Folder Access blocks JSON creation.

12. GST Schema Mismatch

Sometimes:

Latest GST Portal

changes schema before software vendors release updates.

Result:

Excel works.

JSON fails.

Always install latest Tally release.

13. Company Contains Invalid Historical Transactions

Transactions outside return period may still affect:

• Document numbering
• GST sequence
• Amendment references

14. Internal JSON Generator Bug

Occasionally,

certain TallyPrime releases contain bugs affecting JSON export.

Symptoms:

• All companies affected
• No exceptions
• Excel works
• JSON fails

Usually resolved through hotfix updates.

Step-by-Step Troubleshooting

Step 1

Update TallyPrime.

Step 2

Check:

GSTR-1

No Exceptions

Step 3

Verify Company Data.

Step 4

Disable TDL.

Step 5

Export to:

C:\GST\

Step 6

Run as Administrator.

Step 7

Disable antivirus temporarily.

Step 8

Export individual GST sections.

Step 9

Check whether:

HSN Summary

causes failure.

Step 10

Check:

Marked for Deletion

transactions.

Step 11

Test with another company.

If another company exports successfully,

problem is company-specific.

Step 12

Create a new sample company.

Generate one invoice.

Export JSON.

If sample company works,

existing data requires investigation.

Advanced Diagnostics

Check:

• TallyPrime.log
• tsf*.log
• Tally.imp

inside Tally installation folder.

These logs sometimes indicate:

• JSON validation failure
• Collection errors
• Export exceptions

Best Practices

• Always keep latest Tally release.
• Backup before upgrades.
• Verify company periodically.
• Avoid unnecessary TDL.
• Keep GST masters clean.
• Use proper HSN codes.
• Maintain sequential invoice numbering.
• Review document summary before filing.

Conclusion

When Excel export works but JSON export fails, the problem is rarely simple GST data entry. It is usually related to stricter JSON validation, internal voucher inconsistencies, HSN or document summary issues, company data integrity, TDL interference, folder permissions, antivirus restrictions, or release-specific bugs.

A systematic troubleshooting approach—verifying company data, exporting section-wise, testing with a sample company, disabling custom TDLs, checking export permissions, and reviewing internal logs—helps identify the exact cause quickly. Following these steps minimizes filing delays and ensures smooth GSTR-1 JSON generation in TallyPrime Edit Log.

#TallyPrime #TallyEditLog #TallyGST #GSTR1 #GST #GSTReturn #GSTPortal #JSONExport #ExcelExport #Accounting #Bookkeeping #CharteredAccountant #CA #TaxConsultant #GSTCompliance #GSTIndia #GSTFiling #BusinessAccounting #AccountingSoftware #Finance #Taxation #GSTN #HSN #Invoice #GSTAudit #GSTTroubleshooting #TallySupport #TallySolutions #GSTSoftware #GSTUpdate #AccountingTips #BusinessSolutions #FinancialManagement #IndirectTax #IndiaBusiness #CompanyAccounts #TaxReturn #OfficeAutomation #ERP #DataValidation #SoftwareSupport #TaxProfessional #TallyPrimeHelp #GSTExpert #ExportError #JSON #Excel #BusinessIndia #FinanceTechnology #EnterpriseSoftware