GST E-Invoicing and E-Way Bills after the August 2026 Changes
Introduction
Goods do not always move directly from the supplier to the buyer. A company may order machinery for delivery to a factory, while a distributor may ask a manufacturer to send goods directly to its customer.
These arrangements are common, but they create an important GST question: whose details should appear as the Bill to party, and whose details should appear as the Ship to party?
The Goods and Services Tax Network addressed this issue in an advisory dated 17 June 2026. From 1 August 2026, revised system checks apply when an e way bill is generated with an Invoice Reference Number, or IRN, and when an e way bill is generated later using an existing IRN. The changes mainly require more accurate Ship to information and introduce an optional facility for closing an e way bill after delivery.
Why the changes matter
An e invoice records the commercial and tax details of a sale. An e -way bill records the physical movement of goods. In a simple sale, the buyer and delivery location may be the same. Problems arise when the person receiving the invoice is different from the person or location receiving the goods.
For example, Company A buys equipment but asks the supplier to deliver it directly to Company B, its contract manufacturer. Company A is the Bill to party and Company B is the Ship to party. The updated system connects both sides of the transaction more clearly. It checks whether the GSTIN, State code and PIN code used for the delivery location make sense together.
The change is therefore not just about adding another field. GSTN is checking whether the invoice, e way bill and actual movement of goods tell the same commercial story.
When the Ship to GSTIN is required
Where an IRN and e way bill are generated together, the Ship to GSTIN becomes conditionally mandatory. If Ship to details are entered and an e way bill is required, the Ship to GSTIN must also be provided. Where the person at the delivery location is unregistered, or a GSTIN does not apply, URP ( “Unregistered Person”) may be used where appropriate.
For an e way bill generated later through an existing IRN, GSTN has added a mandatory GSTIN field under the expanded Ship to details. A trade name field is also available.
The practical point is straightforward: the sales and accounts teams should confirm the final delivery party and address before the IRN is generated. If the correct details arrive later, the system may reject the e way bill or prevent important information from being changed.
Bill to and Ship to checks
In a genuine Bill to and Ship to transaction, the Ship to GSTIN cannot be the same as the Bill to GSTIN. The system may also reject an invalid GSTIN, a State code that does not match the GSTIN, or a PIN code that is inconsistent with the State.
This is likely to expose old or incomplete customer data. A valid GSTIN may still fail if the delivery address has the wrong PIN code or State. Businesses should therefore review customer and delivery master records instead of waiting for an urgent shipment to reveal the problem.
Using URP correctly
URP may be used where the Ship to party is unregistered or no GSTIN applies. For instance, a registered dealer may buy goods and ask the supplier to deliver them directly to an unregistered customer. The dealer remains the Bill to party, while URP may be appropriate for the Ship to party.
URP should not be used simply because an employee cannot find the GSTIN. Before selecting it, the business should confirm the Ship to party’s legal name, complete address, registration status and the reason why delivery is being made to someone other than the buyer. That confirmation should be kept with the purchase order, sales order or delivery instruction.
Exports B2B and SEZ transactions
The system treats exports differently from domestic business to business and Special Economic Zone transactions. For export e way bills generated from an IRN, Ship to details may be replaced during e way bill generation. This recognises that an export may involve an overseas buyer, an Indian port, a freight forwarder and more than one logistics location.
For B2B and SEZ supplies, Ship to details entered while generating the IRN generally cannot be replaced when the e way bill is generated later. A missing Ship to GSTIN may be supplied at the e way bill stage, subject to validation, but other recorded Ship to details cannot simply be rewritten.
This makes last minute redirection more difficult. Businesses should set a cut off after which a change of warehouse, project site or customer requires approval from the tax team.
Bill from and Dispatch from transactions
Sometimes the supplier issuing the invoice is not the location from which the goods leave. A registered office may issue the invoice while a third party warehouse dispatches the goods. If the goods also go to a separate Ship to party, four points must be recorded correctly: the invoice issuer, the dispatch location, the buyer and the final recipient or delivery location.
The invoice, e way bill, warehouse release and transport documents should describe the same movement. Businesses using warehouses, contract manufacturers or drop shipment arrangements should test these cases separately.
Voluntary closure of e waybills
GSTN has also introduced a voluntary facility for closing an e waybill after delivery. Closure may be completed by the supplier, recipient, transporter, driver or another authorised person whose mobile number has been provided. It can be done for individual e waybills or date wise.
Closure is not the same as cancellation. Cancellation removes an e way bill in permitted circumstances; closure records that the delivery has been completed. Used properly, closure can help reconcile dispatches with proof of delivery, identify consignments that remain open and create a clearer audit trail.
A useful internal rule is to close the e way bill only after receiving a delivery acknowledgement or electronic proof of delivery. Responsibility should be assigned clearly so the supplier, transporter and driver do not each assume that someone else will complete the task.
What businesses should change
The August 2026 update should be treated as a workflow and data project, not merely a software patch. Businesses should consider the following steps:
- Store Bill to and Ship to names, GSTINs, State codes and PIN codes separately.
- Prevent users from leaving the Ship to GSTIN blank when it is mandatory.
- Check that the GSTIN, State code and PIN code match before submission.
- Allow URP only after the user confirms why no GSTIN applies.
- Warn users that B2B and SEZ Ship to details generally cannot be replaced after IRN generation.
- Test ordinary sales, exports, SEZ supplies, unregistered recipients, drop shipments and third party warehouse dispatches.
- Connect voluntary closure to proof of delivery and reconciliation records.
- Train sales, accounts, warehouse, logistics and tax teams on the same process.
The risk of mismatched documents
A successful system submission does not always mean the transaction is fully compliant. The e invoice, e way bill, tax invoice, purchase order, delivery challan, lorry receipt and proof of delivery should all describe the same transaction.
Common problems include last minute delivery changes, wrong GSTINs, misuse of URP and invoices generated before delivery instructions are final. These mismatches can delay dispatches and create questions during GST checks or input tax credit disputes.
The strongest control is a shared process. Sales, finance, warehouse, logistics and tax teams should all work from the same verified instruction and preserve any customer request that changes the place of delivery.
Conclusion
The main purpose of the August 2026 changes is to ensure that the e-invoice, e-way bill and actual movement of goods contain accurate and matching information. Businesses must therefore identify the buyer, the person receiving the goods, the place from which the goods are dispatched and the final delivery address with greater care. The changes also leave less room to correct delivery details in B2B and SEZ transactions after an Invoice Reference Number (IRN) has been generated. By collecting the correct information at the beginning of the transaction, businesses can reduce the risk of rejected e-way bills, delayed shipments, input tax credit disputes and questions during GST audits.
Businesses should use these changes as an opportunity to update their customer and delivery records, confirm delivery instructions before generating an IRN and improve coordination between their sales, accounts, warehouse, logistics and tax teams. They should also consider linking the voluntary closure of an e-way bill with proof of delivery. When the invoice documents and the actual movement of goods match from the beginning, GST compliance becomes simpler and the business is less likely to face avoidable delays or disputes.
