GST E-Invoicing Thresholds: A Practice Guide for Advocates and Tax Counsel

By LegalInk Editorial · 2026-06-04

GST E-Invoicing Thresholds: A Practice Guide for Advocates and Tax Counsel

GST e-invoicing has become one of the more consequential operational changes within the GSTN framework, and the compliance burden has expanded steadily as the turnover threshold has been lowered in successive phases. For advocates advising MSMEs, trading entities, or any business with B2B transactions, staying current on the e-invoicing threshold requirements is not optional. A missed obligation can trigger input tax credit reversals for the client's buyers, attract scrutiny under the GST audit provisions, and generate demand notices that land on counsel's desk months after the event. This post sets out the statutory framework, the current threshold and its progression, exempted categories, the mechanics of IRN generation, and the consequences of non-adherence — referenced to the Act, Rules, and notifications as they stand.

The Statutory Foundation

Where the obligation originates

E-invoicing under GST is governed by Rule 48 of the Central Goods and Services Tax Rules, 2017 (CGST Rules), as amended. The substantive authority flows from Section 31 of the Central Goods and Services Tax Act, 2017 (CGST Act), which deals with the issuance of tax invoices. Sub-rule (4) of Rule 48, inserted by the Central Goods and Services Tax (Eighth Amendment) Rules, 2020, provides that notified classes of registered persons must prepare invoices only by uploading the relevant particulars to the Invoice Registration Portal (IRP), obtaining an Invoice Reference Number (IRN), and incorporating the Quick Response (QR) code generated by the IRP into the invoice.

The notification-based architecture means that the obligation — and critically, the turnover threshold — is activated and revised by CBIC notifications issued under Section 148 of the CGST Act, which empowers the government to notify special procedures for particular classes of registered persons. Every threshold change has been effected through a fresh notification. Tracking this compliance area therefore requires monitoring the CBIC gazette rather than relying on a static reading of the Rules.

What constitutes an "e-invoice" in law

A terminological point that frequently confuses clients is worth clarifying at the outset. An "e-invoice" under GST is not simply a digitally prepared invoice. It is an invoice for which a valid IRN has been generated by the IRP and a digitally signed QR code has been embedded. An invoice generated by accounting software but not authenticated through the IRP does not satisfy Rule 48(4). The practical consequence — discussed further below — is that an unauthenticated invoice is treated as an invalid invoice for the purpose of Input Tax Credit under Section 16 of the CGST Act, with cascading effects on the buyer.

The Threshold Journey: From ₹500 Crore to ₹5 Crore

Understanding the current e-invoicing threshold requirements requires appreciating how the obligation has been progressively extended downward. The threshold has moved in five distinct phases.

Phase-wise rollout

The e-invoicing obligation was first made applicable to registered persons with an aggregate annual turnover exceeding ₹500 crore in any preceding financial year, effective 1 October 2020 (Notification No. 61/2020–Central Tax). The ₹100 crore threshold followed for transactions from 1 January 2021 (Notification No. 88/2020–Central Tax). The next reduction brought the threshold to ₹50 crore from 1 April 2021, then ₹20 crore from 1 April 2022, and ₹10 crore from 1 October 2022.

The most significant extension in terms of the number of taxpayers covered occurred when the threshold was reduced to ₹5 crore, effective 1 August 2023 (Notification No. 10/2023–Central Tax). This is the current operative threshold: any registered person whose aggregate turnover in any preceding financial year from 2017–18 onwards has exceeded ₹5 crore is required to comply with e-invoicing for eligible supplies.

How "aggregate turnover" is calculated for this purpose

The threshold is assessed against aggregate turnover as defined under Section 2(6) of the CGST Act: the aggregate value of all taxable supplies (excluding the value of inward supplies on which tax is paid on reverse charge), exempt supplies, exports of goods or services, and inter-State supplies of a person having the same Permanent Account Number, computed on an all-India basis but excluding central tax, State tax, Union territory tax, integrated tax, and cess.

Two practical points warrant emphasis. First, the threshold is measured against any preceding financial year — not the immediately preceding year alone. A business that crossed ₹5 crore in, say, FY 2021–22 but has since scaled down remains within scope. Second, turnover from all GSTINs under a single PAN is aggregated, so a business with multiple registrations across states cannot claim exemption on the basis that each individual GSTIN's turnover is below the limit. Counsel reviewing a client's compliance position should therefore obtain consolidated PAN-level turnover data for every year since the GST rollout, not just the current year's books.

Exempted Persons and Transactions

