E-invoice 30-day limit in 2026: who it covers, what breaks in Tally, and how to monitor IRNs

Every finance team has a version of this story. A sales invoice dated the 2nd sits in a branch Tally, nobody pushes it to the IRP, and it surfaces on the 6th of the following month during GSTR-1 preparation. Before April 2025, for a company with ₹30 crore turnover, that was a late e-invoice and an awkward conversation with the buyer. Since 1 April 2025 it is an invoice that cannot get an IRN at all.

This post sets out exactly who the 30-day limit covers in October 2026, what happens when it is missed, how credit notes and cancellations fit in, where Tally and ERP flows break, and a monitoring routine that catches the invoice on day 7, not day 31.

The rule

GSTN’s advisory of 5 November 2024 bars taxpayers with annual aggregate turnover (AATO) of ₹10 crore and above from reporting e-invoices older than 30 days on any Invoice Registration Portal, effective 1 April 2025. The restriction applies to all document types for which an IRN is generated: invoices, credit notes and debit notes. The advisory states there is no such restriction for AATO below ₹10 crore “as of now” (Taxmann summary of the GSTN update).

The limit was first introduced in 2023 for AATO of ₹100 crore and above. The 2025 extension brought in every mid-size business that has crossed ₹10 crore in any year since 2017-18.

Two points practitioners keep flagging. First, the limit is enforced by validation on the IRPs under a GSTN advisory, not by an amendment to the CGST Rules; the effect is identical, because the portal simply refuses the document (TaxGuru on the 2026 position). Second, ₹10 crore is not the e-invoicing threshold. E-invoicing itself has been mandatory above ₹5 crore since 1 August 2023 under Notification 10/2023-Central Tax.

Who it applies to

We found no GSTN advisory extending the block below ₹10 crore as of 22 October 2026. Given the trajectory from ₹100 crore to ₹10 crore, a business in the ₹5 to ₹10 crore band should run the same monitoring anyway; the discipline costs little and the next step down, when it comes, will give a few months’ notice at best.

How the 30 days are counted

The clock runs from the document date to the date of reporting on the IRP. An invoice dated 1 April cannot be reported after 30 April. There is no grace for weekends, portal downtime or the IRP being slow at month-end. The practical implication for anyone near the line: the day the invoice is dated is day zero, and your internal deadline should be day 7, not day 29.

What happens when you miss it

No IRN. The IRP rejects the document. There is no late-reporting route and no pay-a-fee-and-proceed option on the portal.

The invoice is not a valid tax invoice. Rule 48(5) says an invoice issued by a person required to e-invoice, in any manner other than through the IRP, is not treated as an invoice. For the buyer, that makes the ITC contestable; for you, it is a supply made without a valid invoice (Tally on the ITC impact for buyers and sellers).

Penalty exposure. Section 122 of the CGST Act penalises supply without an invoice at ₹10,000 or the tax involved, whichever is higher, and failure to issue an invoice in accordance with the Act or rules at up to ₹25,000 under sub-section (3)(e). How officers apply these to a missed IRN varies by jurisdiction; the exposure is real either way.

Goods in transit. An e-way bill without a valid invoice behind it invites detention.

GSTR-1 and the buyer’s 2B. IRP data auto-populates GSTR-1. A document that never reached the IRP has to be added manually, and the buyer sees nothing in GSTR-2B until you do. Buyers running monthly GSTR-2B reconciliation will spot it on the 14th and hold payment.

The commercial consequence is usually the one that hurts first: a large customer refuses to pay an invoice with no IRN, and you are now issuing a credit note and a fresh invoice to a procurement team that remembers.

Credit notes, debit notes and the 24-hour cancellation window

Credit and debit notes sit inside the 30-day limit for ₹10 crore-plus taxpayers. The common failure is the quarter-end credit note: a rate difference agreed in September, documented in a credit note dated 30 September, raised in the system on 5 November. Date the note when it is raised, not when the difference was agreed.

Cancellation is a separate and much tighter window. The official e-invoice FAQ states that an IRN can be cancelled only within 24 hours of reporting, and not while an active e-way bill is attached to it (e-invoice FAQs; IRN cancellation in detail). Partial cancellation is not possible, and a cancelled invoice number cannot be reused for a new IRN. After 24 hours, the only route is a credit note against the original and, where needed, a fresh invoice with a new number.

Where Tally and ERP flows break

The rule is simple. The failures are operational, and they repeat.

• Invoice date versus entry date. Branch staff key an invoice on the 20th with the date of the 2nd because that is when the goods moved. The 30 days ran from the 2nd.
• Offline or manual invoices. A branch without connectivity, a counter sale written by hand, a sales executive’s invoice book. These reach head office in a bundle at month-end.
• Validation errors nobody re-tries. Inactive buyer GSTIN, pin code not matching the state code, HSN at fewer digits than your turnover band requires, a duplicate invoice number, a distance error on the e-way bill. Tally shows the error once; if the user clicks past it, the invoice sits in the pending-for-IRN list until somebody runs the report.
• Expired credentials. IRP API passwords, GSP tokens and the two-factor authentication on the e-invoice and e-way bill systems, compulsory for all taxpayers since 1 April 2025. One expired login at a branch means a week of unreported invoices.
• Multiple systems. A billing app for one vertical, Tally for another, Excel for exports. Each has its own pending list and nobody sees all three.
• Credit notes against old invoices. The note is dated correctly but references an invoice from a cancelled series, or the amount exceeds the original, and the IRP rejects it. The rejection is noticed 28 days later.
• The IRP is slow on day 30. It happens at month-end. If your process pushes documents on day 29, you have no buffer.

A monitoring workflow

What catches these is not a better rule but a daily report with an owner.

1. Daily, 10 am: pending-IRN list. Every document dated in the last 30 days without an IRN, across every system, in one list. In TallyPrime this is the e-invoice report filtered to pending and rejected; for other systems it is a query on the sales register joined to the IRN response log.
2. Age it. Three buckets: 0 to 7 days (normal), 8 to 15 days (chase), 16 to 25 days (escalate to the finance head). Nothing should ever reach a 26-plus bucket.
3. Classify the reason. Not pushed, pushed and rejected, pushed and pending at the IRP. Each has a different owner.
4. Fix the data for rejections, not the process. GSTIN status check before invoicing, HSN master at the required digits, pin code master validated against state codes.
5. Weekly: IRP versus books. Pull the portal’s generated-IRN list for the week and match it to the sales register. Anything in books and not on the IRP is the chase list; anything on the IRP and not in books is a duplicate or a test document that needed cancelling within 24 hours.
6. Month-end: freeze. No sales invoice is backdated more than two days without finance sign-off. The 30-day limit is the enforcement; the backdating control is the prevention.
7. Credentials calendar. Every IRP login, GSP token and 2FA device per GSTIN, with expiry and owner.

For a CA firm doing this across clients, it is a standard module in the CA office automation playbook: one dashboard, every client GSTIN, every pending document, aged. We build this as part of accounting automation, and the pending-IRN ageing view is in the accounting demo.

What to automate

• A single pending-IRN list pulled daily from every billing system and aged into 7, 15 and 25-day buckets with an owner on each row.
• Rejection re-tries with reason codes, so a pin code or HSN error is fixed and re-pushed the same day instead of discovered at month-end.
• Pre-invoice validation: GSTIN active status, HSN digits, pin code to state code, duplicate number, before the invoice is saved.
• IRP-to-books reconciliation weekly, with the 24-hour cancellation window flagged on any document that should not exist.
• WhatsApp or email escalation at day 15 and day 25 to the branch head and finance head, naming the invoice numbers.