Missed the 24-hour e-invoice cancellation window? The credit note is the clean fix
Once 24 hours pass, an e-invoice's IRN cannot be cancelled or edited on the IRP. The fix is a Section 34 credit note plus a fresh e-invoice under a new document number. GSTN also lets you edit or delete the auto-populated GSTR-1 record instead, but the original IRN stays valid, so the two will disagree.
The e-invoice portal gives you exactly one function for a wrong IRN, and it only works for 24 hours — cancel. There is no edit, no amend, and no extension for a genuine mistake caught late. Once that window closes, the IRP-consistent fix is a Section 34 credit note against the wrong invoice and a fresh e-invoice against the right one. GSTN also lets you edit or delete the same record in an unfiled GSTR-1 — but the IRN itself stays valid on the IRP either way, and the credit-note route has its own timing problem, on both sides of the transaction.
There's no "amend" button on the e-invoice portal — not before 24 hours, not after
It's worth being precise about this because so much confusion starts here: the Invoice Registration Portal (IRP) has never had a function to edit a field on a generated e-invoice — not the buyer's GSTIN, not the invoice date, not the value, at any point after the IRN is issued. The only action available on a live e-invoice is cancellation, and per TallyPrime's own documentation, that cancellation window is open for 24 hours from IRN generation (as of 28 Sep 2026; also confirmed in GSTN's own e-invoice System FAQ, Q90). Past that, the portal doesn't offer a workaround screen — it simply stops the request. Tally's guidance describes exactly what happens when you try: "A message appears indicating that the time limit for cancellation has exceeded."
At that point, deleting the voucher in your own accounting software does nothing to the government-side record. Tally's documentation is direct about this too: doing so "will only delete the voucher in TallyPrime and will not impact the e-Invoice or e-Way Bill." The IRN stands, valid, on the IRP and in the supplier's GSTR-1, regardless of what your books now say.
Within 24 hours vs after — what's actually different
| Within 24 hours | After 24 hours | |
|---|---|---|
| Cancel the IRN on the IRP | Allowed, unless a connected e-way bill is active or has already been verified by an officer in transit | Blocked — no exception |
| Edit a field (GSTIN, date, value) | Not possible at any time | Not possible at any time |
| Delete the voucher locally (Tally or similar) | Doesn't touch the IRN either way | Doesn't touch the IRN either way |
| Correct the transaction | Cancel, then re-issue under a new document number (the cancelled number can't be reused) | Credit note, then re-issue |
The row that trips people up is the last one. Within 24 hours, "cancel and re-issue" is genuinely free — the wrong IRN is cancelled, though GSTN's e-invoice System FAQ (Q90) blocks the cancellation outright if a connected e-way bill is active or has already been verified by an officer in transit — you'd need to deal with the e-way bill first. After 24 hours, nothing disappears. The wrong invoice stays live, valid, and already reported; the correction is a second, separate transaction layered on top of it, not an undo, and it takes a fresh document number — the cancelled one cannot be reused for the reissue.
The credit-note fix, step by step
Tally's own guidance states the workaround plainly: once the cancellation window has lapsed, "you may record a credit note for the voucher and generate a new e-Invoice for the same." In practice that's two documents, not one:
- Issue a credit note against the wrongly-issued invoice, under Section 34 of the CGST Act. Section 34(1) lets a supplier issue a credit note where the taxable value or tax charged on an invoice exceeds what's actually payable, or goods are returned, or goods or services are found deficient. A wrong-GSTIN invoice is corrected on the reading that the tax charged to that recipient exceeds what is payable for that supply; the Act does not list "invoice issued in error" as a ground in those words, so this is the closest fit the statute provides, framed as a "may", not a mandatory correction mechanism.
- Check whether the credit note itself needs an IRN. This is the step most workaround guides skip. If you're covered by the Rule 48(4) e-invoicing mandate — turnover above ₹5 crore in any preceding financial year from 2017-18 onwards, a threshold that once crossed never lapses — that mandate applies to credit and debit notes you issue, not only to invoices. (A handful of categories sit outside it regardless of turnover — government departments, local authorities, SEZ units, banks/NBFCs/insurers, GTAs, passenger transport and multiplex operators.) Rule 48(4)/(5) itself speaks only of an "invoice"; credit-note coverage comes from Notification 13/2020-CT (as amended by 10/2023-CT), which extends the mandate to "other prescribed documents". On the prevailing reading, a credit note raised outside that process, for a taxpayer it applies to, carries the same Rule 48(5) consequence as a wrongly-issued invoice — "shall not be treated as an invoice" — though that is an extension of the rule's express words, not the rule's own text.
- Raise a fresh e-invoice with the correct GSTIN, date or value, going through the IRP in the normal way and getting its own new IRN.
- Declare the credit note in the return for the month you issue it — Section 34(2) fixes the deadline as the earlier of 30 November following the financial year the original supply was made in, or the date you file the annual return, whichever comes first (as of 28 Sep 2026). Filing GSTR-9 early can close this window before 30 November arrives.
Video walkthrough by CA Puneet Jain — embedded with credit; the guide above is our own.
The GSTR-1 vs GSTR-2B desync this leaves behind
The credit note fixes the invoice. It does not fix the timing, and that's the part most people don't plan for. Section 34(2) requires the credit note to be declared in the return for the month it is issued — not the month the original wrong invoice was raised. Since the correction, by definition, happens after the mistake is discovered, the reduction to the supplier's output liability lands in a later period than the invoice it's correcting. On the recipient's side, IMS can hold that credit note Pending for a further full tax period before the Pending option is disabled and the recipient must Accept or Reject it — or, if they still do nothing, it's deemed accepted like any other IMS record — so the reversal your books record on the day you raise the credit note is not necessarily the reversal that shows up in the counterparty's GSTR-2B for that same period. If the recipient does nothing, it's deemed accepted into the 2B for the period the supplier reported it; if they mark it Pending, it can trail by one further tax period.
The re-issued invoice makes the gap worse, not better: it's a brand-new IRN, dated today, so it enters the buyer's 2B for the current filing period — not the period the original supply actually happened in. For one stray invoice a quarter, this is a mental note. Across a real invoice volume, it's exactly the kind of gap a total-level "does my books figure match my 2B figure" check will never surface, because the numbers can net out to a false match while the wrong invoice, the credit note and the reissued invoice are each sitting in different periods on different sides of the transaction. Catching which specific credit note is still unmatched in your books against your GSTR-2B, invoice by invoice, every month, is exactly the kind of reconciliation that's painful to do manually at any real volume — and it's the check that would have flagged the gap before it aged into a bigger one.
Four specific situations, answered directly
The buyer's GSTIN was wrong, and it's now well past 24 hours
72 hours or 72 days makes no difference once the window has closed — it doesn't reopen and there's no exception for how the error was found. The fix is the same regardless of elapsed time: credit-note the wrongly-addressed invoice and raise a fresh e-invoice against the correct GSTIN. Worth checking, too: if the wrong GSTIN belonged to a real, existing registered taxpayer, that invoice's data will, unless they rejected it in IMS, already have reached their GSTR-2B for the period — credit they never should have seen, and now have to Accept, Reject or leave Pending against your credit note, or, if they do nothing, it is deemed accepted.
Wrong invoice date, e-invoice not reflecting in GSTR-1
The invoice date is fixed at IRN generation along with every other field — there's no separate "correct the date only" path, 24 hours or not. If the date itself is genuinely wrong, the credit-note-and-reissue route above applies. If the e-invoice generated correctly and the date is right, but the line still isn't appearing in your GSTR-1, that's usually a distinct, later-stage issue — auto-population from the IRP into GSTR-1 is its own process, separate from IRN generation, and a valid IRN doesn't guarantee it flows through cleanly. Per GSTN's auto-population advisory, the process follows the document's own date, not the IRN date, and runs about two days after generation (as of 28 Sep 2026). An e-invoice won't auto-populate at all if GSTR-1 for its period had already been filed by the time you reported it to the IRP — it then shows up only in the "Download details from e-invoice (Excel)" file on that period's GSTR-1 dashboard and is not auto-populated into any later GSTR-1, so it has to be reported manually — or if you'd already entered the same document manually in GSTR-1, since manual entries aren't overwritten.
IRN shows "Auto Population Failed"
Per GSTN's GSTR-1 e-invoice advisory, "Auto Population Failed" is one of four statuses GSTN shows in that same "Download details from e-invoice (Excel)" file on the GSTR-1 dashboard, alongside Auto-populated, Deleted and Deletion failed; the file's "Error in auto-population/deletion" column gives the reason for each document. What can be said independent of that status: a failed auto-population into GSTR-1 doesn't change anything about IRN cancellation or amendment — those still run on the same 24-hour rule described above regardless of what your GSTR-1 draft currently shows.
Cancelled the bill in Tally, but the e-invoice on the portal wasn't cancelled
This is a scope limit, not a bug. Tally's own guidance is explicit: "You can cancel e-Way Bill and e-Invoice from TallyPrime, only if those are generated in TallyPrime." If the e-invoice was generated directly on the portal, through a different GSP, or from another login, deleting the voucher inside Tally removes it only from your books — the IRN on the government side is untouched and still needs cancelling (inside 24 hours) or credit-noting (after) through whichever channel actually generated it.
A second clock that can bite larger taxpayers
There's a separate time limit stacked on top of all this, and it cuts the other way — it can block the corrective e-invoice, not just the original mistake. Per GSTN's advisory of 5 November 2024 (effective 1 April 2025), taxpayers with an aggregate annual turnover of ₹10 crore or more cannot report an invoice, credit note or debit note to the IRP if it's more than 30 days old on the date of reporting — and the clock runs from each document's OWN date, not the date of the original supply it relates to. GSTN's own advisory states there is "no such reporting restriction" below that ₹10 crore threshold, as of now. A commonly repeated version of this — a ₹2 crore threshold, or a 3-day reporting window — is not a figure GSTN has notified (as of 28 Sep 2026); it appears to conflate this rule with the separate annual-return filing exemption thresholds, which are a different mechanism entirely. If you're above ₹10 crore AATO, this 30-day check bites the correction only if you delay reporting the credit note or the new invoice past 30 days of their own dates — the replacement invoice carries the date you actually issue it, so its 30 days run from then — check it before assuming the credit-note-and-reissue fix is still available.
How Recoup fits in
Recoup doesn't generate or cancel e-invoices — that's the IRP's job, and the mechanics above don't change regardless of which system you file through. What Recoup does is sit downstream of exactly this failure mode: it reconciles your books against GSTR-2B invoice by invoice, so a supplier's credit note sitting Pending or Rejected in your IMS, or accepted into your 2B without a matching ITC reversal in your books, shows up as a named exception, not a rounding error buried in a total. The one-off cost of a wrong GSTIN or a stale invoice date is the re-issue above. The compounding cost is not noticing the credit note and the reissued invoice landed in different periods until an auditor or a DRC-01C does.
Stop losing corrections in the gap between periods
Recoup reconciles your books against GSTR-2B invoice by invoice and names the exact credit note or reissued invoice still sitting unmatched — before it ages into a bigger gap.
Book a demo →Related guides
e-Invoicing
Why an invoice without a valid IRN isn't a legal tax invoice at all — the rule this whole workaround exists inside.
Setting up e-invoicing (IRN) in SAP
The GSP configuration that generates the IRN in the first place — where a wrong-GSTIN invoice usually starts.
GST reconciliation: the 2026 guide for finance teams
The invoice-by-invoice check that catches a credit note sitting unmatched in a counterparty's books.
Ship-to GSTIN mandate: deferred, no new date
A different field on the same e-invoice API layer that GSTN pulled back from making mandatory.