Consolidated E-Way Bill for the Vehicle, Not the Consignment
A single truck leaves the depot carrying eleven consignments for six customers. Each has its own bill. The driver needs one document that says what is on that vehicle for that movement. KO Fleetz builds it from the manifest you already assembled to load the truck.
Part loads are the norm, and the paperwork was designed for full ones
Look at how a real fleet loads. Full loads and part loads sit side by side on the same board, and the part loads are what pay for the empty leg home. So a 20-footer runs out with a stack of consignments that were booked separately, by different clerks, for customers who have never heard of each other. Every one of them generated its own bill.
The driver cannot carry a stack. He needs the one document that describes this vehicle on this movement, and somebody in the office has to build it by collecting bill numbers off a screen and pasting them into a portal form. They do this while the truck is loaded, running, and the gate is waiting. It is the least forgiving moment in the day to be doing careful clerical work.
The list they are assembling already exists, incidentally. It is the manifest. Somebody wrote down what goes on that vehicle for that trip in order to load it in the first place. The office builds the same list twice because the loading list and the compliance list live in different places and nobody ever connected them.
The manifest is the list. Use it.
A manifest has the same shape as a consolidated bill: one vehicle, one movement, a defined set of consignments. In KO Fleetz the manifest is built when the truck is loaded, each line on it carries its LR, and each LR carries its bill. The Consolidated EWB screen assembles from that. The office is not collecting numbers; it is confirming a list somebody already made for a physical reason.
There is a second entry point that matters more than transporters expect. Fetch Transporter Ewaybills pulls in bills that a supplier raised naming your GSTIN as the transporter. You did not create those documents and you may not know they exist, yet your vehicle is the one carrying the goods and your driver is the one at the check post. Fetching them puts documents you are responsible for into a list you can actually see, and from there they can be grouped onto the trip like any other.
The module deliberately does not decide which bills belong on which vehicle. That is a loading decision made by a person in a yard, and it is recorded in the manifest by the person who made it. Nor does it interpret the rules on what a consolidated document must contain or when one is needed — that is your finance function's call, not a dropdown's. KO Fleetz assembles from your loading reality and keeps the record. It does not pretend to know your goods better than you do.
Capabilities
What KO Fleetz consolidated e-way bill gives your team
Built from the manifest
The consignment list comes from the manifest built to load the vehicle, so the compliance document and the physical load describe the same truck.
Fetch Transporter Ewaybills
Bills raised by a supplier naming you as transporter are pulled in, so you can see documents you are answerable for but did not create.
Multi-consignment grouping
Eleven LRs for six customers on one vehicle become one trip document, with each underlying bill still reachable from its own consignment.
Vehicle and trip binding
The consolidated record is tied to the registration and the movement, not to a customer, which is the axis a driver and a check post care about.
Part load and full load handling
A full load with one bill and a part load with nine are the same operation here, because the manifest already knows which one it is looking at.
Transshipment splits
When a load breaks across two vehicles mid-route, each vehicle gets its own consolidated record against the consignments it actually took.
Transporter-of-record visibility
Fetched bills are listed against your GSTIN with their consignor, so a document assigned to you by somebody else is not a surprise at the gate.
One document per movement
The driver leaves with a single trip-level record instead of a folder, and the office can reproduce it from the manifest at any point afterwards.
How it works
How KO Fleetz does it
Step 1: Build the manifest as you load
The yard assembles the vehicle's consignments into a manifest — the list that already governs what physically goes on the truck. Each line carries its LR.
Step 2: Pull in the bills you did not raise
Fetch Transporter Ewaybills brings across documents where a supplier has named your GSTIN. These join the pool of bills available to attach to a movement.
Step 3: Assemble the consolidated record
The Consolidated EWB screen groups the individual bills sitting under the manifest against the vehicle and the trip. The office confirms rather than collects.
Step 4: Keep it attached to the trip
The consolidated record stays bound to the manifest and the vehicle, so a question three weeks later is answered from the trip rather than from a portal search.
Outcomes
What changes
- The loading list and the document list are the same
- One list
- Bills naming you as transporter stop being invisible
- Visible
- The record follows the movement, not the customer
- Per vehicle
- The trip can be reconstructed from the manifest
- Reproducible
Frequently asked questions
They describe the same thing from two angles. A manifest says what physically goes on a vehicle for a movement, and it exists because somebody has to load the truck. A consolidated bill says which documents that vehicle is carrying for the same movement. One vehicle, one journey, one set of consignments. In KO Fleetz the manifest is the source and the consolidated record is assembled from it, which is why the paperwork and the load cannot drift apart the way they do when two people build two lists.
Because a supplier can raise a bill and name your GSTIN as the transporter. From that moment the document is your operational problem — your vehicle, your driver, your check post conversation — even though it was created in an office you have never visited. Most transporters find out about these late or by accident. Fetch Transporter Ewaybills brings them into a list you can look at, which turns a document assigned to you into a document you are aware of before the truck leaves.
No. That decision belongs to the person in the yard looking at the goods, the vehicle and the day's commitments, and it involves things no software has access to — what actually fits, which customer will accept a late drop, which driver knows the address. The manifest records that decision. The consolidated record follows the manifest. We are automating the clerical consequence of the loading call, not the call itself.
This is a real case and it is handled by the manifest, not by an exception. Each vehicle ends up with its own manifest covering the consignments it actually carried, and each gets a consolidated record built from that. The individual bills underneath stay attached to their own consignments throughout. Updating the documents to reflect the new vehicles happens through the portal's own mechanisms, and the exchanges land in EWB Logs so the split is legible afterwards.
As many as the manifest carries — the module is not the constraint. The practical limits come from elsewhere: what the portal accepts, and what the vehicle can physically hold. Part load work in this country routinely puts a long list on one truck, and the module was built expecting that rather than treating it as an edge case. If your typical vehicle carries a large mixed load, that is the normal shape here, not a stress test.
No. The module assembles your consignments against your vehicle and submits what the portal asks for. It does not interpret requirements, advise on categories or tell you when a consolidated document is appropriate. Those are questions for your finance team and your consultant, and the answers move. What KO Fleetz guarantees is that the list going onto the document is the list that is actually on the truck, and that every exchange is recorded where you can read it later.
See a trip document built from a real manifest
Bring one part-load vehicle and its consignment list. We will assemble the grouping from the manifest and show you what fetching transporter bills surfaces.