E-Way Bill Changes from 1 August 2026: Mandatory Ship-To GSTIN and Voluntary Closure

Two changes to the e-Way Bill system that were originally due to roll out in June 2026 have been pushed back and are now set to take effect from 1 August 2026. GSTN confirmed the revised timeline through Advisory No. 663 (9 June 2026) and followed up with Advisory No. 664 (17 June 2026) and an FAQ set on 2 July 2026 to help businesses prepare. If you generate e-Way Bills through the IRN (e-invoice) API, both changes will directly affect your billing and logistics workflow.

Change 1: Ship-To GSTIN becomes mandatory in Bill-To/Ship-To transactions

Where an e-Way Bill is generated through the IRN API and the transaction involves a Bill-To/Ship-To structure – that is, the party being billed is different from the location goods are actually shipped to – the Ship-To GSTIN field will become mandatory from 1 August 2026.

The requirement applies only when the shipping destination differs from the billing party; if the billing and shipping addresses are the same, there is no additional field to fill.
Where goods are delivered to an unregistered person or location, businesses must enter URP (Unregistered Person) in the Ship-To GSTIN field rather than leaving it blank.
This is aimed at closing a long-standing gap where the actual delivery point on a multi-party transaction wasn’t captured on the e-Way Bill, which made verification harder for field officers and reconciliation harder for businesses with drop-shipping or third-party billing arrangements.

Change 2: Voluntary closure of e-Way Bills after delivery

GSTN is also rolling out a facility to formally close an e-Way Bill once goods have reached their destination. Key points to know:

The supplier, recipient, transporter, or driver associated with the e-Way Bill can mark it closed after delivery.
Closure must be done on the same day as delivery, or at the latest, the immediately succeeding day.
For now, this is voluntary – there is no penalty for not closing an e-Way Bill after goods are delivered. It exists primarily to give businesses (and the department) a cleaner record of completed movements rather than a permanently active e-Way Bill sitting on the portal.

Why the original June 2026 date was postponed

Trade bodies, GST Suvidha Providers (GSPs), and ERP vendors asked GSTN for more time, citing the need for system changes, API integration and testing, and updates to master data (particularly Ship-To party records) before the mandatory field could go live without disrupting invoicing. GSTN accepted those representations and pushed the effective date to 1 August 2026, giving businesses roughly seven additional weeks.

What to check before 1 August

Confirm your ERP or billing software has been updated to capture and transmit the Ship-To GSTIN field on IRN-based e-Way Bill generation.
Audit your master data for Ship-To parties – incomplete or outdated GSTIN records for delivery locations will cause failures once the field is mandatory.
Brief your logistics and dispatch teams on the URP convention for unregistered delivery points so shipments aren’t held up over a data-entry gap.
Decide internally who is responsible for closing e-Way Bills post-delivery if you choose to use the voluntary closure facility, and build it into your dispatch reconciliation process.

Our recommendation

Even though the deadline has moved, the underlying system change has not – treat 1 August 2026 as fixed rather than assuming a further extension. Businesses with multi-party billing (common in distribution, e-commerce fulfilment, and job-work arrangements) should test their Ship-To GSTIN data now rather than in the last week of July. If you would like us to review your e-Way Bill workflow and master data readiness ahead of the change, get in touch with us.