The 30-Day Time Limit for Reporting E-Invoices

E-invoicing tells you whether you must report a B2B invoice to the Invoice Registration Portal. The 30-day rule tells you by when. If your turnover is in the covered band and a document is more than 30 days old on the day you submit it, the IRP refuses it. No IRN, no QR code, and for a business inside the mandate, no valid tax invoice. This post covers who the rule applies to, what the portal actually checks, what a missed window costs you and your buyer, and the operating controls that stop it happening.

What the 30-day rule says

When e-invoicing began, there was no limit on how late a document could be reported to the IRP. A business could raise an invoice in its ERP, sit on it, and generate the IRN weeks or months later. That defeated the point of real-time reporting, so GSTN introduced a time limit through advisories on the e-invoice system.

The mechanism is simple. For taxpayers in the covered turnover band, the IRP compares the document date in the e-invoice payload with the date of reporting. If the document is older than 30 days, the IRP returns a validation error instead of an IRN. The example GSTN has used: an invoice dated 1 April cannot be reported after 30 April.

This is a portal validation, not a penalty provision. There is no late fee to pay and then proceed. The request simply fails. What follows from that failure comes from the invoicing rules in the CGST Rules, covered below.

Who it applies to: the turnover bands

The restriction was rolled out in two stages, both announced through GSTN advisories:

• From 1 November 2023 — taxpayers with aggregate annual turnover (AATO) of ₹100 crore or more.
• From 1 April 2025 — extended to taxpayers with AATO of ₹10 crore or more.

AATO is computed on PAN, across all GSTINs registered under that PAN, not per registration. If you are unsure how it is calculated, the annual aggregate turnover guide walks through what goes in and what stays out. The e-invoicing threshold itself has not moved: it remains above ₹5 crore, as explained in the e-invoicing threshold guide.

Notified exempt categories, such as SEZ units, banks and insurers, stay outside e-invoicing whatever their turnover, so the time limit does not reach them either. The exemption list changes, so confirm it on cbic-gst.gov.in rather than relying on a summary.

If you sit between ₹5 crore and ₹10 crore, do not build your process around the absence of the rule. GSTN has lowered the band once already, and the advisories give only a few months of notice. A process that reports within 30 days today costs you nothing extra if the band drops again.

Which documents are covered

The e-invoicing mandate covers tax invoices, credit notes and debit notes issued for B2B supplies, exports and the other notified transaction types. The 30-day restriction sits on top of that, and it clearly applies to invoices and credit notes.

The position on debit notes needs a check. GSTN advisories on the time limit have not described it the same way at every point, and some explanations state that debit notes are not restricted. Read the current advisory on the e-invoice portal before you treat a late debit note as safe to report. For how the two notes differ in the first place, see GST debit notes and credit notes.

How the IRP counts the 30 days

Three points trip people up.

It is the document date, not the supply date. The IRP has no idea when goods left your warehouse. It reads the date you put in the document date field of the payload and compares it with the date of submission. Your ERP's invoice date and the date you send to the IRP must be the same date.

It is a hard cut-off on submission. The check happens when the IRP processes the request. A document that was queued in your system on day 29 but submitted on day 31, because an integration was down or a batch job failed, is late.

It is separate from the time to issue an invoice. Section 31 of the CGST Act, read with Rule 47, already controls when an invoice must be issued, including the 30-day period for most services. The IRP limit is a second, independent clock that starts from the document date. Meeting one does not satisfy the other. The time of supply rules explain which date the law treats as the date of supply.

The IRP also validates GSTINs in the payload. A document that keeps failing on a wrong or cancelled buyer GSTIN can burn through the 30 days while your team works out why, which is one reason to validate buyer GSTINs when you onboard the customer rather than at invoice time.

What happens when you miss the window

Once the document is older than the limit, the IRP will not generate an IRN for it. There is no override request and no late-reporting route on the portal.

The legal consequence comes from the invoicing rules. Rule 48(4) of the CGST Rules requires a taxpayer inside the mandate to prepare the invoice by uploading its particulars to the IRP and obtaining an IRN. Rule 48(5) says an invoice issued any other way is not treated as an invoice. So for a covered business, a document without an IRN is not a valid tax invoice.

That lands on your buyer. Input tax credit under Section 16 depends on holding a valid tax invoice, and e-invoice data is what auto-populates the supplier's GSTR-1 and, from there, the buyer's GSTR-2B. A buyer who cannot see the invoice in GSTR-2B will usually hold your payment until it is fixed.

Treat any document past the window as an exception to be escalated, not something the billing team patches on its own.

Controls that keep you inside the limit

Almost every missed window traces back to a process gap, not a legal grey area. These controls close most of them.

Generate the IRN at the moment of invoicing. The e-invoice should be created when the invoice is finalised, not in a month-end batch. Direct integration between your billing system and the IRP, either through an IRP's own API or a GSP, makes this the default. The billing software integration guide covers the options.

Report pending IRNs every day. Keep a daily list of documents that have an invoice number but no IRN, sorted by age. Anything past 20 days goes to a named owner. The IRN tracking guide explains how to record the IRN, acknowledgement number and date at generation so the list is accurate.

Reconcile against the IRP, not just your ERP. Your ERP can show a document as reported when the call actually failed. Compare the IRNs you hold against what the IRP returns, periodically and in bulk; checking e-invoice status in bulk shows how.

Clean the master data first. Invalid buyer GSTINs, wrong state codes and HSN errors are the common reasons a document keeps being rejected. Validate a customer's GSTIN when you create them in your system. GSTIN API does this through a single lookup that returns registration status and GSTR filing history, at ₹0.50 per verification. It does not generate IRNs or e-invoices; it only confirms that the GSTIN you are about to put on the invoice is real and active.

Keep e-invoice and e-way bill steps separate. For goods, the e-way bill is often generated from the IRN, and a delay on one holds up the other. The e-way bill vs e-invoice post sets out how they connect.

Watch the advisories. Both stages of the 30-day rule came through advisories on the e-invoice portal with a few months' notice. Someone in your finance team should read them as they are published, and confirm current positions on gst.gov.in or the e-invoice portal before acting on a summary, including this one.

Frequently asked questions