E-Invoice JSON Generator (India)

About the E-Invoice JSON Generator (India)

Make the e-invoice JSON file for the Invoice Registration Portal (IRP) from the sales data you already have: an Excel or CSV sales register (from Tally, Busy, Vyapar, Zoho or your own sheet), a Shopify, WooCommerce or Amazon export, or invoices saved by the Invoice Generator. Columns are matched once and remembered. Every invoice, credit note and debit note is checked the way the IRP checks it — GSTIN check characters, State and PIN codes, HSN/SAC digits, unit codes, CGST + SGST or IGST by the place of supply, item and invoice totals — and written in the IRP schema (version 1.1) for the portal’s bulk upload, split into files of at most 2 MB.

Once the portal has generated the IRNs, load its results to print each e-invoice with its IRN, Ack No., Ack Date and the signed QR code (with a Premium pass; the free preview shows the first pages marked). MySmartCoPilot never asks for your portal login and never contacts the IRP or a GSP: you upload the file yourself, and everything else happens in your browser.

Common uses

• Businesses above the e-invoicing turnover limit that bill from Excel, a shop platform or simple billing software without e-invoicing.
• Accountants preparing e-invoice files for several clients without filling NIC’s Excel macro workbooks by hand.
• Turning a month of Shopify, WooCommerce or Amazon B2B orders into one upload.
• Printing e-invoices with the IRN and QR code after a bulk upload, in one batch.

What goes into the file

• Seller: your details from step 1 — every e-invoice of a file belongs to one GSTIN.
• Document: type (INV, CRN, DBN), number (as in your sheet), date and supply type — B2B, SEZ with or without payment, export with or without payment, or deemed export; reverse charge, IGST on an intra-State supply and the e-commerce operator’s GSTIN when the columns have them.
• Buyer, ship-to and dispatch-from: name, GSTIN, address, location, PIN and State (the ship-to GSTIN when the sheet has one); for exports GSTIN URP, State 96, PIN 999999 and the buyer’s country code, which the IRP requires.
• Items: description, HSN/SAC (and whether it is a service), quantity and unit, unit price, gross amount, discount, taxable value, GST rate, IGST or CGST + SGST, cess and the item total.
• Totals: taxable value, taxes, document discount, other charges, round-off and invoice value.
• Credit and debit notes: the original invoice number and date. Exports: shipping bill, port, country, currency and whether a refund is claimed. E-way bill part (optional): mode, distance, transporter and vehicle from transport columns — Part-A only (no mode) when the vehicle or transport document the mode needs is missing.

Printing with the IRN and QR code

The IRP returns, for each invoice, the IRN, the acknowledgement number and date, the signed invoice and the signed QR code; NIC’s QR code procedure lets the taxpayer print that signed QR code on the invoice copy. After a bulk upload the portal’s results Excel lists them per invoice (the layout NIC’s own GePP tool imports); software that uses the IRP’s API gets the same in a JSON response. Load either one: the QR code is drawn from the signed text exactly, and the invoice details come from the signed invoice or from the sales data loaded above. To check the signatures, load NIC’s public key from the portal’s public keys page.

What it does not do

It does not generate IRNs. An IRN exists only once the IRP has accepted the invoice — through the portal’s bulk upload, which you do with your own login, or through API access that needs your own GSP or e-invoice API credentials. MySmartCoPilot asks for neither and sends nothing to the IRP; the file is made in your browser. It does not file returns either: e-invoice details reach GSTR-1 from the IRP.

Where the format comes from

Field names, lengths, allowed values and the 2 MB limit are those of the e-invoice portal’s bulk generation tools (EINVOICE_SCHEMA.xlsx, schema version 1.1) and its master codes; the business rules and the rounding tolerance follow NIC’s Generate IRN validations. E-invoicing itself is rule 48(4) of the CGST Rules, 2017, on CBIC’s tax information portal. The schema version is pinned and re-checked against the portal’s files with every release.

Limitations

• The IRP has the final word: it also checks things no file can show, such as whether a GSTIN is active or an IRN already exists for the document, and the time limit within which larger businesses must report invoices (see NIC’s release notes).
• Payment details, batch details, additional documents and other optional IRP blocks are not filled from the register.
• A results Excel without the signed QR codes cannot be printed with QR codes here; print those invoices on the portal (e-Invoice → Print) or load the response JSON.
• The prints are plain e-invoice copies without your logo or signature image; the Invoice Generator makes branded invoices.
• This is not an official NIC tool. The schema is pinned to version 1.1; when NIC publishes a new version, the tool is updated before it is used.

Privacy

Your sales data, the e-invoice JSON and the IRP results are read and written in your browser; nothing is uploaded. Your business details and column choices are kept in this browser’s storage. The optional HSN/SAC master is a static file of this site.