Businesses crossing ₹10 crore in Annual Aggregate Turnover don't get unlimited time to push an invoice through the e-invoice system. Since 1 April 2025, any eligible invoice, credit note or debit note has to reach an Invoice Registration Portal for IRN generation within 30 days of the document's own date - miss that window, and the portal simply won't accept it anymore.

That rejection isn't just a technical inconvenience. It can leave you holding a document that doesn't count as a valid e-invoice, stall the buyer's Input Tax Credit, delay payment approvals, and throw off your GSTR-1 reconciliation.

This guide breaks down who the rule applies to, exactly how the 30-day count works, a practical filing checklist, and the habits that keep large-turnover businesses from getting caught out by the deadline.

• Key Takeaways
• What the 30-Day Rule Actually Requires
• Which Documents Are Covered and How the Deadline Is Counted
• The 30-Day Reporting Checklist
• Daily, Weekly and Monthly Controls
• What Happens If the Deadline Is Missed
• Frequently Asked Questions

Key Takeaways

• Taxpayers with AATO of ₹10 crore or more must report eligible e-invoice documents within 30 days of the document date, effective from 1 April 2025.
• The rule covers invoices, credit notes and debit notes that require an IRN - not just standard sales invoices.
• The 30-day count runs on calendar days from the document date, including weekends and holidays.
• Once the window closes, the portal rejects the document outright and no IRN can be generated for it.
• General e-invoicing applies from ₹5 crore AATO, but the strict 30-day reporting cutoff currently applies only from ₹10 crore AATO.
• Treat 30 days as a hard ceiling, not a target - aim for same-day or next-day IRN generation instead.

What the 30-Day Rule Actually Requires

The rule requires businesses above the threshold to submit eligible invoice data to an authorised Invoice Registration Portal within 30 days of the document's date. Once the portal validates that data, it issues an Invoice Reference Number, a digitally signed version of the invoice, and a signed QR code - together, these are what make the document a recognised e-invoice under GST.

It's worth being clear about what the rule doesn't say: it doesn't give a business 30 days to actually issue the invoice to the customer. The invoice still has to be created in line with the normal GST time-of-supply rules. The 30-day window only governs how long you have to get an already-created document through IRN generation.

The restriction applies where a taxpayer's Annual Aggregate Turnover is ₹10 crore or above, and that turnover is checked across every GSTIN registered under the same PAN, not GSTIN-by-GSTIN. Before assuming the rule applies - or doesn't - a business should confirm its combined turnover across all registrations, its e-invoicing enablement status, and whether its specific category or supply type carries any exemption.

It also helps to keep the ₹5 crore and ₹10 crore thresholds separate, since they cover different things:

Which Documents Are Covered and How the Deadline Is Counted

The 30-day restriction covers every document type that needs an IRN - B2B tax invoices, export invoices, debit notes, credit notes, and specified supplies to government or registered entities. Ordinary B2C invoices generally sit outside this rule, since B2C supplies don't go through IRN generation under the current framework. Some notified entities and supply types may also carry their own exemptions regardless of turnover, so it's worth checking category-specific rules before assuming full coverage.

The 30-day clock starts from the date printed on the invoice, credit note or debit note - not the date it's entered into your accounting system. An invoice dated 1 April, for example, has to reach the portal by 30 April; from 1 May onward, that same document gets rejected. The same logic applies whatever the starting date is - a 10 April invoice is good through 9 May, a 15 June invoice through 14 July, and so on.

Because the count runs on calendar days rather than working days, weekends and public holidays eat into the window just like any other day. That's exactly why waiting until close to day 30 is risky - a portal outage, a missing approval, or a staff absence at the wrong moment can push you past the deadline with no way back.

The 30-Day Reporting Checklist

Run through this checklist for every B2B invoice, export invoice, credit note or debit note that requires an IRN:

• Confirm e-invoice applicability - supplier coverage, transaction type, valid recipient GSTIN, and any notified exemption
• Lock the invoice date first, since it starts the 30-day clock - keep ERP, invoice PDF and IRP data consistent
• Verify supplier and buyer GSTINs, legal names, state codes and place of supply before submission
• Check invoice numbering - correct format, no duplicates within the financial year, no stray characters
• Confirm HSN/SAC codes match the goods or services and carry the correct GST rate and cess treatment
• Recheck taxable value and tax computation - quantity, price, discounts, CGST/SGST/IGST, cess and rounding
• Confirm place of supply and tax type, paying extra attention to bill-to/ship-to transactions
• Submit through your chosen route - API integration, GSP, authorised IRP software, bulk JSON, or billing software
• Confirm the IRP actually returned an IRN, acknowledgement number, signed QR code and success status - don't assume export means success
• Share only the authenticated, IRN-linked invoice with the customer, never an unauthenticated draft

