Ship-to GSTIN Compulsory from 1 August 2026: Detailed GSTN FAQ-Based Guide

From 1st August 2026, the GST ecosystem will see a significant compliance enhancement: Ship-to GSTIN will become a mandatory field for specified e-Way Bill and e-Invoice flows wherever the Ship-to party is registered. This requirement, notified through GSTN FAQs dated 01.07.2026, has far‑reaching implications for ERPs, API users, exporters, transporters and business teams handling Bill-to/Ship-to transactions.

This article consolidates and rephrases the clarifications issued by GSTN, and presents them in a structured, practitioner-friendly format for quick implementation.

A. Snapshot of the Change

1. What exactly is changing?

For certain transaction types, the Ship-to GSTIN field changes from being optional to compulsory, subject to specific rules:

  • In Bill-to/Ship-to and Combination transactions:
    • If the Ship-to party is registered:
      • You must report the correct Ship-to GSTIN.
    • If the Ship-to party is unregistered or a GSTIN is genuinely not available:
      • You must enter “URP” (Unregistered Person) in the Ship-to GSTIN field.
  • Where this mandatory field is not populated:
    • The system will block generation of e-Way Bill / IRN with relevant error codes.

Note: “URP” is not case‑sensitive; the system will accept variants like urp, Urp, etc.

2. From when is this applicable?

  • Effective date for production: 1st August, 2026 (revised date announced by GSTN).
  • This date applies both to:
    • Standalone e-Way Bill related changes; and
    • e-Invoice APIs where e-Way Bill is generated along with IRN.

3. Where can testing be done?

  • A Sandbox (test) environment incorporating the new validations is already live.
  • Assessees and solution providers are expected to:
    1. Update their integrations and payloads.
    2. Execute full-fledged testing in Sandbox.
    3. Move to production only after successful validation.

4. Transaction flows impacted

The following API flows are directly impacted:

  • Standalone Generate EWB API
  • Generate IRN + EWB together
  • e-Way Bill by IRN API

These changes are part of GSTN’s larger aim to enable:

  • Better traceability of goods movement,
  • A more robust system-based audit trail, and
  • Easier verification by authorised officers during enforcement.

B. Applicability Across Transaction Types

Q1. In which transactions is Ship-to GSTIN required, and in which is it prohibited?

The need to capture Ship-to GSTIN is determined solely by the nature of transaction, not by business labels in ERP.

1. Regular transactions

  • Pattern:
    • Billing: X Ltd. (seller) to Y Ltd. (buyer)
    • Movement: Goods move from X Ltd. to Y Ltd.
  • Ship-to GSTIN requirement:
    • Not applicable.
  • System rule:
    • Ship-to GSTIN must not be sent in the payload.
    • If provided, the system will trigger Error 616.

2. Bill-to / Ship-to transactions

  • Pattern:
    • Billing: X Ltd. invoices Y Ltd. (Bill-to).
    • Movement: Goods travel from X Ltd. to Z Ltd. on the instructions of Y Ltd.
  • Ship-to GSTIN requirement:
    • If Z Ltd. is registered: Ship-to GSTIN of Z Ltd. is mandatory.
    • If Z Ltd. is unregistered or GSTIN is unavailable: enter “URP”.
  • System rule:
    • Non-reporting or incorrect reporting will result in Error 608.

3. Bill-from / Dispatch-from transactions

  • Pattern:
    • Billing: X Ltd. bills Y Ltd.
    • Movement: Goods move from some other premises D (Dispatch-from) to Y Ltd. (Bill-to).
  • Ship-to GSTIN requirement:
    • Not required, as the buyer is already covered in Bill-to.
  • System rule:
    • Ship-to GSTIN should not be sent.
    • If sent, the system returns Error 864.
    • Only Dispatch-from details of D are needed.

4. Combination transactions

  • Pattern:
    • Billing: X Ltd. bills Y Ltd. (Bill-to).
    • Movement: Goods move from D (Dispatch-from) to Z Ltd. (Ship-to) based on Y Ltd.’s instructions.
  • Ship-to GSTIN requirement:
    • If Z Ltd. is registered: Ship-to GSTIN of Z Ltd. is mandatory.
    • If not registered or GSTIN is not available: “URP” must be captured.
  • System rule:
    • Ship-to GSTIN omission or incorrect handling triggers Error 608.
    • Dispatch-from details of D must also be properly populated.

Q2. Can the Bill-to GSTIN and Ship-to GSTIN be identical?