E-Invoice Ship-to GSTIN Mandate: Timeline Extended (June 2026)

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

What Changed

GSTN issued an advisory on 9 June 2026 extending the timeline for two specific e-invoicing features:

1. Mandatory 'Ship to GSTIN' capture in the e-Invoice API, businesses will now get more time before this field becomes compulsory.
2. Voluntary e-Way Bill closure functionality, the rollout of this feature has also been pushed back.

A follow-up notification dated 17 June 2026 announced further enhancements to the e-invoicing system. The precise revised deadlines and technical specifications are detailed in the official GSTN advisory, refer to the official notification for exact dates and field-level requirements.

Why This Matters

The 'Ship to GSTIN' field captures the GST registration number of the location where goods are actually delivered, which may differ from the buyer's billing address. Making this mandatory in the API tightens reconciliation between e-invoices and e-way bills, and reduces disputes over place of supply.

The voluntary e-way bill closure feature, once live, will let suppliers close e-way bills themselves under defined conditions, reducing dependency on transporters to update delivery status.

Who Is Affected

• Businesses generating e-invoices through the API (direct integration or via GSP/ASP)
• ERP and billing software vendors who need to update their API payloads
• Logistics and dispatch teams managing e-way bill lifecycles
• Any taxpayer whose 'ship to' address regularly differs from the 'bill to' address

If you use a third-party e-invoicing solution, your vendor will likely push an update, but you should confirm they are aware of both the June 9 and June 17 advisories.

What You Should Do

• Check the revised timeline in the official GSTN advisory to know exactly when the 'Ship to GSTIN' field becomes mandatory in API calls.
• Audit your master data, ensure your system stores valid GSTINs for all ship-to locations, not just billing addresses. Missing or invalid GSTINs will cause API rejections once the field is mandatory.
• Talk to your ERP or GSP vendor about the June 17 enhancements and confirm their update schedule.
• Train your dispatch/logistics team on the upcoming voluntary e-way bill closure feature so they are ready to use it correctly when it goes live.
• If you handle high invoice volumes, run a test in the sandbox environment before the deadline to catch any payload errors early.

Bottom Line

This is a timeline extension, not a rollback, the mandate is still coming. Use the extra time to clean up ship-to GSTIN data and align your API integration. Getting this right now will prevent bulk invoice rejections and e-way bill mismatches down the line.

Source: Official notification