E-way bills in India: an ERP and dispatch readiness guide

An e-way bill supports the movement of goods; a useful ERP-to-dispatch process links the business document, goods, delivery details, transporter and valid movement record before release. Start by deciding whether the movement requires an e-way bill, then verify the generated record and its validity. The official NIC FAQ explains the portal process and important exceptions.

Sources checked: 3 November 2026.

When should a business check whether an e-way bill is needed?

The NIC e-way bill FAQ says an e-way bill must accompany goods when the value is more than ₹50,000, and that specified handicraft and job-work movements need one even below that value. Intra-state provisions can differ. Have the GST adviser document the applicable rule for each recurring movement instead of using the threshold as the only decision.

Build a movement register covering customer deliveries, inter-branch transfers, returns, job work and other actual business flows. For each flow, specify the document used, who causes the movement, who generates the e-way bill where required, which state provisions were checked and who authorizes an exception. A recorded decision helps warehouse staff act consistently without interpreting tax rules at the loading bay.

What data should be ready before goods are released?

Reconcile the source document number and date, supplier and recipient, dispatch and delivery locations, goods and values, applicable classifications, transport mode and available transporter/vehicle details. Separate the party being billed from the place receiving the goods when the transaction calls for it. Ask operations to verify the actual loading and delivery addresses against the order.

Use a clear handover between finance, sales and dispatch. Finance approves the source document, the warehouse confirms the goods to be moved, and the assigned transport operator supplies the movement information. Keep a named owner for last-minute vehicle changes and failed portal requests. An incomplete record should remain an exception with a visible reason rather than appearing in the same queue as dispatch-ready goods.

How should validity and older documents be controlled?

The updated NIC FAQ gives regular movement validity as one day per 200 km or part thereof and describes the separate 20 km treatment for over-dimensional cargo. Use the portal’s displayed expiry for the actual movement and check the applicable mode-specific rules. Do not reuse old 100 km guidance.

Check the current NIC advisories for any limit on the age of the base document and on extensions, and keep those checks separate from the bill’s ordinary validity. Build distinct checks for document age, the current bill’s expiry and any permitted extension.

Assign a queue owner to review departures and goods still in transit. Agree an escalation before a bill expires, with the transporter’s current location and the remaining journey available. Do not assume that changing the vehicle creates a fresh validity period. Exceptional movement issues need the applicable portal procedure and authorized review.

Are the proposed 2026 Ship-to and closure features mandatory now?

The NIC API release notes updated 30 July 2026 say that the proposed mandatory Ship-to GSTIN and voluntary EWB Closure changes were kept on hold; the May changes are marked withdrawn. Do not describe the earlier proposed rollout date as a current mandate. Check for a subsequent advisory when configuring or publishing this guide.

Keep delivery evidence in the operational workflow even when a proposed government portal feature is on hold. A proof of delivery, a customer dispute and a cancelled dispatch are different events. Record who may close the internal shipment and how an unresolved discrepancy is handed to finance. Internal status names should make their meaning clear to users.

How should the ERP handle failures and changes in transit?

Demonstrate the difference between a rejected generation request, an uncertain timeout and a confirmed e-way bill. Operators need to find the existing result before starting another attempt. Capture the provider response and the business record it belongs to; protect credentials and restrict access to sensitive movement information.

Agree an exception checklist for a changed transporter, an incorrect source detail, delayed goods, a return and an outage. For every case, name the decision maker and the evidence retained. Do not promise that every field can be edited after generation. Have the implementation team show the permitted route in the selected provider and business process.

What should the acceptance session demonstrate?

Use an agreed test environment and approved sample scenarios. Cover an ordinary delivery, a separate bill-to and delivery address, a return or transfer, an invalid master value, a missing transport detail and a recovery from an uncertain response. Include the real modes and states in which the business operates. Production submissions require separate authorization.

Have warehouse users perform the handover themselves while finance checks the source-document match. Record expected versus observed outcomes, defects, permissions and approval. The handover should include monitoring, support contact ownership, a manual contingency approved by the business and reconciliation of the first dispatches after go-live.

What questions should dispatch teams ask?

Does getting an IRN automatically complete dispatch compliance?

Treat invoice registration and the movement checks as separate acceptance points. Verify whether the required e-way bill was generated, whether its details match and whether it is valid for the actual movement.

Can several invoices simply be treated as one movement record?

Ask the operator to demonstrate the correct individual and consolidated-record handling for the real shipment. The official FAQ describes one e-way bill per invoice and a consolidated record for multiple bills travelling in one vehicle.

Should a dispatch team rely on an expired bill?

Do not release movement on an expired record. Escalate to the authorized operator to assess the permitted procedure for the specific circumstances before movement continues.

Use GST e-invoicing alongside inventory management and ERP software for India when defining the invoice-to-dispatch demonstration. Confirm the supported integration scope in writing.