30 Day E-Invoice Rule for GST

30 Day E-Invoice Rule for GST

From April 2026, every B2B tax invoice subject to e-invoicing must reach the Invoice Registration Portal (IRP) within 30 calendar days of the invoice date. Miss that window and the IRP rejects the JSON outright — no Invoice Reference Number (IRN) is generated, your buyer's Input Tax Credit (ITC) is blocked in GSTR-2B, and the supply cannot be reported in GSTR-1. For any business above the prevailing CBIC e-invoicing threshold (Rs. 5 crore aggregate annual turnover as notified), this rule is now a hard system constraint enforced at the API level — not a compliance suggestion your team can finesse after the fact.

What the 30-Day Rule Actually Says

The legal backbone is Rule 48 of the Central Goods and Services Tax Rules, 2017, which requires notified taxpayers to generate e-invoices by uploading invoice details to the IRP before or at the time of supply. The 30-day upload window was introduced by GSTN to close a persistent loophole: businesses were generating IRNs weeks or months after actual supply, undermining the real-time audit trail CBIC is building toward.

The rule covers:

• Tax invoices for all B2B supplies (goods and services)
• Credit notes linked to B2B invoices
• Debit notes issued to registered recipients
• Export invoices, including zero-rated supplies under a Letter of Undertaking (LUT)
• Supplies to SEZ units and developers — note that SEZ units as suppliers are exempt from e-invoicing, but supplies to SEZ units require the supplier to generate an IRN

The clock starts on the date printed on the invoice document — not the upload date, not the delivery date, and not the date your ERP generated a draft.

If you attempt to upload an invoice dated more than 30 days before today, the IRP returns an error at the JSON validation stage — effectively Error Code 2150 in the GSTN error directory: "Invoice date is not within the allowed time period." No IRN, no QR code, no signed XML. The invoice exists in your books but is legally not an e-invoice under Rule 48.

One important nuance: the 30-day clock governs IRN generation, not subsequent amendment. If you generate an IRN within the window and later need to correct the invoice, you follow the standard amendment path through GSTR-1 — the 30-day constraint does not restart.

Who Falls Within the Net in FY 2026-27

CBIC has progressively reduced the e-invoicing threshold since the scheme launched at Rs. 500 crore in October 2020. As of 1 August 2023 (Notification No. 10/2023-Central Tax dated 10 May 2023), the threshold stands at Rs. 5 crore aggregate annual turnover, and this remains the operative limit for FY 2026-27 unless CBIC notifies a further reduction. Determine your applicability using turnover in any preceding financial year from FY 2017-18 onwards — a one-year dip below Rs. 5 crore does not exempt you if you crossed the limit in an earlier year.

Who Remains Exempt

Even above Rs. 5 crore, the following categories are excluded from e-invoicing:

• SEZ units (as suppliers — they cannot issue through the IRP)
• Insurance companies, banking companies and NBFCs
• Goods Transport Agencies (GTA)
• Passenger transport service providers
• Multiplex cinema operators
• Government departments and local authorities as specifically notified

Always verify against the current CBIC notification — exemptions are notification-specific and can change between financial years.

The QRMP Scheme Does Not Grant Extra Time

Taxpayers under the Quarterly Return Monthly Payment (QRMP) scheme with turnover between Rs. 5 crore and Rs. 20 crore file GSTR-1 quarterly, but e-invoicing obligations remain monthly and per-invoice. The 30-day window is measured from each individual invoice date. A quarterly filing cycle does not give you a quarterly upload window.

How the IRP Portal Processes — and Rejects — a Late Upload

Understanding the technical sequence helps you build the right controls upstream. When your ERP or billing software fires an IRN generation request, the payload goes to one of the authorised IRPs — the NIC-operated portal at einvoice1.gst.gov.in or a private IRP (IRIS IRP, Clear IRP, Cygnet IRP, among others authorised by GSTN). The IRP then:

1. Validates the JSON schema against the prescribed e-invoice schema (currently Version 1.1 as published by GSTN)
2. Checks for duplicate IRNs using a hash of GSTIN + Financial Year + Document Type + Document Number
3. Validates the invoice date — if the invoice date is more than 30 days before today, it returns the date-range error and stops processing
4. Returns a signed e-invoice with embedded QR code and 64-character IRN hash if all validations pass

Step 3 is the hard stop. There is no override, no exception queue, and no manual correction mechanism for taxpayers. The only remedies for a definitively missed window are:

• IRP downtime evidence: If the IRP was unavailable during your upload window (GSTN publishes downtime advisories), keep server logs, API timestamps and error codes as contemporaneous evidence to contest any penalty
• Fresh invoice in the current period: Raise a new invoice dated today, issue a commercial credit note against the old document, and document the business rationale carefully for the audit file
• Provisional invoices prospectively: Restructure your billing process so the invoice date is always current at the time of raising — see the pitfalls section below

Worked Example: The Real Cost of Five Late Invoices

