E-Invoice JSON Generator – Create GST E-Invoice JSON Schema

Utility & Preparation Notice: This is an independent data preparation tool. The generated JSON should be validated against the applicable official government e-invoice schema and submitted via your authorized credentials on the official government IRP (e.g. einvoice1.gst.gov.in). Flow-Invoice does not submit filings directly to government servers.

Invoice Data Fields

Document & Transaction (DocDtls / TranDtls)

Tax Scheme

Supply Type *

Reverse Charge *

Doc Type

Invoice Number *

Invoice Date * Format: DD/MM/YYYY

Seller Details (SellerDtls)

Legal Name *

GSTIN *

Location / City *

Pincode *

State Code *

Buyer Details (BuyerDtls)

Legal Name *

GSTIN *

Place of Supply (POS) *

Pincode *

State Code *

Line Items (ItemList)

Generated E-Invoice JSON

0 bytes

{ "Version": "1.1", "TranDtls": {}, "DocDtls": {}, "SellerDtls": {}, "BuyerDtls": {}, "ItemList": [], "ValDtls": {} }

Want to verify this JSON? Test in Validator →

Structure of GST E-Invoice JSON Schema (v1.03)

The GST electronic invoicing standard is maintained by the Goods and Services Tax Network (GSTN) and the National Informatics Centre (NIC). Every JSON payload submitted to an IRP must strictly conform to the hierarchical object layout:

Version: Currently "1.1" or "1.03", identifying the schema version definition.
TranDtls: Details describing the taxation category, including TaxSch ("GST"), SupTyp ("B2B", "SEZWP", "EXPWP"), and RegRev ("Y" or "N").
DocDtls: Document serial classification, including Typ ("INV", "CRN", "DBN"), No (Document number), and Dt (formatted strictly as DD/MM/YYYY).
SellerDtls: Legal name, 15-digit GSTIN, address, location name, PIN code, and 2-digit state code of the supplier.
BuyerDtls: Legal name, GSTIN, place of supply (POS), delivery address, PIN code, and state code of the buyer.
ItemList: An array of line items detailing serial numbers, item descriptions, HSN/SAC codes, quantities, units of measure, assessable values, GST tax rates, CGST, SGST, IGST, and total line values.
ValDtls: Summary financials including cumulative assessable value (AssVal), cumulative CGST/SGST/IGST, rounding off adjustments (RndOffAmt), and total invoice value (TotInvVal).

Field Format Rules to Remember

Date Format: Dates must follow DD/MM/YYYY format. Submitting ISO formats (e.g. 2024-05-12) directly to the IRP will fail schema validation.
Document Number Restrictions: Maximum 16 characters consisting strictly of alphanumeric characters, hyphens (-), and slashes (/). Leading zeros or spaces must be formatted properly.
Mathematical Balance: ValDtls.AssVal must exactly equal the sum of AssAmt across all items in ItemList. Rounding discrepancies beyond ±₹2 will cause payload rejection.

Frequently Asked Questions

Yes, this tool produces structured JSON corresponding to the official NIC E-Invoice Schema v1.03. However, taxpayers must ensure that their registered business details and HSN codes meet their specific statutory filing conditions before official batch upload.

Direct API transmission pushes invoice data from enterprise software straight to the IRP programmatically. JSON file upload is used by businesses without active API credentials: they generate JSON files and manually upload them via the official portal’s Bulk Upload utility.

Yes! You can use our companion E-Invoice JSON Validator to check schema compliance, data types, GSTIN syntax, and tax math with one click.