Mandatory E-Invoices with turnover 5 Crore

No matching skills found for this content writing task. Proceeding directly to generate the blog post.

Mandatory E-Invoices with Turnover 5 Crore

If your business's aggregate turnover crossed ₹5 crore in any financial year from FY 2017-18 onwards, you are required to generate a valid Invoice Reference Number (IRN) and embed a GSTN-signed QR code on every B2B invoice, export invoice, credit note, and debit note you issue — effective 1 August 2023, per CBIC Notification No. 10/2023-CT dated 10 May 2023. An invoice without an IRN is not a valid tax invoice under Section 31 of the CGST Act, 2017. Your buyer cannot claim Input Tax Credit (ITC) on it, and you face a penalty of ₹10,000 per document under Section 122.

Why the ₹5 Crore Threshold Is a Hard Line, Not a Guideline

The CBIC has progressively collapsed the e-invoicing turnover threshold over five years:

The current ₹5 crore limit captures almost every mid-market manufacturer, trader, and exporter in India. There is no indication that the threshold will rise — the direction of travel has been consistently downward, and a ₹1 crore threshold for FY 2027-28 is widely anticipated in the GST Council discussions.

Two features of the threshold make it a hard line:

1. Once crossed, always applicable. If your aggregate turnover exceeded ₹5 crore in any financial year from FY 2017-18 to FY 2025-26, e-invoicing is mandatory for you in FY 2026-27 — even if your current-year turnover has since fallen below ₹5 crore.

1. No grace period on the first invoice. The obligation applies from the first taxable supply you make after crossing the threshold. There is no interim window or cooling-off period.

What Counts as Aggregate Turnover — and Two Traps to Avoid

"Aggregate turnover" for e-invoicing purposes follows the definition in Section 2(6) of the CGST Act: the sum of all taxable supplies, exempt supplies, exports, and inter-state supplies of persons having the same Permanent Account Number (PAN), computed across all GSTINs on an all-India basis.

This creates two traps that regularly catch businesses off guard.

Trap 1 — Multiple GSTINs under one PAN are aggregated. A trading company with GSTINs in Maharashtra, Delhi, and Karnataka must add up the turnovers of all three registrations. If the Maharashtra unit alone shows ₹3 crore but the combined PAN-level turnover is ₹6 crore, every GSTIN is inside the e-invoicing net.

Trap 2 — Exempt turnover counts. A pharma distributor selling both GST-exempt medicines and taxable medical devices must include the exempt sales in the turnover computation. Many businesses dealing in exempt goods assume they are outside the threshold — they are not, if total supplies exceed ₹5 crore.

What does not count toward aggregate turnover: central tax (CGST), state tax (SGST/UTGST), integrated tax (IGST), and cess. Also excluded: inward supplies taxed under reverse charge.

Transactions That Must Carry an IRN in FY 2026-27

Not every document you issue is e-invoice-mandated. Use this checklist to map your document types correctly.

IRN mandatory:

• B2B supply invoices for goods and services (supply type: B2B)
• Export invoices — goods and services (supply type: EXPWP or EXPWOP)
• Supplies to SEZ developers and units — with or without payment of tax (supply type: SEZWP or SEZWOP)
• Deemed export invoices
• Credit notes and debit notes issued against any of the above
• Bill of supply (where applicable, e.g., exempt supplies by registered supplier)

Outside the e-invoice mandate:

• B2C invoices (you still need a dynamic QR code under Rule 46(r) of the CGST Rules if turnover exceeds ₹5 crore, but that is a separate obligation — no IRN is generated)
• Supplies where an e-commerce operator pays GST under Section 9(5) (Zomato, Ola, Swiggy model)
• Supplies by banking companies, insurance companies, NBFCs (notified via Notification No. 13/2020-CT, as amended)
• Supplies by Goods Transport Agencies (GTA) and passenger transport services
• Special Economic Zone units (not developers) for inward supplies
• Invoices issued under the Input Service Distributor (ISD) mechanism

