E-way bills: when you need one, and how to stop generating them by hand

An e-way bill is an electronic document required for the movement of goods above a specified consignment value. It carries the details of the goods, the consignor and consignee, and the transporter, and it has a limited validity tied to the distance being covered.

The practical rules

• Generated before the movement of goods begins, not after.
• Required above the notified consignment value — the interstate threshold and intrastate thresholds can differ by state.
• Validity is distance-based and expires; an expired e-way bill in transit is a problem at the checkpost.
• Part-A carries the invoice and goods details; Part-B carries the vehicle number and can be updated as the vehicle changes.
• Cancellation is time-limited if the consignment does not move.

Why manual generation goes wrong

The common failure is re-keying. Someone raises the invoice in the billing system, then opens the e-way bill portal and types the same details again. Any divergence between the two documents — a quantity, a value, an HSN code, a GSTIN — becomes a discrepancy that surfaces during transit or at reconciliation.

Generating the e-way bill directly from the invoice removes the second entry entirely. The document that moves with the goods is derived from the document that was billed, so they cannot disagree.

Handling vehicle changes and multi-leg movement

Goods rarely travel on one vehicle from door to door. Part-B updates let you record a change of conveyance mid-journey without regenerating the whole document. Keep the transporter ID on file against the party so this is a two-click update rather than a data-entry exercise.

Pair it with e-invoicing

If your turnover has crossed the e-invoicing threshold, the invoice registration and the e-way bill can be handled in a single flow — the IRN and the e-way bill generated together from one billing action. That is the configuration to aim for.