Consolidated E-Way Bill (EWB-02) for Multi-Consignment Vehicles

A part-load truck leaves a transporter's Bhiwandi branch at 22:10 with nine consignments from five shippers. The driver carries one consolidated e-way bill, the branch believes the paperwork is complete, and at 03:15 a mobile squad near the Gujarat border finds that three of the nine underlying bills expired at midnight. The trip sheet itself was valid. The goods it listed were not.

That gap between a consolidated bill and the bills inside it is where most transporter losses on Form GST EWB-02 begin. Once the branch treats the consolidated e-way bill as a trip sheet that inherits nothing, and checks every constituent bill's own expiry against the truck's arrival time, detention for expired bills on a groupage vehicle becomes a scheduling error caught at the dock rather than a penalty paid at the roadside.

• What this guide covers: the text of CGST Rule 138(6) and (7), which bills the portal accepts into a consolidated bill, validity, vehicle changes, partial unloading and the Section 129 exposure when a constituent bill lapses.
• What it adds: a timed branch incident, the portal's consolidation payload, a rupee penalty calculation with a US contrast, and a rollout checklist for depot staff.

Form EWB-02 is a trip sheet, not a new e-way bill for the goods

A consolidated e-way bill groups existing e-way bills that are travelling in one conveyance; it creates no new tax document for the goods. Each consignment still needs its own valid e-way bill in Form GST EWB-01, and the consolidated bill only lists those numbers against one vehicle.

CGST Rule 138(6) says that after e-way bills are generated under sub-rule (1), where multiple consignments are intended to be transported in one conveyance, the transporter may indicate the serial numbers of those bills on the common portal and a consolidated e-way bill in Form GST EWB-02 may be generated before the goods move. The verb is "may" in both places. The e-way bill portal's own FAQ calls the consolidated bill a document like a trip sheet.

Consolidated e-way bill practice under CGST Rule 138(6) lets a transporter list many Form EWB-01 bills against one vehicle on the NIC e-way bill system, but every listed bill keeps its own validity, so a branch should release a groupage truck only when each bill outlasts the planned arrival by at least 4 hours.

The portal FAQ also answers the common question about multiple invoices between the same two parties: each invoice needs its own e-way bill, invoices cannot be clubbed into one bill, and a consolidated bill can be prepared afterwards if the goods travel in one vehicle. That is the correct order of work. Consolidation comes last, after every invoice or delivery challan has a complete bill.

Our page on the e-way bill vehicle change workflow deals with a single bill whose truck breaks down or is swapped. This article covers the branch case, where many bills share one truck, are loaded together, and may be split, dropped or moved to another vehicle as a group.

Optional consolidation versus the transporter's duty in sub-rule (7)

No rule forces a transporter to generate Form EWB-02. What the rules do force, in one situation, is generation of the underlying bills by the transporter when the shippers have not done it.

Rule 138(7) applies where neither consignor nor consignee has generated an e-way bill and the aggregate consignment value of goods carried in the conveyance exceeds fifty thousand rupees. For inter-State supply, except by railways, air or vessel, the transporter must then generate the e-way bill in Form EWB-01 on the basis of the invoice, bill of supply or delivery challan, and may also generate a consolidated bill before movement. The trigger is the aggregate value on the vehicle, not the value of one parcel.

Which e-way bills the portal lets into a consolidated trip sheet

The portal accepts a bill into a consolidated e-way bill only when three conditions hold: the person consolidating generated it or is its assigned transporter, the bill is active, and its validity has not expired. Branch software should apply the same three tests before the clerk presses submit.

The NIC API documentation for the consolidation call, action GENCEWB, lists those validations. It adds that for road movement the vehicle number is required and the transport document number is optional, while for rail, air or ship the transport document number is mandatory. Since 1 January 2025 the API also limits generation of e-way bills to documents dated within 180 days and blocks extension beyond 360 days from generation.

• Ownership test: a bill generated by a shipper and assigned to another transporter's ID is refused; the branch must first get the assignment under Rule 138(5A).
• Status test: a bill cancelled within its 24-hour cancellation window under Rule 138(9) cannot be consolidated, even if the printout is still in the docket.
• Validity test: an expired bill is refused outright; the clerk must extend it first if the extension window is still open.
• One transporter per sheet: because of the ownership test, a sheet cannot mix bills held by different transporters, so a truck shared by two transporters needs two sheets or a re-assignment.

The request body is short. The branch sends the place and State the truck starts from, the mode, the vehicle number and the list of twelve-digit bill numbers; the response returns a consolidated bill number and timestamp. The listing below uses the field names from the NIC version 1.03 documentation, with this article's illustrative values, and a pre-release check the branch can compute for each listed bill.

