Mon – Sat: 9:00 AM – 7:00 PM IST
GST & Compliance

What is GST e-invoicing in India?

What e-invoicing actually requires, who it applies to, and what changes inside your ERP when it does.

In short

GST e-invoicing means reporting a B2B invoice to the government's Invoice Registration Portal before it is issued, and receiving back an Invoice Reference Number and a signed QR code. The invoice is still raised in your own system — e-invoicing does not replace your ERP. What changes is that an invoice without a valid IRN is not a valid tax invoice.

Why It Matters

Why this matters in practice

The practical impact is on process, not on tax. An invoice that has not been registered cannot legitimately be sent to a customer, and your customer's input tax credit depends on it appearing correctly. Businesses that bolt e-invoicing on as a separate portal step usually end up with a reconciliation problem between what was registered and what was invoiced.

The IRN and signed QR code must appear on the invoice you issue
Registered invoices auto-populate GSTR-1, reducing filing work
E-way bill data can be generated from the same submission
An unregistered B2B invoice is not a valid tax invoice
How It Works

How it works in practice

1

Invoice is raised in the ERP

Normally, with all the GST fields correctly populated — GSTIN, HSN, place of supply, tax rates.

2

Payload sent to the IRP

In the prescribed JSON schema, directly from the ERP or through a GST Suvidha Provider.

3

IRP validates and returns

If the payload passes validation, the portal returns an IRN, a signed QR code and an acknowledgement number.

4

Invoice is issued with the IRN

The QR code and IRN are printed on the document. This is the version the customer receives.

5

Downstream population

GSTR-1 is populated from registered invoices, and the e-way bill can be raised from the same data rather than re-keyed.

Worked example

A worked example: where the rejections come from

A manufacturer switches on e-invoicing and sees roughly eight percent of submissions rejected in the first fortnight. The assumption is that the integration is broken. It is not — the integration is working correctly and reporting real data problems.

Categorised, the rejections fall into three groups. About half are invalid or inactive customer GSTINs, some of them years out of date in the customer master. A third are HSN codes that are either missing, the wrong number of digits for the turnover slab, or simply invented. The rest are schema issues: a state code that does not match the address, a unit of measure outside the permitted list, a total that disagrees with the line sum by a rounding paisa.

None of these were created by e-invoicing. They were all present before, sitting in the customer and item masters, invisible because no system ever validated them. The portal is simply the first consumer of that data that refuses to accept it. Which is why the real preparation for e-invoicing is a master data cleanse — validate every GSTIN, complete every HSN, fix every state code — done before go-live rather than discovered through rejections afterwards.

Key terms

The vocabulary, briefly

Term What it means
IRP Invoice Registration Portal — the government system that validates an invoice and returns its reference number.
IRN Invoice Reference Number, the unique hash the IRP returns. An invoice without one is not valid where e-invoicing applies.
Signed QR code The digitally signed code the IRP returns, which must be printed on the invoice.
Schema The prescribed JSON structure an invoice must be submitted in. Most rejections are schema failures rather than tax errors.
Cancellation window The limited period in which an IRN can be cancelled on the portal. Afterwards the correction is a credit note.
What Goes Wrong

Common mistakes worth avoiding

Treating the portal as a separate step

Manual upload creates a gap between invoices raised and invoices registered. Automate it from the ERP.

Incorrect HSN or place of supply

These are validated at the IRP. A systematic error produces systematic rejections at the worst possible moment.

No handling of cancellations

An IRN can only be cancelled within a limited window. The process has to exist before you need it.

Ignoring the reporting time limit

Since 1 April 2025, taxpayers with AATO of ₹10 crore and above must report invoices to the IRP within 30 days of the invoice date.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
IRN success rate at first attempt Master data quality more than integration quality. Counting retries as successes, which hides the underlying data fault.
Rejection reasons by category Which master file needs attention — customer, item, or the invoice build itself. A large 'other' bucket, which usually means errors are not being parsed.
Time from invoice to IRN Whether registration is inline or batched. Batched means dispatch can leave ahead of a valid invoice. Averaging across the day; portal response slows near filing deadlines.
Cancellations and credit notes Whether invoices are being raised correctly first time. Credit notes raised for commercial reasons mixed in with correction ones.
FAQ

Questions we are asked about this

The IRN requirement applies to B2B, exports and certain other categories rather than ordinary B2C sales. Larger taxpayers have separate requirements around dynamic QR codes for B2C.
The invoice can be prepared offline, but the IRN has to be obtained from the portal before the invoice is validly issued. Plan for the connectivity dependency.
It depends on aggregate annual turnover, and the threshold has been lowered repeatedly since the scheme began — it started with very large taxpayers and has come down in stages to cover much smaller ones. Because it has moved several times, check the limit currently in force on the GST portal rather than relying on a figure quoted anywhere, including here. Certain categories, such as SEZ units, banks and passenger transport, have their own treatment.
Build for it, because it happens. The standard pattern is to queue submissions and retry rather than block dispatch, with a clear internal rule about whether goods may leave before an IRN is received. Decide that rule in advance with your finance and compliance people — discovering it during an outage, under pressure, with vehicles waiting, is how bad precedents get set.
Not in place. An IRN can be cancelled on the portal only within a limited window and only in full, never partially. After that window the correction is a credit note or debit note with its own IRN, which means your process has to treat a wrong invoice as a document to reverse rather than a field to edit. Systems that allow users to edit posted invoices will cause problems here.
No, though it feeds it. Registered invoice data flows through to your returns and to the e-way bill system, which reduces re-entry and the mismatches that come with it. You still file. The practical benefit is that the data in your return and the data on your invoices come from the same source, so reconciliation becomes a check rather than an exercise.
Related

Where to read next

GST e-invoicing inside iDempiere

Read more

What is an IRN?

Read more

What is an e-way bill?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.