E-invoice
E-invoices built to the NIC schema, IRP-ready.
Every B2B invoice generates an IRN payload and QR per schema v1.03. Production portal submission is on the roadmap.
What an e-invoice carries
Six blocks, every one a real field in the payload built from your invoice.
- 01
Document
Invoice number and date, with the transaction typed as B2B.
- 02
Seller
Your GSTIN, legal name and address.
- 03
Buyer
Their GSTIN, legal name, state and place of supply.
- 04
Lines
HSN, quantity, unit price, tax rate and the CGST, SGST and IGST split.
- 05
Values
Assessable value, tax totals and the invoice total.
- 06
IRN
The invoice reference number returned by the IRP, with the signed QR generated alongside.
From payload to portal
Three steps. The first is built today; the last is on the roadmap.
- 01
Payload prepared
Every B2B invoice generates the full IRN payload per the NIC e-invoice schema v1.03, QR included.
- 02
Sandbox validation
The same payload is checked against the NIC test IRP before anything is relied upon.
- 03
Production IRP connection
Live portal submission is on the roadmap. Until it lands, nothing is claimed that the gateway has not confirmed.
E-way bill payloads are prepared from sales invoices above the value threshold; portal connection is on the roadmap.
How it fits
The e-invoice is not a side artifact. It is one step in the same flow that reaches GSTR-1 and the ledger.
- 01
E-invoice generated
IRN payload prepared for the supply, QR alongside.
- 02
Lands in GSTR-1
The supply appears in the outward-return data for the period.
- 03
Posted to the ledger
The same invoice already debited receivables and credited revenue and output tax.
Your e-invoices, prepared and waiting for the IRP.
Start free. The payload is built from your invoices; the portal connection is next on the roadmap.