E-Way Bill Cancellation and Rejection: The 24- and 72-Hour Windows

A truck is booked for 2 p.m., the e-way bill is raised at 2:05, and by evening the load is still on the dock because the vehicle failed its brake check. Nobody touches the bill until the next afternoon, when someone tries to cancel it and the portal says no. A second bill for the same invoice is now live, the buyer's accounts team sees both under its GSTIN, and the transport desk cannot explain which one describes the real movement.

That situation is avoidable with two clocks and one rule about who holds each. The generator can cancel within 24 hours of generation under Rule 138(9) of the CGST Rules, unless an officer has verified the bill in transit. The other party can reject within 72 hours under Rules 138(11) and 138(12), after which silence counts as acceptance. Running both clocks from the dispatch screen, not from memory, keeps every live bill matched to a real truck.

• What the guide explains: the difference between cancelling and rejecting, how each window is counted, what to do when a vehicle never moves, and where the NIC portal stops you without asking.
• What it adds: the NIC cancel and reject payloads with the four cancellation reason codes, a timestamped failure trace, a rupee penalty exposure example with a US contrast in dollars, and a cutoff checklist for dispatch and receiving teams.

Cancel or reject: two actions held by two different parties

Cancellation withdraws a bill and belongs only to the person who generated it; rejection records that the counterparty disputes the consignment and belongs only to that counterparty. Neither one can stand in for the other, and confusing them is the root of most stranded bills in the e-way bill system.

NIC's API documentation for version 1.03 states the split plainly. The cancel call validates that "E-way bill can be cancelled by the generator of the e-way bill only" and only within 24 hours of generation. The reject call allows the other party to reject a bill generated by the supplier or recipient, and allows either supplier or recipient to reject a bill generated by a transporter, within 72 hours of generation.

How the 24-hour cancellation clock in Rule 138(9) is counted

The cancellation window opens at the timestamp printed on the bill and closes exactly 24 hours later; a calendar day, a shift change or a public holiday does not extend it. Rule 138(9) allows cancellation where goods "are either not transported or are not transported as per the details furnished" in the bill.

Two provisos narrow it further. A bill cannot be cancelled once it has been verified in transit under Rule 138B, so an inspected truck keeps its bill whatever happens next. The second proviso keeps the unique number from Part A valid for 15 days for adding Part B, which matters when a supplier raises Part A early and the transporter has not yet been assigned.

E-way bill cancellation on the NIC portal is limited to the generating GSTIN within 24 hours of generation under CGST Rule 138(9), and is barred once an officer verifies the bill under Rule 138B; a dispatch desk that reviews every unmoved bill by hour 20 leaves a 4-hour margin for the cancel call.

The portal does not let anyone edit Part A. NIC's own FAQ says a bill "cannot be edited or corrected" and that the only route for wrong details is to cancel and generate a new one. That makes the 24-hour window the only correction path for a wrong GSTIN, quantity, value or HSN code on the bill itself, and a reason to check Part A against the invoice before the truck is called forward.

When the cancel is made through the API rather than the web screen, the request carries the bill number, a reason code from NIC's master list and an optional remark of up to 50 characters. The reject request carries only the bill number. Logging both responses, with the returned cancel or rejection date, gives the desk proof of what it did and when.

// CANEWB: data element before encryption (NIC e-way bill API v1.03)
{
  "ewbNo": 361004827715,        // 12-digit e-way bill number
  "cancelRsnCode": 2,           // 1 Duplicate, 2 Order Cancelled,
                                // 3 Data Entry mistake, 4 Others
  "cancelRmrk": "Vehicle failed brake check, load held"   // max 50 chars
}

// REJEWB: data element sent by the counterparty
{ "ewbNo": 361004827715 }

// Desk clock (all times IST, from the bill's generation timestamp g)
cancel_deadline  = g + 24 h          // generator only, if not verified
reject_deadline  = min(g + 72 h, t_delivery)   // counterparty
review_alarm     = g + 20 h          // unmoved bills listed for decision

When the vehicle never left: cancel, update Part B or let it lapse

