E-invoicing under GST is the process of electronically reporting certain business-to-business invoices to a government-notified portal, which validates the invoice and returns a unique reference number before the invoice is treated as complete for GST purposes. It is not a new invoice format you design yourself — it is a validation step layered on top of the invoice you already raise. For businesses above the applicable turnover threshold, an invoice that has not gone through this process is not a valid tax invoice, regardless of how correctly it is otherwise prepared.
This guide walks through what e-invoicing actually involves, the step-by-step flow, what appears on a completed e-invoice, and how it feeds into your other GST filings.
What E-Invoicing Actually Does
At its core, e-invoicing standardizes how B2B invoice data is reported to the tax department in real time (or near-real time), rather than the department finding out about your sales only when you file GSTR-1 weeks later. Once an invoice is reported and validated, it is registered with a unique Invoice Reference Number (IRN), and that data is meant to auto-populate into your GSTR-1 and, in principle, flow through to your buyer's GSTR-2B.
How the Process Works, Step by Step
- You generate the invoice in your usual billing or accounting system, following the standard GST invoice fields.
- The invoice data is submitted, in a prescribed schema, to an Invoice Registration Portal (IRP) — either directly, through a GST Suvidha Provider (GSP), or via software that integrates with the IRP.
- The IRP validates the data (checking GSTINs, HSN codes, duplicate invoice numbers, and mandatory fields).
- On successful validation, the IRP generates a unique Invoice Reference Number (IRN), digitally signs the invoice, and creates a QR code containing key invoice details.
- The signed invoice, IRN, and QR code are returned to you. This QR code and IRN typically need to be printed on the physical or PDF copy you hand to your customer.
- The IRP shares the validated data with the GST system, where it is expected to flow into your GSTR-1 and, from there, into your buyer's GSTR-2B.
What a Completed E-Invoice Includes
| Element | What it is |
|---|---|
| IRN (Invoice Reference Number) | A unique hash generated by the IRP for that specific invoice |
| QR Code | A scannable code embedding key invoice details for quick verification |
| Acknowledgement Number and Date | Confirms when the IRP registered the invoice |
| Digitally signed JSON | The validated invoice data, signed by the IRP, treated as the legal record |
Which Documents Are Covered
E-invoicing generally applies to B2B tax invoices, and typically extends to debit notes and credit notes issued in relation to B2B supplies, and to export invoices. B2C invoices are generally outside the e-invoicing requirement, though QR code requirements can apply separately for large B2C taxpayers in some contexts. Because coverage details are refined periodically by the department, confirm exactly which document types apply to your business on the official e-invoice portal.
Who Needs to Generate E-Invoices
Applicability is based on aggregate turnover crossing a notified threshold, and that threshold has been lowered progressively over time to cover more businesses. Rather than quoting a specific figure here that may already be outdated by the time you read this, treat it as a rule you need to actively check: look up the current notified turnover limit on the official GST e-invoice portal, or read our dedicated breakdown on e-invoice applicability and turnover limits.
How E-Invoicing Connects to GSTR-1
One of the practical benefits of e-invoicing, once it is working correctly, is that validated invoice data is meant to auto-populate into the relevant tables of your GSTR-1, reducing manual data entry and the risk of typos between your invoice and your return. In practice, businesses still cross-check this auto-populated data against their own sales register before filing, since integration issues or timing gaps can occasionally cause data to be missing or duplicated. OneBooks GST's GSTR-1 automation is built to help with exactly this kind of validation, flagging discrepancies before you file rather than after.
Common Errors When Reporting to the IRP
| Error | Typical cause |
|---|---|
| Duplicate IRN request | Same invoice number submitted twice, often due to a retry after a timeout |
| Invalid GSTIN | Buyer or supplier GSTIN mistyped or inactive on the GST database |
| HSN/SAC code errors | Code not matching the notified list or missing required digits for the applicable turnover slab |
| Value mismatch | Taxable value, tax amount, or total not adding up per the prescribed formula |
| Invoice date issues | Reporting the invoice after the applicable reporting window for its date |
Cancelling and Amending E-Invoices
An IRN can generally be cancelled within a limited window after generation if the invoice was raised in error, but once that window closes, cancellation is typically not possible through the IRP and the correction has to be made through a credit or debit note instead. Amendments to invoice content after IRN generation are usually handled the same way — through GSTR-1 amendment processes rather than editing the original e-invoice. Confirm current cancellation windows on the e-invoice portal, since these operational rules are set by the department and can be revised.
Getting Ready for E-Invoicing
If your business is approaching the applicability threshold, it is worth testing your invoicing workflow against the IRP's sandbox environment before your obligation starts, so you are not troubleshooting integration issues on your first live filing day. It also helps to review your master data — customer GSTINs, HSN/SAC codes, and address details — since the IRP is stricter about data accuracy than a manually typed invoice ever was. For a closer look at how e-invoicing and the separate e-way bill requirement relate to each other, see e-invoice vs e-way bill, and for the exact fields every GST invoice needs regardless of e-invoicing status, see GST invoice format: mandatory fields.
Frequently asked questions
Is e-invoicing the same as raising an invoice through the GST portal?
No. You still generate the invoice through your own billing or accounting system. E-invoicing is the additional step of reporting that invoice to the IRP for validation and IRN generation.
What happens if I forget to generate an IRN for an applicable invoice?
An invoice that should have been e-invoiced but was not is generally treated as not a valid tax invoice for the recipient's ITC purposes, and can also expose the supplier to penalty. If you discover a missed invoice, address it promptly and consult a GST professional on the correct remediation.
Do I need special software to generate e-invoices?
You need a way to submit invoice data to the IRP in the prescribed schema — this can be direct integration, a GSP, or invoicing software that handles the submission on your behalf. Confirm with your software provider whether IRP integration is included.
Does e-invoicing replace the e-way bill?
No, they are separate requirements that can apply to the same transaction. E-invoicing validates the invoice itself; the e-way bill covers the movement of goods above a certain value or distance. See our comparison for the details.
Can export invoices be e-invoiced?
Export invoices are generally within the scope of e-invoicing where a business crosses the applicability threshold, though specific treatment (such as under LUT or with payment of tax) can affect the exact fields required. Verify current rules on the e-invoice portal.
Where software takes over: OneBooks GST
For teams running this every return period, OneBooks GST sits either side of the transport document rather than issuing it: importing sales, validating GSTIN and tax data, and exporting reviewed GSTR-1 output.
Reviewing the output in OneBooks GST before it leaves the system is the step that catches period, GSTIN and tax-rate errors while they are still easy to fix.
