Consolidated E-Way Bill (Form EWB-02) Explained

A consolidated e-way bill is a single document, generated in Form GST EWB-02, that lists the e-way bill numbers of several consignments being carried in one vehicle. It exists so the driver carries one reference instead of a fistful of separate bills, and it is created by the transporter before the movement starts. The thing to understand before anything else: EWB-02 is a carrier document. It does not merge the consignments, it does not create a new validity period, and each underlying EWB-01 continues to live and expire entirely on its own terms.

What a consolidated e-way bill is

Rule 138(6) of the CGST Rules deals with the ordinary situation where one lorry carries goods for several different invoices, often for several different consignees. Each of those consignments has already been covered by an e-way bill in Form GST EWB-01, generated under the normal rules. What Rule 138(6) permits is for the transporter to indicate the serial numbers of those e-way bills on the common portal and generate a consolidated e-way bill in Form GST EWB-02, before the goods move.

The clearest mental model is a trip sheet. The consolidated bill answers one question — "what is on this vehicle for this trip?" — and answers it by pointing at other documents rather than by restating their contents. It carries the conveyance details and a list of e-way bill numbers. It does not carry consignment values, HSN codes, or party details of its own, because those already sit on the individual bills it references.

That distinction matters for compliance. A consolidated e-way bill is not a shortcut past the ordinary e-way bill rules and thresholds. If a consignment on the vehicle needed an EWB-01, it needed one whether or not a trip sheet was later generated on top.

When EWB-02 is worth generating

Generating a consolidated e-way bill is optional. Rule 138(6) says a consolidated bill may be generated, not that it must be. Whether it earns its keep depends on the shape of the movement:

• Multi-drop road transport. A goods transport agency picks up from several consignors, or drops at several consignees, on one route. This is the case the rule was written for and the case where the trip sheet genuinely reduces friction at a check post.
• Hub-and-spoke line hauls. Goods aggregated at a transporter's hub and moved on a single long-distance vehicle to a downstream hub, then broken up again. The consolidated bill describes the long-haul leg.
• Own-fleet distribution runs. A distributor loading fifteen invoices for fifteen retailers into one owned vehicle. There is no third-party transporter involved at all, but the consolidation still makes the paperwork carried by the driver manageable.

Where it adds nothing is a single-consignment movement, or two consignments going to the same consignee on the same invoice date. In those cases you are creating an extra document and an extra thing to keep in sync for no benefit.

Who can generate a consolidated e-way bill

The text of Rule 138(6) puts the action with the transporter, which reflects the normal commercial reality: the transporter is the party who knows which consignments are actually on which vehicle. A transporter enrolled on the e-way bill portal — including an unregistered transporter operating with a Transporter ID — can generate EWB-02 for consignments assigned to them.

In practice, the portal also allows a registered person to generate a consolidated bill when they are moving multiple consignments in their own conveyance and hold the relevant e-way bill numbers. That is the own-fleet case above. The functional requirement is simple: whoever generates it must have a portal login and must have the individual e-way bill numbers to enter.

What EWB-02 actually contains

The form is short by design. Broadly, it captures the conveyance and the list of consignments, and nothing else.

Because Part B — the conveyance details — is what starts the validity clock on an individual e-way bill, treat filling Part B on the underlying bills as the safe default rather than assuming the vehicle number on the trip sheet substitutes for it. Portal behaviour around Part B and consolidation has been adjusted over the years; if your process depends on generating EWB-02 over bills that have only Part A, confirm the current behaviour against the portal user manual on ewaybillgst.gov.in before you rely on it.

Validity: the part people get wrong

This is the single most common misunderstanding about EWB-02, and it is worth stating flatly: the consolidated e-way bill has no validity period. It is not valid for a day, or for the longest of the bills it contains, or for anything else. Validity attaches only to the individual EWB-01s, each of which was issued with a period derived from the approximate distance declared for that consignment under Rule 138(10).

