(INDIA) — Indian tax authorities are rolling out a mandatory Ship-To GSTIN field and a voluntary E-Way Bill Closure facility on the e-way bill portal in mid-June 2026, with production rollout scheduled for 15 June 2026.

The change applies to Bill-To/Ship-To e-way bills, a narrower category than the entire e-way bill system. In those transactions, users must capture the Ship-To GSTIN; if the consignee is unregistered, they must enter URP instead.

Authorities are also adding the closure feature as an optional post-delivery step. It lets users mark an e-way bill as closed after delivery is completed, creating a formal end point for that document without treating it as a cancellation.

That distinction sits at the center of the update. Cancellation remains the route for wrong or mistaken e-way bills, while E-Way Bill Closure serves as confirmation that delivery has been completed.

India’s e-way bill framework still follows the standard interstate rule that goods moving above Rs 50,000 require an e-way bill. States can set different thresholds for intrastate movement, leaving businesses to track both the general framework and local rules.

Non-compliance carries a direct financial and operational risk. Penalties can reach Rs 10,000 or the tax evaded, whichever is higher, and authorities can detain or seize both the goods and the vehicle.

Those baseline rules give the June changes their practical weight. A missing or incorrect consignee identifier in a Bill-To/Ship-To transaction can create trouble well beyond data entry, especially where goods move through layered supply chains before reaching the final recipient.

Bill-To/Ship-To structures are common in drop-ship, third-party logistics, warehousing and e-commerce arrangements, where the billed party and the physical delivery point do not always match. By making Ship-To GSTIN mandatory in those cases, the portal aims to sharpen recipient identification and improve reconciliation.

That is likely to matter most in transactions where multiple parties touch the goods but only one party receives them. A cleaner consignee record can reduce confusion between invoice details and delivery details, particularly where businesses rely on shared logistics networks or outsourced warehousing.

The new field does not apply to every e-way bill generated in the system. It applies specifically to Bill-To/Ship-To e-way bills, which means businesses must first identify whether a movement falls within that structure before changing their data capture process.

Where the consignee does not hold registration, the system will require URP in place of a GSTIN. That preserves a standardized entry even when the recipient sits outside the registered taxpayer base.

Closure adds a different layer of control. Suppliers, recipients, transporters, and drivers or other authorized persons can perform it, giving businesses several points in the delivery chain from which they can formally close an e-way bill once goods arrive.

Users can complete closure either e-way-bill-wise or date-wise. That gives companies handling smaller volumes the option to close individual documents, while businesses managing heavier daily dispatches can work through transactions in batches.

Operationally, the feature extends the life cycle of an e-way bill beyond generation and transit. It gives companies a portal-based way to record that delivery has ended, which can support internal tracking after the vehicle reaches the destination.

That function may prove useful in supply chains where one team raises the bill, another arranges transport, and a third confirms receipt at a warehouse or customer location. The ability to close the document through different actors reflects how freight operations often work in practice.

Suppliers will not hold exclusive control over that final step. Recipients can close the bill, and so can the transporter or driver, or another authorized person, which spreads responsibility across the transaction and may reduce delays where one participant is unavailable.

Technology providers are already on the clock. ERP vendors, GSPs, ASPs, and API integrators have been advised to complete testing before the production launch because the API changes are already available in sandbox mode.

That testing window matters for businesses that generate e-way bills directly from enterprise systems rather than typing each one on the portal. A mandatory new field in the Bill-To/Ship-To flow can break validation logic, data mapping or downstream reconciliation if software teams leave changes until rollout day.

GSPs and ASPs, which many companies use to connect tax and logistics systems with government platforms, face the same deadline pressure. Sandbox access gives them time to check whether Ship-To GSTIN, URP handling, and closure workflows pass cleanly through their integrations before 15 June 2026.

Businesses with large shipping volumes may need to review master data first. If invoice systems capture billing details but not the final consignee GSTIN in a structured way, teams may have to adjust order-entry fields, warehouse processes, and transporter instructions before the portal turns the rule on in production.

Companies using third-party fulfillment or warehousing will need the same discipline. A consignee mismatch in a drop-ship or warehousing transaction can become a compliance issue if the e-way bill does not carry the required Ship-To detail for that movement.

Internal ownership will also matter once the closure facility goes live. Firms that want to use the feature will need to decide whether the supplier, recipient, transporter or driver will close documents, and whether that happens transaction by transaction or in date-wise batches.

Some businesses may choose to leave closure to the receiving warehouse, especially where receipt confirmation already sits there. Others may assign it to transport teams to align the final portal action with proof of delivery and trip completion.

The feature remains voluntary, which means companies do not have to use it merely because it exists. Even so, its availability creates a new option for firms that want cleaner end-of-journey records inside the e-way bill system rather than relying only on offline delivery documents or internal logs.

June’s rollout does not alter the underlying compliance architecture. Goods valued above Rs 50,000 in the general interstate framework still need an e-way bill, intrastate thresholds can still vary by state, and the penalty exposure for non-compliance remains Rs 10,000 or the tax evaded, whichever is higher, alongside possible detention or seizure of goods and vehicle.

What changes on 15 June 2026 is the precision expected in one common transaction type and the formal closing option now attached to it. Businesses that routinely handle Bill-To/Ship-To movements, especially in warehousing, 3PL and e-commerce chains, now have less room for loose consignee data and more reason to finish system testing before the new fields and workflows go live.