What e-invoicing actually requires, who it applies to, and what changes inside your ERP when it does.
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.
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.
Normally, with all the GST fields correctly populated — GSTIN, HSN, place of supply, tax rates.
In the prescribed JSON schema, directly from the ERP or through a GST Suvidha Provider.
If the payload passes validation, the portal returns an IRN, a signed QR code and an acknowledgement number.
The QR code and IRN are printed on the document. This is the version the customer receives.
GSTR-1 is populated from registered invoices, and the e-way bill can be raised from the same data rather than re-keyed.
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.
| 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. |
Manual upload creates a gap between invoices raised and invoices registered. Automate it from the ERP.
These are validated at the IRP. A systematic error produces systematic rejections at the worst possible moment.
An IRN can only be cancelled within a limited window. The process has to exist before you need it.
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.
| 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. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.