// GENCEWB "data" element (decrypted form), NIC e-way bill API v1.03
{
  "fromPlace": "BHIWANDI",
  "fromState": 27,
  "vehicleNo": "MH04KU7319",
  "transMode": "1",
  "transDocNo": "BHW-LR-55817",
  "transDocDate": "13/11/2026",
  "tripSheetEwbBills": [
    { "ewbNo": 271012844310 },
    { "ewbNo": 271012844587 },
    { "ewbNo": 241009377125 }
  ]
}
// success response "data": { "cEwbNo": "<10-digit number>", "cEWBDate": "dd/mm/yyyy hh:mm:ss AM" }

// Branch release check, run for every listed bill i
// H_i = hours from planned departure to the bill's expiry (expiry = 23:59 on its last valid day)
// T_i = planned driving hours to the point where bill i is unloaded
// B   = buffer hours (this article uses 4)
release_ok  =  for all i:  H_i >= T_i + B
extend_flag =  any i where  H_i < T_i + B   and  expiry_i - now <= 8 h

Validity stays with each constituent bill, not with the trip sheet

A consolidated e-way bill has no validity period of its own. Each listed consignment must reach its destination within the validity of its own bill, which was fixed when Part B was first entered.

Rule 138(10) gives one day for the first 200 km and one more day for every further 200 km or part of it, for cargo other than over-dimensional cargo; over-dimensional cargo gets one day per 20 km. The Explanation counts validity from the time of generation, with each day expiring at midnight of the day after the generation date. The portal FAQ adds that validity starts from the first Part B entry and is not recalculated when Part B is later updated.

E-way bill validity under CGST Rule 138(10) runs one day per 200 km from the first Part B entry and expires at midnight, so a bill generated at 11:00 on 10 November for 420 km lapses at 23:59 on 13 November even if a consolidated EWB-02 listing it was created hours earlier.

The arithmetic matters because a groupage branch holds freight. A consignment that left a Nashik shipper two days ago has used two of its days in transit and storage before it reaches the hub, while a parcel picked up locally this afternoon has its full validity. The same truck therefore carries bills with very different remaining hours, and the consolidated bill hides that spread unless the branch system shows it.

Extension is the control that saves such a load. The portal FAQ says the extension option is available from eight hours before to eight hours after expiry, that only the transporter carrying the goods when validity expires can extend, and that the new validity is based on the remaining distance. The NIC master code list gives the reasons: natural calamity, law and order, transshipment, accident and others. Our guide to e-way bill validity extension walks through that procedure step by step.

Vehicle changes at a branch: regenerating instead of editing

When the truck carrying a consolidated load changes, the branch regenerates the consolidated bill with the new vehicle number; it does not edit Part B of each listed bill one at a time. Regeneration produces a new consolidated number and the old one becomes invalid for use.

The portal FAQ describes a "regenerate CEWB" option under the consolidated EWB menu that changes the vehicle number without changing the individual bills, and the API action REGENTRIPSHEET does the same with a reason code from the master list: breakdown, transshipment, others or first time. The documentation states that only the generator of the consolidated bill or the current transporter can regenerate it, and that only active, unexpired bills are carried into the new sheet.

• Breakdown on the highway: regenerate with reason code 1 before the relief truck moves; the driver of the relief vehicle must carry the new sheet, not the old printout.
• Transshipment at a hub: use code 2 when the whole sheet moves to the next linehaul vehicle; if only some bills move, build a fresh sheet for those bills instead.
• Silent drop of bills: regeneration quietly excludes bills that have expired since the original sheet, so the branch must compare the old and new bill lists after every regeneration.

The other route is the Part B update on each bill. The FAQ notes that Part B can be updated as many times as needed within validity, and that a transporter moving goods through several branches can either update the vehicle on each bill or generate a consolidated bill at each branch for the bills leaving together. Our e-way bill API integration guide covers single-bill updates through the VEHEWB call and the authentication they need.

Drop-offs en route, partial unloads and splitting one load in two

One consolidated bill can cover consignments for several destinations, and the transporter may deliver some on the way and continue with the rest under the same sheet. A single consignment split across several vehicles is a different case and uses the multi-vehicle facility, not consolidation.

The portal FAQ gives the example of ten bills on one sheet, three for destination Y and seven for destination X: the truck may deliver the three at Y and continue to X with the same sheet, or the branch may generate two sheets at the start. Two sheets are easier for a roadside officer to read after the first drop, because the remaining sheet then lists only the goods still on board.