The practical consequence is that a single vehicle can be carrying bills with different expiry moments. A consignment dropping 150 km down the route and a consignment continuing 700 km beyond it were issued different numbers of days, and they run out at different times. The trip sheet does not harmonise them. The mechanics of how those days are counted — including why "one day" ends at midnight rather than after a full 24 hours, and the narrow eight-hour-either-side window for extending a bill — are covered in detail in our guide to e-way bill validity and distance.

Transhipment, vehicle change and regeneration

A consolidated e-way bill is bound to one conveyance. The moment the goods move to a different vehicle — a breakdown, a scheduled hub transfer, a change from a line-haul truck to a local delivery vehicle — the trip sheet stops describing what is actually happening on the road.

The fix is regeneration rather than amendment. The portal provides a regenerate option that produces a fresh consolidated e-way bill against the new vehicle number for the consignments continuing on that leg. What does not change is the underlying e-way bill numbers: those stay the same, keep the same validity, and are simply now referenced by a new trip sheet. A few points that follow from that:

1. Regeneration is not a validity reset. A consignment that had six hours left before the transhipment has six hours left after it. Moving to a new vehicle buys nothing.
2. Partial unloading is normal. If half the consignments are delivered at the hub and half continue, the regenerated sheet should list only what is still on board. Carrying delivered consignments on the sheet is a self-inflicted discrepancy at the next check.
3. Part B on individual bills still needs attention. Where the transporter is responsible for updating conveyance details on an individual bill after a vehicle change, that update is a separate action from regenerating the consolidated bill. Doing one is not doing the other.
4. Multimodal legs need care. A consolidated bill is generated for a mode of transport. A road leg followed by a rail leg is two different conveyances, and the documentation should reflect that rather than stretching one sheet across both.

Where transporters get caught out

Almost every problem with consolidated e-way bills traces back to the sheet and the reality diverging. The recurring ones:

• Generating the sheet after the vehicle has left. Rule 138(6) contemplates the consolidated bill being generated prior to the movement of goods. A sheet created retrospectively because a check post is ahead is a poor position to be in.
• Consignments on the sheet that are not on the vehicle. Usually a loading plan that changed after the sheet was generated. It reads as a discrepancy between documents and goods, which is exactly what roadside verification is designed to find.
• Consignments on the vehicle that are not on the sheet. Worse, because the natural inference is that the missing consignment has no e-way bill at all.
• Assuming the sheet extends a stale bill. Covered above, but it is common enough to repeat: an expired EWB-01 inside a freshly generated EWB-02 is still an expired EWB-01, with the full Section 129 detention and penalty exposure that carries.
• Wrong state or dispatch place on the sheet. Easy to fumble when a transporter operates across branches. The state codes used on GST documents are listed in our GST state code reference if you need to sanity-check one.

None of these are exotic. They are all versions of the same operational discipline problem — the sheet is generated once, the load changes, and nobody regenerates. If your dispatch process has a step where the loading plan can change after documentation, that step needs a corresponding regeneration step next to it.

Checking the GSTINs behind the underlying bills

A consolidated e-way bill inherits the quality of the bills it references, and those bills carry consignor and consignee GSTINs. Two things are worth checking on the parties, ideally before the consignment is documented rather than after:

• Is the counterparty's registration active? A cancelled or suspended GSTIN on a consignment is a problem for the invoice and the input tax credit behind it, quite apart from the movement. Our note on what a suspended GSTIN status means covers what the different portal statuses actually imply.
• Does the GSTIN belong to the party you think it does? Legal name and trade name on the registration should match the party on the invoice. Mismatches here are one of the standard signals in checking whether a GST number is genuine.

For a transporter or a distributor with a large counterparty base, doing this one GSTIN at a time on the portal does not scale. A verification API lets you check a GSTIN as part of the flow that creates the consignment record, and the same call can be run over an existing master in a batch — the approach is described in our guide to bulk GSTIN verification.

To be explicit about scope: this is a verification API, not a GSP integration. It tells you whether a GSTIN is valid and what the portal holds against it. It does not generate e-way bills, consolidated or otherwise — that happens on the e-way bill portal or through a GSP. The honest connection between the two is upstream: good counterparty data going into EWB-01 means fewer defects to discover when EWB-02 is checked at the roadside.

Frequently asked questions