GST E-Invoicing in India: Complete Guide for Businesses
Quick Summary
- E-invoicing under GST is mandatory for notified taxpayers whose aggregate annual turnover exceeds ₹5 crore in any financial year from 2017-18 onwards, subject to the notified exemptions. The threshold has been in force from 1 August 2023.
- From 1 April 2025, taxpayers with AATO of ₹10 crore and above must report invoices, credit notes, and debit notes to the IRP within 30 days of the document date. If they miss that window, the portal rejects reporting.
- E-invoicing applies to covered documents issued by notified taxpayers to registered persons or for exports. In practical terms, that means tax invoices, debit notes, and credit notes for B2B and export transactions are the core focus. B2C invoices are outside the present e-invoicing framework.
- The IRP generates a unique Invoice Reference Number, or IRN, and returns a signed payload along with a QR code. For notified taxpayers, a GST invoice becomes valid only when it carries a valid IRN in the prescribed e-invoicing framework.
- Cancellation is allowed only within 24 hours on the IRP. Amendments are not made on the IRP and must be handled through the GST return system and normal document correction routes.
What Is E-Invoicing Under GST?
E-invoicing under GST does not mean that the government portal creates your invoice for you. Businesses still prepare invoices in their own ERP, billing, or accounting software. What changes is that certain notified taxpayers must report invoice data to a government-designated Invoice Registration Portal, or IRP, and obtain an Invoice Reference Number , or IRN, before the document is treated as a valid GST e-invoice.
Once the invoice data is successfully reported, the IRP validates it, generates the IRN, digitally signs the payload, and returns the signed invoice data with a QR code. That QR code helps verify whether the invoice has actually been reported on the IRP.
The legal significance is important. Under Rule 48(5), where Rule 48(4) applies, an invoice issued otherwise than in the prescribed manner is not treated as a valid invoice. That is why e-invoicing is not just a formatting exercise. It directly affects invoice validity, buyer acceptance, return flow, and downstream compliance.
Generate Bulk E-Invoices Instantly with BUSY
E-Invoicing Implementation Timeline
E-invoicing was rolled out in phases, beginning with very large taxpayers and then gradually extending to smaller businesses. The current threshold of more than ₹5 crore AATO took effect from 1 August 2023.
Phase-wise rollout
| Phase | Aggregate Turnover Threshold | Mandatory From |
|---|---|---|
| Phase 1 | Exceeding ₹500 crore | 1 October 2020 |
| Phase 2 | Exceeding ₹100 crore | 1 January 2021 |
| Phase 3 | Exceeding ₹50 crore | 1 April 2021 |
| Phase 4 | Exceeding ₹20 crore | 1 April 2022 |
| Phase 5 | Exceeding ₹10 crore | 1 October 2022 |
| Phase 6 | Exceeding ₹5 crore | 1 August 2023 |
A key compliance point is that the threshold is tested with reference to turnover in any financial year from 2017-18 onward, not just the current year. Businesses often miss this and assume that if turnover has now fallen below ₹5 crore, e-invoicing no longer applies. That assumption is unsafe.
Who Must Comply - Current Threshold
As of April 2026, e-invoicing applies to notified registered persons whose aggregate annual turnover exceeds ₹5 crore in any preceding financial year from 2017-18 onwards, subject to the notified exemptions. The test is based on the PAN, not on one individual GSTIN.
E-invoicing currently applies to invoices, credit notes , and debit notes issued by notified taxpayers to registered persons or for exports. That means it generally includes:
- B2B taxable supplies
- supplies to SEZs
- exports
- deemed exports where relevant document treatment and recipient status fit the framework
It does not generally apply to:
- B2C invoices
- bills of supply for exempt supplies
- documents outside the notified e-invoice document set, such as ordinary delivery challans or proforma invoices
What Is Annual Aggregate Turnover and How Is It Calculated?
Aggregate turnover is defined under Section 2(6) of the CGST Act. It includes the aggregate value of: taxable outward supplies, exempt supplies, exports of goods or services and inter-State supplies of persons having the same PAN
It excludes:inward supplies on which tax is payable under reverse charge and CGST, SGST, UTGST, IGST, and compensation cess
The turnover has to be computed on an all-India PAN basis. If one business has multiple GST registrations in different states, you do not test each GSTIN separately for e-invoicing threshold. You combine turnover across all such registrations under the same PAN.
Practical example
Suppose a company has GST registrations in Maharashtra, Karnataka, and Delhi under one PAN.
| GSTIN / State | Taxable Turnover | Exempt Turnover | Export Turnover |
|---|---|---|---|
| Maharashtra | ₹2.5 crore | ₹0.3 crore | ₹0.5 crore |
| Karnataka | ₹1.2 crore | ₹0.2 crore | ₹0 |
| Delhi | ₹0.8 crore | ₹0 | ₹0.2 crore |
| PAN Total | ₹4.5 crore | ₹0.5 crore | ₹0.7 crore |
In this example, aggregate turnover becomes ₹5.7 crore, so the PAN crosses the current e-invoicing threshold. The compliance test is satisfied at the PAN level, not by looking only at one registration.
The 30-Day IRP Reporting Rule
From 1 April 2025, taxpayers with AATO of ₹10 crore and above must report their invoices, debit notes, and credit notes to the IRP within 30 days of the document date. If they try to report after that period, the system rejects the request.
What this means in practice
| Scenario | Result |
|---|---|
| Invoice dated 1 April, reported on 20 April | Accepted |
| Invoice dated 1 April, reported on 5 May | Rejected |
| Debit note dated 10 April, reported after 30 days | Rejected |
The practical effect is that businesses in the ₹10 crore and above category cannot treat e-invoicing as a back-office upload task done long after invoicing. The IRN has to move much closer to the actual invoice-creation process.
This restriction does not currently apply to taxpayers with AATO below ₹10 crore, though same-day or near real-time reporting remains the safer operational approach.
Documents and Transactions Covered
The official e-invoice framework identifies the following covered documents: invoices, credit notes and debit notes These are covered when issued by notified taxpayers to registered persons or for exports.
Coverage snapshot
| Document / Transaction | Covered? |
|---|---|
| B2B tax invoice | Yes |
| Export invoice | Yes |
| SEZ supply invoice | Yes |
| Debit note | Yes |
| Credit note | Yes |
| Bill of supply | No |
| Proforma invoice | No |
| Delivery challan | No |
| Ordinary B2C invoice | No |
Imports are not part of the normal e-invoicing flow for Indian suppliers because the invoice is typically issued by the foreign supplier, not by a notified GST-registered Indian supplier under Rule 48(4).
Who Is Exempt from E-Invoicing?
Certain classes of taxpayers are exempt from the e-invoicing requirement regardless of turnover, as reflected in the notification framework and official GSTN materials. These include:
- insurers
- banking companies
- financial institutions, including NBFCs
- goods transport agencies supplying goods transport service by road
- suppliers of passenger transportation service
- suppliers of services by way of admission to exhibition of cinematograph films in multiplex screens
- SEZ units
- government departments and local authorities, through later amendment
Authorised Invoice Registration Portals
There are six authorised IRPs for reporting e-invoices and generating IRNs, and IRN generation on these portals is free of charge.
GSTN’s recent overview material identifies the following six active IRP portals:
- einvoice1
- einvoice2
- einvoice3
- einvoice4
- einvoice5
- einvoice6 on the official GST e-invoice portal network
The practical takeaway is that businesses are not dependent on only one IRP. If one portal has operational issues, businesses can use another authorised portal. The underlying IRN logic is designed to avoid duplicate registration across portals.
Step-by-Step IRN Generation Process
Generating an e-invoice usually follows three broad steps.
Prepare the invoice
The supplier creates the invoice in its own ERP, billing system, accounting software , or approved utility. The data must be structured in the prescribed INV-01 JSON format and must satisfy the portal validations.
BUSY's e-invoice software integrates directly with all six authorised IRPs, generates IRN-compliant JSON automatically from your billing workflow, embeds the QR code on the final invoice copy, and enforces the 30-day reporting window for ₹10 crore-and-above taxpayers so your team doesn't need to manage portal deadlines manually.
Report the invoice data to the IRP
The invoice JSON is reported to the IRP through one of the available methods, such as:
- API integration
- GSP-based integration
- offline tool
- online web utility where available on the active portal ecosystem
Receive the IRN and signed payload
If validation succeeds, the IRP:
- generates the IRN
- digitally signs the invoice payload
- returns the QR code
- sends the data onward into the GST and e-way bill ecosystem for downstream use
The IRN is based on the supplier GSTIN, document type, document number, and financial year. This is why duplicate document reporting is blocked and why the same combination cannot be reused casually.
E-Invoice JSON Schema - Mandatory and Practical Fields
The invoice must conform to the current INV-01 schema and the live portal validations. GSTN and the official portal continue to publish schema-related tools and materials for bulk generation and validation.
Core field groups businesses must get right
In practical terms, invoice JSON preparation usually depends on accurate completion of these broad groups:
- document details
- supplier details
- recipient details
- item-level details
- tax details
- invoice totals
- supply-type and place-of-supply information where applicable
Businesses should follow the latest schema and current portal validations instead of relying on generic field lists copied from old blogs.
Important practical rule
From 1 June 2025, document numbers are treated as case-insensitive for IRN purposes. So a change from lowercase to uppercase does not create a different valid document for IRN computation.
QR Code in E-Invoice - What It Contains
Every authenticated e-invoice carries a QR code generated as part of the IRP response. The QR code supports quick verification of the invoice and helps confirm whether the invoice was genuinely reported.
It typically includes key particulars such as:
- supplier GSTIN
- recipient GSTIN
- invoice number
- invoice date
- invoice value
- IRN
- other core verification details embedded by the system
The practical rule remains simple: the invoice copy issued to the buyer should carry the QR code returned by the IRP so that the document can be verified properly.
E-Invoice Cancellation - The 24-Hour Rule
Cancellation on the IRP is allowed only within 24 hours of generation. After that, the IRP cancellation route closes.
Practical cancellation rules
| Timing | Status | Action |
|---|---|---|
| Within 24 hours | Active | Can be cancelled on IRP |
| After 24 hours | Locked | Cannot be cancelled on IRP |
If an active e-way bill already exists for the IRN, the system may not allow IRN cancellation until the e-way bill issue is addressed first.
Once cancelled, the same invoice number should not be treated as casually reusable within the e-invoicing logic. Businesses should reissue properly rather than trying to patch old document identity errors.
E-Invoice Amendment - How to Correct Errors
Amendment is not done on the IRP. If the reported invoice contains an error and cannot be cancelled on time, correction has to be handled through the GST return system and normal commercial correction routes such as credit notes or debit notes, depending on the nature of the error.
Practical distinction
| Issue | IRP route | Return / document route |
|---|---|---|
| Wrong invoice reported but within 24 hours | Cancel on IRP | Reissue correctly |
| Value or tax correction after 24 hours | No amendment on IRP | Correct through return process / note route |
| Major immutable identity error after 24 hours | No IRP fix | Manage through commercial correction and return treatment |
This is one of the most common operational failures in businesses that treat e-invoicing as a late-stage upload task. The later the IRN is generated, the less room there is to fix mistakes cleanly.
E-Way Bill Integration
E-invoicing and e-way bills are connected, but they are not the same compliance requirement. E-invoice data is shared with the e-way bill system and transport-related fields such as transporter ID and vehicle number can be used to create the e-way bill with minimal re-entry where available.
That said, businesses should not describe this as “every e-invoice automatically generates a complete e-way bill.” That is too broad. Transport details and e-way bill rules still matter independently.
For example: if a supplier generates an IRN for a dispatch-ready B2B invoice and already has transport details in the system, the e-way bill process becomes much faster. But if transport details are not available at that stage, separate completion and compliance checks are still needed.
Seamless E-Invoicing Compliance for Growing Businesses
GSTR-1 Auto-Population
Reported e-invoice data flows into the GST system and updates the supplier’s GSTR-1 . This is useful because it reduces repetitive entry, but it does not remove the need for reconciliation. Businesses still need to compare:
- books
- IRP-reported data
- GSTR-1
- cancellation and note adjustments
before filing their returns. That is especially important when corrections happen after the original IRN was already generated.
What to Do When You First Cross the Threshold
If your PAN-level turnover exceeds the notified e-invoicing threshold in any financial year from 2017-18 onwards, check applicability and portal status immediately and prepare your systems without delay. The requirement comes from the notification framework and Rule 48, while portal enablement is only the operational layer. If an eligible business issues covered invoices without following the prescribed e-invoicing process, the invoices may become invalid and may create downstream issues for customers, including Input Tax Credit disputes.
Taxpayers are generally enabled on the e-invoice system based on their reported Aggregate Annual Turnover. If your business is eligible but your GSTIN is still not enabled, the portal provides a self-enablement facility. Non-enablement on the portal does not by itself remove the compliance requirement.
Practical first steps
Check enablement
Confirm whether your GSTIN is enabled for e-invoicing through the official portal tools. This is an operational check and does not decide the legal obligation. Even if the portal status is not updated in time, you should still verify whether your business falls within the notified class and act accordingly.
Fix masters and invoice design
Review GSTIN masters, customer classification, supply-type mapping, item classification,
HSN reporting
, state codes, and invoice numbering before going live. Incorrect master data often leads to IRP rejection and correction issues after reporting. The e-invoice system also expects businesses above ₹5 crore AATO to use 6-digit HSN reporting for outward supplies.
Test your software flow
Make sure your ERP or billing system produces schema-compliant JSON, stores the IRN and acknowledgement details properly, and prints or embeds the QR code correctly on the final invoice copy. Use the official portal tools, documentation, and sandbox resources instead of relying on an older setup.
Train the billing team
Your billing and accounts team should understand three rules clearly. In covered cases, the invoice is not valid without a proper IRN workflow. Cancellation on the IRP is allowed only within 24 hours. Taxpayers with AATO of ₹10 crore and above cannot report invoices beyond 30 days from the document date.
System Readiness Checklist
Use this checklist before full rollout.
Infrastructure
- Billing or ERP system produces current INV-01 compliant JSON
- IRN, acknowledgement number, and response data are stored properly
- QR code can be printed or embedded on the final invoice copy
- Invoice numbering is controlled and consistent
- Customer GSTIN, HSN, and state-code masters are clean and updated
Portal and reporting
- GSTIN enablement has been checked
- Registration is completed on at least one authorised IRP
- An alternate IRP is known in case of operational issues
- The reporting flow has been tested using actual business invoice formats
Workflow
- B2B and B2C invoice logic is clearly separated
- Cancellation responsibility is assigned internally
- Post-24-hour correction workflow is documented
- Transport and e-way bill details are handled at the correct stage of billing and dispatch
Team readiness
- Finance and billing teams understand the significance of IRN
- Dispatch teams know that covered invoices should not move without compliant document flow
- Management knows whether the business falls within the ₹10 crore 30-day reporting category
Penalties and Practical Consequences of Non-Compliance
For notified persons, an invoice not issued in the prescribed e-invoicing manner is not treated as a valid invoice under Rule 48(5).
Section 122 of the CGST Act remains the broad statutory provision for invoice-related contraventions. Non-compliance may also lead to:
- invoice validity disputes
- buyer objections
- delayed payment processing
- return mismatches
- downstream ITC issues
- complications during movement of goods where documentation is questioned
For covered taxpayers, e-invoicing forms part of the legal identity of the invoice.
What Is Actually Changing in 2026-27
The 30-day rule continues for taxpayers with AATO of ₹10 crore and above
Invoices, credit notes, and debit notes covered by this rule cannot be reported after 30 days from the document date. Businesses using delayed batch uploads will face automatic rejection on the IRP, making those documents legally invalid.
Document numbers remain case-insensitive for IRN generation
The IRP change introduced on 1 June 2025 remains in effect for 2026-27. A change only in letter case (e.g., "INV01" vs "inv01") does not create a separate valid invoice identity for IRN purposes and will be flagged as a duplicate.
There is no official notification in force bringing a ₹2 crore threshold into effect
As of the 2026-27 cycle, the mandatory threshold remains at ₹5 crore AATO. A ₹2 crore threshold is speculative and should not be presented as current law unless a new official notification is issued by the GST Council.
Explore All BUSY Calculators for Easy GST Compliance
Conclusion
GST e-invoicing is now a core compliance requirement for a large slice of formal Indian businesses, not just big enterprises. As of April 2026, the law and portal ecosystem clearly support three practical truths:
- the main threshold remains AATO exceeding ₹5 crore
- taxpayers with ₹10 crore and above face a hard 30-day reporting block
- covered invoices become valid only when handled through the prescribed IRP process with a valid IRN
The best way to stay compliant is to check PAN-level applicability, verify enablement, make IRN generation part of the real invoice process, train teams on the 24-hour cancellation rule, and for ₹10 crore and above businesses, stop relying on delayed uploads.
-
GST Rates for ProductsGST Rates: GST for marriage hall GST for car GST on online gaming GST for vegetables cold drinks GST rate GST for restaurant GST on electricity GST for spices GST for bakery products GST rate for transportation GST for computer parts GST on camera GST on vehicle insurance gst on postpaid mobile bill GST for silk sarees GST on plastic items GST on consultancy services GST on movie tickets GST for electrical items GST on insurance premium
