CBIC reduces Limit for E-invoice

CBIC reduces Limit for E-invoice

Every GST-registered business with an aggregate turnover exceeding ₹5 crore in any preceding financial year from FY 2017-18 onwards must generate e-invoices for B2B supplies, exports and supplies to SEZ units. This threshold, in force since 1 August 2023, continues through FY 2026-27 unchanged. The "preceding year" test means the obligation is triggered once and stays — there is no exit if your turnover later falls. Invoices issued without a valid Invoice Reference Number (IRN) are invalid under Rule 48(5) of the CGST Rules; your buyer's input tax credit can be denied as a direct consequence.

How the Threshold Evolved — and Why the ₹5 Crore Level Matters

CBIC has compressed the e-invoice threshold in six steps since the system launched in October 2020:

The governing provision is Rule 48(4) of the CGST Rules, 2017, inserted by Notification No. 68/2019-Central Tax and progressively amended. The specific notification reducing the threshold to ₹5 crore is Notification No. 10/2023-Central Tax dated 10 May 2023, effective 1 August 2023. As of FY 2026-27 this threshold remains in force — CBIC has made no announcement of a further reduction, though the direction of travel since 2020 suggests it is a matter of when, not if.

The practical impact of the ₹5 crore cut-off is substantial. The shift from ₹10 crore to ₹5 crore brought an estimated additional one to one-and-a-half lakh businesses into the mandatory system, most of them manufacturers, distributors, wholesalers and service firms that had never previously interacted with the Invoice Registration Portal (IRP). For these businesses, readiness is not a future agenda item — it is an overdue compliance obligation.

Who Is Covered, and Who Is Not

Covered Taxpayers

You must generate e-invoices if all three of the following conditions apply simultaneously:

1. You are a GST-registered supplier (the obligation rests with the supplier, not the recipient).
2. Your aggregate turnover in any preceding financial year from FY 2017-18 onwards exceeded ₹5 crore.
3. The transaction is a B2B supply, export, supply to an SEZ unit or developer, or a deemed export.

The most misread element here is the phrase "any preceding financial year." If your turnover was ₹6 crore in FY 2021-22 but has since settled at ₹3 crore, you remain covered in FY 2026-27 and every subsequent year. There is no provision in Rule 48 for a taxpayer to exit the e-invoicing obligation once triggered.

Transactions That Require an IRN

• Tax invoices for B2B supplies to registered persons (domestic)
• Credit notes and debit notes issued to registered buyers
• Exports with payment of IGST
• Exports under bond or LUT (zero-rated supplies)
• Supplies to SEZ units or SEZ developers (with or without IGST)
• Deemed exports notified under Notification No. 48/2017-Central Tax

Transactions Exempt from E-Invoicing

• B2C supplies to unregistered persons (separate QR code provisions apply above ₹500 crore, but not via the IRP)
• Supplies by banks, financial institutions and NBFCs
• Insurance companies and the General Insurance Council
• Goods Transport Agencies issuing consignment notes
• Passenger transportation service providers
• Multiplex operators issuing admission tickets
• Free samples and gifts on which no GST is charged
• SEZ units acting as suppliers (they are exempt as suppliers; the obligation applies when they are the recipient and the selling party meets the threshold)
• Government departments and local authorities that are not required to be registered under GST

How to Calculate Your Aggregate Turnover

Aggregate turnover is computed at the PAN level, aggregating all GSTINs registered under that PAN across all states. It includes taxable supplies, exempt supplies, export supplies and the value (not the tax) of supplies taxable under reverse charge. It excludes CGST, SGST, IGST, compensation cess and inward supplies taxable under reverse charge.

Worked example — Multi-GSTIN aggregation:

Vijay Polymers Private Limited holds two GSTINs — Maharashtra (turnover ₹3.8 crore in FY 2024-25) and Gujarat (₹1.4 crore). Neither GSTIN individually crosses ₹5 crore. But aggregate turnover = ₹5.2 crore. Vijay Polymers is required to generate IRNs from 1 April 2025 onwards and continues under the obligation through FY 2026-27. Failure to check across GSTINs is one of the most common reasons businesses unknowingly remain non-compliant.

What an E-Invoice Actually Is — Clearing Up the Confusion

Many business owners assume e-invoice means a government-mandated template replacing their current invoice design. It does not.

An e-invoice is your existing GST tax invoice — with your letterhead, columns and branding — reported to the IRP before issuance to the buyer. The IRP validates mandatory fields, checks for duplicate invoice numbers under your GSTIN, assigns a unique IRN (a 64-character alphanumeric hash), digitally signs the JSON payload, and generates a QR code encoding key parameters.

You then embed this IRN and QR code on the invoice and deliver it to the buyer. Your invoice format is unchanged; only two new data elements are added.

What the IRP Auto-Populates

Once the IRP generates an IRN, the invoice data flows automatically to:

• GSTR-1 (Tables 4A, 4B, 6B, 6C as applicable) — eliminating manual entry for reported invoices
• Part A of the e-Way Bill — for goods consignments, removing the need to re-enter invoice details
• Buyer's GSTR-2B — giving the recipient a monthly confirmed view of available ITC

