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 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 entered as 'URP'. Failure to update your ERP or e-invoicing software in time can block IRN generation and halt invoicing.

CH

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, available 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. Wherever a document carries ship-to details — that is, delivery to a party different from the billing party — you must populate the Ship-to GSTIN in both the IRN-generation payload and the e-Way Bill API. If the ship-to party is unregistered under GST, you enter "URP" (Unregistered Person) instead of a GSTIN. The field cannot be left blank.

This is a technical API change, not a change in GST law. But its operational impact is high: if your ERP, GSP, or e-invoicing software is not updated by 1 August 2026, IRN and e-way bill generation for Bill-to/Ship-to transactions can fail — and without a valid IRN, you cannot issue a lawful e-invoice.

Key point: Ship-to GSTIN becomes mandatory in the e-Invoice and e-Way Bill APIs from 1 August 2026; unregistered ship-to parties must be entered as 'URP', and failure to comply can block invoicing for bill-to/ship-to transactions.

What the GSTN is changing

Per the GSTN advisories dated 17 June 2026 and 20 June 2026, three functional updates take effect on 1 August 2026:

  • Ship-to GSTIN is mandatory when ship-to details are present. In a Bill-to/Ship-to transaction (where goods are delivered to a party other than the invoice buyer), the Ship-to GSTIN must be populated in both the IRN API payload and the e-Way Bill API payload. This applies to all e-invoicing taxpayers under Rule 48(4), CGST Rules 2017.
  • Unregistered ship-to parties use 'URP'. Where the ship-to recipient is not registered under GST, you must enter "URP" (Unregistered Person) in the Ship-to GSTIN field. Leaving the field blank will cause the API to reject the request.
  • New voluntary e-way bill closure feature. The GSTN has introduced an optional "E-Way Bill Closure" facility that allows you to close an active e-way bill before its validity expires, once the consignment has reached its destination. This is a housekeeping convenience and is not mandatory.

Scope and applicability

Taxpayer TypeAffectedWhy
Mandatory e-invoicing taxpayer (AATO > ₹5 crore)YesRule 48(4), CGST Rules 2017; must generate IRNs via the IRP API
Any taxpayer with bill-to/ship-to invoicesYesShip-to GSTIN now required in the IRN and e-Way Bill API payloads
B2C or single-address invoices (no ship-to)LimitedApplies only if ship-to details are present; direct delivery invoices unaffected
E-way bill filers (movement > ₹50,000)YesRule 138, CGST Rules 2017; e-Way Bill API now requires Ship-to GSTIN where applicable
ERP, GSP, and e-invoicing software vendorsYesMust update API integration code to include Ship-to GSTIN field and URP handling

Why the date was deferred

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 (advisory dated 9 June 2026). Treat 1 August 2026 as the firm operative date and plan your integration testing and software updates accordingly.

Your 3-step action plan before 1 August 2026

  • Confirm vendor readiness this week. Contact your ERP, GSP, or e-invoicing software vendor. Obtain written confirmation that they will deploy the updated API payload (including Ship-to GSTIN field and URP handling) before 1 August 2026. Request a firm testing window.
  • Audit and clean your ship-to master data. Review all ship-to locations in your system. Ensure the correct GSTIN is captured for each registered ship-to party. For genuinely unregistered ship-to recipients, flag or tag them in your master data so your system can automatically insert "URP" when generating IRNs and e-way bills.
  • Run a sandbox test before cut-over. Generate at least one bill-to/ship-to invoice and one corresponding e-way bill on the updated APIs in a test environment. Verify that IRN generation and e-way bill generation both succeed. Do not wait until 1 August to discover that your software is not ready.

Statutory and technical context

E-invoicing (IRN): Rule 48(4), CGST Rules 2017 requires a notified class of registered persons to prepare invoices by uploading specified particulars to the e-Invoice portal (IRP) and obtain an Invoice Reference Number (IRN). The Ship-to GSTIN is now a specified particular where ship-to details are present.

E-way bill: Rule 138, CGST Rules 2017 requires an e-way bill for movement of goods of consignment value exceeding ₹50,000. The e-Way Bill API now mandates the Ship-to GSTIN where applicable.

Aggregate Annual Turnover (AATO): The GSTN advisory (No. 666, dated 1 July 2026) separately revised the AATO amendment window for FY 2025-26 to 1–31 July 2026. If your turnover crossed the e-invoicing threshold, update your registration accordingly before the window closes.

If your business relies on bill-to/ship-to invoicing — stock transfers to branches, third-party or drop-ship deliveries, project site consignments — act now. A delay in software readiness can halt your invoicing on 1 August 2026. I'm CA Harun Raaj, Visakhapatnam. If you're concerned about e-invoicing or e-way bill readiness before this date, reach out — we can help.

---

See Also

Frequently Asked Questions

From when is Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs?+

Per the GSTN advisories dated 17 June 2026 and 20 June 2026, Ship-to GSTIN becomes mandatory in the e-Invoice (IRP) and e-Way Bill APIs with effect from **1 August 2026**. The go-live was originally scheduled for 15 June 2026 but was deferred to 1 August 2026 following industry representations on vendor readiness.

What if my ship-to party is not registered under GST?+

Enter **'URP' (Unregistered Person)** in the Ship-to GSTIN field. The field cannot be left blank; the API will reject requests with a missing or blank Ship-to GSTIN where ship-to details are present.

Is this a change in GST law or GST rates?+

No. This is a technical API change to the GSTN's e-Invoice and e-Way Bill systems. The underlying statutory obligations under Rule 48(4) (e-invoicing) and Rule 138 (e-way bill) of the CGST Rules 2017 remain unchanged; only the API field requirements are being tightened.

What happens if my ERP or e-invoicing software is not updated by 1 August 2026?+

For bill-to/ship-to documents where ship-to details are present, IRN generation and e-way bill generation may fail because the mandatory Ship-to GSTIN field is missing. Without a valid IRN, you cannot issue a lawful e-invoice, which can disrupt your invoicing and dispatch operations.

Do I have to use the new e-way bill closure feature?+

No — the e-way bill closure feature is **voluntary**. It is a convenience option introduced by the GSTN to allow you to close an 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. Am I affected?+

The mandatory Ship-to GSTIN applies **where ship-to details are present**. If your invoices carry no separate ship-to party (direct delivery to the buyer), this specific change has limited direct impact. However, confirm with your software vendor that your system continues to generate IRNs correctly after the API update.

Which taxpayers are affected by the Ship-to GSTIN mandatory field?+

Any taxpayer covered by mandatory e-invoicing under Rule 48(4), CGST Rules 2017 (aggregate annual turnover above ₹5 crore in any financial year from 2017-18 onwards) is affected if they have bill-to/ship-to transactions. Additionally, any taxpayer filing e-way bills for goods movement is affected where ship-to details apply.

When should I run a test on the updated e-invoice and e-way bill APIs?+

Run your sandbox testing in **July 2026**, well before 1 August 2026. Generate at least one bill-to/ship-to invoice and one e-way bill on the updated APIs to confirm that IRN and e-way bill generation succeed. This ensures you identify any integration issues before the mandatory cut-over date.

Topics:ship-to GSTIN mandatorye-invoice API changes August 2026e-way bill closure feature GSTNURP unregistered person GSTINmandatory e-invoicing Rule 48GSTN advisory June 2026bill-to ship-to invoicing GST

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.