Ship-to GSTIN Now Mandatory in E-Invoice and E-Way Bill APIs

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

What Has Changed

GSTN has made it mandatory to capture the Ship-to party's GSTIN in both the e-Invoice API and the e-Way Bill by IRN API. Previously, this field was optional or not consistently enforced in API transactions. Now, when a consignment is being shipped to a location or party different from the billing address, the Ship-to GSTIN must be explicitly included in the API request.

Alongside this, GSTN has introduced a voluntary closure option for e-Way Bill functionality, though the specifics of what this covers should be confirmed from the official advisory.

Timelines for implementing these changes were revised through two advisories: one dated 09-06-2026 and a follow-up dated 17-06-2026, indicating that the original deadline was extended to give businesses and technology providers more time to comply.

Who Is Affected

• Businesses generating e-Invoices where goods are shipped to a location or GSTIN different from the bill-to party
• Logistics and ERP software vendors who build or maintain e-Invoice and e-Way Bill integrations via GSTN APIs
• GSP (GST Suvidha Providers) and other intermediaries handling bulk API calls on behalf of taxpayers
• Any registered taxpayer whose supply chain involves third-party or branch-location deliveries

If your invoices always have the same bill-to and ship-to party, the impact may be minimal, but it's worth reviewing your API payload structure regardless.

What You Should Do

1. Audit your current API integration, check whether your e-Invoice and e-Way Bill API calls already include the Ship-to GSTIN field and whether it's being populated correctly.
2. Update your ERP or billing software, if the Ship-to GSTIN field is blank or missing in your system's API payload, work with your vendor or IT team to add it.
3. Coordinate with your GSP, if you use a GSP for API access, confirm they have updated their platform in line with the revised advisories.
4. Check the revised timeline, the advisory dated 17-06-2026 contains the current go-live deadline. Refer to the official GSTN advisory page for the exact date before planning your rollout.
5. Test in the sandbox environment, GSTN typically provides a sandbox for API testing. Validate your updated payload before pushing changes to production.

Why This Matters

Mismatched ship-to details have long been a source of e-Way Bill errors and GST reconciliation issues. Making Ship-to GSTIN mandatory at the API level improves data accuracy, reduces mismatches during audits, and strengthens the audit trail for goods movement, particularly for multi-location businesses and e-commerce operators.

Don't wait for the final deadline. Start your API review now.

Source: Official notification