26 October 2026 · Ruhu AI
E-Invoice Ship-to GSTIN Mandate: What Businesses Must Know
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 issued an advisory requiring businesses to mandatorily capture the Ship-to GSTIN in the e-Invoice API. Previously, this field may have been optional or inconsistently populated. Going forward, it must be correctly filled when the ship-to party is a registered GST taxpayer.
Separately, the advisory also covers an extension of the timeline for the voluntary closure of e-Way Bill functionality. The original advisory was issued on 09 June 2026, with further updates published on 17 June 2026.
Why This Matters
The Ship-to GSTIN field identifies where goods are actually being delivered, which can differ from the billing address. Capturing this accurately matters for:
- Correct GST liability assignment between states (inter-state vs intra-state)
- Accurate input tax credit (ITC) flow to the recipient
- Consistency between e-Invoice and e-Way Bill data
Errors or omissions here can trigger ITC mismatches, compliance notices, or reconciliation headaches down the line.
Who Is Affected
This applies to any taxpayer who:
- Is currently required to generate e-Invoices under the GST framework
- Ships goods to a location different from the billing address
- Generates e-Way Bills alongside e-Invoices
If your ERP or billing software auto-populates e-Invoice fields, check whether the Ship-to GSTIN is being passed correctly in the API payload.
What You Should Do
Immediately:
- Review your e-Invoice API integration to confirm the Ship-to GSTIN field is mapped and populated for all relevant transactions
- Coordinate with your ERP vendor or IT team if this field is currently blank or defaulting to the Bill-to GSTIN
On e-Way Bills:
- Note the extended timeline for the voluntary closure of e-Way Bill functionality, refer to the official GSTN notification for the exact revised dates, as the summary indicates an extension but does not specify the new deadline
Ongoing:
- Reconcile existing transactions to identify any invoices where Ship-to GSTIN was not captured, especially if those transactions involve ITC claims
- Train your accounts and dispatch teams to verify ship-to details before invoice generation
Key Takeaways
- Mandatory: Ship-to GSTIN must now be captured in the e-Invoice API
- Extended: The timeline for voluntary e-Way Bill functionality closure has been pushed out, check the official advisory for the exact date
- Advisories issued: 09 June 2026 (original) and 17 June 2026 (update)
- Action needed now: Audit your API integration and fix any gaps before they create compliance issues
Source: Official notification