India’s e-Way Bill system continues to become more closely connected with e-Invoicing, GST registrations and digital transportation records. During 2026, GSTN announced important changes involving Ship-To GSTIN details and the closure of e-Way Bills after delivery.
However, businesses must note an important development: the proposed mandatory Ship-To GSTIN and voluntary e-Way Bill closure changes have currently been placed on hold. The earlier updates published in May 2026 were subsequently marked as withdrawn by the official e-Way Bill API portal on 30 July 2026.
Transporters, manufacturers, distributors and shippers should therefore understand three things clearly:
- Which proposed changes are currently on hold
- Which 2026 changes are already active
- Which existing compliance controls continue to apply
Current Status: Two Major Changes Are on Hold
GSTN had initially planned to introduce two significant enhancements:
- Mandatory capture of the Ship-To GSTIN in Bill-To/Ship-To transactions
- A voluntary facility for closing e-Way Bills after successful delivery
These changes were originally proposed for implementation during 2026. However, the official e-Way Bill release notes now state that both enhancements have been kept on hold. The earlier update dated 22 May 2026 has also been marked as withdrawn.
Therefore, as of 4 August 2026, businesses should not treat these proposed features as mandatory operational requirements unless GSTN announces a fresh implementation date.
1. Mandatory Ship-To GSTIN: What Was Proposed?
In a Bill-To/Ship-To transaction, the party receiving the invoice and the party physically receiving the goods may be different.
For example, a company’s head office may purchase goods and receive the invoice, while the goods are delivered directly to one of its customers, dealers or another registered entity.
The proposed change would have required businesses to compulsorily enter the GSTIN of the actual consignee in the Ship-To field when the consignee was registered under GST.
GSTN had also clarified that a genuine Bill-To/Ship-To transaction should normally involve three different parties. Where the Bill-To and Ship-To GSTIN were the same, the transaction was expected to be treated as a regular transaction rather than a Bill-To/Ship-To transaction.
What Businesses Should Do Now
Because this validation is currently on hold, the new Ship-To requirement should not yet be treated as mandatory.
Nevertheless, shippers should continue maintaining accurate records of:
- The buyer or Bill-To party
- The actual delivery location
- The consignee receiving the goods
- The applicable GSTIN for each location
- Dispatch-from and ship-to addresses
Maintaining this information will reduce disruption whenever GSTN reintroduces the validation.
2. Voluntary E-Way Bill Closure: What Was Proposed?
At present, an e-Way Bill may remain in the system even after the goods have reached their destination. There has traditionally been no separate action confirming that the delivery has been completed.
The proposed e-Way Bill closure facility was intended to allow an authorised stakeholder to mark an e-Way Bill as closed after successful delivery.
The proposed framework distinguished closure from cancellation:
- Cancellation applies when an e-Way Bill was generated incorrectly or when the goods were not transported.
- Closure would confirm that the goods had been delivered and the movement was complete.
The original GSTN advisory indicated that closure could be performed on the date of delivery or the immediately succeeding day. The facility was intended to be voluntary rather than compulsory.
However, the closure functionality has also been placed on hold. Businesses do not currently need to close every e-Way Bill after delivery.
Why Transporters Should Still Prepare
Even though closure is not currently active, transporters should improve their proof-of-delivery processes by capturing:
- Delivery date and time
- Receiver’s name
- Digital or physical acknowledgement
- Shortage and damage details
- Vehicle arrival and unloading time
- Delivery challan or goods receipt confirmation
These records will make future e-Way Bill closure easier to manage and will also strengthen the company’s audit trail.
3. Invoice Amount Validation Relaxation Is Active
One confirmed e-Way Bill system change became effective on 1 February 2026.
Earlier, the portal could generate error code 620 when the total invoice value was lower than the combined taxable value and tax value. This created problems for products where tax is calculated using a Retail Sale Price or RSP-based mechanism.
GSTN has relaxed this validation for specified HSN codes covered under Notification No. 20/2025–Central Tax. The relaxation applies where at least one line item belongs to an eligible RSP-based HSN category.
What This Means for Shippers
Businesses dealing in RSP-based goods should:
- Verify whether their HSN codes are covered by the notification
- Keep item-level HSN classifications accurate
- Avoid changing invoice values merely to bypass portal validation
- Update ERP validation logic for the eligible products
- Test mixed invoices containing both regular and RSP-based goods
This relaxation is limited to eligible HSN codes. It should not be treated as a general relaxation for every invoice.
4. The 180-Day Document Date Restriction Continues
An e-Way Bill cannot be generated when the underlying invoice, bill of supply or delivery challan is more than 180 days old.
The system compares the document date with the date on which the e-Way Bill is being generated. Where the permitted period has passed, the portal may reject the request. This validation has been effective since 1 January 2025 and remains operationally important in 2026.
Practical Impact
Shippers should avoid holding old invoices and attempting to generate e-Way Bills several months later. Delayed dispatches should be reviewed by the accounts and GST teams before transportation begins.
ERP systems should also display warnings when the document date approaches the permitted limit.
5. E-Way Bill Extensions Beyond 360 Days Are Restricted
The portal also restricts the extension of an e-Way Bill beyond 360 days from its original generation date.
This is particularly relevant for:
- Long-running project cargo
- Machinery movement
- Over-dimensional consignments
- Goods stored temporarily in warehouses
- Multimodal road and rail transportation
- Shipments affected by prolonged disputes or detention
Transporters should not depend on repeated extensions as a permanent solution. Exceptionally delayed consignments should be escalated to the shipper and GST compliance team well before the maximum period is reached.
6. Two-Factor Authentication Remains Mandatory
Two-factor authentication has been mandatory for all e-Way Bill taxpayers and transporters since 1 April 2025.
Businesses should ensure that access is not dependent on the personal mobile number of only one employee.
Recommended controls include:
- Registering authorised users properly
- Keeping recovery options updated
- Removing access when employees leave
- Avoiding shared login credentials
- Maintaining backup users for night and emergency dispatches
- Testing OTP access before high-volume dispatch periods
Failure to manage authentication can delay vehicle movement even when all transportation documents are ready.
7. Additional Supplier and Railway Validations
The e-Way Bill system has also introduced additional validations that continue to affect operations in 2026.
A GSTIN registered only for TDS or TCS purposes cannot be entered as the supplier GSTIN while generating an e-Way Bill.
For rail transportation, the Railway Receipt number entered as the transport document number must carry the appropriate prefix:
- P for PMS
- F for FOIS
- L for leased wagons
These validations were added in December 2025 and remain relevant to businesses handling rail and multimodal freight.
What Transporters Must Change in Their Daily Operations
Transporters should focus on data accuracy rather than waiting for a portal error.
Before dispatching a vehicle, verify:
- E-Way Bill number and validity
- Invoice or delivery challan number
- Document date
- Consignor and consignee GSTIN
- Actual delivery address
- Transporter ID
- Vehicle number
- Transport mode
- Approximate distance
- HSN and invoice values
- Railway Receipt details, where applicable
When a vehicle is changed during transit, the transportation details must be updated before further movement. Dispatch, transshipment and delivery teams should have clearly assigned responsibilities for these updates.
What Shippers and Manufacturers Should Do
Shippers should review their accounting and ERP systems to ensure that invoice, consignee and transport information flows correctly into the e-Way Bill portal.
Particular attention should be given to:
- Bill-To/Ship-To orders
- Direct customer deliveries
- Depot and warehouse transfers
- Job-work movements
- Rail dispatches
- Old invoices awaiting dispatch
- RSP-based products
- Proof-of-delivery records
Businesses using APIs, GSPs or custom ERP integrations should keep the proposed Ship-To GSTIN and closure changes ready behind configurable settings rather than enforcing withdrawn validations in their production workflow.
A Practical 2026 Compliance Checklist
Before generating an e-Way Bill:
- Confirm that the document is within the permitted date range.
- Validate supplier, buyer and consignee GSTINs.
- Select the correct transaction type.
- Verify the HSN codes and invoice values.
- Confirm the vehicle or railway document details.
- Ensure that authorised users can complete two-factor authentication.
During transportation:
- Update the vehicle number after transshipment.
- Monitor the e-Way Bill validity period.
- Record breakdowns, delays and route changes.
- Apply for validity extension within the permitted window.
- Keep the driver informed about the documents carried with the vehicle.
After delivery:
- Collect proof of delivery.
- Record shortages or damages.
- Close internal trip and consignment records.
- Retain invoice, e-Way Bill and delivery documents together.
- Monitor GSTN announcements regarding the proposed closure facility.
Conclusion
The most important e-Way Bill lesson for 2026 is that businesses must distinguish between announced changes and changes that are actually in force.
Mandatory Ship-To GSTIN capture and voluntary e-Way Bill closure were proposed, but both have currently been placed on hold. Meanwhile, controls such as two-factor authentication, the 180-day document date restriction, the 360-day extension limit and newer invoice-value validations continue to affect daily transportation operations.
Transporters and shippers should use this period to clean their master data, strengthen proof-of-delivery processes and prepare their ERP systems. Being ready before the next GSTN announcement will help prevent failed e-Way Bill generation, delayed vehicles and compliance disputes.
Disclaimer: This article is based on GSTN and e-Way Bill portal updates available as of 4 August 2026. Businesses should review the latest official advisories or consult a GST professional before making legal or system-level compliance decisions.