GSTR1 JSON Errors and Resolutions: A Detailed Guide
- Farheen Mukadam
- Jul 14
- 6 min read
If the invoice information in GSTR1 is processed incorrectly during the upload process to the GST Portal, the status will be changed to Processed with Error and a link to generate an error report will be displayed in the Error Report column. You can download these error files in JSON format. We have a list of the common JSON issues seen by users, along with an explanation of each error and its fixes, to facilitate filing for businesses and CAs. Here is a complete guide on potential GSTR1 JSON errors and their respective solutions.
Table of Contents
Common GSTR1 JSON Errors and Solutions
The following list highlights the errors you may encounter when uploading your GSTR1 online, and the possible steps that can help address them.
Error number | Error description | Solution |
RET191106 | Error in JSON structure validation: There are either structural issues in the uploaded JSON file or the GSTN is unable to recognise the JSON file. | Ensure that the JSON file has the GSTIN. Verify that the supplied JSON file is the most recent, accurate, and hasn't been processed incorrectly in GSTR 1. |
RET191113 | The GSTIN is invalid. Please provide a valid GSTIN.: The GSTIN in the JSON file and the GSTIN of the customer or the GSTIN the GST account are different. | Verify that the JSON file was submitted to the appropriate GST account. Make sure the GSTIN that needs to be entered in the GST tool is accurate. Create a JSON file from the GSTIN. After saving, submit it to the GST Portal. Verify that the customer's GSTIN is current. |
RET191114 | Date is invalid. Date of invoice cannot be before registration date.: The selected invoice date falls prior to the customer's receipt of their GSTIN or GST registration. A business can start claiming the ITC (input tax credit) as soon as they receive their GSTIN. | Delete the customer's GSTIN that is listed on the invoices and move them to the B2C(S) section. Recalculate the summary of B2C(S). Reupload to the government website. Please be aware that since your customer was not registered for those invoice dates, he will not be eligible for input tax credit in these situations. |
RET191115 | Invoice number does not exist. Please enter a valid invoice number.: The invoice can include no more than 16 characters, including numbers, letters, special characters, hyphens, dashes, and slashes, which are represented by the symbols "-" and "/," respectively, as well as a special combination for the fiscal year (FY). | Ensure that a GST invoice number appears on every invoice. According to GST regulations, if an invoice has no invoice number, it must be assigned one and a JSON file must be created afresh. The item should be removed from the JSON and it should be uploaded again if the invoice is found invalid in any way. |
RET191124 | Original invoice is invalid. Original invoice cannot be tracked. Please enter the correct invoice number and date.: It's possible that the invoice was not uploaded or was written incorrectly. | Verify whether the invoice number "inum" that appears in the CDN has already been uploaded. Upload the invoice first, followed by the CDN, if it hasn't already been done. Verify whether the problem is associated with the credit/debit note invoice number. |
RET191133 | Invoices already exist with different CTIN or same CTIN. Please delete the existing invoice and re-upload again: If user uploads an invoice that already exists on the GST portal, this error will appear. | Verify if the invoice has already been posted to the GST system. Verify that the invoice data you are attempting to upload and the one that was previously uploaded are the same. Simply overlook the error and don't make any changes to the invoice if it has already been uploaded. The old invoice that is now on the government portal needs to be removed before any changes can be made. Upload the updated invoice along with the accurate JSON file now. |
RET191148 | No section data or Gross Turnover is available to process the request: Details of the invoice have not been provided | An alternative process (manual filing at the GST portal) must be used if a NIL return is being filed without the invoice. Before proceeding to the next step, it is mandatory to upload the invoices if a NIL return is filed. |
RET191150 | IGST is mandatory for interstate supply and CGST & SGST should not be present.: For interstate supplies, the SGST and CGST are incorrect, and for intrastate supplies, the IGST is incorrect. | For "inter-state" supply, eliminate the CGST and SGST rates. Include the IGST rate. Verify that the state code of your client is accurately entered in the Place of Supply. For "intra-state" supply, take the IGST rates off. Include the SGST and CGST rates. Verify that the state code of your client is accurately entered in the Place of Supply. . |
RET191166 | Decryption/Decoding failed: An issue in decoding the data has occurred. | Reach out TaxBuddy experts |
RET191175 | The rate entered is not valid according to the rate list: The GST rates on the uploaded invoices may be incorrect or erroneous. | The IGST rates are divided into seven slabs: 0%, 0.25%, 5%, 12%, 18%, and 28%. In contrast, there are seven slabs for the CGST and SGST: 0%, 0.125%, 2.5%, 6%, 9%, and 14%. The exact GST rate needs to be added to the invoice. Ensure that the JSON file contains the GST rates without the % symbol. Equal and accurate division of the CGST and SGST rates is required. |
RET191179 | The place of supply and state code of the supplier should be different for inter-state supply: The JSON file that appears next to the words "POS" contains the place of supply information for all B2C large invoices as well as B2B invoices. Every interstate supply needs to have a location that is distinct from the supplier's state. The location of supply must match the state for all intra-state supplies. | For "inter-state" supply, verify that your state code and your customer's state code are correct in the Place of Supply. For "intra-state" supply, verify that your state code and your customer's state code are correct in the Place of Supply. |
RET191205 | Tax amounts are not in line with the taxable value and the declared tax rate (percentage). Please edit the tax amount or taxable value: There are two instances of this error: 1. For the data previously uploaded but before February 22, 2018.2. With regard to uploads made after February 22, 2018 | Each line item's tax amount, as calculated from sales invoices or other similar records, should equal the taxable value * tax rate, rounded to the nearest two digits. For instance, the tax amount should be Rs. 28.15 if the taxable value is Rs. 100.53 and the tax rate is 28%. The GSTN will give an error for values like 28, 28.1, 28.148, 28.1484, 28.1, 28.20, and 29. Once the required adjustments have been made, the Excel data will be uploaded once more. |
RET291107 | The invoice no. (s) already exist in the GSTR 1.: According to the GSTN, the invoice number needs to be modified since the provider has already used it elsewhere. You can also claim ITC | After correcting the invoice number, it should be uploaded again. |
RET291109 | The GSTIN of the supplier is invalid.: The supplier's GSTIN number that appears on the invoice is incorrect. | Provide the correct GSTIN number of the supplier. |
RET291106 | Error in JSON structure validation: In addition to the uploaded JSON file possibly having structural issues, the GSTN is unable to identify the file. The JSON file should include the GSTIN number. | The most recent and accurate JSON file should be uploaded to the GST Portal with the appropriate GSTIN. |
Conclusion
Being aware of these errors and potential solutions can help you ensure a smooth GSTR1 filing, even if you encounter an error. If you feel stuck with GSTR1 JSON errors at any point, it is best to consult experts to help you address the issue.
Frequently Asked Questions
What is a JSON error in GSTR-1 filing?
If the invoice details are processed erroneously once it is uploaded to the GST Portal, the status will change to “Processed with Error”. Also, the Error Report column contains a link to generate an error report. These error files can be downloaded in JSON format.
What causes JSON errors while uploading GSTR1?
Among the frequent causes of JSON issues are inaccurate data format, problems with Schema validation, exceeding character restrictions for particular fields, and missing necessary fields, such as the invoice number, date, or GSTIN. Duplicate invoices, invalid GSTIN, tax mismatch errors, and a corrupt JSON file may also lead to a JSON error while uploading GSTR1.
How to open a GST JSON error file?
Step 1: Upload the JSON file that has the error report.
Step 2: Examine each section's errors
Step 3: Go through the Error Notifications
Step 4: Address the errors
Step 5: Examine the error report again.
What does the 'Duplicate Invoice' error in GSTR1 JSON indicate?
The "duplicate invoice" problem indicates that the GSTR1 already has the invoice number. Since the invoice number has been used elsewhere, it must be altered in order to fix the problem.
How do I prevent JSON errors in GSTR1 filing?
Use the most reliable GST Offline Tool to validate data; properly format data before creating JSON; verify GSTINs and HSN codes before uploading; eliminate duplicate invoices; and double-check JSON Schema Compliance.





