E-invoicing requires certain businesses to report B2B invoices to the Invoice Registration Portal (IRP) before or at the time of issue. The portal validates the invoice and returns a unique Invoice Reference Number (IRN) and a signed QR code, which must appear on the invoice.
E-invoicing applies above a notified turnover threshold. It standardises invoice data across the GST system and feeds GSTR-1 and e-way bills, reducing reconciliation effort.
Under the bonnet the flow is machine-to-machine: the seller's system generates the invoice, converts it to the notified JSON schema, and transmits it to the Invoice Registration Portal. The IRN it receives back is a hash computed from the supplier's GSTIN, the financial year, the document type and the document number — which is why the same invoice can never be registered twice, and why the numbering series must never repeat within a year.
Coverage is wider than the word invoice suggests: B2B invoices, export invoices, and the credit and debit notes attached to them all need IRNs once a business is within the mandate, while B2C bills stay outside it. The QR code the portal returns is signed, which is what makes the printed invoice verifiable offline — anyone can scan it and confirm the document was really registered, and that its key details match what the seller reported.
The operational traps are mundane. An invoice issued without an IRN by a mandated business is not a valid tax invoice, which puts the buyer's credit at risk — large buyers increasingly refuse such documents outright. Editing an already-registered invoice in the books breaks the tie between the ledger and the IRP record. And because IRN data flows automatically into GSTR-1, a document cancelled on the portal but left alive in the books produces a mismatch that surfaces at filing.