A bill for a truck that did not move needs one of three decisions before hour 24: cancel it, update its Part B to the vehicle that will actually carry the goods, or confirm it will move inside its validity. Leaving the choice until the next shift turns a free correction into a permanent mismatch.

• Load cancelled outright: cancel with reason code 2 and tell billing, because the invoice may also need cancelling or a credit note, and the bill should not outlive the sale.
• Same load, different truck: update the vehicle number in Part B instead of raising a second bill; NIC's FAQ allows Part B updates as many times as needed within validity. Our vehicle change workflow covers the mechanics of that update; this article covers the decision to cancel instead.
• Wrong value, GSTIN or quantity: cancel with reason code 3 and regenerate, since Part A cannot be edited after generation.
• Partial load shipped: treat the bill as "not transported as per the details" and cancel and regenerate within the window, rather than letting a full-quantity bill cover a part shipment.
• Load delayed beyond validity: extend validity under the Rule 138(10) proviso, which permits extension within eight hours from expiry, rather than cancelling a bill whose goods will still move.

The recipient's 72 hours under Rules 138(11) and 138(12)

A registered recipient or supplier who did not raise the bill has 72 hours to reject it, and if it says nothing in that time, or before delivery if delivery comes first, the details are treated as accepted. Deemed acceptance is the real risk for a receiving GSTIN that never looks at the bills raised in its name.

Rule 138(11) makes the details available to the supplier where the recipient or transporter filled Part A, and to the recipient where the supplier or transporter filled it. Each must "communicate his acceptance or rejection of the consignment". Rule 138(12) then deems acceptance after 72 hours from the details being made available on the portal, or at delivery if earlier.

Rejection of an e-way bill under CGST Rules 138(11) and 138(12) must reach the NIC portal within 72 hours or before delivery, whichever is earlier; a receiving GSTIN that reviews the portal list of bills generated by other parties every 24 hours keeps at least two chances to reject an unknown consignment.

NIC gives the receiving side three ways to see what has been raised against its GSTIN: the dashboard after login, a daily SMS summarising e-way bill activity on the GSTIN, and the report of bills generated by other parties. The reject screen itself lists bills by date. A company that receives from hundreds of suppliers should give that review to a named sub-user, which the portal supports, rather than relying on the main login.

• Unknown supplier on the bill: reject the same day, because a bill naming your GSTIN for goods you never ordered can be used to give cover to a movement you know nothing about.
• Known supplier, wrong quantity or value: reject and ask the supplier to cancel within its own 24 hours, or to raise the correction through a credit or debit note if that window has passed.
• Goods arrived and match: no action is needed; acceptance is deemed, and the receiving record should carry the bill number against the goods receipt note.

What a rejection does not do, and what still follows it

Rejecting a bill records disagreement; it does not withdraw the bill, move the goods back or reverse the supplier's invoice. Each of those needs its own action by the party who owns it, and the receiving side should not treat a rejection as the end of the matter.

NIC's master codes list three bill statuses, ACT for active, CNL for cancelled and DIS for discarded, with no separate status for a rejected bill. The reject call returns a rejection date, which becomes part of the record. Where goods are physically refused at the gate, NIC's FAQ directs the transporter to get a fresh bill generated by the supplier or recipient, showing the supply as a sales return, before carrying the goods back.

Treat the rejection as evidence rather than a fix. Store the rejection date beside the bill, the email or ticket in which the counterparty objected, and the supplier's reply. If a scrutiny notice later asks about a bill with no matching receipt, that bundle answers the question without anyone reconstructing events from memory.

The same discipline applies in reverse. A supplier that receives a rejection on a bill it believes is correct should call the recipient before doing anything else; a rejection raised by mistake on a valid bill is easier to explain in a same-day email than in a reply to an officer months later.

Incident trace: a cancelled pickup that left a live bill behind

The failure below cost nothing at the moment it happened and created a document gap that took a week to close. Each step is ordinary; the error is that no one owned the clock that started at generation.