Not all registered persons above the threshold are within scope. The threshold requirements operate alongside a set of categorical exclusions that are equally important to understand.

Exempt categories of registered persons

Certain classes of registered persons are specifically excluded from the e-invoicing obligation, regardless of turnover. These exclusions are set out in Notification No. 13/2020–Central Tax and subsequent amendments. The major excluded categories include:

• Insurers, banking companies, financial institutions, and NBFCs
• Goods Transport Agencies (GTAs)
• Registered persons supplying passenger transportation services
• Suppliers of services by way of admission to cinema exhibitions
• Special Economic Zone (SEZ) units (though SEZ developers are not excluded)
• Government departments and local authorities

The exclusion for SEZ units has been a recurring source of confusion. SEZ units are not required to generate IRNs for their outward supplies, but registered buyers receiving supplies from SEZ units cannot, in the absence of clear documentation, be expected to verify exemption status on their own. The practical advice to clients receiving supplies from SEZ entities is to obtain a written declaration of the supplier's exemption status and retain it with the invoice file. This protects the buyer's ITC claim in the event of a later audit query.

Exempt categories of transactions

Even where the registered person is within scope, certain document types and supply categories do not require an IRN. Business-to-consumer (B2C) supplies do not require e-invoicing, though dynamic QR codes are separately mandated for B2C invoices issued by taxpayers above a specified turnover threshold. Exports of goods and services, on the other hand, do attract e-invoicing obligations for in-scope taxpayers, including deemed exports.

Credit notes and debit notes linked to an e-invoiced supply must also be reported to the IRP. This is a compliance detail that clients frequently overlook when issuing post-supply adjustments — a credit note that should have been e-reported but was not, in respect of a buyer who has already claimed ITC on the underlying invoice, creates a downstream reconciliation gap that surfaces during departmental matching.

The Mechanics of Compliance

The IRP and IRN generation process

Once a taxpayer falls within the e-invoicing threshold requirements, every eligible B2B invoice must be uploaded to one of the authorised IRPs before it is issued to the recipient. The NIC-managed portal (einvoice1.gst.gov.in) was the original IRP; GSTN has since authorised additional IRPs to reduce technical bottlenecks and provide redundancy during peak filing windows.

The IRP validates the invoice data against the GSTN database, deduplicates it, generates a unique IRN (a 64-character hash), digitally signs the data, and returns a QR code. The invoice presented to the buyer must carry this IRN and QR code. The IRP also auto-populates the data into the GSTR-1 return, which reduces reconciliation work in theory — though mismatches between IRP data and what the supplier finally reports in GSTR-1 remain a recurring source of notices in practice, particularly where supplier accounting software is not fully integrated with the IRP submission layer.

Time limit for IRN generation

A time limit for reporting invoices to the IRP was introduced for larger taxpayers and has been progressively extended in scope. Taxpayers with aggregate turnover at or above ₹100 crore must upload invoices to the IRP within 30 days of the invoice date, failing which the IRP rejects the upload. For taxpayers below ₹100 crore, no such uniform fixed time limit has been universally mandated as of the latest consolidated notifications, but CBIC has signalled intent to extend time-bound reporting across the base. Counsel should monitor subsequent notifications closely, since a missed window converts a curable lapse into a hard non-compliance.

Record-keeping and audit trail

From a litigation and advisory standpoint, the e-invoicing system creates a Government-side record of every B2B transaction at the point of invoice generation. This has significant implications for GST audit proceedings under Section 65 and investigation proceedings under Section 67 of the CGST Act. When a proper officer examines a taxpayer's records, the IRP-logged invoice data serves as an independent reference point that the taxpayer cannot retrospectively alter. Discrepancies between filed returns, IRP data, and e-way bill data are now a primary trigger for audit selection.

Advising clients to conduct periodic three-way reconciliation — GSTR-1, IRP records, and e-way bill logs — is sound practice. A quarterly internal reconciliation, ideally signed off by the client's finance head, is a defensive measure that pays for itself the first time the department issues a discrepancy notice. For matters involving GST-related disputes or demand proceedings, the LegalInk finance compliance framework can assist in mapping a client's invoice trail against applicable statutory periods and notification-based obligations.

Consequences of Non-Compliance

Invalid invoice and ITC denial

