E-Way Bill Validity and Extension Rules With Worked Distances

A truck carrying auto components from Chakan to Bengaluru loses its gearbox near Davanagere on the last afternoon of its e-way bill. The driver calls the transport desk at 14:05, the desk promises to "extend it in the morning", and at 09:10 the next day the portal refuses: the extension window closed at 08:00. By evening the repaired truck is stopped near Chitradurga with an expired document and goods worth ₹18.4 lakh on board.

Validity and extension failures are almost always timing failures, and timing can be computed. Every e-way bill's expiry follows from its distance, its vehicle type and the moment Part B was first filled. The extension window follows from that expiry. A desk that calculates both at generation, alerts before the window opens and files the extension with the right reason, place and remaining distance will rarely see a detention for an expired bill.

• What this guide covers: the distance slabs in CGST Rule 138(10), the midnight rule, over-dimensional cargo and ship legs, the eight-hour extension window, the fields NIC asks for, and the 360-day cap.
• What it adds: worked expiry dates for four consignments, a timestamped breakdown trace, a validity formula a TMS can run, a cost table with a US contrast, and an implementation checklist.

How Rule 138(10) converts kilometres into days of validity

Validity is one day for the first 200 km and one more day for every further 200 km or part of it, for ordinary cargo. CGST Rule 138(10) sets this in a four-row table, with 200 km substituted for the earlier 100 km by Notification 94/2020-Central Tax from 1 January 2021. Over-dimensional cargo and multimodal moves with a ship leg use 20 km instead.

Explanation 1 to the sub-rule defines how a day is counted. Validity runs from the time the bill is generated, and each day expires at midnight of the day following the date of generation. In practice, a one-day bill raised at 15:20 on 3 November is valid until midnight at the end of 4 November, and an N-day bill expires at midnight at the end of the generation date plus N days.

NIC's FAQ adds one operational detail that the rule text does not spell out: validity starts when Part B is first filled, meaning the first vehicle number for road or the first transport document number for rail, air or ship. Later Part B updates do not restart the clock. A bill generated as a Part A slip on Monday and given a vehicle on Wednesday therefore runs from Wednesday.

E-way bill validity and extension window (CGST Rule 138(10); NIC portal behaviour)

  slab_km     = 20   if vehicle_type = 'O' (over-dimensional) or route has a ship leg
              = 200  otherwise
  days        = CEILING(distance_km / slab_km)            -- minimum 1
  start_date  = DATE(first_part_b_entry_ts)                -- NIC FAQ: clock starts at first Part B
  expiry_ts   = (start_date + days) at 23:59:59            -- Explanation 1: day ends at midnight
  window_open = expiry_ts - 8 hours                        -- NIC: extend from 8 h before expiry
  window_shut = expiry_ts + 8 hours                        -- Rule 138(10) proviso: within 8 h after
  hard_cap    = DATE(generation_ts) + 360 days             -- NIC advisory, from 1 January 2025

Example: 840 km, regular, first Part B 03-11-2026 15:20
  days = CEILING(840 / 200) = 5
  expiry_ts   = 08-11-2026 23:59:59
  window_open = 08-11-2026 16:00   window_shut = 09-11-2026 08:00

E-way bill validity under CGST Rule 138(10) is one day per 200 km or part for ordinary cargo and one day per 20 km for over-dimensional cargo, each day ending at midnight. An 840 km bill with Part B filled at 15:20 on 3 November expires at 23:59 on 8 November.

The distance field: PIN-to-PIN auto value and the 10% ceiling

The day count can only be as good as the distance entered, and the portal limits how far that number can move. NIC's user manual says the system auto-calculates the motorable distance between the dispatch and delivery PIN codes and lets the user enter the actual route distance, capped at 10% more than the auto value. Where both PIN codes are the same, the maximum is 100 km.

The 10% headroom exists for real routes that are longer than the shortest road, such as a diversion around a weight-restricted bridge. It can change the day count legitimately: an auto distance of 760 km gives 4 days, while a documented 836 km route gives 5. Entering the ceiling by default to buy a spare day is a misstatement, and it also weakens the remaining-distance figure you will need for any later extension.

