What is an eWay Bill?
Electronic Way Bill
Definition
An eWay Bill is an electronic document required under India’s GST regime for moving goods worth more than a threshold value. It has two parts: Part-A (invoice and consignment details) and Part-B (vehicle and transporter details). It is generated on the NIC eWay Bill portal.
Why it matters for Indian fleets
Goods moving without a required valid eWay Bill can face detention and penalties. Accurate generation, transport-detail updates, and validity review help manage that risk; software does not guarantee compliance.
How to generate an eWay Bill
- Log in to ewaybillgst.gov.in with your GST credentials.
- Fill Part-A: document type, recipient GSTIN, taxable value and HSN details.
- Fill Part-B: enter the vehicle number for road transport, or the transporter document number.
- Submit to get a unique 12-digit eWay Bill Number (EBN). Validity depends on distance, roughly one day per 200 km.
When you actually need one
The central rule is a consignment value above ₹50,000, counted per consignment rather than per invoice, for movement of goods by road, rail, air or ship.
Two details catch people out. States set their own intra-state thresholds and some are lower than the central figure, so a movement that needs no bill in one state needs one across the border. And the requirement follows the goods, not the vehicle, so a single truck can carry consignments that individually need bills and others that do not.
There are exemptions, including specified goods and certain short movements, and they change. Anything with a penalty attached should be checked against the official eWay Bill portal for the states you actually operate in, rather than taken from any summary including this one.
How validity is calculated, and when the clock starts
This is the part most operators get wrong, because the clock does not start when the bill is created.
Validity runs from when Part-B is first entered, not from Part-A. A bill generated on Monday with the vehicle added on Wednesday is valid from Wednesday.
For regular cargo the allowance is one day per 200 km, with any part of a further 200 km counting as another full day. Over-dimensional and multimodal cargo runs on a much shorter allowance per day.
A day here means until midnight of the following day rather than a rolling 24 hours, which is why a bill created late in the evening effectively gets less time than one created in the morning.
So a 1,000 km run needs five days of validity, and the practical question is never the arithmetic but whether a breakdown, a detention or a long check-post queue eats the margin.
Part-B is where it actually breaks
Part-A rarely fails. It is filled once, in an office, from an invoice that already exists.
Part-B carries the vehicle number, and vehicles change. A breakdown, a transshipment at a hub, or a last-minute swap in the yard all mean the number on the bill no longer matches the truck on the road. The bill is then invalid, and an invalid bill is treated as no bill.
This is the single most common eWay Bill failure in road transport, and it is entirely an operational problem rather than a tax one. Nobody decides not to update Part-B; it is forgotten, because the person who knows the vehicle changed is the driver and the person who can update the bill is in an office. See eWay Bill Part-B for what it contains and when it can be skipped.
Multiple vehicles on one consignment
A consignment that moves on more than one vehicle does not need a new eWay Bill each time. It needs Part-B updated at each leg.
The pattern is: generate once, then update the vehicle number at every transshipment while the same bill number stays live. For a hub-and-spoke operation that can be several updates on one consignment.
Where goods are split across vehicles, each vehicle carries its own documentation for the portion it holds, because enforcement checks the vehicle in front of it against what that vehicle is carrying.
Keep the actual vehicle assignment and bill together at each handoff. MoboSafe’s eWay Bill workflow supports fetching, generation, trip links, and eligible extension requests. A transport-detail update needs the required information and portal acceptance; GPS coordinates do not continuously update Part-B.
What to do when it expires in transit
Where a valid eWay Bill is required, do not continue movement after expiry. Detention and penalties depend on the facts and applicable legal process; expiry does not mean the underlying consignment ceases to exist.
Eligible extension requests can be made within eight hours before or after expiry by an authorised current transporter or eligible generator, subject to reasons, portal acceptance, and the 360-day outer limit. The post-expiry request window is not permission to move goods. See the official extension API.
The realistic answer is to see it coming. Expiry is predictable from the moment Part-B is entered, so an operation tracking its own vehicles knows which bills are going to run out before the vehicle arrives. Discovering it at a check-post means the decision has already been made for you.
On what detention actually costs, see the real penalty for an expired eWay Bill.
Related MoboSafe workflows
Review the documented product scope and setup requirements for these related operational tasks.
E-Way Bill Management
Manage e-way bills with GST portal connections, generation, trip links, expiry review, and eligible extension requests in MoboSafe.
Loading & Dispatch
Create loading sheets with vehicle and driver assignments, consignment items, weight checks, documents, and dispatch printouts.
Trip Management
Plan, monitor, and analyse fleet trips with vehicles, drivers, waypoints, documents, exception handling, and delivery records.
Fleet APIs & Integrations
Configure MoboSafe integrations, API access, device connections, connection tests, usage monitoring, and dashcam backup settings.
Related terms
Begin
Ready to connect your whole operation?
Explore tracking, trips, assets, fuel, inventory, accounting, and payroll with the MoboSafe team. Build a rollout around the workflows your fleet needs.