E-Way Bill Compliance Guide 2026 Rules, Validity & TMS

An e-way bill is an electronic document mandatory for moving goods worth more than ₹50,000 in India, generated on the government’s e-way bill portal before transport begins. It carries consignment details (Part A) and vehicle details (Part B), and non-compliance can trigger a penalty of ₹10,000 or the tax sought to be evaded — whichever is higher — plus detention of goods and vehicle.

Key takeaways

• E-way bills are required for most inter-state movements of goods above ₹50,000 consignment value; several states set different thresholds for intra-state movement, so multi-state shippers need state-wise rules encoded, not remembered.
• Validity is distance-based: one day per 200 km (or part thereof) for normal cargo — an expired e-way bill in transit is one of the most common and most avoidable detention triggers.
• Part B (vehicle number) is where manual operations break. Every vehicle change, trans-shipment or hub transfer requires a Part B update — exactly the events a TMS already tracks.
• Penalties compound: monetary penalty under Section 129 of the CGST Act, goods/vehicle detention, working-capital lock-up, and SLA breaches downstream.
• A transport management system removes the failure modes by generating, validating, updating and archiving e-way bills automatically from trip data — compliance becomes a by-product of dispatch, not a parallel clerical process.

When is an e-way bill required (and when is it not)?

An e-way bill is required when goods worth more than ₹50,000 (invoice value including GST) move by road, rail, air or vessel — whether the movement is a sale, a branch transfer, a job-work shipment or a return. Key scenarios operations teams get wrong:

The pattern to notice: the rules are conditional and state-dependent. Multi-state shippers relying on a dispatcher’s memory are one exception away from a detained truck.

Part A vs Part B: where compliance actually fails

• Part A — consignment details: GSTINs of supplier/recipient, delivery pin code, invoice number and date, HSN code, goods value. Usually generated at invoicing. Rarely the problem.
• Part B — transport details: vehicle registration number (road) or transport document number (rail/air/ship). The e-way bill is not valid for movement until Part B is filled (with limited exceptions such as movements up to 50 km to a transporter’s hub within the state).

Part B is where real operations collide with compliance, because Part B changes whenever the physical plan changes:

1. Vehicle breakdown mid-route → new vehicle → Part B must be updated before onward movement.
2. Hub-and-spoke trans-shipment → line-haul truck to last-mile vans → every leg’s vehicle must be reflected. (This is routine in a hub and spoke model.)
3. 3PL handoffs → your invoice, their truck: someone must own the update, and “someone” fails at 2 a.m.
4. Consolidated loads → one vehicle, many e-way bills: a transporter can bundle them into a consolidated e-way bill (EWB-02) — powerful, but another manual step if done by hand.

Validity rules: the silent detention trap

Validity starts when Part B is first entered. It can be extended within a window around expiry (currently 8 hours either side) by the current transporter — but only if someone notices in time. Typical failure: a Delhi→Bengaluru load (~2,150 km, 11 days validity) hits a two-day breakdown plus a weekend hub delay, the bill expires quietly, and an interception near the destination costs more in penalty and detention than the freight earned.

What good looks like: your system tracks remaining validity against live vehicle position and predicted ETA, and alerts the control tower before expiry with a one-click extension.

What non-compliance actually costs

Under Section 129 of the CGST Act, moving goods without a valid e-way bill exposes you to a penalty of ₹10,000 or the tax sought to be evaded, whichever is higher — in practice, detention cases are frequently settled at 200% of the tax payable on the goods for release. Add the hidden costs: vehicle and driver idled for days, perishable or promised-date cargo devalued, customer SLA penalties, and a compliance record that invites future scrutiny. For cold-chain loads (pharma, dairy, F&B), detention can mean total product loss — see our cold chain compliance guide.

How a TMS automates e-way bill compliance end to end

A transport management system doesn’t “help with” e-way bills — done right, it makes them a by-product of the dispatch process you already run:

1. Auto-generation at dispatch. Trip creation pulls invoice, GSTIN, HSN and route data and generates the e-way bill via the portal/API integration — no re-keying, no transcription errors (mismatched invoice numbers and wrong pin codes are top interception findings).
2. Validation before the gate. Rule engine checks threshold applicability (state-wise), document completeness and vehicle assignment; a truck can’t be gate-out without a valid, Part B-complete bill.
3. Automatic Part B updates. Vehicle reassignments, trans-shipments and 3PL handoffs in the TMS update Part B in the same action — the physical event and the compliance event can’t drift apart.
4. Validity monitoring against live ETA. GPS/telematics feed vs remaining validity, with pre-expiry alerts and extension workflows.
5. Consolidation support. Auto-build consolidated e-way bills for multi-consignment line hauls planned in load planning.
6. Audit-ready archive. Every bill, update, extension and exception logged against the trip — GST audits become an export, not an excavation.

Compliance metrics worth tracking monthly: % trips with e-way bill generated before gate-out (target: 100%), Part B update lag on vehicle changes, expiry-in-transit incidents (target: zero), interception/detention count, penalty spend.

Frequently asked questions

Who is responsible for generating the e-way bill — consignor or transporter? Primarily the registered person causing the movement (usually the consignor, or consignee in some purchase flows). If neither generates it, the transporter must, based on documents provided. In practice, contracts should assign ownership explicitly — and a shared TMS removes the ambiguity.

What is the e-way bill limit for 2026? The central threshold is ₹50,000 per consignment for inter-state movement. Intra-state thresholds vary by state — check the state notification for every lane you operate, or encode them in your TMS rule engine.

Can an expired e-way bill be extended? Yes — the current transporter can extend validity within the allowed window around expiry (currently 8 hours before/after), citing reasons like breakdown or trans-shipment delay. After the window closes, a fresh bill is generally required.

Is an e-way bill required for goods below ₹50,000? Generally no, with exceptions that apply regardless of value — notably inter-state job work and inter-state movement of handicraft goods by exempt dealers.

What happens if a vehicle changes mid-journey? Part B must be updated with the new vehicle number before the goods move onward. A TMS that links vehicle reassignment to automatic Part B updates eliminates this failure mode.

Does ZenDMS handle e-way bill compliance? Yes — ZenDMS TMS generates e-way bills at dispatch, validates them before gate-out, auto-updates Part B on vehicle changes and trans-shipments, monitors validity against live trip ETAs, and maintains an audit-ready archive per trip.