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 wherever ship-to details are present. Unregistered parties must be marked as "URP". Failure to update your ERP or invoicing software in time can block IRN generation and halt your invoice issuance.
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 advisory dated 17 June 2026 and 20 June 2026 at 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 (IRP) and e-Way Bill system APIs. Wherever a document carries Ship-to details, the Ship-to GSTIN) becomes a mandatory field in both IRN-generation and e-Way Bill API payloads. If your ERP or invoicing software is not updated in time, IRN and e-way bill generation can fail — meaning you cannot issue a valid tax invoice.
This is a technical/portal change, not a change in GST law — but its operational impact is material, because it directly affects the point where invoices are actually generated and validated on the GSTN portal.
What is changing on 1 August 2026
Per the GSTN advisory dated 17 June 2026 (read with the advisory dated 20 June 2026):
- Ship-to GSTIN is now mandatory when Ship-to details are present. In a Bill-to/Ship-to transaction (where goods are delivered to a party different from the buyer), the Ship-to GSTIN must be populated in the IRN and e-Way Bill API payloads. The field cannot be left blank.
- Unregistered ship-to party? Enter "URP" (Unregistered Person) in place of the GSTIN.
- New voluntary E-Way Bill Closure feature. You can now close an active e-way bill before its validity expires, once the consignment has reached its destination — a useful housekeeping option to reduce stale e-way bills on the portal.
Timeline: why 1 August 2026
These API 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 via advisory dated 9 June 2026. The deferred date is now firm. Plan your testing and vendor coordination well in advance.
Who is affected
- Every registered person covered by mandatory e-invoicing under Rule 48(4), CGST Rules 2017 (current applicability: aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards).
- Any taxpayer generating e-way bills for movement of goods, especially those using Bill-to/Ship-to structures — stock transfers between locations, third-party/drop-ship deliveries, consignments to project sites, or dispatches to branches.
- ERP, GSP and e-invoicing software vendors, who must update their API integration payloads and test thoroughly before 1 August 2026.
Your action plan: three steps before 1 August 2026
Step 1: Engage your software vendor immediately. Contact your ERP, GSP, or e-invoicing platform vendor this week. Confirm they are releasing the updated API payload (with Ship-to GSTIN as mandatory + URP handling) before 1 August 2026. Request a test date and sandbox access for early integration testing.
Step 2: Audit and clean your Ship-to master data. Review your vendor, customer, and inter-location master records. For every ship-to location, ensure the correct GSTIN is captured. For genuinely unregistered parties, explicitly mark them in your system so the API can auto-insert "URP" and avoid blank fields.
Step 3: Run sandbox testing. Before 1 August, generate at least one test Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs in sandbox/UAT mode. Verify both IRN generation and e-way bill creation succeed. A failed IRN on or after 1 August will halt your invoice issuance.
Key point: Ship-to GSTIN is mandatory in the e-Invoice and e-Way Bill APIs from 1 August 2026 wherever ship-to details are present; unregistered parties must be marked as "URP".
Legal and regulatory backdrop
E-invoicing obligation: Rule 48(4), CGST Rules 2017 — registered persons in a notified class must prepare invoices by uploading specified particulars to the IRP and obtaining an Invoice Reference Number (IRN).
E-way bill requirement: Rule 138, CGST Rules 2017 — an e-way bill is required for movement of goods in a single consignment of value exceeding ₹50,000.
Applicability threshold: The e-invoicing mandate applies to registered persons with aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards (subject to periodic amendment notifications by the GST Council).
The Ship-to GSTIN mandatory field change does not alter these underlying statutory obligations; it only tightens the API validation rules on the GSTN portal.
I'm CA Harun Raaj, Visakhapatnam. If your business operates Bill-to/Ship-to transactions or relies on third-party dispatch, reach out to discuss your e-invoicing and e-way bill readiness for 1 August 2026.
---
See Also
Frequently Asked Questions
When does the Ship-to GSTIN mandatory requirement take effect?+
Per the GSTN advisory dated 17 June 2026, the mandatory Ship-to GSTIN requirement takes effect from **1 August 2026**. The original go-live date of 15 June 2026 was deferred to allow ERP and GSP vendors more time for system updates and testing.
What should I do if the ship-to party is not registered under GST?+
If the ship-to party is unregistered, enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank; the system will reject the IRN or e-way bill request if Ship-to details are present but the GSTIN is missing or empty.
What happens if my invoicing software is not updated before 1 August 2026?+
If your ERP or GSP does not support the updated API payload (with mandatory Ship-to GSTIN), IRN generation and e-way bill creation for Bill-to/Ship-to transactions will fail. Without a valid IRN, you cannot issue a compliant e-invoice, which can halt your billing process.
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. You can continue to let e-way bills expire naturally if you prefer.
Is this a change in GST law or GST rates?+
No. This is a technical change to the GSTN's e-Invoice and e-Way Bill APIs. The underlying statutory obligations under Rule 48(4) and Rule 138 of the CGST Rules 2017 remain unchanged; only the API field validation rules are being tightened.
I only issue B2C invoices with no separate ship-to party. Am I affected?+
The mandatory Ship-to GSTIN requirement applies **only where Ship-to details are present** in the document. If your invoices have no separate ship-to party (e.g., direct B2C sales), this specific API change has limited impact on your workflow — but confirm with your software vendor that your existing invoices will still generate IRNs correctly after the API update.
What is the current e-invoicing mandate threshold?+
E-invoicing is currently mandatory for registered persons with aggregate annual turnover exceeding ₹5 crore in any financial year from 2017-18 onwards. However, this threshold may be amended periodically by the GST Council; check the latest GSTN advisory for any updates.
How should I prepare my master data before 1 August 2026?+
Audit your vendor, customer, and inter-location master records. For every Bill-to/Ship-to transaction, ensure the correct Ship-to GSTIN is captured. For unregistered parties, explicitly flag them in your system so your invoicing software can auto-insert "URP" and avoid blank or missing fields in the API payload.
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.