• Same-PIN moves: a 45 km intra-city transfer with one PIN code on both ends is accepted up to 100 km.
• Part A slips: under the second proviso to Rule 138(9), the number generated for a Part A slip stays valid for 15 days for Part B to be added.
• No restart on vehicle change: a replacement truck entered in Part B continues the original validity, so a breakdown never buys time by itself.
• Cancellation limit: Rule 138(9) allows cancellation within 24 hours of generation, and not after the bill has been verified in transit.

Vehicle replacement is a separate workflow from extension. Our guide on handling a vehicle change without losing the e-way bill trail covers the Part B update and its evidence; this article covers what to do when the clock itself will run out. For how the distance and validity are first set when a bill is raised from an e-invoice, see our IRN to e-way bill guide.

Over-dimensional cargo and ship legs run on a 20 km day

A transformer, a wind-turbine blade or a pressure vessel moving on a hydraulic trailer gets ten times as many days per kilometre as ordinary cargo. Explanation 2 to Rule 138(10) defines over-dimensional cargo as a single indivisible unit that exceeds the dimensional limits in Rule 93 of the Central Motor Vehicles Rules, 1989. Mixed loads that merely fill a large truck do not qualify.

Notification 31/2019-Central Tax extended the 20 km slab to multimodal shipments in which at least one leg is by ship, and the same notification added the eight-hour extension proviso. NIC's portal enforces the pairing in reverse: its user manual says that when the mode is ship or road-cum-ship, the vehicle type must be over-dimensional cargo and regular is not allowed.

Worked distances show the scale. A 186 km move of one 42-tonne transformer from a Vadodara works to a substation is valid for 10 days. A coastal multimodal shipment of 1,600 km from Mundra to Kochi with road legs at both ends is valid for 80 days. An ordinary truckload over the same 186 km would be valid for a single day.

Over-dimensional cargo validity under CGST Rule 138(10), Explanation 2, applies only to a single indivisible unit beyond Central Motor Vehicles Rules 1989 Rule 93 limits. A 186 km transformer move earns 10 days on the NIC portal, while an ordinary 186 km truckload earns one day ending at midnight.

The extension window opens eight hours before midnight expiry

Extension is possible only from eight hours before expiry to eight hours after it, and only by the transporter currently assigned. The third proviso to Rule 138(10) says validity may be extended within eight hours from the time of expiry; NIC's API documentation and FAQ implement a window running from eight hours before to eight hours after, and reject other attempts with error 382.

The second proviso supplies the grounds: circumstances of an exceptional nature, including transshipment, where goods cannot reach the destination within validity. NIC's FAQ lists natural calamity, law and order problems, transshipment delay, accident and vehicle breakdown as examples. A separate first proviso lets the Commissioner extend validity by notification for specified categories of goods, which is a policy route, not a desk tool.

Part A cannot be changed during an extension; NIC's FAQ is explicit on this. The portal then grants validity "depending upon the distance to travel", in the words of the user manual, and sets the new expiry to midnight of the last extended day. Read the validUpto value in the response rather than assuming a date, and store it as the new clock.

Incident trace: a gearbox failure and an extension filed too late

The trace below uses illustrative document numbers and the 840 km Chakan to Bengaluru example. It shows the failure path first and the controlled path the same desk now follows.

1. 3 November 15:20, bill generated: E-way bill 3410 2287 6615 is raised with Part B for a regular vehicle, 840 km. The TMS stores 5 days, expiry 8 November 23:59, window 8 November 16:00 to 9 November 08:00.
2. 8 November 14:05, breakdown: The driver reports a gearbox failure on the highway near Davanagere, 265 km from the consignee. The workshop job card promises repair by the next afternoon. The desk logs "extend tomorrow" in its chat group and no TMS task is created.
3. 9 November 09:10, extension rejected: The desk attempts EXTENDVALIDITY and receives error 382, because the window shut at 08:00. The bill is now expired, and NIC's FAQ says goods are not supposed to move on an expired bill.
4. 9 November 18:45, interception: The repaired truck is stopped near Chitradurga. The officer records the expired bill, and the detention and penalty process begins; our Section 129 penalty guide walks through the MOV forms and release options.
5. Controlled path, 8 November 16:20: Under the revised process, the TMS opens an extension task at 16:00. The desk files reason 99 with remarks "gearbox failure, job card WS-4471", status T, transit type R, current PIN at Davanagere and 265 km remaining, then saves the new validUpto returned by the portal.