If you are unsure whether a specific document type falls within the mandate, check the e-invoice applicability tool on einvoice1.gst.gov.in — it lets you verify using your GSTIN and supply type before you commit to a workflow.

The E-Invoice Workflow — How a Valid IRN Gets Generated

The e-invoice workflow is not a separate invoicing system. It is a reporting layer that sits on top of your existing invoicing process. Here is the exact sequence:

1. Create the invoice in your ERP or accounting software using your normal process. The invoice data must conform to the GST e-invoice JSON schema (Schema version 1.1) — fields include supplier GSTIN, recipient GSTIN, HSN/SAC code, tax amounts, and document type.

1. Push the JSON to the Invoice Registration Portal (IRP). You can use:
2. The NIC-operated IRP at einvoice1.gst.gov.in (API or offline utility)
3. Any of the six authorised private IRPs (Cygnet, Clear, IRIS, E&Y, Deloitte, Ernst & Young — list current as of FY 2026-27; verify on GSTN website)
4. Your ERP's built-in IRP integration if it is API-enabled (Tally Prime, SAP, Zoho Books, Busy Accounting have live integrations)

1. IRP validates the JSON. It checks structural integrity, supplier and recipient GSTINs against the GSTN database, HSN/SAC codes against the master, and tax computation accuracy.

1. On success, IRP returns a digitally signed response containing:
2. The IRN — a 64-character alphanumeric hash unique to the document
3. A signed QR code carrying key invoice parameters
4. A digitally signed invoice JSON (the Signed Invoice)

1. Embed the IRN and QR code on the printed or PDF invoice before dispatching it to the buyer. The QR code must be scannable — minimum print size standards apply.

1. Dispatch the invoice to the recipient. Share the Signed JSON via your ERP's API push or download from the IRP portal.

1. Data flows automatically to GSTR-1 via the GSTN-IRP link, typically within 24 hours of IRN generation. From GSTR-1, it flows to the recipient's GSTR-2B, enabling ITC claim.

1. If the supply involves goods moving interstate, the e-way bill can be generated simultaneously at the IRP step — the IRN and e-way bill number are linked, saving a separate login.

Cancellation rule: An IRN can be cancelled only within 24 hours of generation. After 24 hours, cancellation is not permitted on the portal. If you discover an error after 24 hours, you must issue a credit note to reverse the original invoice and generate a fresh IRN for the corrected invoice.

Worked Example: What Non-Compliance Actually Costs

Consider a Pune-based auto component manufacturer — call it Precision Parts Pvt. Ltd. — with a PAN-level turnover of ₹8.5 crore in FY 2025-26. E-invoicing was mandatory from 1 August 2023, and Precision Parts has been using it correctly for outward B2B supplies.

In Q2 FY 2026-27 (July–September 2026), the ERP team upgrades the billing module. During the migration, the IRP API push breaks silently. For 45 days, invoices are generated in the ERP but the JSON is never pushed to the IRP. No IRN is generated. 52 B2B invoices go out without an IRN.

The compliance exposure:

The pure Section 122 minimum penalty exposure is ₹5.2 lakh. If the GST officer frames it as tax evasion (which is increasingly common in risk-based audit selection), the penalty can scale to the full tax amount of ₹18 lakh. Beyond the monetary cost, every buyer whose GSTR-2B is short receives a notice from their jurisdictional officer, and Precision Parts becomes a "risky supplier" in those buyers' vendor compliance ratings.

The fix — retroactive IRN generation — is not available after 24 hours. The correct remediation is to contact each buyer, issue credit notes for all 52 invoices with correct IRN, and re-invoice with fresh IRNs. That is 104 additional documents, plus amended GSTR-1 filings for the months affected.

Lesson: A silent API failure costs more than the fix ever would. Build a daily IRN reconciliation check into your closing process.

Penalties Under Section 122 — The Numbers You Need to Know

The penalty framework for e-invoice non-compliance is worth understanding in precise terms, not summaries.

