On June 17, 2026, the Goods and Services Tax Network issued Advisory No. 664. This advisory outlines changes to the e-Invoice API, the e-Way Bill by IRN API, and a new optional e-Way Bill closure feature.
Businesses operating across Saudi Arabia and the UAE now have two major e-invoicing compliance deadlines to prepare for. Delaying ERP readiness could result in invoice processing failures and regulatory non-compliance.
On June 17, 2026, the Goods and Services Tax Network issued Advisory No. 664. This advisory outlines changes to the e-Invoice API, the e-Way Bill by IRN API, and a new optional e-Way Bill closure feature. These changes will go live on August 1, 2026. Sandbox testing is already available. Your team must ensure system readiness -regardless of whether you are using a direct API integration, an ERP system, or an ASP or GSP -before that date.
If your business issues invoices with different billing and shipping addresses, which applies to many manufacturers, distributors, and traders operating across various locations, the e-Invoice API now requires the Ship-to GSTIN as a conditionally mandatory field whenever Ship-to details are included and an e-Way Bill is also needed.
The field is ShipDtls.Gstin in the Generate IRN schema. If the Ship-to party is unregistered, you must enter “URP.” You cannot use the same GSTIN as the Bill-to party in the Ship-to field; otherwise, the system will reject it with error code 2323. Additionally, the Ship-to State Code must match the GSTIN state code, and the PIN Code must correspond to the Ship-to State.
GSTN has confirmed this requirement across four transaction flows: generating IRN and e-Way Bill together, generating an e-Way Bill using an existing IRN, Bill-to/Ship-to transactions, and combination transactions (which include both Bill-to/Ship-to and Bill-from/Dispatch-from details). This change impacts the core payload of most intercompany and multi-warehouse operations in India.
The API used to create an e-Way Bill through an IRN now includes a new mandatory field called “Gstin” under “ExpShipDtls.” There is also an optional field “TrdNm” (Trade Name). Any ERP system, GSP integration, or API setup that currently generates e-Way Bills via IRN and does not send this field will receive system error code 5001 starting August 1, 2026.
For B2B and SEZ transactions, the Ship details provided during IRN generation cannot be changed while generating an e-Way Bill using IRN. In cases of exports where no domestic GSTIN applies, enter ‘URP.’
GSTN has introduced a Voluntary Closure feature for e-Way Bills. This allows suppliers, recipients, transporters, or drivers to close an e-Way Bill once delivery is complete, creating an official record of goods movement completion.
Closure can be done EWB-wise or date-wise using the portal. An API has been made available for system integrators, requiring the EWB number, closure date, and remarks. GSTN has confirmed that post-closure actions such as Update Transporter and Extend Validity will still be permitted during the initial stabilisation period. Bulk API closure, driver-based closure via API, and a separate ‘Closed’ status are planned for a later phase.
Businesses using Odoo should review their GST integrations before August 1 to avoid invoice validation failures and disruptions to order processing. Any Odoo environment handling Bill-to/Ship-to transactions with integrated e-Way Bill generation needs to be verified and updated before the deadline.
The update focuses on the API payload level: ensuring the Ship-to partner’s GSTIN is assigned to the ShipDtls.Gstin field in outbound IRN calls, and that the ExpShipDtls.Gstin field is populated in the EWB-by-IRN flow. Odoo’s Accounting and Inventory modules already support multi-location operations and partner address management -the change sits at the integration layer, not in the platform itself.
The team at Greytrix Business Solutions is currently working on this compatibility update as part of ongoing GST compliance maintenance. For businesses that have not yet linked their Odoo environment with GSTN’s e-Invoice or e-Way Bill APIs, this deadline is also an important prompt -a compliant, API-connected tax workflow should be in place before system failures occur at month-end, not after.
✓ Identify all Bill-to/Ship-to and combination transactions in your current invoice processes.
✓ Confirm that Ship-to GSTIN or ‘URP’ is recorded in master data for all Ship-to parties.
✓ Verify that your ERP or API configuration sends ShipDtls.Gstin in the IRN+EWB combined flow.
✓ Check that the Gstin field in ExpShipDtls is filled for e-Way Bill by IRN API calls.
✓ Test all adjustments in the GSTN Sandbox environment before going live.
✓ Review B2B and SEZ transaction flows -Ship details cannot be modified after IRN in these cases.
✓ Inform finance and logistics teams about the new Voluntary EWB Closure feature.
Don't wait for a validation failure on August 2nd. Review your Odoo GST integration now and get compliant before the deadline -Talk to Greytrix Business Solutions
Yes. The Ship-to GSTIN requirement applies across all four flows. If Ship-to details are provided and an e-Way Bill is required, the GSTIN field must be populated -regardless of whether the e-Way Bill is generated at the same time as the IRN or separately.
Enter "URP" (Unregistered Person) in the Ship-to GSTIN field wherever the Ship-to party is unregistered or GSTIN is not applicable. This is the designated system value specified by GSTN.
No. GSTN's validation (error code 2323) rejects transactions where the same GSTIN appears in both fields. In a Bill-to/Ship-to transaction, the two parties must be distinct.
No. The facility is voluntary -it allows delivery completion to be recorded in the system for audit trail purposes, but it is not a compliance requirement.
Your Odoo e-Invoice and e-Way Bill API configuration must be updated to transmit the Ship-to GSTIN in the relevant payload fields. The Greytrix Business Solutions team can assess your current configuration and implement the required changes before August 1. Reach out here.
Greytrix Business Solutions (GBS) is a certified Odoo partner in India, helping manufacturers, distributors, and growing businesses implement and scale Odoo ERP with confidence. From consultation and configuration to data migration, GST localisation, team training, and post-go-live support, GBS delivers end-to-end Odoo services built around how your business actually works.
Backed by the Greytrix Group’s 25 years of ERP expertise, GBS brings the implementation experience and regional knowledge that turns a software investment into a genuine business advantage.
