Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN requires Ship-to GSTIN as a mandatory field in e-Invoice and e-Way Bill API payloads whenever ship-to details are present. Unregistered parties must be entered as 'URP'. Failure to update your ERP or invoicing software in time can block IRN generation.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — effective from 1 August 2026. Source: GSTN advisories dated 17 June 2026, 20 June 2026, and 9 June 2026 at https://www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: August 2026.
From 1 August 2026, the GSTN is enforcing a mandatory Ship-to GSTIN) field in the e-Invoice (IRP) and e-Way Bill system APIs. Where your documents carry separate ship-to details — the address to which goods are physically delivered — you must populate the Ship-to GSTIN in both the IRN-generation payload and the e-Way Bill API. If your ERP, GSP, or e-invoicing software is not updated in time, IRN and e-way bill generation can fail, which means you cannot issue a valid tax invoice or movement document.
This is a technical API change to the GSTN portal, not a change in GST law. The underlying obligations under Rule 48(4) (mandatory e-invoicing for notified taxpayers) and Rule 138 (e-way bill for goods movement) remain unchanged. But the operational impact is direct: a blocked IRN stops your invoicing.
What is changing on the GSTN platform
Per the GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN becomes mandatory whenever a document contains separate ship-to details (that is, the delivery address differs from the billing address).
- Unregistered ship-to parties must be marked as "URP" (Unregistered Person) in the Ship-to GSTIN field. The field cannot be left blank or empty.
- E-Way Bill Closure feature introduced (voluntary): taxpayers can now close an active e-way bill before its validity expires, once goods have reached destination — a housekeeping convenience to reduce stale e-way bills on the portal.
The change applies to both the Invoice Registration Portal (IRP) for e-invoicing and the e-Way Bill API for goods movement documents.
Timeline: why 1 August 2026
These functionalities were originally scheduled for 15 June 2026. Following industry representations on ERP, GSP, and software readiness, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). Treat 1 August 2026 as the firm operative date.
Who is affected
Key point: Mandatory Ship-to GSTIN affects only documents where the billing address and delivery address are different; blank fields or missing updates will cause IRN and e-way bill generation to fail.
Three critical steps before 1 August 2026
- Contact your ERP, GSP, or e-invoicing vendor immediately. Ask whether they have released (or have a firm release date for) the updated API payload that handles Ship-to GSTIN as a mandatory field, and Ship-to "URP" logic. Request a sandbox / test environment date and confirm their support for testing before the cut-over.
- Audit and clean your master data. For every ship-to location in your ERP, ensure the correct GSTIN is captured and linked. For genuinely unregistered ship-to parties (e.g., delivery to a consumer's home, or to a location without a GST registration), flag these in your system so the invoicing software can auto-populate "URP" in the Ship-to GSTIN field.
- Run end-to-end UAT on the updated APIs. Generate at least one complete Bill-to/Ship-to invoice (with separate bill and ship addresses) on the updated system, obtain an IRN, and generate an e-way bill. Do this in sandbox mode before 1 August so a failed IRN or e-way bill generation does not disrupt your dispatch operations on go-live.
Statutory context
- E-invoicing / IRN: Rule 48(4), CGST Rules 2017 requires notified registered persons to prepare invoices by uploading specified particulars to the Invoice Registration Portal (IRP) and obtaining an Invoice Reference Number (IRN).
- E-way bill: Rule 138, CGST Rules 2017 mandates an e-way bill for movement of goods where the consignment value exceeds ₹50,000.
- Applicability threshold: Currently, e-invoicing is mandatory for registered persons whose aggregate annual turnover (AATO) exceeds ₹5 crore in any financial year from 2017-18 onwards.
I'm CA Harun Raaj, Visakhapatnam. If your business is affected by this API change and you need help preparing your e-invoicing or e-way bill setup, reach out to discuss your specific workflow.
---
See Also
Frequently Asked Questions
When does Ship-to GSTIN become mandatory in the e-Invoice and e-Way Bill APIs?+
From **1 August 2026**, per the GSTN advisories dated 17 June 2026 and 20 June 2026. The go-live was deferred from the original date of 15 June 2026 to allow time for ERP and software vendor readiness. The 1 August 2026 date is now firm.
What do I enter in the Ship-to GSTIN field if the delivery party is unregistered?+
Enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank or empty. This applies when goods are delivered to a location that does not have a GST registration (e.g., direct delivery to a consumer, or to a supplier's unregistered branch).
Does this apply to all my invoices, or only certain types?+
This mandatory Ship-to GSTIN requirement applies **only where your document contains separate ship-to details** — that is, where the delivery address is different from the billing address. If your invoices show the same address for billing and delivery (Bill-to = Ship-to), this change has limited impact. Confirm your software still generates IRNs correctly post-update.
What happens if my ERP is not updated by 1 August 2026?+
For invoices containing separate ship-to details, IRN generation and e-way bill generation can fail because the mandatory Ship-to GSTIN field is missing from the API payload. Without a valid IRN, you cannot issue a valid e-invoice, which will halt your invoicing process. Start coordination with your vendor immediately.
Is the new E-Way Bill Closure feature mandatory?+
No — the E-Way Bill Closure feature is **voluntary**. It is a convenience utility to close an active e-way bill before its validity expires, once goods have reached their destination. You may use it or leave e-way bills to expire naturally.
Is this a change in GST law or GST tax rates?+
No. This is a **technical change to the GSTN API requirements**, not a change in GST law or rates. The underlying obligations under Rule 48(4) (mandatory e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 are unchanged. Only the API field structure and validation rules are being tightened.
Who needs to update their systems before 1 August 2026?+
All taxpayers covered by **mandatory e-invoicing** (aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards), and any taxpayer who generates **e-way bills** for goods movement. ERP vendors, GSPs, and e-invoicing software providers must update their API integration payloads before the go-live date.
What is the first step I should take now?+
Contact your ERP, GSP, or e-invoicing software vendor this week and confirm they have (or have a firm timeline for) releasing the updated API payload that handles mandatory Ship-to GSTIN and unregistered party logic. Request a sandbox test date and plan an end-to-end test of a Bill-to/Ship-to invoice and e-way bill generation before 1 August 2026.
Go deeper with our hub guides
Statute-cited, section-by-section guides covering the same ground this article does.
Need help with this?
Our team handles the paperwork. You focus on your business.