Timeline update: GSTN has deferred two major e-way bill changes from June 15, 2026 to August 1, 2026: mandatory Ship-To GSTIN in Bill-To/Ship-To transactions, and the voluntary e-way bill closure facility. Use the additional 6 weeks to update your ERP, billing software, and internal processes.
Key Takeaways
- Mandatory Ship-To GSTIN: From August 1, 2026, every Bill-To/Ship-To e-way bill must capture the GSTIN of the party receiving the goods (the Ship-To party). The portal will reject requests where this field is blank.
- Voluntary closure: A new feature allowing the consignee or transporter to close an e-way bill on the delivery day or the next day, confirming receipt of goods.
- Original date was June 15, 2026. GSTN deferred both features to August 1, 2026 after receiving representations from trade bodies, GST Suvidha Providers (GSPs), and ERP vendors.
- Who is affected: Any business that uses Bill-To/Ship-To supply chains, e-commerce sellers using fulfilment centres, and manufacturers shipping to distributors who re-route goods to retail.
- Action needed: Update ERP/billing software API integrations, train dispatch teams on the closure feature, and map Ship-To GSTINs for recurring delivery destinations.
On June 10, 2026, GSTN announced a 6-week deferral of two e-way bill enhancements that were set to go live on June 15. The reason was straightforward: ERP vendors, GSPs, and transporters needed more time to update their systems. The features themselves are not cancelled. They take effect from August 1, 2026.
This is not a cosmetic change. The mandatory Ship-To GSTIN requirement fundamentally changes how Bill-To/Ship-To e-way bills are generated. If your supply chain involves third-party deliveries (goods billed to one entity but shipped to another), you need to prepare before August 1.
Looking for expert help with e-way bill compliance and GST filing support? The team at Tax Garden, based in Kondapur, Hyderabad, helps Indian SMEs stay compliant end-to-end: filings, notices, and advisory, all in one place.
What Is Changing: Two New Features
1. Mandatory Ship-To GSTIN in Bill-To/Ship-To Transactions
Currently, when generating an e-way bill for a Bill-To/Ship-To transaction, the Ship-To GSTIN field is optional. From August 1, 2026, it becomes mandatory.
A Bill-To/Ship-To transaction occurs when:
- Party A (the supplier) bills Party B (the buyer/principal)
- But the goods are physically shipped to Party C (the consignee/delivery location)
Today, you can generate this e-way bill with only Party B's GSTIN and a delivery address. After August 1, you must also provide Party C's GSTIN in the Ship-To field. If Party C is unregistered, the rules for handling unregistered recipients will apply (likely requiring "URP" designation, consistent with existing GSTR-1 Ship-To reporting).
Why this matters: The department wants to close the gap between e-way bill data and GSTR-1 data. In GSTR-1, Bill-To/Ship-To invoices already require both GSTINs (in Table 4). But e-way bills have been inconsistent, making reconciliation unreliable. This change aligns e-way bill data with invoice-level reporting.
2. Voluntary Closure of E-Way Bills
Currently, an e-way bill remains "active" until its validity period expires (based on distance: 200 km per day for over-dimensional cargo, 100 km per day for regular). There is no mechanism to close it early when goods are delivered.
From August 1, 2026, the consignee or the transporter can voluntarily close an e-way bill:
- On the day of delivery, or
- On the next calendar day
Why this matters: Open e-way bills with remaining validity have been used to cover undocumented movement of goods. If an e-way bill is valid for 3 days but goods are delivered on day 1, the remaining 2 days of validity could theoretically cover a second, unreported shipment. The closure feature eliminates this window.
This is voluntary, not mandatory. But businesses should expect it to become a factor in audits and inspections. A pattern of e-way bills that are never closed despite short delivery distances could attract scrutiny.
Why the Deferral from June 15 to August 1
GSTN received representations from:
- Trade bodies and industry associations highlighting the need for operational process changes (training dispatch staff, updating SOPs)
- GST Suvidha Providers (GSPs) who integrate e-way bill generation into their platforms and needed time to update API calls
- ERP vendors (Tally, SAP, Oracle, Zoho, and others) whose e-way bill modules required code changes to make Ship-To GSTIN a mandatory field
- Transporters and logistics companies who generate e-way bills in bulk and needed to restructure their data capture workflows
The deferral gives all stakeholders until August 1 to complete system modifications and testing.
Who Is Affected
Directly Affected
- Manufacturers who bill distributors but ship directly to retailers or end-customers
- E-commerce sellers using fulfilment centres (goods shipped from a warehouse that is not the seller's registered place of business)
- Traders in Bill-To/Ship-To supply chains, common in FMCG, pharma, and auto parts distribution
- Job workers receiving goods from principals for processing (the principal bills the job worker but goods may ship from a third-party vendor)
Indirectly Affected
- Transporters who generate e-way bills on behalf of consignors. They will need the Ship-To GSTIN before they can generate the bill.
- GSP/API users whose automated e-way bill generation scripts will fail if the Ship-To GSTIN field is not populated for Bill-To/Ship-To transactions.
Not Affected
- Regular point-to-point shipments where the buyer and receiver are the same entity. These do not have a separate Ship-To party.
- Exempt supplies and goods that do not require e-way bills (consignment value below Rs 50,000, or goods exempt from e-way bill requirements).
How to Prepare Before August 1
Step-by-Step Guide
Identify Bill-To/Ship-To Transactions
Collect Ship-To GSTINs
Update ERP and Billing Software
Update API Integrations
Train Dispatch and Logistics Teams
Test End-to-End Before Go-Live
Impact on ERP and Billing Software
If your business uses software to generate e-way bills (Tally, SAP, Zoho Books, Busy, GIDDH, or a custom solution), the following changes are needed:
API-level change: The shipToGstin field in the e-way bill API request body transitions from optional to mandatory for Bill-To/Ship-To transactions. API calls without this field will receive an error response.
UI-level change: The Ship-To GSTIN input field in the e-way bill generation form should be marked as required. Validation should prevent form submission without the GSTIN when a Bill-To/Ship-To flag is set.
Data migration: If your system stores customer data without a dedicated Ship-To GSTIN field, you may need to add one. Alternatively, your system should pull the GSTIN from the delivery address record if it is linked to a registered entity.
Most major ERP vendors have already released or announced updates. Contact your vendor for the timeline of their patch.
What Happens If You Are Not Ready by August 1
The e-way bill portal will reject Bill-To/Ship-To e-way bill generation requests where the Ship-To GSTIN is missing. This means:
- Goods cannot move without a valid e-way bill
- Delivery delays until the GSTIN is obtained and the e-way bill is generated
- Potential penalties for moving goods without a valid e-way bill (detention, seizure, penalty equal to tax payable or Rs 25,000, whichever is higher, under Section 129 of the CGST Act)
Do not treat this as a soft launch. The system enforcement is binary: the field is either populated or the request fails.
Source and Verification
The deferral was announced by GSTN on June 10, 2026. The original implementation date of June 15, 2026 was communicated via the e-way bill portal (ewaybillgst.gov.in). The revised date of August 1, 2026 is confirmed by GSTN advisory. Ship-To GSTIN requirements align with existing GSTR-1 Table 4 reporting for Bill-To/Ship-To invoices under Section 31 of the CGST Act. Voluntary closure provisions are part of the ongoing e-way bill system enhancements under Rule 138 of the CGST Rules. All information verified against GSTN advisories and CBIC notifications as of June 2026.