Ship-to GSTIN Now Mandatory: Major Changes to e-Invoice and e-Way Bill APIs (Effective 1 August 2026)

What's Changed

On 17 June 2026, GSTN issued an important advisory introducing API-level changes to how e-Invoices and e-Way Bills (EWB) are generated. If your business uses ERP software, a GSP, ASP, or private IRP for GST compliance, this update directly affects you.

This advisory builds on an earlier one dated 20 May 2026, which first introduced the requirement for capturing Ship-to GSTIN. The latest advisory clarifies exactly how this works at the API level.

1. Ship-to GSTIN Is Now Conditionally Mandatory

Wherever Ship-to Legal Name and Address are provided and an e-Way Bill needs to be generated, Ship-to GSTIN must also be provided. If the consignee is unregistered, the value "URP" can be entered instead.

Here's where this applies:

• Generating IRN and EWB together — ShipDtls.Gstin is now conditionally mandatory
• Generating EWB later using IRN — New field Gstin added under ExpShipDtls, and it's mandatory
• Bill-to/Ship-to transactions — Ship-to GSTIN must be different from Bill-to GSTIN
• Export EWB — Ship details can be replaced
• B2B/SEZ transactions — Ship details entered at the IRN stage cannot be changed later

⚠️ Key rule: Entering the same GSTIN for both Bill-to and Ship-to will now be rejected by the system — Error code 2323.

New validation error codes (already live in Sandbox):

• Missing Ship-to GSTIN — Error 5002 / 5001
• Bill-to GSTIN same as Ship-to GSTIN — Error 2323
• State code mismatch — Error 2325 / 4074
• PIN code mismatch — Error 3039

2. A New Way to Close e-Way Bills

Once delivery is complete, businesses can now formally "close" an e-Way Bill — this is optional, not mandatory.

Who can close an EWB:

• The supplier
• The recipient
• The transporter
• The driver or an authorised person (via registered mobile number, through the portal)

How to close it:

• Through the portal: Log in and close EWBs individually or by date
• Through the API: Submit the EWB number, closure date, and remarks

Current limitations to know:

• Mobile-number-based closure is available only through the portal, not via API
• There's no API yet to retrieve a list of closed EWBs
• A dedicated "Closed" status hasn't been introduced yet — EWBs will continue showing as Active, Cancelled, or Discarded for now
• Even after closure, actions like updating the transporter or extending validity will still be allowed during this initial phase

Implementation Timeline

• Sandbox release — Already live
• Production rollout — 1 August 2026

What You Need to Do

If you or your clients use ERP, GSP, or API-based integrations for e-Invoice/EWB generation:

• Test the revised API specifications in the Sandbox environment
• Update your system to capture Ship-to GSTIN (with "URP" as a fallback where applicable)
• Make sure Bill-to and Ship-to GSTINs are never identical in your data
• Ensure your systems are production-ready well before 1 August 2026

Acting early avoids last-minute disruptions to invoicing and logistics once the new validations go live.