Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026
From 1 August 2026, the GSTN is making Ship-to GSTIN a mandatory field in e-Invoice and e-Way Bill APIs. If your software isn't updated, IRN and e-way bill generation for Bill-to/Ship-to transactions will fail. Unregistered ship-to parties must be marked as 'URP'.
CA Harun Raaj
Chartered Accountant · Harun Raaj & Associates
Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — Effective: 1 August 2026. Source: GSTN advisories dated 17 June 2026, 20 June 2026, and 9 June 2026 (https://www.gst.gov.in/newsandupdates). Last reviewed by CA Harun Raaj: August 2026.
From 1 August 2026, the GSTN is tightening the e-Invoice and e-Way Bill system APIs. Wherever a transaction includes Ship-to details, the Ship-to GSTIN) becomes a mandatory field in the IRN-generation and e-Way Bill payloads. If your ERP 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 move goods legally.
This is a technical/portal change, not a change in the underlying GST law — but the operational impact is high because it touches the exact moment your invoices are generated and validated.
What is changing from 1 August 2026
Per the GSTN advisories dated 17 June 2026 and 20 June 2026:
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction (goods delivered to a party different from the buyer), you must populate the Ship-to GSTIN in both the IRN API and e-Way Bill API payloads.
- For unregistered ship-to parties, enter 'URP'. If the ship-to location is not GST-registered, you must explicitly populate the field with "URP" (Unregistered Person) — leaving the field blank will cause generation to fail.
- New voluntary e-Way Bill Closure feature. You can now close an active e-way bill before its validity expires once the goods reach the destination, reducing stale open e-way bills on the portal.
Timeline: why 1 August and not 15 June
The GSTN originally scheduled this go-live for 15 June 2026. Following industry representations about ERP and GSP readiness, the GSTN deferred implementation to 1 August 2026 (per advisory dated 9 June 2026). This is not a soft deadline — treat 1 August as firm and plan your integration testing accordingly.
Who must act now
Key point: If your software doesn't populate the Ship-to GSTIN field (or "URP" for unregistered parties) before 1 August 2026, invoice and e-way bill generation will fail and halt your operations.
Your action plan before 1 August 2026
Week 1: Contact your software vendor. Confirm they have committed to releasing the updated API payload (Ship-to GSTIN field + URP handling) before 1 August. Get a specific test date and pilot availability.
Week 2–3: Clean your ship-to master data. Audit every ship-to location in your system and ensure the correct GSTIN is recorded. Mark genuinely unregistered ship-to parties so your software can auto-populate "URP" when generating invoices and e-way bills.
Week 4: Run sandbox testing. Generate at least one Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs in your test environment. Confirm IRN generation succeeds and e-way bill gets generated without errors. Document the test results for your records.
Statutory context
E-invoicing (IRN): Rule 48(4) of the CGST Rules 2017 requires a notified class of registered persons to prepare invoices by uploading particulars to the e-Invoice Portal (IRP) and obtaining an Invoice Reference Number. The Ship-to GSTIN field is now part of those mandatory particulars.
E-way bill: Rule 138 of the CGST Rules 2017 requires an e-way bill for movement of goods of consignment value exceeding ₹50,000. The updated e-Way Bill API will enforce the Ship-to GSTIN requirement for any document carrying ship-to details.
Note on AATO: The GSTN separately issued an advisory (dated 1 July 2026) on the Aggregate Annual Turnover amendment window for FY 2025-26; that change is independent of this API update.
Why this matters: common failure scenarios
- Scenario 1: Stock transfer to a branch. Your branch location has a separate GSTIN. If your software cannot populate that Ship-to GSTIN in the IRN payload, IRN generation fails on 1 August — the invoice is not valid.
- Scenario 2: Drop-ship to an unregistered distributor. Your distributor has no GSTIN. If you don't flag them as "URP" in your master data, your software will reject the invoice or leave the field blank — both cause IRN failure.
- Scenario 3: Third-party logistics. Goods move from your warehouse to a customer's site via a logistics partner. The e-Way Bill API requires Ship-to GSTIN. Without it, e-way bill generation fails and goods cannot move legally.
I'm CA Harun Raaj, Visakhapatnam. If your business uses Bill-to/Ship-to invoices or e-way bills, reach out to confirm your software is ready before the 1 August deadline.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in e-Invoice and e-Way Bill APIs?+
The Ship-to GSTIN field becomes mandatory in e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**, per GSTN advisories dated 17 and 20 June 2026. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 to allow vendors and businesses time for integration testing.
What do I enter in the Ship-to GSTIN field if the ship-to party is unregistered?+
Enter **'URP' (Unregistered Person)** in the Ship-to GSTIN field. You cannot leave the field blank. Your software must be configured to auto-populate 'URP' for unregistered ship-to locations, or you must manually ensure it is present in every invoice and e-way bill for unregistered destinations.
What happens if my software is not updated by 1 August 2026?+
For any Bill-to/Ship-to transaction where Ship-to details are present, IRN generation and e-Way Bill generation will fail because the mandatory Ship-to GSTIN field is missing. Without a valid IRN, you cannot issue a valid e-invoice, and without a valid e-Way Bill, you cannot move goods legally.
Is this a change in GST law or GST rules?+
No. This is a technical change to the GSTN's e-Invoice and e-Way Bill API payload requirements. The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged; only the mandatory API fields are being tightened.
Do I have to use the new e-Way Bill Closure feature?+
No — the e-Way Bill Closure feature is **voluntary**. It allows you to close an e-way bill before its validity expires once goods have reached the destination. Using it is optional and is a convenience feature to reduce stale open e-way bills on the portal.
I only issue B2C invoices with no separate ship-to. Am I affected?+
The mandatory Ship-to GSTIN requirement applies **where Ship-to details are present in the transaction**. If your invoices carry no separate ship-to party (i.e., Bill-to and Ship-to are the same), this change has limited direct impact — but confirm your software vendor has tested the updated API to ensure IRN generation still works correctly.
Who must update their software before 1 August 2026?+
All businesses under mandatory e-invoicing (aggregate annual turnover above ₹5 crore in any FY from 2017-18 onwards) must ensure their ERP, GSP, or e-invoicing software is updated. If you use third-party software to generate invoices or e-way bills, contact your vendor immediately to confirm the update timeline.
How do I prepare my data for this change?+
Audit your ship-to master data and ensure the correct GSTIN is recorded for every ship-to location. For unregistered ship-to parties (branches, distributors, or delivery points without GST registration), flag them in your system so your software can auto-populate 'URP'. Run a test IRN and e-Way Bill generation before 1 August in your sandbox environment.
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.