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 issued an advisory (dated 17 June 2026) making the Ship-to GSTIN a mandatory field in two places:

• The e-Invoice API, and
• The e-Way Bill by IRN API

Previously, the Ship-to GSTIN was either optional or not consistently validated. Going forward, transactions where goods are shipped to a registered business location must explicitly include that location's GSTIN at the time of IRN generation.

A timeline extension was also announced on 9 June 2026, suggesting the original enforcement date was pushed out to give taxpayers more time to comply. The revised deadline is not specified in detail here, refer to the official GSTN advisory for the exact go-live date.

Why This Matters

When goods are sold to one party but delivered to a different address (a common scenario in B2B supply chains, think warehouses, third-party logistics, branch deliveries), the Ship-to location details are critical for:

• Correct input tax credit (ITC) eligibility at the recipient's end
• Accurate movement records for e-Way Bill purposes
• Reducing disputes around place of supply

By mandating the Ship-to GSTIN, GSTN closes a data gap that previously allowed incomplete or mismatched records to pass through the system.

Who Is Affected

This applies to all taxpayers who generate e-Invoices, particularly those involved in:

• Multi-location B2B deliveries
• Drop-shipment arrangements
• Deliveries to customer warehouses or third-party addresses that have a separate GSTIN

If your Ship-to party is an unregistered person or a consumer, this field may not apply, but confirm the exact scope in the official advisory.

What You Should Do Now

1. Review your ERP or billing software, check whether it currently captures and transmits Ship-to GSTIN in the API payload. Many systems store Ship-to address but may not map the GSTIN separately.

2. Coordinate with your IT or software vendor, the API schema may need an update to include the Ship-to GSTIN field correctly.

3. Audit your master data, ensure GSTIN records for all Ship-to locations (your own branches, customer warehouses, consignees) are up to date.

4. Check the official advisory for the exact enforcement date, any transition period, and whether there are exceptions for specific transaction types.

5. Train your accounts and logistics teams, this is an operational change, not just a technical one. The person raising the invoice needs to know the correct Ship-to GSTIN before generation.

Bottom Line

This is a meaningful tightening of e-Invoice data requirements. The good news is the timeline extension gives businesses some breathing room. Use it to get your systems and data ready before the mandatory date kicks in.

Source: Official notification