This integration is not cosmetic. It is the mechanism by which e-invoicing becomes the real-time spine of GST compliance — errors caught at source, data flowing forward without manual re-keying, and reconciliation effort dramatically reduced.

Step-by-Step IRP Workflow

Step 1: Prepare the Invoice JSON

Your ERP or accounting software must produce the invoice in the JSON schema prescribed by GSTN (currently Schema Version 1.1). Key mandatory fields include: supplier GSTIN, buyer GSTIN, place of supply state code, HSN/SAC codes, item-level quantities and values, tax rates and amounts, invoice number and date. Test your output in the IRP sandbox at sandbox.einvoice1.gst.gov.in before going live.

Step 2: Choose Your Upload Route

For most MSMEs entering the ₹5 crore bracket, a licensed GSP is the practical sweet spot — the GSP manages API authentication, error handling and retry logic, and most offer integration plugins for Tally, Busy and other popular packages.

Step 3: Receive IRN and QR Code

Within seconds (longer during peak filing periods), the IRP returns the IRN, a digitally signed JSON, and a QR code string or image. Your software must store all three against the invoice master record.

Step 4: Print the IRN and QR Code on the Invoice

The IRN and QR code must appear on the invoice delivered to the buyer — whether as a paper printout, PDF email attachment or EDI transmission. There is no prescribed location on the invoice, but both elements must be present.

Step 5: Manage Errors Within 24 Hours

If you discover an error immediately after IRN generation, cancel the IRN within 24 hours on the IRP. After 24 hours the IRN is locked — no amendment is possible on the IRP. To correct the invoice after the window, issue a credit note linked to the original IRN and generate a fresh invoice. Note: IRN cancellation does not auto-cancel the e-Way Bill generated against it; cancel the e-Way Bill separately if goods have not moved.

Worked Example: Sizing the Penalty Exposure

Let us put a rupee figure on what non-compliance actually costs.

Scenario: Rajesh Engineering Works, a Pune-based manufacturer, crossed ₹5 crore in aggregate turnover in FY 2023-24 but was unaware of the IRP obligation. Through April and May 2026, the firm issues 240 B2B invoices — total taxable value ₹1.8 crore, IGST at 18% = ₹32,40,000 — without generating any IRNs.

Legal consequence under Rule 48(5): All 240 invoices are deemed invalid as GST tax invoices.

Penalty under Section 122(1) of the CGST Act: The penalty for issuing an invoice in contravention of the Act's provisions is ₹10,000 per invoice or the tax involved, whichever is higher.

• Average IGST per invoice = ₹32,40,000 ÷ 240 = ₹13,500
• Since ₹13,500 exceeds ₹10,000, the applicable penalty is ₹13,500 per invoice
• Total potential penalty = 240 × ₹13,500 = ₹32,40,000

Rajesh Engineering Works faces a penalty bill equivalent to the entire GST it collected during those two months.

Ripple effect on buyers:

One of Rajesh's customers booked ITC of ₹5,00,000 in April 2026 against these invalid invoices. When a notice is issued in August 2026 (say, 120 days after availment), the buyer must reverse ₹5,00,000 and pay interest at 18% per annum from the date of original availment.

Interest = ₹5,00,000 × 18% × 120 ÷ 365 = approximately ₹29,589

The buyer is out ₹5,29,589 through no fault of its own process — and may face its own scrutiny for inadequate vendor due diligence. This is precisely why IRN verification is now a procurement-level requirement, not just a finance-team formality.

Common Mistakes — and How to Avoid Them

Mistake 1: Treating the ₹5 Crore Test as the Current Year's Turnover

The obligation looks backward, not at the current year. Run a PAN-level turnover check across all GSTINs for every financial year from FY 2017-18. If the aggregate crossed ₹5 crore in even one of those years, you are covered today.

Mistake 2: Excluding Exempt Supplies from the Aggregate

Aggregate turnover includes exempt supplies. A trader who sells both taxable and exempt goods (e.g., certain agricultural inputs) may incorrectly compute aggregate turnover by looking only at the taxable invoice register. Include all supply values before concluding you are below the threshold.

Mistake 3: Generating Invoices First, Uploading IRNs Later

Some businesses generate invoices in their ERP, dispatch goods, and batch-upload to the IRP at day-end or week-end. This is impermissible. The IRN must exist before the invoice reaches the buyer. Retroactive IRN generation for already-dispatched invoices creates both legal exposure and reconciliation complications — particularly if the invoice date is in a prior GSTR-1 filing period.

Mistake 4: Stale Buyer GSTIN Data in the Customer Master

The IRP validates the buyer's GSTIN in real time. An inactive, cancelled or incorrectly entered GSTIN causes an IRN push failure. Implement a quarterly GSTIN verification routine against the GST portal's Search Taxpayer function at gst.gov.in/searchablelist. Many GSPs offer bulk GSTIN validation as a standard feature.

Mistake 5: Ignoring Error Logs on the GSP or IRP Portal

