--- title: "30-Day IRP Reporting Rule: Who It Hits at Rs 10 Cr and How to Comply" description: "The 30-day rule does not extend the e-invoicing deadline, it removes it. Report an invoice to the IRP more than 30 days after its date, at Rs 10 crore turnover and above, and the portal simply refuses to generate an IRN for it. Here is who is covered, how the window is counted, and how to build a process that never misses it." author: "Himanshu" published: 2026-09-18T13:01:42.703Z updated: 2026-09-18T13:01:42.895Z url: https://blog.mybillplease.com/invoice-30-days-reporting-rule --- # 30-Day IRP Reporting Rule: Who It Hits at Rs 10 Cr and How to Comply ## Key takeaways - Taxpayers with aggregate annual turnover of Rs 10 crore or more in any financial year from 2017-18 onward cannot report an e-invoice to the IRP more than 30 days after the invoice date; the portal blocks generation past that window. - The 30-day count runs from the invoice date, not from the date you attempt to submit it, so a backdated or delayed invoice can already be outside the window before you even try to raise the IRN. - There is no late-reporting fallback on the IRP for this rule. An invoice that misses the window has to be handled as a fresh, correctly dated document, which usually means a credit note against the old dating and reissue. - Below Rs 10 crore turnover the 30-day restriction does not currently apply, but the e-invoicing mandate itself starts at Rs 5 crore, so many sellers are already reporting IRNs without yet being bound by the 30-day cutoff. The 30-day IRP reporting rule blocks e-invoice generation for any invoice reported more than 30 days after its invoice date, and it applies to taxpayers with aggregate annual turnover of Rs 10 crore or more. Once that window closes, the Invoice Registration Portal will not issue an IRN for the invoice as dated, regardless of the reason for the delay. This is a harder cutoff than most GST deadlines, because there is no late fee, no penalty-and-file option, and no amendment path that revives the original invoice number past 30 days. Businesses that generate e-invoices in batches, close billing at month-end rather than in real time, or rely on a manual upload process are the ones most likely to discover the rule the hard way, on the invoice they most needed to report. This guide covers exactly who the rule applies to, how the 30-day window is counted, what happens when an invoice misses it, and how to build a process that keeps every invoice inside the window by default. For the e-invoicing process itself, see the [e-invoicing guide](/e-invoicing-guide). ## Who the rule applies to The 30-day reporting restriction currently applies to taxpayers with aggregate annual turnover of Rs 10 crore or more, using the same PAN-based, cross-GSTIN aggregate turnover test that determines e-invoicing eligibility in the first place. If your turnover crossed Rs 10 crore in any financial year since 2017-18, the rule applies to you going forward, even in a year where turnover is lower. This is a narrower group than everyone who does e-invoicing. The e-invoicing mandate itself starts at Rs 5 crore aggregate turnover, so a business between Rs 5 crore and Rs 10 crore is already generating IRNs for B2B supplies but is not currently bound by the 30-day cutoff. That gap matters for planning, because the threshold for this specific restriction has moved before, having originally applied only above Rs 100 crore before being extended downward, and a business approaching Rs 10 crore should build the discipline before the rule technically applies rather than after. ## How the 30-day window is counted The count runs from the invoice date, the date printed on the document under Section 31, not from the date you attempt to submit it to the IRP and not from the date your billing software created the record. An invoice dated the 1st of a month has until the 31st to be reported; on the 32nd day, generation is blocked. This distinction catches businesses that create invoices in their system on one date but only push them to the IRP in a later batch run, whether because of a manual upload process, an integration that syncs periodically, or a backlog that built up during a busy period. If the gap between invoice creation and IRP submission regularly runs to a week or two, it does not take much additional delay, a public holiday, a system outage, an unnoticed backlog, to push a batch of invoices past 30 days without anyone intending it. > **The window measures from the invoice date, not from when you notice the problem** > > An invoice sitting unreported in your system for three weeks already has only nine days of runway left, whether or not anyone has checked on it. Treat every unreported invoice as a countdown from its own date, not from today, and review the oldest unreported invoices first, not the newest. ## What happens when an invoice misses the window There is no fallback on the IRP for a late submission under this rule. The portal's API and the offline utility both reject the request once the invoice date is more than 30 days in the past, with no manual override available to the taxpayer or, as far as the published process goes, to the tax authority either. Once an invoice is in this state, it cannot be reported as originally dated for e-invoicing purposes. For a B2B supply above the e-invoicing threshold, an invoice without a valid IRN is not treated as a valid tax invoice, which affects the recipient's ability to claim ITC against it and affects how the supply flows into your own GSTR-1. The practical fix, in most cases, is to treat the original document as void for e-invoicing purposes and issue a fresh, correctly dated tax invoice for the supply, while resolving the original number through cancellation if still within its own [24-hour IRN cancellation window](/invoice-cancellation-time-limit), or a credit note if the supply has already moved. The [credit note and debit note guide](/credit-note-debit-note-gst) covers how the correction itself is issued. ## Staying inside the 30-day window: a practical process The rule is unforgiving, but it is also entirely avoidable with an invoicing process that reports promptly by default rather than in periodic batches. 1. Generate the tax invoice and submit it for an IRN on the same day, or the next business day at the latest, rather than accumulating a batch. 2. If your system integrates with the IRP through an API, confirm the integration runs continuously or on a short schedule, not once a week. 3. Build a standing report of invoices without an IRN, sorted by invoice date, oldest first, and review it at least twice a week. 4. Flag any unreported invoice approaching 20 days old for immediate attention, giving a 10-day buffer before the hard cutoff. 5. For any manual upload process, assign an owner and a fixed cadence, so submission does not depend on someone remembering. 6. When onboarding a new billing system or switching software, confirm historical invoices already inside the 30-day window are migrated and reported promptly, since a migration delay is a common way this rule gets triggered unintentionally. ## Weekly check for e-invoice reporting - List of invoices without an IRN, sorted oldest first - No invoice older than 20 days still unreported - API or integration for IRN generation running without a backlog - Manual uploads, if any, completed on a fixed schedule with a named owner - New invoices reported the same day or the next business day ## Batch invoicing and backdating: the specific traps Two operational habits collide with this rule more than any others, and both are worth checking for directly rather than assuming your process avoids them. Batch invoicing, where invoices are created throughout the month but only pushed to the IRP in a single monthly run before the GSTR-1 deadline, is the most common trap. It looks efficient because it groups the work, but it puts every invoice from early in the month at serious risk of missing the 30-day window, especially if the batch run happens close to the 11th of the following month. Backdating, where an invoice is entered into the system today but given an earlier date to match a delivery or a customer request, has the opposite problem: it can create an invoice that is already outside the 30-day window the moment it is created. If your process ever needs to record a supply that happened weeks ago, check the invoice date against the 30-day rule before generating the invoice, not after attempting to report it. ## Turnover and what applies to you | Aggregate turnover | E-invoicing mandate | 30-day reporting rule | | --- | --- | --- | | Below Rs 5 crore | Not mandatory | Not applicable | | Rs 5 crore to below Rs 10 crore | Mandatory for B2B supplies | Not currently applicable, but report promptly regardless | | Rs 10 crore and above | Mandatory for B2B supplies | Applies; IRN blocked past 30 days from invoice date | ## Measuring your own reporting gap Most businesses that comply with the 30-day rule without incident have never had to think about it, because their gap between invoice date and IRN generation is already a day or two, well inside the window by default. It is worth actually measuring this gap rather than assuming it, especially if your invoicing has grown to involve more than one team or more than one system feeding invoices toward the IRP. A simple way to check is to pull a sample of recently reported invoices and compare each one's invoice date to its actual IRN generation timestamp on the IRP acknowledgment. If the typical gap is under three days, the 30-day rule is effectively invisible to your operations. If it regularly runs to a week or more, you have less margin than it feels like, and a single disruption, a staff absence, a software outage, a backlog during a sale period, is enough to push some invoices past the line. Running this check quarterly, rather than only after a problem surfaces, catches a growing gap while it is still easy to fix. ## Below Rs 10 crore today, above it tomorrow If your turnover is approaching Rs 10 crore, plan for this rule before it technically applies rather than after. Turnover crossing the threshold mid-year does not come with a grace period for the 30-day rule specifically, since aggregate turnover is assessed on a financial year basis and the restriction, once it applies, applies to invoices going forward from whenever the taxpayer becomes covered. A business that has already built the habit of same-day or next-day IRN generation feels no difference the day the rule technically starts applying to them, because their invoices were already inside the window. Billing software that generates the invoice and submits it for an IRN in one action removes the gap where a batch process would otherwise sit. myBillPlease does this, alongside GSTR-1 and GSTR-3B preparation built from the same invoice records, so the reporting step happens as part of issuing the invoice rather than as a separate task someone has to remember. **Report every invoice for an IRN the same day it is issued** Create the invoice and submit it for an IRN in one step, so no invoice sits unreported long enough to approach the 30-day cutoff. [Create a free account](https://www.mybillplease.com/signup) The 30-day rule rewards a simple habit: report as you invoice, not as you file. Businesses that already do this notice nothing when the rule applies to them; businesses that batch their reporting are the ones who find out the rule exists on the one invoice that mattered. ## FAQ ### Does the 30-day rule apply to every business that does e-invoicing? No. It applies specifically to taxpayers with aggregate annual turnover of Rs 10 crore or more, in any financial year since GST began. ### How is aggregate turnover for this rule calculated? It uses the same aggregate turnover concept as the e-invoicing mandate itself: PAN-based, across all GSTINs, for any financial year from 2017-18 onward. ### What happens if I try to generate an IRN 31 days after the invoice date? The IRP rejects the submission outright. There is no override, no penalty-and-proceed option, and no manual exception process on the portal itself. ### Can I just change the invoice date to fit inside the 30-day window? No, and doing so creates a bigger problem than the one it solves. ### Does the 30-day rule affect GSTR-1 filing directly? Indirectly. ### Is the 30-day window the same as the e-way bill validity period? No, they are unrelated rules that happen to both involve time limits. The 30-day rule governs how long after the invoice date you can still generate an IRN.