When generating an Invoice Reference Number (IRN) on the Invoice Registration Portal (IRP), an ERP export often fails before reaching business validation. The portal immediately rejects the JSON file if a field type is wrong, a date format is invalid, or a required block is missing. Because schema validation stops processing upfront, no IRN is generated, and the document is not registered on the portal.
Statutory basis of the e-invoice JSON schema
E-invoicing for notified taxpayers operates under Rule 48(4) of the CGST Rules, which mandates reporting invoice particulars electronically in Form GST INV-01. The technical structure is formally notified under Notification No. 60/2020-Central Tax. This standard prescribes exact technical keys, required parent arrays, data types, and permitted value enumerations.
If your accounting package outputs an integer where a decimal string is expected, or supplies an unlisted document type code, the IRP parser rejects the request instantly. Understanding the standard schema rules prevents repeated upload failures.
Common mistake: Attempting to create a new invoice number when a schema validation fails. Schema validation rejection means the IRP rejected the payload before registering it. Unlike a cancelled IRN, the original document number remains completely usable once the JSON error is corrected.
Common schema validation errors and fixes
Most JSON schema errors fall into four specific technical categories across the supplier, recipient, and item detail blocks:
1. Document type enumeration failure
Field 1.3 of the schema accepts only specific enumerated strings: INV for Tax Invoice, CRN for Credit Note, and DBN for Debit Note. Passing values like TAX_INV, INVOICE, or lowercase inv triggers an instant schema parsing rejection.
2. Recipient state code mismatch (Error 2265)
As documented in official NIC e-Invoice system error codes, Error 2265 indicates that the recipient GSTIN state code does not match the state code passed in the recipient details block. The first two digits of the 15-digit recipient GSTIN represent the state code and must align exactly with the state code passed in the JSON address block.
If your recipient has an inactive or cancelled GSTIN, check our guide on fixing e-invoice error 2283 for inactive recipient GSTIN.
3. Data type and number formatting mismatches
All currency values, including taxable value and tax amounts, must be numeric with up to two decimal places. Passing numbers formatted with commas such as "1,25,000.00" or enclosing numeric values in quote strings where numbers are expected causes schema parser failures.
4. Date format errors
All document dates must follow the strict DD/MM/YYYY format. Supplying dates in YYYY-MM-DD or DD-MM-YYYY format violates the regex validation patterns defined in the official schema.
Worked example: resolving tax value calculation in JSON payload
Consider an enterprise issuing a tax invoice for intra-state supply of engineering goods with an aggregate value of ₹1,00,000 subject to 18% GST (9% CGST and 9% SGST).
The billing software prepared the JSON payload with a rounding inconsistency where line totals did not equal the summary total, leading to a schema evaluation failure:
| Field Name | Erroneous Payload | Corrected Payload | Validation Rule |
|---|---|---|---|
| DocTyp | "INVOICE" | "INV" | Enumeration check: must be INV, CRN, or DBN |
| AssVal (Item) | 100000 | 100000.00 | Decimal precision up to 2 decimal places |
| CgstVal (9%) | 9000.00 | 9000.00 | Formula: 1,00,000.00 * 9% = 9,000.00 |
| SgstVal (9%) | 9000.00 | 9000.00 | Formula: 1,00,000.00 * 9% = 9,000.00 |
| TotInvVal | "1,18,000.00" | 118000.00 | Numeric float: no string commas permitted |
In this example, correcting the document type to INV, removing the comma from total invoice value, and formatting values to two decimals resolved the schema error on the subsequent submission.
Step-by-step procedure to fix schema validation errors
- Inspect the rejection log: Review the exact JSON path returned by the IRP or GSP error response. The log indicates the specific node and attribute causing the rejection.
- Validate against Form GST INV-01: Confirm that field names match case-sensitive schema specifications. For example, verify that item details are nested inside the ItemList array.
- Check state codes against GSTIN: Ensure that the supplier state code matches the first two digits of the supplier GSTIN, and the recipient state code matches the first two digits of the recipient GSTIN.
- Verify date formats: Confirm all dates follow DD/MM/YYYY format strictly.
- Re-submit original document: Upload the corrected JSON to the IRP. Because the earlier call failed schema validation, the document number remains available for IRN generation.
Frequently asked questions
What causes a JSON schema validation error during e-invoice generation?
A JSON schema validation error occurs when your payload structure or data types violate Form GST INV-01 specifications, such as string values in numeric fields, invalid document types, or missing mandatory fields.
Can an IRN be re-generated for the same document number after fixing the JSON error?
Yes. If the payload failed JSON schema validation, no IRN was generated on the portal. You can fix the payload errors and submit the same document number again.
Why does the IRP return Error 2265 for recipient details?
Error 2265 occurs when the first two digits of the recipient GSTIN do not match the state code passed in the recipient details block of the JSON payload.
Check your own GSTR-2B
Once your suppliers resolve e-invoice generation errors and file returns, reconcile your inward supplies against your books. Your GSTR-2B and purchase register files are read in your browser and never uploaded to any server.
Last checked: 22 October 2026. Sources: Rule 48(4) CGST Rules, Notification No. 60/2020-Central Tax, NIC e-Invoice System Error Codes.