Scenario: Prism Components Pvt Ltd, a Pune-based manufacturer, has FY 2025-26 aggregate turnover of Rs. 8.4 crore and is e-invoice mandated. In March 2026, the sales team raises five B2B invoices dated 15 March through 25 March for a bulk order. A quantity dispute delays client sign-off. The accounts team uploads the JSON batch on 20 April 2026 — between 26 and 36 days after the invoice dates. Three of the five invoices fall outside the 30-day window and are rejected by the IRP.

Per rejected invoice:

Exposure across three rejected invoices:

The taxable revenue on these three invoices is Rs. 9,00,000. Worst-case compliance exposure exceeds one-third of that revenue — a real cash-flow event, not a rounding error.

The two invoices uploaded within 30 days cleared cleanly and generated IRNs on 20 April. The difference between a clean record and a blocked supply is a single day's delay on the earliest invoice. That is the business case for daily IRN monitoring.

How the 30-Day Rule Disrupts GSTR-1 Reconciliation

GSTR-1 auto-population draws directly from the IRN database. When your accounts team finalises GSTR-1 on the 9th or 10th of the month, only invoices with valid IRNs appear in Table 4 (B2B Supplies). A blocked invoice is invisible to GSTN.

Your buyer's GSTR-2B for that period will not reflect the ITC — and under Section 16(2)(aa) of the CGST Act, 2017 (inserted by Finance Act 2021, effective 1 January 2022), ITC is available only to the extent it reflects in GSTR-2B. This is now the statutory basis for ITC claims, not merely an advisory.

The cascade runs like this:

1. Your accounts receivable: invoice is in your books but absent from GSTN — a permanent reconciliation gap unless you raise a fresh invoice
2. Buyer's books: ITC mismatch triggers a notice from the buyer's CA or auditor; the buyer may reverse the credit and pay interest under Section 50
3. GSTR-1 vs GSTR-3B mismatch: if you report the supply in GSTR-3B (paying the tax) but cannot show it in GSTR-1 (no IRN), GSTN's auto-scrutiny system flags a systemic variance and may generate a notice under Section 61
4. GSTR-9 for AY 2027-28: unreconciled invoices from FY 2026-27 create additional disclosure burden in the annual return, requiring a reconciliation statement that will attract examiner attention

The practical fix is to reconcile your invoice register against the IRN log every morning before 10 AM — not at month-end. Daily reconciliation means you catch a blocked upload on day 2 or 3, while 25 to 28 days of upload window still remain.

Common Pitfalls and How to Fix Them

1. Back-Dated Invoices for Revenue Management

Finance teams under quarterly revenue pressure raise March invoices in April to hit targets. Before April 2026, this was a reconciliation irritant. Now it is a system rejection.

Fix: Configure your ERP to block invoice creation more than 25 days in the past, preserving a 5-day buffer before the 30-day wall. Any legitimate back-date beyond five days must go through a documented exception requiring CFO written approval.

2. Project-Based Billing with Slow Client Sign-Off

IT, engineering, and consulting firms raise invoices only after client acceptance certificates — which routinely take 45 to 60 days post-delivery.

Fix: Raise a provisional tax invoice on the delivery date for the confirmed milestone value. If scope changes after sign-off, issue a credit note or supplementary debit note. The original invoice date stays current, the IRN is generated on time, and corrections are handled cleanly within GSTR-1.

3. Export Invoices Under LUT

Teams assume that because no GST is payable on zero-rated exports under an LUT, e-invoicing does not apply. It does. Rule 48 applies regardless of whether tax is charged. Export IRNs also flow into the ICEGATE customs portal and populate GSTR-1 Table 6A. Treating export invoices as outside the e-invoice net is a compliance gap that will surface in any DGFT or tax audit.

4. Credit Notes Referencing Prior-Year IRNs

A credit note raised in FY 2026-27 for an invoice from FY 2025-26 must itself be e-invoiced (where required) and must reference the original IRN in the preceding document reference field of the e-invoice JSON. Verify that your ERP schema correctly populates this cross-year reference field — many mid-market ERPs leave it blank.

5. Multi-Branch Operations Under a Single GSTIN

Large businesses routing all invoicing through a single head-office GSTIN sometimes accumulate branch invoice batches for three to five days before upload. Each invoice is still judged by its own date.

Fix: Delegate IRP upload authority to each branch's accounting team with a target of same-day or next-day IRN generation. Centralised upload is a bottleneck the 30-day rule has made unaffordable.

6. IRP Downtime as a Defence

The IRP portals do experience downtime, and GSTN publishes advisories. If the IRP was genuinely unavailable during your upload window, document it: preserve API response codes, server error logs, and timestamps from your ERP or GSP dashboard. This contemporaneous evidence is your only defence if a penalty is contested — verbal claims of system downtime carry no weight in adjudication.

Penalty Exposure: What the Law Actually Prescribes

