e-Invoice Update: Ship-to GSTIN Becomes Mandatory from August 1, 2026

GSTN has issued a new advisory outlining important changes to the e-Invoice and e-Way Bill API systems, effective from August 1, 2026. The most significant change: when Ship-to information is present in a B2B invoice, the Ship-to GSTIN becomes mandatory. This affects businesses involved in bill-to ship-to transactions where goods are delivered to a location different from the billing address.

What is a Bill-to Ship-to Transaction?

In a bill-to ship-to arrangement, Company A bills Company B, but the goods are delivered directly to Company C (a depot, warehouse, or branch of Company B in a different state). Under GST, this type of transaction requires careful reporting because the place of supply, ITC eligibility, and e-way bill requirements depend on where the goods actually go — not where the invoice is raised.

What the New API Rule Requires

When Ship-to information is present in the IRN (Invoice Reference Number) API call, the Ship-to GSTIN must now be provided. If the consignee at the ship-to location is unregistered, the value to pass is URP (Unregistered Person) — a defined code, not a blank field. In B2B and SEZ transactions, any Ship-to details entered during IRN generation will not be overridden during e-Way Bill creation.

Voluntary Closure of e-Way Bill Also Delayed

GSTN had also planned to introduce Voluntary Closure of the e-Way Bill — a functionality allowing businesses to close an active e-way bill once the movement of goods is complete, before the automatic expiry. This functionality was originally scheduled for June 15, 2026, but has been postponed along with the Ship-to GSTIN field. Both features will now go live on August 1, 2026.

Who is Affected?

Businesses with aggregate annual turnover above the e-invoicing threshold who regularly handle bill-to ship-to transactions are directly affected. This includes manufacturers supplying to dealer networks, distributors supplying to multi-location buyers, e-commerce operators using third-party warehouses, and exporters using CHA or freight forwarder addresses at the port.

Action Points Before August 1, 2026

Review your billing software or ERP to confirm whether Ship-to GSTIN is captured in your invoice master data. For every delivery location that belongs to a GST-registered entity, collect and store the Ship-to GSTIN. For delivery locations with unregistered parties, ensure your system passes URP as the Ship-to GSTIN in the API call. Test your IRN generation flow with the Ship-to GSTIN field populated before the go-live date. Coordinate with your IT or software vendor to update API integration before July 31, 2026.

Consequence of Non-Compliance

From August 1, 2026, IRN generation will fail if Ship-to information is present but Ship-to GSTIN is missing. A failed IRN means the invoice is not a valid GST invoice — your buyer cannot claim ITC on it, and you face exposure under the e-invoicing mandate. With GSTR-3B outward liability now hard-locked from GSTR-1 data, IRN failures will cascade into return-filing problems.

Disclaimer: Refer to the official GSTN advisory for exact API specifications. Consult your CA or IT team for implementation.