Harun Raaj & AssociatesHarun Raaj & Associates
GST

Ship-to GSTIN Mandatory in e-Invoice & e-Way Bill APIs from 1 August 2026

From 1 August 2026, the Ship-to GSTIN becomes a mandatory field in e-Invoice and e-Way Bill APIs whenever ship-to details are present. Unregistered parties must be marked as 'URP'. Businesses must update their ERP and invoicing software before the deadline to avoid IRN generation failures.

CH

CA Harun Raaj

Chartered Accountant · Harun Raaj & Associates

Legal basis: Rule 48(4) and Rule 138, CGST Rules 2017 — API field requirement effective: 1 August 2026. Source: GSTN advisories dated 17 June 2026 and 20 June 2026 (https://www.gst.gov.in/newsandupdates). Last reviewed by CA Harun Raaj: December 2024.

The change in plain terms

From 1 August 2026, the GSTN's e-Invoice (IRP) and e-Way Bill APIs will) enforce a mandatory Ship-to GSTIN field wherever a document contains ship-to details. This means that in any Bill-to/Ship-to transaction — where goods are delivered to a party different from the buyer — the Ship-to GSTIN must be populated in both the IRN-generation and e-Way Bill API payloads. If the ship-to party is unregistered under GST, you must enter "URP" (Unregistered Person) instead of leaving the field blank. The field cannot remain empty.

This is a technical change to the API specification, not a change to GST law itself. Rule 48(4) (e-invoicing obligation) and Rule 138 (e-way bill requirement) remain unchanged. But the operational impact is significant: if your ERP or e-invoicing software is not updated in time, IRN and e-way bill generation will fail — and without a valid IRN, you cannot issue a compliant e-invoice.

Who this affects

Taxpayer TypeApplicabilityDetails
Mandatory e-invoicing filersHighThreshold: aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards (Rule 48(4), CGST Rules 2017)
Bill-to/Ship-to transactorsHighStock transfers, third-party drop-ship, consignments to project sites or branches
B2C-only filers (no separate ship-to)LowMandatory Ship-to GSTIN applies only where ship-to details are present; confirm software updates still allow IRN generation
ERP and GSP vendorsCriticalAPI payload structure must be updated before 1 August 2026
Key point: Any registered business issuing e-invoices with separate bill-to and ship-to parties must ensure its invoicing software captures and submits the ship-to GSTIN (or "URP" for unregistered recipients) before 1 August 2026, or invoice generation will fail.

Timeline: why 1 August, not 15 June

The GSTN originally scheduled this go-live for 15 June 2026. Following industry representations on ERP and GSP readiness, the Authority deferred the effective date to 1 August 2026 (GSTN advisory dated 9 June 2026). Treat 1 August 2026 as the firm operational deadline and plan your integration and testing well ahead.

The voluntary e-Way Bill Closure feature

Alongside the mandatory Ship-to GSTIN requirement, the GSTN has also introduced a voluntary "E-Way Bill Closure" facility. You can now close an active e-way bill before its validity expires, once the consignment has reached its destination. This is optional housekeeping — you are not required to use it — but it helps manage the portal by removing expired or inactive e-way bills from your open list.

What to do before 1 August 2026

1. Confirm vendor readiness. Contact your ERP vendor, GSP (GST Suvidha Provider), or e-invoicing software provider this week. Ask explicitly:
- Will the updated API payload (Ship-to GSTIN + URP handling) be live before 1 August 2026?
- What is the scheduled test/sandbox date for your integration?
- Do they have a rollback or support plan in case of API issues?

2. Audit and clean your master data. Review your ship-to party records:
- Confirm the correct GSTIN is captured for every registered ship-to location.
- Flag any genuinely unregistered parties so your system can automatically insert "URP".
- Test a few sample invoices in your sandbox to ensure the data flows correctly.

3. Run a sandbox invoice and e-way bill generation. Before the cut-over:
- Generate at least one test Bill-to/Ship-to invoice on the updated API and obtain an IRN.
- Generate at least one test e-way bill with the updated payload.
- Verify that both succeed and that the Ship-to GSTIN / URP appears correctly in the generated documents.

A failed IRN on 1 August could halt your invoicing and dispatch workflow, so dry-run your setup now.

Statutory context

Under Rule 48(4) of the 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). The e-Way Bill requirement under Rule 138 applies to movement of goods with consignment value exceeding ₹50,000. The mandatory Ship-to GSTIN field tightens the data that must be supplied to these systems, but the underlying obligations are unchanged.

