E-Invoicing Turnover Limit vs GST Registration Threshold: What Is the Difference?

For exclusive suppliers of goods, the lower limit applies in Arunachal Pradesh, Manipur, Meghalaya, Mizoram, Nagaland, Sikkim, Telangana, Tripura, Uttarakhand, Puducherry, and Sikkim.

The ₹40 lakh threshold is not available to every goods supplier. Notification No. 10/2019-Central Tax limits it to eligible persons engaged exclusively in supplying goods and excludes specified persons, goods and locations.

Note: Turnover is not the only registration test. Compulsory-registration provisions may require a person to register below the applicable threshold, depending on the nature and location of the supply.

What Counts as Aggregate Turnover?

Aggregate turnover covers taxable supplies, exempt supplies , exports, and inter-state supplies made by all GST registrations linked to the same PAN. It is calculated on an all-India basis.

GST and compensation cess are not included. Inward supplies on which the recipient pays tax under reverse charge are also excluded from the recipient’s aggregate turnover.

E-Invoicing Turnover Limit in 2026

E-invoicing applies if aggregate turnover under the same PAN exceeded ₹5 crore in any preceding financial year from 2017-18 onward, unless a notified exemption applies. Turnover of exactly ₹5 crore does not trigger the mandate.

How PAN-Wise Turnover Is Calculated

Consider a company with three GST registrations:

No individual GST registration has a turnover above ₹5 crore. However, the combined turnover under the PAN is ₹5.50 crore.

If this turnover was recorded in a preceding financial year, the non-exempt GST registrations under the PAN become subject to the e-invoice turnover condition. Checking each GSTIN separately would give an incorrect result.

What Happens When the Limit Is Crossed During the Current Year?

Suppose a business had never crossed ₹5 crore before FY 2026-27 but records an aggregate turnover of ₹5.40 crore during FY 2026-27.

The notification tests turnover in the preceding financial years. FY 2026-27 becomes a preceding financial year from 1 April 2027. The business would therefore generally become liable for e-invoicing from FY 2027-28, provided the law and its exemption status remain unchanged.

This differs from GST registration, where liability may arise during the financial year in which the relevant registration threshold is crossed.

Complete the e-invoice applicability review before the beginning of each financial year. This gives the finance and technology teams time to configure the ERP, register with an IRP , test document flows, and correct customer-master data before the first applicable invoice is issued.

Why Applicability Continues After Turnover Falls

Assume a company recorded aggregate turnover of ₹6.20 crore in FY 2023-24, but its turnover later fell to ₹3.80 crore.

FY 2023-24 remains a preceding financial year in which aggregate turnover exceeded ₹5 crore. The earlier crossing, therefore, continues to make e-invoicing applicable under the current notification.

This is sometimes described as “once applicable, always applicable”, but it is not a separately named rule. It is the result of the historical look-back built into Notification No. 13/2020-Central Tax, as amended.

As of July 2026, the latest official threshold notification continues to prescribe turnover exceeding ₹5 crore. No official notification establishing a ₹2 crore limit or an effective date has been issued.

Circular No. 186/18/2022-GST clarifies that an exemption applies to the entity as a whole, not only to its main business activity. For example, an exempt banking company does not become liable for e-invoicing merely because it also sells bullion, office equipment, or other goods.

SEZ Unit vs SEZ Developer

An SEZ unit is specifically exempt from mandatory e-invoicing , but an SEZ developer is not covered by this exemption.

ERP and GSTIN masters should therefore distinguish between an SEZ unit and an SEZ developer. A PAN-level turnover trigger should not override a valid exemption attached to a particular entity or GSTIN.

What About Composition Taxpayers?

Composition taxpayers are not included in the notified exemption list alongside banks, GTAs, or SEZ units. However, they issue bills of supply rather than tax invoices and operate below the current e-invoicing turnover limit, so the mandate does not apply to them in practice.

Which Documents and Transactions Require an IRN?

For a covered supplier, the requirement for an Invoice Reference Number , or IRN, depends on both the document type and the transaction.

The official GSTN overview identifies tax invoices, credit notes , and debit notes relating to B2B supplies, SEZ supplies, exports, and deemed exports as covered documents.

Supplies to Government Customers

A government customer’s registration status should be checked through its GSTIN. Circular No. 198/10/2023-GST clarifies that government departments, establishments, agencies, local authorities, and PSUs registered only to deduct tax at source under section 51 are treated as registered persons under GST.

A covered supplier must therefore generate an IRN for an applicable supply made to such a recipient. However, a transaction does not require an IRN merely because the customer is a government body.

Reverse-Charge Transactions

Reverse charge should not be treated as an automatic exclusion from e-invoicing. A supplier-issued document for a covered B2B transaction may still require an IRN where the supplier and document are otherwise covered by the mandate. A self-invoice created by the recipient under the reverse-charge provisions is a separate document flow.