Every failed IRN push generates a logged error with a specific error code. Businesses that ignore these logs accumulate uncomplied invoices, discovered only when a GST officer or a buyer's accounts-payable team raises a flag — sometimes months later when the 24-hour correction window is long past.

Mistake 6: Assuming Credit Notes Are Outside the Scope

Credit notes issued to registered persons by covered taxpayers require IRN generation. This is frequently missed during year-end volume adjustments, price revisions and return settlements. Every such uninvoiced credit note creates the same invalid-document exposure as a missing invoice IRN.

Mistake 7: Not Training the Dispatch Team

The e-invoicing compliance gap often lives in the warehouse, not in the accounts office. Dispatch staff release goods against pre-IRN drafts because "the accounts team will sort it out." Implement a physical or system-level lock: no goods leave the dock without an IRN-bearing invoice attached to the consignment.

Protecting Your ITC as a Buyer

If you purchase goods or services from suppliers who should be generating e-invoices, your ITC is only as secure as their compliance. Here is what your accounts-payable process should include:

1. Pre-onboarding turnover check: Before adding a new vendor, assess whether their turnover likely exceeds ₹5 crore. If yes, insist on e-invoices as a condition of payment terms.

1. QR code verification at the invoice stage: Scan the QR code on incoming invoices using the NIC QR Code Verifier (available on the e-invoice portal or as a mobile app). The scan confirms whether the IRN is genuine, active and uncancelled.

1. GSTR-2B reconciliation before ITC booking: If a supplier's invoice does not appear in your monthly GSTR-2B, it was not reported on the IRP. Do not book that ITC until the GSTR-2B entry is confirmed — even if the supplier insists the invoice is valid.

1. Contractual protection: Include an e-invoice warranty clause in your standard purchase orders: "The supplier confirms that all tax invoices issued under this purchase order will carry a valid IRN as required under Rule 48(4) of the CGST Rules, 2017, and that the supplier meets the eligibility threshold for e-invoicing."

FY 2026-27 Action Plan for Covered Businesses

1. Re-verify your trigger. Pull consolidated turnover data from GSTR-3B for all GSTINs under your PAN for FY 2017-18 through FY 2025-26. Add up the aggregate for each year. A single year above ₹5 crore means you are covered for FY 2026-27.

2. Choose integration mode proportionate to volume. Fewer than 20 invoices per day: IRP Excel utility is adequate. Between 20 and 100: engage a licensed GSP. Above 100 per day: invest in direct API integration within your ERP — the ROI in reduced GSTR-1 entry errors and auto-populated e-Way Bills typically pays back the development cost within two quarters.

3. Set up real-time failure alerts. Configure your GSP or ERP to trigger an SMS or email notification the moment an IRN push fails. Do not discover failures at month-end when the 24-hour correction window has closed.

4. Reconcile IRNs against GSTR-1 before filing. Download your IRN log from the IRP portal (available under the "Report" section) and compare it with GSTR-1 auto-population. Unexplained discrepancies — invoices in GSTR-1 without a corresponding IRN, or IRNs not appearing in GSTR-1 — must be investigated and resolved before filing.

5. Establish a 6-hour internal review SLA. Build a process whereby every IRN generated is reviewed by the accounts team within six hours. This keeps error correction well within the 24-hour cancellation window.

6. Retain IRN logs as statutory records. Under Section 36 of the CGST Act, GST records must be retained for 72 months (six years) from the due date of the relevant annual return. Your IRN log, signed JSON files and QR code records are part of these statutory records. Store them in a retrievable format — not just on a GSP dashboard that may change or lapse.

7. Explore TReDS and invoice discounting. E-invoices carrying valid IRNs are electronically verifiable and therefore more readily accepted on Trade Receivables Discounting System (TReDS) platforms. For MSMEs with working capital pressure, the ability to discount validated receivables against IRP-confirmed invoices can meaningfully reduce financing costs — a benefit that extends well beyond GST compliance.

Key Takeaways

• The ₹5 crore aggregate turnover threshold for mandatory e-invoicing has been in force since 1 August 2023, under Notification No. 10/2023-Central Tax, and continues unchanged through FY 2026-27.
• The trigger tests any preceding financial year from FY 2017-18 at the PAN level, aggregating all GSTINs — neither GSTIN needs to individually cross ₹5 crore, and once triggered the obligation never lapses.
• Exempt supply value counts toward the aggregate — do not compute aggregate turnover from the taxable invoice register alone.
• An invoice issued without a valid IRN is legally invalid under Rule 48(5) and renders the recipient's ITC under Section 16 vulnerable to denial or reversal with 18% per annum interest.
• Penalty exposure under Section 122 can reach ₹10,000 per invoice or the GST amount on that invoice, whichever is higher — in a typical MSME scenario with average invoice tax above ₹10,000, this equals the entire GST collected on non-compliant transactions.
• The 24-hour IRN cancellation window is an absolute limit; after expiry, only a credit note can correct the original document, and the e-Way Bill must be cancelled separately.
• Treat GSTR-2B verification and QR code scanning as standard accounts-payable steps before booking ITC — your ITC is only protected to the extent your supplier's IRP compliance is verified.