Section 122(1) of the CGST Act, 2017 prescribes a penalty of Rs. 10,000 or the amount of tax involved per invoice, whichever is higher, for specified offences — including supplying goods or services without issuing a valid invoice (and an invoice without an IRN is not a valid e-invoice under Rule 48). On a Rs. 3 lakh invoice attracting Rs. 54,000 GST, the operative penalty is Rs. 54,000 per invoice.

Section 125 covers residual contraventions — failure to comply with any provision of the Act or rules not otherwise specifically penalised — with a penalty of up to Rs. 25,000 per contravention.

Beyond the direct penalty:

• Buyer's ITC reversal with interest: Under Section 50 CGST Act, the buyer must reverse wrongly claimed ITC and pay interest at 18% per annum from the date of claim. For large buyers, this becomes a commercial dispute directed at you.
• Section 65 audit trigger: GSTN's compliance analytics — visible to GST officers through the AIS/TIS portal — score taxpayers on e-invoice adherence. Persistent failures elevate your scrutiny risk. A Section 65 departmental audit or Section 66 special audit is expensive in management time and professional fees, independent of whether any additional liability is found.
• E-way bill continuity risk: While no automatic e-way bill block is in place today, a history of e-invoice non-compliance on goods movements creates an evidentiary problem if an e-way bill is challenged at a check post.

Building 30-Day Compliance Into Your Operations: A Practical Playbook

You do not need expensive new software. You need disciplined configuration of what you already have.

ERP Configuration — Do This Once

1. Block invoice back-dating beyond 25 days in the system parameters. This is a one-line configuration in most ERPs (Tally Prime, SAP B1, Oracle NetSuite, Zoho Books). Test it.
2. Auto-trigger the IRP API on invoice save — not on a nightly batch run, not on a manual "push to IRP" button, but immediately on save. Nightly batches fail silently; real-time API calls return an error code you can act on in minutes.
3. Embed the IRN and QR code in the customer-facing PDF automatically. If a PDF leaves your system without a QR code, the IRN generation failed — your team sees it on every single invoice without running a report.
4. Log every IRP API response code in a queryable table within your ERP or document management system. This log is your audit trail and your downtime evidence.

Daily Monitoring — Do This Every Working Day

1. At 9:00 AM, pull a report: invoices created yesterday with no IRN. Zero should be the target. Anything on the list is a same-day escalation.
2. Any invoice more than 7 days old without an IRN triggers an automated email to the Finance Head — not just the accounts executive who processes it.
3. Error Code 2150 (date out of range) is treated as a Severity-1 incident in your incident management log, triggering the same response protocol as a failed payroll run.

Month-End Close — Before Filing GSTR-1

1. Export the full invoice register from the ERP and the full IRN log from your IRP/GSP dashboard. Reconcile line by line before touching GSTR-1.
2. Verify that the total outward supply value in GSTR-1 Table 4 equals the IRN-stamped supply total. Any gap must be documented with a business reason before filing.
3. For every credit note, confirm the original IRN reference is correctly mapped in the e-invoice JSON and reflected in GSTR-1 Table 9.

People and Process Controls

• Sales team briefing: Sales personnel must understand they cannot offer a back-dated invoice as a commercial concession. The system will not allow it, and attempting it creates a hard block, not a delay.
• Vendor-side mirror: If you are a buyer, your vendor SOP should require suppliers to share an IRN-bearing e-invoice PDF within 48 hours of dispatch. Without it, your team cannot pre-verify ITC availability before GSTR-2B is published.
• Quarterly internal audit: Randomly select 100 invoices, verify each IRN, check the IRP timestamp against the invoice date, and confirm the date gap is within 30 days. This exercise takes approximately two hours and is the single most cost-effective early warning control available.

Key Takeaways

• The 30-day e-invoice rule is enforced at the IRP API layer — there is no manual override, no extension request mechanism, and no remedy once the window closes on a specific invoice date.
• It applies to all e-invoice-mandated taxpayers (aggregate annual turnover above Rs. 5 crore as notified by CBIC) for tax invoices, credit notes, debit notes, exports, and supplies to SEZ units.
• A blocked IRN means zero ITC for your buyer under Section 16(2)(aa) CGST Act, 2017 — this is now a statutory entitlement condition, not a procedural one.
• Penalties under Section 122 CGST are the higher of Rs. 10,000 or the tax amount per invoice — on a realistic five-invoice late-upload scenario involving Rs. 9 lakh of taxable revenue, total financial exposure including ITC loss and interest can exceed Rs. 3.25 lakh.
• The highest-risk operational failure is back-dated invoicing for revenue management — fix it permanently by locking your ERP to a 25-day maximum back-date with CFO approval beyond five days.
• Project billers and LUT exporters face disproportionate exposure — raise provisional invoices at delivery and correct via credit notes; do not wait for client sign-off to generate the invoice date.
• Daily reconciliation of the invoice register against the IRN log is the only reliable control — monthly checks leave too small a window to remediate a rejection before 30 days expires.