Section 122(1)(ii) of the CGST Act penalises a taxable person who issues a tax invoice or makes a supply without issue of an invoice at ₹10,000 or the amount of tax evaded, whichever is higher, per offence (i.e., per invoice).

Section 16(2)(aa) of the CGST Act (inserted by the Finance Act 2022) provides that ITC is available to a recipient only to the extent that the invoice appears in the supplier's GSTR-1 and is reflected in the recipient's GSTR-2B. An invoice without an IRN will not auto-populate GSTR-1, meaning the buyer's GSTR-2B is zero for that transaction, and ITC is blocked until the supplier corrects the situation.

Cascading risk: A large buyer running a vendor compliance programme will blacklist suppliers who repeatedly cause ITC mismatches. In capital-intensive industries like infrastructure, pharma, and automotive, ITC blockage of even ₹5 lakh per month is significant enough to trigger vendor replacement.

Risk-based audit selection: GSTN's analytics engine flags GSTINs with high IRP-failure rates. Once flagged, a GSTIN enters the enhanced scrutiny queue, increasing the probability of a Section 73 (non-fraud) or Section 74 (fraud) SCN (Show Cause Notice) for the entire period under examination — not just the offending invoices.

Common Mistakes in E-Invoice Implementation

These are the errors that appear most frequently in practice — and how to correct each one.

1. Generating the invoice in ERP first, forgetting to push to IRP. Fix: Configure your ERP to block invoice dispatch (PDF generation or printing) unless the IRN field is populated. Most modern ERPs support this workflow lock.

2. Trying to cancel an IRN after 24 hours. Fix: The 24-hour window is absolute. After expiry, issue a credit note linked to the original IRN and re-invoice. Document the error in your books.

3. Wrong supply-type code. Sending an SEZ supply as B2B instead of SEZWP means the IRP returns an IRN, but the downstream data in GSTR-1 is classified incorrectly. This triggers mismatches when the SEZ unit files its returns. Fix: Build a supply-type mapping table in your ERP keyed to customer master (B2B, SEZ, export, deemed export).

4. Mismatched recipient GSTIN. A single-character typo in the 15-digit GSTIN causes IRP rejection. The error is not always immediately visible if your ERP does not surface IRP error codes prominently. Fix: Validate recipient GSTINs against the GST search tool (taxpayersearch.gst.gov.in) at the customer onboarding stage, not at invoicing.

5. HSN/SAC mapping errors. IRP validates HSN codes against the master. An outdated 4-digit HSN code where 6 or 8 digits are required (based on turnover) will be rejected. Fix: Update your item master to include the correct HSN digits as mandated by your turnover bracket.

6. Portal downtime — no manual workaround. GSTN portals experience periodic downtime. Without a documented workaround (offline utility, secondary IRP, or a pre-approved manual invoice procedure), your dispatch operations stop. Fix: Maintain a backup IRP subscription (most authorised IRPs offer this). Document the GSTN downtime SOP in your accounts manual.

7. Not reconciling IRN with GSTR-1 monthly. Auto-population does not mean error-free population. Occasionally, data pushed to IRP does not flow to GSTR-1 due to technical errors. Fix: Run a monthly IRN-to-GSTR-1 reconciliation report before GSTR-1 filing (due by the 11th of the following month for monthly filers).

Benefits Beyond Compliance: Why This Actually Helps Your Business

E-invoicing is not just a regulatory burden — it restructures your billing workflow in ways that deliver measurable operational gains.

Faster ITC for your buyers. IRN-backed invoices appear in GSTR-2B within 24–48 hours. Buyers who previously waited until GSTR-1 was filed (up to the 11th of the following month) can now claim ITC faster. Large buyers will explicitly prefer IRN-backed vendors for this reason.

Elimination of GSTR-1 data entry. Once your ERP pushes to IRP, GSTR-1 for B2B supplies is auto-populated. For businesses with hundreds of monthly B2B invoices, this removes significant manual data entry and the reconciliation effort that follows.

