Business
E-Invoice JSON Generator (IRP schema)
Turn a spreadsheet of invoices into the JSON the GST e-invoice portal accepts — schema 1.1, one file for bulk upload — with GSTINs, PINs, HSN codes and the CGST/SGST or IGST split checked before you upload. Runs in your browser; nothing is uploaded here.
Privacy
Your file never leaves your device. It is read and converted by your own browser, so nothing is uploaded, queued or logged — which is what makes this safe for a client’s books.
Tips
- One row per line item: invoice number, date, buyer GSTIN and name, item description, HSN, quantity, unit, unit price, GST rate. Rows with the same invoice number become one invoice.
- The tax split is decided by the state codes — the first two digits of the seller’s and buyer’s GSTINs (or the place of supply you give). Same state, CGST + SGST; different, IGST. You cannot get this wrong by typing.
- Every GSTIN is checked against its checksum digit, PINs must be six digits, HSN four to eight, and totals are computed from the items, so what you upload is arithmetically consistent.
- Upload the file on the e-invoice portal (Bulk upload → JSON) or through your GSP. The portal returns the IRN, acknowledgement and signed QR for each invoice.
Frequently asked questions
Which schema version is this?
E-invoice schema version 1.1, the one the IRP has accepted since 2020 and still does. The output is an array of invoice objects, which is what the bulk upload takes; a single invoice is an array of one.
Can it generate the IRN or QR code?
No, and nothing offline can: the IRN is issued by the portal when it accepts the JSON. This produces the JSON the portal issues it against.
What about B2C, exports, SEZ?
Supply type can be set to B2B, SEZ with or without payment, export with or without payment, or deemed export. B2C invoices do not need an IRN (unless the dynamic QR rules apply to you) and are not e-invoiced.