The last row is the one depots forget. The FAQ states that goods stored in the transporter's godown before delivery, even one located in the recipient's own town, must always be covered by a valid e-way bill. Storage is part of the movement, so a bill that lapses on a godown shelf is as exposed as one that lapses on the highway.

Branch hub trace: three bills that lapsed under a valid trip sheet

The failure below is illustrative but built from the portal's own rules. Nothing in it required a system error; every step was allowed, and the loss came from comparing the consolidated sheet's timestamp with the truck's arrival instead of each bill's expiry.

1. 10 Nov, 11:00, Nashik: a shipper generates bills 2710 1284 4310, 4587 and 4612 for three invoices to Ahmedabad, 420 km, with the transporter's ID and a pickup vehicle in Part B. Validity: three days, ending 23:59 on 13 November.
2. 10 Nov, 19:30, Bhiwandi hub: the parcels arrive and wait for a full Gujarat load. The branch system shows them as "in godown" with no expiry column.
3. 13 Nov, 21:52, Bhiwandi hub: the clerk generates a consolidated bill for nine bills on vehicle MH04KU7319 under transport document BHW-LR-55817. The portal accepts all nine because all are still within validity.
4. 13 Nov, 22:10, departure: the truck leaves. Planned arrival at the Ahmedabad branch is 08:30 on 14 November. Three bills lapse at midnight, with the extension window open until 08:00; nobody is assigned to watch it.
5. 14 Nov, 03:15, roadside check: a mobile squad verifies the sheet, finds three expired bills and detains the goods and conveyance under Section 129. The other six consignments sit with the detained truck until release.

The controlled version of the same night differs in one rule. At 21:52 the branch system computes hours to expiry for each bill against the 10.3-hour drive plus a 4-hour buffer, flags three bills, and the clerk extends them with reason "transshipment" from the hub before generating the sheet. The truck leaves at 22:20 instead of 22:10.

Detention exposure under Section 129, worked in rupees and dollars

Goods moving with an expired bill are moving in contravention of the rules, so Section 129 detention applies to those goods and to the conveyance. The penalty is calculated per consignment on the tax payable, which makes even three small bills on a groupage truck expensive.

Section 129(1)(a), as substituted from 1 January 2022, releases taxable goods on payment of a penalty equal to two hundred per cent of the tax payable where the owner comes forward. Under clause (b), where the owner does not come forward, the penalty is the higher of fifty per cent of the value of the goods or two hundred per cent of the tax. Section 129(6) lets the conveyance go on payment by the transporter of the penalty or one lakh rupees, whichever is less.

The tax rate, values, dollar figures and truck cost are assumptions chosen to show the arithmetic, not rates for any particular commodity. The structure is the point: clause (a) is driven by the tax on each lapsed consignment, clause (b) by its value, and neither depends on how valid the consolidated sheet looked. Our separate guide to the Section 129 e-way bill penalty explains notices, timelines and appeals after detention.

Section 129(1)(a) of the CGST Act sets detention release for taxable goods at 200% of tax payable when the owner comes forward, so three lapsed constituent bills carrying ₹1,55,700 of IGST on one groupage truck expose shippers to ₹3,11,400, while the consolidated EWB-02 offers no defence.

Who prepares, checks and signs off each document on the truck

A groupage load involves at least three parties who can touch the same bill, so the branch must decide in writing who generates, who checks and who may extend or regenerate. The rules already limit some of these actions to particular people.

Responsibility also has to cover the checks themselves. The checks that decide whether a truck may leave should be hard rules computed from portal data. Prediction and document-reading tools can help the clerk find information faster, but a person confirms every result they produce.

The software estimate of drive time is useful only because it feeds a fixed release check. If the estimate is allowed to override the buffer, the branch is back to judging validity by eye, which is how three bills lapsed in the trace.

A depot rollout checklist for consolidated e-way bill generation

A branch can adopt consolidated bills in about two weeks if it fixes data first and generation second. The checklist below is ordered so that each item depends only on the ones above it.

Two portal changes are worth watching while the rollout runs. The NIC API announcements page, updated on 30 July 2026, says the proposed e-way bill closure function and mandatory ship-to GSTIN have been kept on hold; if either is reintroduced, branch software that builds sheets will need testing again before go-live.

For the network question of where consolidation should happen at all, our comparison of hub-and-spoke versus point-to-point routing shows how storage days at hubs grow, and those days are exactly what consume e-way bill validity. More India transport guides sit in the logistics and supply chain hub. If you are specifying a branch system that enforces these release checks against the NIC API, you can send us your requirements.