Reduced Section 73/74 notices. Automated data in GSTR-1 means fewer mismatches against GSTR-3B. Fewer mismatches mean fewer ASMT-10 intimations and SCNs.

Seamless e-way bill generation. For goods in transit, the IRN and e-way bill can be generated in a single API call. This saves the logistics team a separate login and reduces the risk of goods moving without an e-way bill.

Better GST compliance rating. GSTN's compliance rating system (currently in development for public disclosure) will factor in consistent IRN generation. Larger corporate buyers are already using portal-based vendor compliance checks during procurement empanelment.

Your 90-Day Rollout Playbook

If you are crossing the ₹5 crore threshold during FY 2026-27 — or if you have crossed it and are still not compliant — use this structured rollout.

Days 1–15: Foundation

• Confirm aggregate turnover across all GSTINs for the trigger year using your GSTR-3B data.
• Register on einvoice1.gst.gov.in — your GSTN login credentials work here.
• Select your IRP: NIC IRP (free) or a private authorised IRP (fee-based, with better support SLAs).
• Decide on integration approach: offline Excel utility (suitable for <20 invoices/day), mobile app (NIC's e-Invoice app), or ERP API integration (recommended for >20 invoices/day).

Days 16–45: Configure and Test

• Update your ERP item master with correct HSN/SAC codes and supply-type flags.
• Update the customer master with validated GSTINs and supply-type classification (B2B, SEZ, export, etc.).
• Configure the ERP–IRP API integration in the sandbox environment at einvoice1.gst.gov.in.
• Run 15–20 test invoices in sandbox, verify IRN generation, QR code rendering, and GSTR-1 auto-population.
• Rework the invoice PDF/print template to include the QR code (minimum 2 cm × 2 cm scannable area) and IRN field.
• Train the billing and finance teams on the new workflow, especially the 24-hour cancellation rule.

Days 46–75: Go Live

• Switch to production IRP.
• Monitor daily: IRN success rate, IRP rejection codes, GSTR-1 auto-population match.
• Build a simple dashboard (even a shared Excel or Google Sheet) showing total invoices issued vs. IRNs generated for the day.
• Establish the credit-note SOP for post-24-hour corrections.
• For inter-state goods movement, integrate the e-way bill step into the IRP push workflow.

Days 76–90: Stabilise

• Embed IRN reconciliation into your monthly closing checklist (compare IRN register with GSTR-1 before filing).
• Subscribe to GSTN portal downtime alerts (available via official GSTN Twitter / WhatsApp advisory channel).
• Document the manual fallback procedure for downtime scenarios.
• Conduct a post-implementation review: What failed? What slowed dispatch? Fix the root causes structurally.

By the end of the 90-day window, IRN generation should be as automatic as invoice numbering. The first quarter is operational, the second quarter is routine, and from the third quarter onwards you are drawing the data-quality dividend — accurate GSTR-1, faster buyer ITC, fewer notices.

Key Takeaways

• The ₹5 crore threshold is permanent once crossed — even if turnover later falls below ₹5 crore, e-invoicing remains mandatory.
• Aggregate turnover is PAN-level, not GSTIN-level — add up all registrations and include exempt supplies in the count.
• An invoice without an IRN is not a valid tax invoice under Section 31 — your buyer cannot claim ITC, and you face a minimum ₹10,000 penalty per document under Section 122.
• IRN cancellation is only possible within 24 hours — after that, you must issue a credit note and re-invoice.
• Silent API failures are the most dangerous risk — build a daily IRN-vs-invoices-issued reconciliation check; do not rely on your ERP's green light alone.
• GSTR-1 auto-population does not replace reconciliation — verify that every IRN has flowed to GSTR-1 before filing on or before the 11th of the following month.
• Private authorised IRPs offer better uptime SLAs than the NIC IRP for high-volume businesses — factor this into your IRP selection if you issue more than 100 B2B invoices daily.