E-Way Bill & E-Invoice API Changes: Ship-to GSTIN Now Mandatory

Auto-drafted from official sources and under review by CA Rajeev Ranjan. Verify against the original notification before you act.

What Has Changed

GSTN issued an advisory on 09 June 2026 announcing two specific updates to e-Way Bill and e-Invoice systems:

1. Mandatory 'Ship-to GSTIN' field, When the delivery address belongs to a registered GST taxpayer, the Ship-to GSTIN must now be explicitly captured in the e-Way Bill. This field was previously optional or inconsistently filled.
2. Voluntary closure of e-Way Bills via API, Businesses can now close (cancel or finalise) e-Way Bills programmatically through both the e-Invoice API and the e-Way Bill API, rather than only through the portal interface.

The implementation is being rolled out in phases, and the original timeline has been extended, the advisory does not specify the exact revised go-live dates, so refer to the official GSTN notification for the current schedule.

Who Is Affected

These changes apply to:

• Businesses generating e-Way Bills where goods are shipped to a location registered under a different GSTIN (for example, stock transfers to a branch, third-party warehouse deliveries, or bill-to/ship-to transactions).
• ERP vendors, GSP/ASP providers, and tech teams who integrate with the e-Invoice or e-Way Bill APIs on behalf of clients.
• Large taxpayers and logistics-heavy sectors (manufacturing, distribution, e-commerce) who generate high volumes of e-Way Bills programmatically.

If your business uses manual portal generation only and your ship-to party is unregistered, the immediate operational impact may be limited, but you should still verify your transaction types.

What You Should Do

For businesses and finance teams:

• Audit your current e-Way Bill templates and master data to check whether the Ship-to GSTIN field is being populated wherever applicable.
• Update your ERP or billing system configuration to make this field mandatory in relevant transaction types.
• Train your accounts and dispatch teams on when a Ship-to GSTIN is required.

For IT and integration teams:

• Review the updated API specifications on the GSTN portal to incorporate the Ship-to GSTIN field correctly in your payload.
• Test the voluntary e-Way Bill closure workflow in the sandbox environment before the phased go-live.
• Coordinate with your GSP/ASP for updated API credentials or schema changes if applicable.

Timing

The rollout is phased. The advisory was issued on 09 June 2026, with the original deadline already extended once. Do not assume you have unlimited time, check the official GSTN advisory page for the current phase dates and act accordingly.

Getting this right early avoids e-Way Bill mismatches, potential detention of goods in transit, and reconciliation issues between your e-Invoice and e-Way Bill data.

Source: Official notification