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 APIs whenever ship-to details are present. Businesses must update ERP and e-invoicing software, clean master data for unregistered parties (marked 'URP'), and test before the deadline to avoid IRN generation failures.
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 on www.gst.gov.in/newsandupdates. Last reviewed by CA Harun Raaj: August 2026.
What is changing
From 1 August 2026, the GSTN is tightening the e-Invoice (IRP) and e-Way Bill system APIs. The Ship-to GSTIN) field becomes mandatory wherever a document carries separate ship-to details — that is, in any Bill-to/Ship-to transaction where goods are delivered to a party different from the buyer.
Three key updates:
- Ship-to GSTIN mandatory when present. The IRN-generation and e-Way Bill API payloads must include a valid Ship-to GSTIN; the field cannot be left blank.
- Unregistered ship-to parties enter "URP". If the ship-to party is not registered under GST, populate the Ship-to GSTIN field with "URP" (Unregistered Person).
- Voluntary E-Way Bill Closure feature added. You can now close an active e-way bill before its validity expires once the consignment reaches its destination — a housekeeping improvement.
Why the deadline moved
These changes were originally scheduled for 15 June 2026. Following industry representations on ERP and GSP readiness, the GSTN deferred the go-live to 1 August 2026 (advisory dated 9 June 2026). This is the firm deadline; plan your integration and testing accordingly.
Who is affected
Key point: From 1 August 2026, IRN and e-way bill generation will fail if the Ship-to GSTIN field is missing or blank whenever ship-to details are present in the document.
What you must do before 1 August 2026
1. Engage your software vendor immediately. Confirm in writing that your ERP, GSP, or e-invoicing platform will ship the updated API payload (with Ship-to GSTIN and URP handling) before 1 August 2026. Request a sandbox/UAT access date and test credentials.
2. Audit and clean your Ship-to master data. Review every ship-to location in your system:
- Capture the correct GSTIN for registered ship-to parties.
- Flag genuinely unregistered parties so your system auto-inserts "URP" when IRN/e-way bill is generated.
- Remove null or placeholder values; they will cause API rejection.
3. Run a test generation before cutover. Generate at least one Bill-to/Ship-to invoice and one e-way bill on the updated APIs using your sandbox environment. Verify that the IRN is generated and the e-way bill is created without errors. Do not wait until 1 August to discover a failure.
4. Coordinate with your finance and operations teams. Brief them that:
- This is a technical API change, not a law change.
- Failed IRN = invalid e-invoice = halted dispatch (on critical dates).
- The E-Way Bill Closure feature is optional; no action needed unless you want to use it.
Technical context (for clarity)
This change does not alter the underlying GST law or filing obligations. Rule 48(4) (e-invoicing for eligible taxpayers) and Rule 138 (e-way bill for goods movement) remain in force. The GSTN is simply enforcing stricter API validation: the Ship-to GSTIN field, which was previously optional or conditionally required, is now mandatory in the API payload whenever ship-to details are present.
For businesses with only Bill-to transactions (no separate ship-to), the impact is minimal — but confirm your software still generates IRNs correctly after the API upgrade.
For drop-ship, third-party logistics, stock-transfer, and project-site delivery models, this is a critical operational change. Test early and plan backup validation workflows if your primary e-invoicing channel is unavailable.
I'm CA Harun Raaj, Visakhapatnam. If your business operates a Bill-to/Ship-to model or uses e-invoicing and e-way bills, reach out to confirm your software is ready before 1 August 2026.
---
See Also
Frequently Asked Questions
From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+
From **1 August 2026**, per GSTN advisories dated 17 June 2026 and 20 June 2026. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 (advisory dated 9 June 2026) to allow industry time to update ERP and GSP systems.
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. The field cannot be left blank; it must contain either a valid GSTIN or the code URP.
What happens if I don't update my software before 1 August 2026?+
For any Bill-to/Ship-to document, IRN generation and e-way bill generation will fail because the mandatory Ship-to GSTIN field is missing or blank. Without a valid IRN, you cannot issue a valid e-invoice, which stops your dispatch and billing workflow.
Is this a change in GST law or GST rates?+
No. This is a technical change to the GSTN's e-Invoice (IRP) and e-Way Bill API field requirements. The underlying obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 are unchanged.
Does the new E-Way Bill Closure feature affect my current e-way bills?+
No. The E-Way Bill Closure feature is **voluntary**. It allows you to close an active e-way bill before its validity expires once goods have reached the destination. You are not required to use it.
I only issue B2C invoices with no separate ship-to details. Am I affected?+
The mandatory Ship-to GSTIN applies only **where ship-to details are present** in the document. If your invoices do not carry a separate ship-to party, this specific change has limited impact — but confirm with your software vendor that your IRN generation continues to work after the API update.
Who must comply with this API change?+
All taxpayers under **mandatory e-invoicing** (aggregate annual turnover above ₹5 crore, per Rule 48(4) CGST Rules) and those generating e-way bills for goods movement, especially those using Bill-to/Ship-to structures (stock transfers, drop-ship, third-party deliveries, project consignments).
What is the first step I should take to prepare?+
Contact your ERP, GSP, or e-invoicing software vendor this week and confirm they will deliver the updated API payload (with Ship-to GSTIN and URP handling) before 1 August 2026. Request a UAT/sandbox test date.
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.