The most immediate consequence of failing to comply with e-invoicing requirements is that the invoice is treated as an invalid invoice in law. Under Rule 48(5) of the CGST Rules, a tax invoice issued in contravention of Rule 48(4) shall not be treated as a tax invoice. The downstream effect is that the recipient of the supply cannot claim Input Tax Credit on that invoice under Section 16 of the CGST Act, since valid ITC claims require a valid tax invoice. This creates a transactional liability for the buyer, not just the supplier, and is frequently the basis on which demand notices travel through a supply chain — the buyer is denied ITC, raises a commercial claim against the supplier, and both parties end up litigating downstream of a single non-compliant invoice batch.

Penalty exposure

Section 122 of the CGST Act provides for penalties for specified offences including the issuance of an invoice in violation of the provisions of the Act or Rules. The penalty prescribed under Section 122(1) is the higher of ₹10,000 or the tax due on the transaction. Where the department frames a case around suppression or evasion, the enhanced penalty provisions of Section 122(1A) and the prosecution provisions of Section 132 may be invoked, the latter applicable where evaded tax exceeds the specified statutory thresholds.

E-way bill linkage

E-invoicing data feeds directly into the e-way bill system: for e-invoiced supplies, Part A of the e-way bill is auto-populated from the IRN data. Where e-invoicing is not done and an e-way bill is separately generated for a movement that ought to have been e-invoiced, the absence of an IRN reference is flagged at the system level, creating interception risk during transit under Section 68 of the CGST Act read with Rule 138 of the CGST Rules. Goods detained on this basis attract demands and penalties under Sections 129 and 130, and release becomes contingent on payment or furnishing of security.

Practical Considerations for Advocates Advising Clients

Threshold verification for new clients

When onboarding a commercial client for GST advisory or litigation, the first task is turnover verification across all preceding financial years from 2017–18 onwards. Given that the threshold has been reduced multiple times, a client may have crossed the current ₹5 crore threshold in an earlier year and continued to operate under the misconception that its current turnover (below ₹5 crore) keeps it outside the obligation. The legal position is otherwise: once the threshold is crossed in any year from 2017–18 onwards, the obligation attaches and continues. The client's own returns, audited financials, and PAN-consolidated GST data are the definitive source.

Responding to show-cause notices

SCNs citing e-invoicing non-compliance are typically framed under Section 74 (where fraud or suppression is alleged) or Section 73 (in other cases) of the CGST Act, with the underlying violation characterised as issuance of invalid invoices resulting in erroneous ITC availment by buyers. When responding, the critical arguments turn on whether the client actually fell within the threshold at the material time, whether the supply category was exempted, and whether any technical failure at the IRP end contributed to non-issuance — an argument that requires contemporaneous evidence such as IRP error logs or screenshots, which clients rarely preserve unless instructed to.

The LegalInk brief generator is useful when structuring the factual matrix of an SCN response involving multiple invoice periods and layered notification applicability, particularly where the threshold-crossing year is in dispute or where exemption status is being asserted for a sub-set of supplies.

Prospective advice for the ₹3–5 crore bracket

Clients currently reporting turnover between ₹3 crore and ₹5 crore should be advised that a further threshold reduction cannot be ruled out given the pattern of successive cuts. Building e-invoicing capability before it is mandated is straightforwardly cheaper than attempting emergency implementation under a compliance deadline. Counsel should consider including a prospective compliance note in standard advisory engagement letters for clients in this turnover band, flagging the regulatory direction of travel.

Buyer-side due diligence

Advising buyers is the mirror-image exercise. For any B2B procurement where the supplier appears to be above the ₹5 crore threshold, the buyer's accounts payable team should be reconciling supplier invoices for the presence of a valid IRN and QR code before recording the ITC claim. A simple control — rejecting invoices that should carry an IRN but do not — eliminates the most common downstream ITC denial scenario. This is the kind of preventive compliance design that holds up under audit far better than retrospective remediation.

Why This Matters

The e-invoicing threshold requirements are no longer a concern only for large enterprises. At ₹5 crore, the obligation covers a substantial proportion of the actively trading registered base, and the automatic data-sharing between the IRP, GSTR-1, and the e-way bill system means non-compliance is structurally visible to the department in a way that older paper-trail violations were not. For advocates practising in indirect tax, corporate advisory, or general commercial matters, a working understanding of these obligations is essential to providing advice that holds up when the client faces scrutiny.

The practical playbook is straightforward: verify thresholds against PAN-level historical turnover, confirm exemption status with documentation, build three-way reconciliation into the client's compliance workflow, and treat every IRP failure as an event that requires contemporaneous evidence capture. Structured, citation-grounded compliance work of this kind is what the tools at legalink.co.in are designed to support.

← Back to all posts