The 30-Day IRP Reporting Rule

From 1 April 2025, taxpayers with AATO of ₹10 crore or more must report eligible invoices, credit notes, and debit notes to the IRP within 30 days of the document date. If an eligible document is reported after the permitted period, the IRP restricts IRN generation.

Note: ₹5 crore and ₹10 crore serve different purposes. Aggregate turnover exceeding ₹5 crore determines whether mandatory e-invoicing applies. AATO of ₹10 crore or more triggers the additional 30-day IRP reporting restriction .

Taxpayers with AATO above ₹5 crore but below ₹10 crore are not currently subject to the 30-day reporting restriction. They must still obtain an IRN before issuing an applicable document.

A shorter internal reporting period may be adopted to allow time for correcting validation errors, but it should be described as an internal control rather than a statutory deadline.

How E-Invoicing Works and Data Reaches GSTR-1

Businesses continue to create invoices in their own accounting, billing, or ERP system. E-invoicing does not mean that invoices are prepared directly on a government portal. The process generally works as follows:

1. The business creates the invoice or other covered document in its system.
2. The prescribed document data is reported to an authorised IRP.
3. After validation, the IRP returns the IRN, digitally signed e-invoice data, and a signed QR code.
4. The final document is issued to the recipient with the required IRN and QR-code details.
5. The IRP shares the data with the GST system for auto-population in the supplier’s GSTR-1 .

Taxpayers must still review and file GSTR-1. Auto-population does not complete return filing or remove the need for reconciliation. E-invoicing also does not automatically grant input tax credit to the buyer. ITC remains subject to the conditions of the CGST Act and the applicable GST return and statement process.

Operational Checklist for Finance and ERP Teams

1. Review Applicability Before Each Financial Year

Maintain year-wise aggregate turnover for the PAN from FY 2017-18 onward and map every GSTIN to the correct PAN.

The review should also record notified exemptions, including SEZ-unit status and entity-level exclusions. Do not treat portal enablement as definitive proof of liability because technical enablement and legal applicability are separate matters.

2. Route Only Eligible Documents to the IRP

Configure the ERP to verify the supplier’s eligibility, recipient registration status, document type, transaction type, and any GSTIN- or entity-level exemptions before sending data to the IRP. Keep in mind that crossing the turnover limit does not mean every document must be reported.

3. Block Invoice Issue Until the IRN Is Received

For an applicable document, the system should release the invoice only after:

• IRP validation is successful;
• the IRN has been received;
• the signed QR code has been stored; and
• the final invoice contains the required details.

This prevents users from issuing an invoice that exists in the ERP but has not completed IRP validation.

4. Control Document Dates and Failed Requests

For taxpayers subject to the 30-day reporting restriction, the ERP should calculate the document age before submitting it to the IRP and block documents that have exceeded the permitted period.

Failed submissions should move to a visible error queue containing the original request, IRP error details, retry history, final response, and the user responsible for approving any exception. A temporary IRP failure should never result in an invoice being issued without an IRN.

5. Reconcile ERP, IRP, and GSTR-1 Records

At the end of each return period, compare eligible documents created in the ERP with successful, cancelled, rejected, and pending IRNs. These records should also be matched with the data auto-populated in GSTR-1.

This reconciliation helps identify missing IRNs, duplicate document numbers, failed credit notes, and differences caused by manual changes in GSTR-1.

Simplify E-invoice compliance with BUSY accounting software . Generate IRNs, print signed QR codes, and keep invoice data connected with your GST records through BUSY.

Under Rule 48(5), an invoice issued by a covered taxpayer without completing the prescribed e-invoice process is not treated as a valid invoice. This can affect both the supplier and the recipient:

There is no universal rule imposing an automatic penalty of ₹10,000 for every invoice without an IRN . The actual consequence depends on the nature of the default and the legal provision invoked.

What to Do When an IRN Is Missed

The finance team should first stop issuing any further affected documents. It should then identify the relevant period, document types, and transaction value, and check whether IRN generation is still technically possible.

The affected records should be reconciled across the ERP, IRP, and GSTR-1 before deciding the correction route. Where the issue involves expired reporting limits, recipient ITC, or multiple invoices, professional advice should be obtained before making any amendment or disclosure.

Conclusion

GST registration and e-invoicing should be assessed separately. Registration depends on the applicable turnover threshold and other registration provisions, while e-invoicing depends on whether PAN-wise aggregate turnover exceeded ₹5 crore in a preceding financial year and whether a notified exemption applies.

For reliable compliance, businesses should review their applicability before each financial year, route only eligible documents to the IRP, and prevent the release of invoices until a valid IRN is received.

The final decision should not be based solely on a single GSTIN’s turnover, portal enablement status, or an unconfirmed report of a possible future threshold.