Cancel an E-Invoice Within 24 Hours (and What to Do After)

An e-invoice's IRN can be cancelled on the Invoice Registration Portal within 24 hours of the moment it was generated, provided the goods or services under it have not moved or been delivered. Once that window closes, the IRP will not cancel the IRN under any circumstance, and the only compliant way to correct the invoice is a credit note, a debit note, or in some cases a fresh invoice for the actual supply.

The 24-hour rule catches people off guard in two specific ways: the clock starts at IRN generation, which is not always the same moment the invoice was created in your billing software, and the window is short enough that a mistake spotted a day later, which feels prompt in ordinary business terms, is already too late for cancellation. This guide covers exactly what starts the clock, how to cancel correctly inside the window, and what changes once you are past it. For the surrounding e-invoicing process, see the e-invoicing guide.

What starts the 24-hour clock

The 24-hour period runs from the timestamp the IRP records when the IRN is generated, which the portal logs to the minute. This is distinct from the invoice date printed on the document and from the moment your billing software created the invoice record internally.

The gap matters most for businesses that create invoices in a batch and push them to the IRP afterward, or that generate an invoice late in the day and only submit it for an IRN the next morning. If an invoice dated the 3rd is generated on the IRP at 11pm on the 4th, the cancellation window runs until 11pm on the 5th, not 24 hours from the invoice date. Checking the actual IRN generation timestamp, available on the acknowledgment the IRP returns, is the only reliable way to know how much time remains.

Cancelling within the window: what to check first

Cancellation is meant for invoices that should not have been issued at all, not as a general-purpose undo for any invoice you regret. Before cancelling, confirm the goods have not moved and the service has not been delivered under that invoice. If fulfilment has already started, a credit note is the correct instrument even if you are technically still inside the 24-hour window, because cancellation implies the transaction never happened, and a partially or fully delivered supply did happen.

The cancellation itself is a short action on the e-invoice portal or through your billing software's e-invoicing screen: select the invoice by its IRN, choose cancel, and record the reason. Once submitted, the IRN status changes to cancelled and the QR code and IRN can no longer be used to validate the document.

A worked example of the cancellation itself

Walking through the actual steps on the e-invoice portal makes the process concrete rather than abstract, particularly for a business cancelling an IRN for the first time.

Log in to the e-invoice portal, einvoice1.gst.gov.in, using the credentials tied to the GSTIN that generated the invoice. Only the generating GSTIN can cancel its own IRN; a recipient viewing the same invoice through their own login has no cancellation option available to them at all, since the action belongs entirely to the issuer.

From the e-invoice menu, select the cancel option and enter either the IRN itself or the acknowledgment number and date shown on the original invoice's e-invoice acknowledgment. The portal will display the invoice details, including its generation timestamp, which is the moment to double-check the 24-hour window rather than relying on memory of when the invoice was created.

Choose a cancellation reason from the list the portal provides, typically duplicate, data entry mistake, order cancelled, or others with a free-text field. Selecting an accurate reason matters beyond the transaction itself, since a pattern of frequent cancellations under the same reason is exactly the kind of internal signal worth investigating, as covered further down.

Submit the cancellation. The portal updates the IRN's status to cancelled immediately, and the QR code previously generated for that invoice no longer validates against a live document if anyone scans it afterward. At this point, the invoice should also be marked cancelled inside your own billing records, not just on the portal, so the two stay consistent when GSTR-1 Table 13 is prepared for that period.

If your billing software integrates with the IRP directly rather than requiring a separate portal login, this entire sequence typically happens as a single action from within the invoice screen itself, with the software calling the cancellation API and updating its own record in the same step. That removes the risk of the two records drifting apart, which is a common source of confusion when the portal and the internal ledger are cancelled by different people at different times.

What happens once the window closes

Past 24 hours, the cancel option on the IRP is simply not available, regardless of how clear the mistake is. This is a deliberate design choice: once an e-invoice has had a full day to circulate, be reported to the recipient, and potentially be acted on, the system treats reversing it outright as too disruptive, and routes the correction through the credit note and debit note mechanism under Section 34 instead.

Credit note vs cancellation: which one applies

The two mechanisms solve different problems, and picking the wrong one either fails outright or creates a messier trail than necessary.

A credit note references the original invoice and reduces or nets out its value; it does not erase the original from the record the way a cancellation does. This is actually useful in an audit trail, because the sequence of what was invoiced, corrected and why remains visible, whereas a cancelled invoice simply disappears from the active count. The credit note and debit note guide covers how to issue either document and the reporting deadline for credit notes tied to a previous financial year.

Effect on GSTR-1, GSTR-2B and IMS

A cancelled e-invoice does not appear as a live invoice in your GSTR-1; instead, it should be reflected in the document series count in Table 13 as a cancelled number, with the total, cancelled and net figures in that series staying arithmetically consistent. If the recipient had already seen the invoice appear in their Invoice Management System before you cancelled it, the cancellation removes it from their pending or accepted queue only after their next GSTR-2B refresh, so a quick message to the customer avoids confusion on their end in the meantime. The ITC and notice guide covers how a mismatch between what you reported and what the recipient sees can surface as a notice later, which is one more reason to coordinate rather than assume a silent cancellation is enough.

A credit note, by contrast, flows through GSTR-1 Table 9B as its own line and appears to the recipient as a document requiring its own IMS action, separate from the original invoice.

When to involve your CA

Most cancellation decisions are straightforward enough to make yourself: a genuine duplicate, a wrong GSTIN caught within the hour, an order cancelled before dispatch. Involve your CA or GST practitioner when the situation is less clean, such as an invoice that has already been referenced in a filed GSTR-1 for a prior period, a case where it is unclear whether the supply has legally occurred yet, or a high-value B2B invoice where the customer disputes whether a credit note or a cancellation is the correct instrument.

A wrong classification at this stage, treating a delivered supply as cancellable or leaving a genuinely void invoice standing because the window closed, creates a mismatch that is far more expensive to unwind during a GSTR-9 reconciliation or an audit than it would have been to get right at the time. When in doubt, treat the invoice as delivered and reach for a credit note; it is the safer default of the two.

Preventing the need to cancel

Most cancellations trace back to a small set of preventable mistakes: a customer's GSTIN typed incorrectly, an amount entered before a last-minute discount was applied, or an invoice generated twice because of a retry after a slow response from the IRP. A customer master that stores GSTIN once and reuses it on every invoice removes the first cause. Generating the invoice only after the final order details, including any discount, are confirmed removes the second. Checking for an existing IRN before resubmitting removes the third, and it is worth building as a deliberate check if your process ever retries a failed submission automatically.

Billing software that validates GSTIN format and checksum before submission, pulls customer details from a saved master, and shows the existing IRN status before allowing a resubmission catches most of these before an IRN is even generated, which is cheaper than any cancellation. myBillPlease applies GSTIN checks and customer masters this way across its invoicing, alongside GSTR-1 and GSTR-3B preparation built from the same invoice records.

The 24-hour rule is unforgiving mainly because it is short, not because it is complicated. Know when the clock actually started, check it against the current time before assuming you can still cancel, and have the credit note process ready as the fallback for everything the window does not cover.