The movement document behind goods in transit under GST — when it is needed, how long it lasts, and who has to raise it.
An e-way bill is an electronic document required for the movement of goods above a prescribed consignment value. It carries the consignment, transporter and vehicle details and produces a unique e-way bill number. Validity is calculated from the distance to be covered, and goods moving without a valid bill where one is required are liable to detention and penalty.
E-way bills are an operational problem rather than an accounting one. They are raised at despatch, under time pressure, often by warehouse staff rather than finance — and a vehicle cannot leave without one. Businesses that generate them on a separate portal rather than from the despatch transaction tend to discover the cost in loading-bay delays.
Based on consignment value, whether movement is inter- or intra-state, and the applicable state rules.
Supplier, recipient, invoice reference, HSN, value, transporter ID and vehicle number.
From the ERP through the API, or on the portal. Where e-invoicing is already in place much of the data can carry across.
The e-way bill number must accompany the goods and be producible on demand during transit.
Vehicle changes are updated against the same bill. Validity can be extended in defined circumstances rather than re-raised.
A consignment moves roughly 1,400 kilometres across four states. The e-way bill is generated on a Friday afternoon as the vehicle loads, and validity is calculated from the distance.
The journey then meets ordinary reality: a driver rest period, a weekend, and half a day lost at a state border. The vehicle arrives after the bill has expired. The goods are correct, the invoice is correct, the tax is correct — and the documentation covering the movement is not valid, which is the thing that gets checked.
Two habits prevent this. Generate Part B as close to actual departure as possible rather than at the start of loading, since validity runs from generation and loading can take hours. And monitor validity against progress, so an extension is requested while the vehicle is still moving rather than after it has stopped. For long hauls, build the rest periods into the expected transit time when deciding whether the validity you have been given is realistic — the distance calculation does not know about weekends.
| Term | What it means |
|---|---|
| Part A | The consignment details — parties, value, HSN, document reference. Generated by the person causing the movement. |
| Part B | The vehicle details. Without Part B the bill is incomplete and the movement is not covered. |
| Validity | The period the bill remains valid, calculated from distance. It expires, and an expired bill in transit is a problem. |
| Consolidated e-way bill | One document covering multiple consignments in a single vehicle, for the transporter's convenience. |
| Transporter ID | The identifier used when the transporter, rather than the consignor, will complete Part B. |
An e-way bill raised while the lorry waits is where data errors enter. Generate it from the despatch transaction.
Validity is distance-based. Underestimating the route leaves goods in transit on an expired bill.
If the vehicle changes mid-journey and the bill is not updated, the consignment is effectively travelling undocumented.
Intra-state thresholds and exemptions vary. Confirm the rules for each state you despatch within.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Expired bills in transit | Whether validity is being tracked against actual progress rather than assumed. | Counting only bills that were checked, which is a fraction of those that expired. |
| Part B completion lag | Hours between generating Part A and recording the vehicle. Long lags mean goods may move uncovered. | Averaging; the outliers are the risk, not the mean. |
| Invoice-to-bill mismatches | Value, HSN or party differences between the invoice and the movement document. | Comparing totals only, where offsetting line errors cancel out. |
| Detention events | Delays at checkpoints, which are the downstream cost of all of the above. | Recording the delay without the reason, which makes the pattern invisible. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.