Ship-to GSTIN Mandatory from 1 August 2026: e-Invoice and e-Way Bill Changes

What Is Changing from 1 August 2026?

GSTN is tightening consignee identification in applicable e-Invoice and e-Way Bill API workflows. In Bill-to/Ship-to transactions, businesses must capture the Ship-to GSTIN wherever the delivery location belongs to a registered GST person.

Earlier, businesses generally captured the Ship-to address, while GSTIN was optional or not consistently enforced in the API validation flow. That created traceability gaps when goods were billed to one GSTIN but delivered to another registered location.

The new requirement is meant to improve data quality across invoices, e-Way Bills and GST reporting. It does not stop genuine Bill-to/Ship-to transactions. It only expects the actual registered consignee to be identified correctly.

Before vs After

This before-after distinction matters. The update should not be read as a simple UI change. It changes how businesses maintain consignee master data and validate delivery-party GSTINs before document generation.

What Becomes Mandatory?

For applicable registered consignees, the Ship-to GSTIN must be captured correctly before generating the relevant document through the API process.

• Capture Ship-to GSTIN wherever the delivery party is registered under GST.
• Use URP only where the consignee is genuinely unregistered.
• Validate GSTIN authenticity before sending data to GSTN.
• Check the state code mapping between GSTIN and delivery details.
• Allow Bill-to and Ship-to GSTIN to differ only in valid Bill-to/Ship-to scenarios.

URP Rule for Unregistered Consignees

URP means Unregistered Person. If goods are delivered to an unregistered consignee, businesses should use URP as per the applicable system requirement instead of entering a wrong GSTIN.

This is where clean master data becomes important. ERP teams should classify registered branches, customer GSTINs, warehouses, project sites and unregistered delivery locations separately.

Voluntary e-Way Bill Closure Facility

GSTN is also introducing a voluntary e-Way Bill Closure facility. The feature helps eligible users mark that a goods movement has reached its logical completion instead of leaving the e-Way Bill to expire without an operational closure trail.

For businesses with high dispatch volumes, this can improve logistics control, reconciliation and internal audit readiness. It is voluntary, but teams should still decide whether it belongs in their dispatch SOP.

Compliance Risk Under GST

Incorrect consignee data can create mismatch risk between e-Invoice records, e-Way Bills, physical movement documents and GST return data. During verification, these mismatches can create unnecessary explanations for billing, dispatch and finance teams.

Where transport documents and actual goods movement do not align, businesses may face proceedings under Section 129/130 depending on facts. The safer approach is to validate consignee data before document generation.

Action Checklist Before 1 August 2026

• Review all Bill-to/Ship-to transaction flows.
• Update customer, branch, warehouse and consignee master data.
• Make Ship-to GSTIN mandatory in ERP where the consignee is registered.
• Create a URP rule for unregistered delivery parties.
• Test e-Invoice and e-Way Bill API payloads before the deadline.
• Train billing, dispatch and logistics teams on the new field requirement.
• Decide whether e-Way Bill closure should be added to internal SOPs.
• Run sample transactions for branches, project sites and third-party deliveries.

Who Is Most Affected?

• Manufacturers shipping directly to customer project sites.
• Distributors and FMCG companies with multiple warehouses.
• EPC, construction and infrastructure businesses.
• Businesses using third-party logistics or drop-shipment models.
• ERP-driven companies generating high volumes of e-Invoices and e-Way Bills.
• Accountants and GST consultants managing multi-location clients.

Frequently Asked Questions