A daily reconciliation between your sales register and IRP records is what catches a missing IRN while there's still time to fix it - comparing invoice numbers, dates, GSTINs, taxable values and document status against what the portal actually shows on file.

Daily, Weekly and Monthly Controls

A structured cadence of checks keeps the 30-day rule from ever becoming an emergency:

• Daily - generate IRNs for eligible invoices, review failed IRP requests, and fix GSTIN or master-data errors as they surface
• Weekly - review invoice ageing, escalate anything past seven days, and check that branch teams are reporting on schedule
• Monthly - reconcile the sales register against IRP data, compare against GSTR-1, and investigate anything nearing day 30

An ageing report with clear risk bands makes escalation almost automatic instead of a judgment call:

What Happens If the Deadline Is Missed

Once a covered document ages past the 30-day window, IRP validation blocks IRN generation for it outright. That has knock-on effects on both sides of the transaction:

• Invalid documentation - where e-invoicing is mandatory, an invoice without a proper IRN may not count as a valid tax invoice
• Buyer ITC disruption - the customer may be unable to claim Input Tax Credit against the document until it's corrected properly
• Payment delays - many corporate buyers check IRN validity before releasing payment, so a missing IRN can stall approvals
• GSTR-1 mismatches - an unreported document can throw off reconciliation between the sales register, IRP data and returns
• Penalty and audit exposure - non-compliance with mandatory e-invoicing can invite notices, penalties and disputes

Why Businesses Commonly Miss the Deadline

A few recurring patterns explain most missed deadlines: batching all IRN generation into month-end GST closing instead of daily, sales teams creating invoices before buyer GSTIN details are confirmed, invoices stuck in multi-team approval chains, branch offices billing locally while head office handles IRP reporting with a lag, repeated validation errors from incorrect HSN codes or GSTINs, credit and debit notes getting overlooked because attention stays on sales invoices, and portal or integration downtime that isn't tracked and retried promptly.

Correcting an E-Invoice After IRN Generation

An e-invoice can't be edited directly on the portal once the IRN has been issued. Where permitted, the IRN itself can usually be cancelled within 24 hours of generation; beyond that, corrections generally have to go through the appropriate GST return, a credit or debit note, or your standard accounting adjustment process. Keep a separate tracked process for cases like incorrect GSTINs, wrong taxable values, cancelled supplies, returned goods, or duplicated invoices - especially ones spotted after the 24-hour cancellation window has closed.

How Billing Software Helps

The businesses that stay ahead of this rule tend to have one thing in common: invoice creation and GST reporting living in the same system instead of scattered across spreadsheets and separate tools. Hitech Billsoft brings GST-compliant invoicing, automated tax calculations, customer and item master data, and business reporting into a single workflow, which shortens the gap between creating an invoice and getting it reported - exactly what the 30-day rule rewards.

Final Audit Checklist Before Closing a GST Period

Before wrapping up each period, confirm:

• AATO has been checked across every GSTIN under the PAN
• Every eligible invoice, credit note and debit note carries an IRN
• No reportable document sits older than 20 days without an IRN
• Customer GSTINs, HSN/SAC codes and place-of-supply details have been validated
• IRP rejections have been resolved and acknowledgement data is on file
• Signed QR codes appear on all final customer-facing invoices
• IRP records agree with the sales register before GSTR-1 filing

Conclusion

For ₹10 crore+ businesses, the 30-day e-invoice reporting rule isn't really about the deadline itself - it's about replacing a batch, month-end approach to compliance with a continuous one. The strongest safeguard isn't a reminder set for day 28; it's a same-day habit of validating the document, generating the IRN, and reconciling it against the books before it ever has a chance to age.

Clean master data, automated tax calculations, daily IRN generation, and clear escalation ownership do most of the work. Get those in place, and the 30-day window stops being a risk and becomes just another background process.