E-invoicing: which threshold applies to you, and what changes on the floor

E-invoicing is described to most manufacturers as a new format for an invoice. It is not. The invoice is the same document it always was. What changed is that before you can hand it to anybody, you have to report it to a government portal and get back an Invoice Reference Number and a signed QR code, and until that comes back the document is not a valid tax invoice.

That single sentence is the whole operational consequence. Everything below is detail hanging off it.

Whether it applies to you

The test is aggregate annual turnover, and the wording catches people out: it is turnover in any financial year from 2017-18 onwards, not the current one. The line has come down in stages — ₹500 crore, then 100, 50, 20, 10 — and has sat at ₹5 crore since 1 August 2023. If you crossed it in 2021-22 and have run smaller ever since, you are still in. There is no exit.

Aggregate turnover is also computed across all GSTINs on the same PAN — every plant, every state, and exempt and export supplies included. A group that thinks of itself as three small units is usually one large taxpayer.

What has to be reported once you are in: B2B supplies, supplies to SEZ, exports, and the credit and debit notes against any of them. B2C invoices are outside the scheme entirely — which is why a plant that sells mostly to distributors reports almost everything and a plant that sells retail reports almost nothing.

A handful of registered persons are exempt regardless of size — banks and insurers, NBFCs, goods transport agencies, passenger transport, cinema exhibitors, and SEZ units. If you are none of those and you are over the line, you are in.

There is a second deadline worth knowing separately from the threshold. Taxpayers with aggregate turnover of ₹10 crore and above cannot report a document older than 30 days to the portal — the window took effect for that band on 1 April 2025, having applied to larger taxpayers before that. An invoice that misses it cannot be reported at all; there is no late-reporting route. That turns a filing habit — “we upload the month’s invoices before the return” — into a compliance failure with no remedy. The band has moved downwards twice already, so treat 30 days as the ceiling and report the same day regardless of your size.

What changes on the shop floor

Dispatch waits on the portal, not on the printer. The moment the IRN becomes part of a valid invoice, the security gate needs to be checking for a QR code, not a signature. Plants that skip this discover the problem at a check post, in somebody else’s district, with a loaded truck.

Your cancel window is short and it is not your window. An IRN can be cancelled on the portal within 24 hours, and only in full — you cannot edit one. After that the only instrument is a credit note. Amendments to the invoice itself happen in the return, not on the portal. So the cost of a wrong invoice is no longer a reprint; it is a document trail with a reason attached to it.

The e-way bill gets easier, not harder. Reporting the invoice can populate the transport document’s first part for you. If your team is still keying the same consignment twice, that is a configuration gap rather than a legal requirement.

Rejections are boring and they are all avoidable. The failures a plant actually hits are a wrong or missing HSN code, a PIN code that does not match the state code, a unit of measure that is not in the portal’s list (your “nos.” against its “NOS”), a document number repeated in the same financial year, or a buyer whose GSTIN was cancelled last quarter and nobody told sales. None of these are difficult. All of them stop a dispatch if you find out at the wrong moment.

What good looks like

The plants that find e-invoicing uneventful have four things in place, and none of them is exotic:

• Masters are clean before the first invoice of the day, not after the rejection. HSN, UOM and buyer GSTIN are validated when the master is created, not when the document is raised.
• Dispatch is blocked in software without a successful IRN. Not warned — blocked. A warning gets clicked through at 7pm.
• Failed reports go to a queue somebody owns, with a retry, rather than an error message in a log file. The portal has bad afternoons; that is survivable, silently losing four invoices is not.
• Somebody reconciles daily: invoices raised in the books against IRNs successfully generated. A difference of one is a five-minute problem. A difference of forty, found at return time, is a week.

What MANUPRIME does about it

E-invoicing runs through the GSP connector you configure in the Integrations Hub, on your own account with your own provider — we do not resell the per-document charge. The IRN and QR print on the invoice, cancellation inside the 24-hour window is a button on the document rather than a separate portal login, the e-way bill is raised from the same record, and the daily reconciliation is a report rather than a spreadsheet somebody maintains.

You can see the compliance module on a demo call, as the accountant who would use it.