Tax & Regulatory Updates
E-Invoice and E-Way Bill API Changes Took Effect From 1 August 2026
Businesses using ERP, GSP or API-based e-Invoice and e-Way Bill processes should check their systems after GSTN's August 2026 changes.
Dated note — the position described here reflects . Requirements change; confirm the current position before acting on it.
- Effective from
- Checked on
If your e-Invoice and e-Way Bill process runs through an ERP, GSP, ASP or another API integration, there is a change worth checking in the system rather than only reading about it.
GSTN introduced a set of API changes with effect from 1 August 2026.
One of the main changes relates to Bill-to / Ship-to transactions.
Where Ship-to details are provided and an e-Way Bill is required, the relevant API flow now requires the Ship-to GSTIN. Where a GSTIN is not available and the transaction permits it, “URP” may be used.
GSTN has also introduced validations around the Ship-to GSTIN, State Code and PIN Code. In Bill-to / Ship-to cases, the Bill-to and Ship-to GSTINs are expected to represent distinct persons and the system applies validations accordingly.
There is another change that is easy to misunderstand: voluntary closure of an e-Way Bill after delivery.
The word voluntary matters here.
This is not a new compulsory closure step for every e-Way Bill. The facility provides a way to record completion of the movement after delivery, and GSTN has also provided an API for system users that want to use it.
For businesses working through integrated systems, the practical questions are therefore quite straightforward:
Has the ERP or integration been updated for the revised fields and validations?
Are Bill-to / Ship-to transactions being mapped correctly?
Where Ship-to GSTIN is unavailable, is the system handling “URP” appropriately?
And if the business intends to use voluntary e-Way Bill closure, has that process actually been built into the operating workflow?
Businesses generating only occasional e-Way Bills manually may see limited impact. Businesses with higher transaction volumes and integrated invoicing systems should give the change more attention because incorrect field mapping can become an operational issue very quickly.
GSTN’s advisory dated 17 June 2026 stated that the changes would be implemented in production from 1 August 2026.
This note reflects the position checked on 5 September 2026. Businesses using ERP or API integrations should also check the current specifications and any later GSTN advisories relevant to their setup.