Recomputing days for the remaining distance after an extension

The extension is sized by the distance still to travel, not by the original route. NIC's FAQ says the transporter gets extended validity based on the remaining distance, and the API rejects a remaining distance larger than the distance on the bill. Two decisions on the desk therefore change the outcome: where the goods are said to be, and how far that place is from the consignee.

In the Davanagere case, 265 km remaining falls in the second 200 km slab, so the extension carries two days' worth of validity. A careless entry of the original 840 km would fail validation with error 390. An entry of 180 km to "keep it simple" would give a single day and risk a second expiry if the repair slips again.

• Use the GPS position: take the current PIN from the vehicle tracker or the workshop address, not from the driver's memory.
• Measure remaining road distance: use the same routing source as the original bill so the two figures are comparable.
• Warehouse holds: where goods are unloaded into a godown during a strike, choose status T and transit type W with the godown address.
• Repeat extensions: each later extension follows the same window rule, measured from the newly returned expiry.

Since 1 January 2025, NIC limits extensions to 360 days from the bill's original generation date. GSTN's advisory of 17 December 2024 announced the cap together with a 180-day limit on the age of the base document. Long-dwell cases, such as goods stuck at a closed border or in a disputed godown, need a plan before day 360, because error 821 ends the extension route.

E-way bill extensions on the NIC portal are sized by remaining distance from the consignment's current PIN, filed between 8 hours before and 8 hours after expiry under CGST Rule 138(10), and capped at 360 days from generation since 1 January 2025. A 265 km remainder yields two slab days.

Four consignments, their clocks and the money at stake

Expired bills cost money even before any penalty, because trucks wait while the desk sorts out documents. The table below takes four consignments, works out their validity and extension windows, and prices the operating cost of a missed window in rupees. The US column is a contrast, because the US has no domestic movement document that expires.

US interstate trucking has no state or federal e-way bill: a delayed truckload costs time and detention but carries no document clock. The nearest US analogue is the customs in-bond move, where 19 CFR 18.1(i) requires delivery to the destination port within 30 days, or 60 days where a barge is used. All rupee and dollar costs below are illustrative.

The arithmetic is simple enough for a spreadsheet, but the cost of getting it wrong grows with the cargo. Over-dimensional moves carry long windows and the largest rebooking costs, while short same-PIN transfers have the tightest clocks and are the ones most often raised late at night and forgotten.

Checks the NIC portal enforces and calls the transport desk owns

The portal enforces timing, distance limits and who may extend, but it cannot tell whether a breakdown is real or whether goods should move. The table below lists each task in the validity and extension workflow and where the decision sits.

Building expiry alerts and extension tasks into the TMS

The desk needs the clock in the TMS, not in a chat group. Store the start time, slab, days, expiry, window opening, window close and 360-day cap on every load at the moment Part B is first filled, and drive tasks from those timestamps. If you call NIC directly, our e-way bill API integration guide covers authentication and the EXTENDVALIDITY call.

• Window-open task: at expiry minus eight hours, open a task for every undelivered load whose ETA is after expiry.
• Night escalation: at 23:00, page a named duty person for any open task; after 08:00 the portal route is closed.
• Proof of delivery link: close tasks automatically when proof of delivery arrives before expiry, so the queue holds only real risks.
• Response capture: write the returned validUpto back to the load and recompute the next window.
• Exception report: list every bill that expired undelivered, with the reason and who owned the task.

Validity and extension control checklist for a transport desk

Most of the control is set-up work done once: the clock fields, the alerts, the duty roster and the reason-code guide. The checklist below sets each item against an owner and a test that proves it works before the next breakdown.

More GST transport and trade-document guides are on the Logistics and Supply Chain hub. If you want validity clocks, extension alerts and NIC calls wired into your TMS, send us a request for proposal with your monthly e-way bill volume, lanes and current desk process.