GST E-Invoicing in 2026: The ₹5 Crore Threshold and the 30-Day Reporting Clock Explained
E-invoicing is mandatory once your turnover crosses ₹5 crore in any year since 2017-18, and businesses above ₹10 crore must report invoices to the IRP within 30 days or lose the IRN. Here is who must comply and how to avoid blocked invoices.
- E-invoicing applies once AATO crosses ₹5 crore in any year since FY 2017-18 — assessed on historical, PAN-wide turnover.
- Once you cross the threshold there is no exit, even if a later year's turnover falls below ₹5 crore.
- Businesses above ₹10 crore must report invoices to the IRP within 30 days of the invoice date or the IRN is blocked.
Two numbers decide your e-invoicing obligations: ₹5 crore and ₹10 crore. If your aggregate annual turnover (AATO) crossed ₹5 crore in any financial year since 2017-18, e-invoicing is mandatory for your B2B and export invoices (Tally Solutions, 2026). If you are above ₹10 crore, you also face a hard 30-day reporting clock that, if missed, permanently blocks that invoice's IRN — and the buyer's ITC with it. Both thresholds stay unchanged heading into FY 2026-27.
- E-invoicing applies once AATO crosses ₹5 crore in any year since FY 2017-18 — assessed on historical, PAN-wide turnover.
- Once you cross the threshold there is no exit, even if a later year's turnover falls below ₹5 crore.
- Businesses above ₹10 crore must report invoices to the IRP within 30 days of the invoice date (effective 1 April 2025).
- Miss the 30-day window and the portal blocks IRN generation — the invoice becomes invalid and ITC is lost for both sides.
Who must generate e-invoices?
Any business whose AATO exceeded ₹5 crore in any financial year from 2017-18 onwards must generate Invoice Reference Numbers (IRNs) for all B2B and export transactions (Tally Solutions, 2026). The test is historical and PAN-wide: if you crossed ₹5 crore even once, you are in — and you stay in even if turnover later dips. For FY 2026-27, the obligation triggers if your AATO crossed ₹5 crore in FY 2025-26.
What is the 30-day reporting rule?
From 1 April 2025, taxpayers with AATO of ₹10 crore and above must report each e-invoice — including credit and debit notes — to the Invoice Registration Portal within 30 days of the invoice date (VATupdate, 2025). This sharply lowered the earlier ₹100 crore threshold. An invoice dated 1 January cannot be uploaded after 30 January — the portal simply refuses the IRN.
What happens if I miss the 30-day window?
The IRP rejects the upload and no IRN is generated, so the invoice is not legally valid under GST (VATupdate, 2025). An unreported invoice cannot support ITC, so your buyer loses credit too — turning a back-office slip into a customer problem. The practical fix is a hard internal SLA: push every invoice to the IRP within a few days of issue, never near day 30.
Will the threshold drop further?
Possibly, but not yet. As of 2026 the mandatory threshold remains ₹5 crore, though proposals to lower it toward ₹2-3 crore have been discussed (ClearTax, 2026). Businesses sitting just below ₹5 crore should set up IRP access proactively rather than scrambling after a notification. Note that SEZ units, banks, NBFCs, insurers, goods transport agencies and passenger transport are exempt.
Frequently Asked Questions
What is the e-invoicing turnover threshold in 2026?
₹5 crore aggregate annual turnover. If your AATO crossed ₹5 crore in any financial year from 2017-18 onwards, e-invoicing is mandatory for B2B and export invoices. The threshold is assessed on historical, PAN-wide turnover and has not changed for FY 2026-27.
If my turnover falls below ₹5 crore later, can I stop e-invoicing?
No. Once you cross the ₹5 crore threshold in any year since FY 2017-18, the obligation is permanent. GST authorities consider historical turnover, so a later dip below ₹5 crore does not exempt you. You must keep generating IRNs for all eligible invoices.
Does the 30-day reporting rule apply to my ₹6 crore business?
Not yet. The 30-day reporting restriction currently applies only to businesses with AATO of ₹10 crore and above, effective 1 April 2025. A ₹6 crore business must still generate e-invoices but has no time-bound reporting limit — though reporting in real time is best practice in case the rule is extended.
What is the penalty for late e-invoice reporting?
The portal blocks IRN generation entirely once 30 days pass from the invoice date for ₹10 crore+ filers. Without an IRN the invoice is invalid under GST, cannot support ITC, and your buyer loses credit. Beyond that, general GST penalties for incorrect or non-compliant invoicing can apply.
What should you do next?
Confirm which band you fall in, and if you are above ₹10 crore, set a 5-7 day internal SLA between invoice date and IRP upload with a buffer well short of day 30. For setup and ongoing compliance, see Bizeract e-invoice registration and our GST 2.0 slab reset guide for the FY 2026-27 invoice housekeeping that goes with it.
What should you verify before using this GST & Finance Updates guide?
Before acting on gst e-invoicing in 2026, verify the current rules or platform behavior with the GST Portal. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.
Use this article as a working checklist, then confirm thresholds, registration status, return forms, document rules, and portal notices. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.
| Checkpoint | Why it matters | Where to confirm |
|---|---|---|
| Current rule or platform status | Limits, forms, policies, and APIs can change after a blog update. | GST Portal |
| Your exact business case | A local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step. | Documents, invoices, campaign data, analytics setup, or workflow logs |
| Implementation evidence | The safest GST decision is backed by proof, not memory or screenshots from an old setup. | Portal acknowledgement, dashboard export, invoice sample, test lead, or error log |
How do we apply this in real business work?
We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.
A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.
When should you get expert review?
Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.
How often should this be rechecked?
Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.
What is the fastest safe way to decide?
Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.
What can go wrong if you skip verification?
The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.
What evidence should you keep after making the change?
Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.
This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.
- Date checked: record when the official source, dashboard, or portal screen was reviewed.
- Business context: note the entity, state, product, campaign, property, or workflow affected.
- Proof of action: save the acknowledgement, report export, test result, or live URL.
- Owner: assign one person to re-check the item when rules, tools, or business volume change.
Which next step should you take after reading this?
Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with E-Invoice Registration, Monthly GST Return Filing, and GST Registration. Then update the decision only after the official source and your own records agree.
Frequently asked questions
What is the e-invoicing turnover threshold in 2026?
₹5 crore aggregate annual turnover. If your AATO crossed ₹5 crore in any financial year from 2017-18 onwards, e-invoicing is mandatory for B2B and export invoices. The threshold is assessed on historical, PAN-wide turnover and has not changed for FY 2026-27.
If my turnover falls below ₹5 crore later, can I stop e-invoicing?
No. Once you cross the ₹5 crore threshold in any year since FY 2017-18, the obligation is permanent. GST authorities consider historical turnover, so a later dip below ₹5 crore does not exempt you. You must keep generating IRNs for all eligible invoices.
Does the 30-day reporting rule apply to my ₹6 crore business?
Not yet. The 30-day reporting restriction currently applies only to businesses with AATO of ₹10 crore and above, effective 1 April 2025. A ₹6 crore business must still generate e-invoices but has no time-bound reporting limit — though reporting in real time is best practice in case the rule is extended.
What is the penalty for late e-invoice reporting?
The portal blocks IRN generation entirely once 30 days pass from the invoice date for ₹10 crore+ filers. Without an IRN the invoice is invalid under GST, cannot support ITC, and your buyer loses credit. Beyond that, general GST penalties for incorrect or non-compliant invoicing can apply.
Let's talk about your business.
Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.
- Free 30-minute call
- A plan built around your goals
- No obligation, no pressure
- Your own account manager