1. Mon 9 Nov, 14:05: Dispatch generates e-way bill 361004827715 for invoice INV/26-27/1184, taxable value ₹4,20,000 with IGST of ₹75,600, Part B showing vehicle MH12AB4521 for a 640 km lane.
2. Mon 9 Nov, 16:40: The truck fails a brake check at the yard and the load stays on dock 3. The dispatcher notes "fix tomorrow" in the TMS comments, with no status change on the bill.
3. Tue 10 Nov, 10:30: Replacement vehicle MH14CX0917 arrives. The morning desk, unaware of the first bill, generates a second bill 361004831902 on the same invoice and the truck leaves at 11:15.
4. Tue 10 Nov, 15:20: The night dispatcher's comment is finally read. The desk tries to cancel 361004827715 and the portal refuses, because the 24-hour window closed at 14:05.
5. Wed 11 Nov, 09:10: The buyer's accounts clerk sees two bills for one invoice on the report of bills raised by other parties and rejects the first. Controlled version: the bill sits on its owner's open list from 16:45 on Monday, and at 10:30 on Tuesday the desk updates its Part B to MH14CX0917, inside validity, so no second bill ever exists.

Penalty exposure when a bill outlives the movement it described

An uncancelled bill is not itself a penalty event, but a truck intercepted while its documents do not match the goods is. The exposure sits in Section 129 of the CGST Act for detention and release, and in Section 122(1)(xiv) for transporting taxable goods without the cover of the specified documents.

Section 129(1)(a) releases detained goods on a penalty of 200% of the tax payable where the owner comes forward. Section 122(1) sets a penalty of ₹10,000 or the tax evaded, whichever is higher, for the listed offences. Our Section 129 penalty guide covers the MOV forms and release steps; the table below shows only the arithmetic a documentation manager needs to brief finance.

Detention exposure under CGST Act Section 129(1)(a) equals 200% of the tax payable, so a consignment carrying ₹75,600 of IGST risks a ₹1,51,200 penalty when its e-way bill does not match the goods; cancelling or updating the bill inside the 24-hour Rule 138(9) window removes that penalty line entirely.

US contrast: export filings have no 24-hour cancel window

The e-way bill is an Indian GST document with no US counterpart for domestic trucking, so the closest US comparison is the export filing that a cancelled export shipment leaves behind. There, the rule is to correct or cancel as soon as possible, with fixed deadlines only for specific system messages.

Under 15 CFR 30.9(a), the US principal party in interest or its authorised agent must transmit corrections, cancellations or amendments to Electronic Export Information in the AES "as soon as possible", and failure to correct is a violation. Under 30.9(b), fatal errors must be fixed before export for predeparture filings, warnings and justified verify messages within four calendar days. Our EEI filing guide covers AES responses in more depth.

• Who acts: in India the generating GSTIN cancels and the counterparty rejects; in the US the filer of the EEI corrects or cancels, and the consignee has no rejection step.
• Clock type: India uses hard windows that lock the portal; the US relies on an obligation to act promptly, enforced afterwards through the penalty provisions in Subpart H of Part 30.
• Domestic moves: a cancelled domestic US truckload leaves a bill of lading and a carrier charge, but no government document to withdraw.

Portal rules versus desk judgement on cancellations and rejections

The NIC portal enforces the windows, the ownership rules and the verification bar without exception; it cannot decide whether a stalled load will move today. Software can surface bills at risk and summarise what transporters report, but the cancel or reject click stays with a named person.

A cutoff checklist for dispatch, billing and the receiving GSTIN

Four owners and two timestamps cover almost every stranded bill: the generator watches hour 20 and hour 24, and the receiver reviews bills raised against it at least daily. The checklist below turns that into tests a site can run during a dispatch-system rollout or an internal audit.

Where the bill was generated from an e-invoice, the order of cancellation matters as much as the timing; our guide to the IRN and e-way bill sequence sets that order out. For more on transport documents across both markets, see the logistics and supply chain hub.

If you are specifying a dispatch or TMS module that should raise the hour-20 list, store cancel and reject responses and show bills raised by other parties against open purchase orders, describe those requirements in a request for proposal and ask each bidder to demonstrate them against a held-truck scenario.