Note: A separate GSTN advisory (referenced but not detailed here) also revised the AATO (Aggregate Annual Turnover) amendment window for FY 2025-26; if your turnover crosses the ₹5 crore threshold, confirm your e-invoicing applicability separately.

I'm CA Harun Raaj, Visakhapatnam. If your e-invoicing or e-way bill setup needs review before 1 August 2026, reach out — we help businesses stay compliant with GST API and portal changes.

---

See Also

Frequently Asked Questions

When does the mandatory Ship-to GSTIN requirement come into effect?+

The mandatory Ship-to GSTIN field in e-Invoice (IRP) and e-Way Bill APIs takes effect from **1 August 2026**, per the GSTN advisory dated 17 June 2026. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 following industry representations on system readiness (GSTN advisory dated 9 June 2026). This is the firm operational date.

What do I enter if my ship-to party is unregistered under GST?+

For unregistered ship-to parties, you must enter **"URP" (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank. This applies to both the e-Invoice API and the e-Way Bill API when ship-to details are present.

What happens if I don't update my e-invoicing software before 1 August 2026?+

If your ERP or e-invoicing software is not updated to support the mandatory Ship-to GSTIN field, IRN generation and e-way bill generation will fail for any Bill-to/Ship-to invoice. Without a valid IRN, you cannot issue a compliant e-invoice, which can halt your invoicing and dispatch operations. Confirm your vendor's update timeline immediately.

Is this a change to GST law or just an API change?+

This is a **technical change to the GSTN's API specification**, not a change to GST law or rates. Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged. The API update simply enforces stricter data validation: the Ship-to GSTIN field becomes mandatory where it was previously optional.

Am I affected if I only issue B2C invoices with no separate ship-to party?+

The mandatory Ship-to GSTIN applies **only where ship-to details are present** in a document. If your invoices carry no separate ship-to party (i.e., bill-to and ship-to are the same), this specific change has limited impact. However, confirm with your software vendor that IRN generation continues to work correctly after the API update.

What is the new E-Way Bill Closure feature?+

The GSTN has introduced a **voluntary "E-Way Bill Closure" facility** (per the advisory dated 20 June 2026) that allows you to close an active e-way bill before its validity expires, once the consignment has reached its destination. This is optional and is a convenience feature; you are not required to use it.

Which taxpayers are required to comply with the Ship-to GSTIN mandate?+

The mandatory Ship-to GSTIN requirement applies to all registered taxpayers under **mandatory e-invoicing rules** (Rule 48(4), CGST Rules 2017) — generally, those with aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards — and any taxpayer issuing e-way bills for Bill-to/Ship-to transactions.

How should I prepare my business before 1 August 2026?+

Take three steps: (1) Contact your ERP, GSP, or e-invoicing vendor to confirm the updated API will be live before 1 August 2026 and schedule a test date. (2) Audit your ship-to party master data and ensure GSINs are correct; flag unregistered parties for "URP" auto-insertion. (3) Run a sandbox test generating at least one Bill-to/Ship-to e-invoice and one e-way bill on the updated APIs to verify success before the cut-over.

Topics:ship-to GSTIN mandatorye-invoice API changes August 2026e-way bill API updatesURP unregistered personGSTN advisory 2026Bill-to Ship-to invoicinge-invoicing compliance

Related Services

Based on this article's category and vertical tag, these services are the most relevant next steps.

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.