Consolidated e-way bill (trip sheet): rules and regeneration

Under the e-way bill system’s validations, an e-way bill can be added to a consolidated e-way bill (CEWB) if the person generating the CEWB is the generator or the assigned transporter of that e-way bill. Each e-way bill added must be active, meaning not cancelled, and within its validity period.

For road transport the vehicle number must be passed and the transport document number is optional. For rail, air or ship the transport document number is required. If a vehicle number is passed its format must be valid.

The system lets the generator of the CEWB, or its current transporter, regenerate it. Regeneration considers only e-way bills that are still active and within validity, so an expired or cancelled one is left out.

The reason codes are the same four as for a vehicle update: 1 Break Down, 2 Transshipment, 3 Others, 4 First Time.

In live use the result is a new trip sheet number, and reading the old number afterwards shows it as cancelled (CNL). It is not an in-place edit, so store the new number as soon as the call returns.

The number is 10 digits, and the requester has to be the generator of the CEWB. Anyone else is told “Could not retrieve data” (code 325).

POST /v1/ewaybill/consolidated takes the list of e-way bill numbers, where the vehicle is now, the transport mode and the vehicle number. POST /v1/ewaybill/consolidated/details reads one back by its 10-digit number, and POST /v1/ewaybill/consolidated/regenerate takes the current number, the new vehicle and a reason.

Generating costs 3 credits however many e-way bills are on it, reading costs 1 credit and regenerating costs 3 credits. If one e-way bill number is not recognised the whole request is refused with “Invalid eway bill number” (code 301) and costs nothing. Every call accepts "test_mode": true for a free sample.