What the E-Way Bill New Rules 2026 Actually Change

Two things change on 1 August 2026, and it is worth being precise about both, because a good deal of the commentary circulating has blurred them together.

The first is the mandatory capture of the Ship-To GSTIN in Bill-To and Ship-To transactions. The second is a voluntary facility to close an e-Way Bill once delivery is complete. One of these can stop your dispatch tomorrow. The other is an optional housekeeping improvement that most businesses will adopt slowly.

How the timeline arrived here

GSTN issued an advisory on 21 May 2026 introducing both changes, with a proposed production rollout of 15 June 2026. Representations followed almost immediately from trade bodies, ERP vendors, GST Suvidha Providers, Application Service Providers and private Invoice Registration Portals, all making the same point: the systems work was real and six weeks was not enough.

A further advisory on 9 June 2026 deferred the rollout to 1 August 2026. Then, on 17 June 2026, GSTN published the detailed specifications covering the e-Invoice API, the e-Way Bill by IRN API and the new EWB Closure API, and released them into the NIC sandbox for testing ahead of production.

That sequence tells you something useful. The department has already granted the one extension it was going to grant. Planning for a second deferral would be an unwise way to run a dispatch operation.

The Framework These Rules Sit Inside

Before the new requirements make sense, the underlying scaffolding is worth restating, because a surprising number of disputes arise from misunderstanding the basics rather than the amendments.

Where the obligation comes from

The e-Way Bill is mandated by Section 68 of the CGST Act, 2017, read with Rule 138 of the CGST Rules, 2017. The document itself is Form GST EWB-01, and where several consignments travel in one vehicle they can be linked under a consolidated e-Way Bill in Form GST EWB-02.

Every generated document carries a unique 12-digit e-Way Bill Number, or EBN. The system has been running nationally since April 2018 and now processes roughly four crore inter-state and eight crore intra-state e-Way Bills every month, which gives some sense of why the department cares about data quality in it.

When an e-way bill is required

The general trigger is the movement of goods of consignment value exceeding ₹50,000. That threshold applies to inter-state movement. For movement within a state, the position varies: several states have set higher limits, in some cases up to ₹2,00,000, so the applicable intra-state threshold is a state-specific question rather than a national one.

Movement can be in relation to a supply, for reasons other than supply such as a stock transfer or job work, or on account of an inward supply from an unregistered person. The obligation can fall on the consignor, the consignee, or the transporter depending on who causes the movement.

Validity and the Part B clock

This trips people up constantly, so it is worth stating plainly. Validity does not begin when you complete Part A. It begins from the first entry of Part B, meaning the first time a vehicle number or transport document number is recorded.

For regular cargo, validity is one day for every 200 kilometres or part thereof. For over-dimensional cargo and certain multimodal shipments, it is one day for every 20 kilometres. Validity expires at midnight on the last day.

A worked example makes the arithmetic obvious. A consignment travelling 310 kilometres by regular vehicle gets one day for the first 200 kilometres, plus one more day for the remaining 110 kilometres, because any part of the next 200-kilometre bracket counts as a full day. Total validity: two days.

Where a journey cannot be completed in time, a transporter may extend validity by updating Part B and giving a reason. The extension window runs from eight hours before expiry to eight hours after it. Accepted reasons include vehicle breakdown, trans-shipment delay, natural calamity and law-and-order disruption.

E-Way Bill New Rules 2026: Mandatory Ship-To GSTIN

Now to the change that matters most. To understand it, start with the transaction pattern it governs.

What a Bill-To / Ship-To transaction is

A Bill-To / Ship-To transaction is any movement where the party you invoice and the party you deliver to are different entities or different registered locations. It is not an exotic arrangement. It is how a large share of Indian trade routinely works.

A retail chain’s procurement office in Bengaluru places an order and receives the invoice. The goods, five hundred cartons of packaged foods, travel directly to the chain’s distribution centre in Nagpur. One invoice, two destinations, and until now the Nagpur GSTIN could be left blank on the e-Way Bill.

The blind spot this closes

Consider what that gap allowed. The e-Way Bill could be generated carrying only the billing party’s GSTIN. The system therefore held no record of where the goods physically ended up. Three problems followed.

• Diversion in transit. Goods could be redirected mid-journey with no GST trail showing it.
• Classification disputes. Arguments arose over whether the actual delivery constituted a further taxable supply.
• Input tax credit on goods never received. The invoice party could claim credit for goods that physically never entered its premises, and the data offered no contradiction.

Auditors have flagged the mismatch between billing GSTIN and delivery GSTIN for years. The new requirement is a direct response.

What exactly became mandatory

From 1 August 2026, where Ship-To details are furnished and an e-Way Bill is to be generated, the Ship-To GSTIN must be furnished too. The portal will not allow the document to be generated without it. Where the consignee is an unregistered person, the value URP is entered instead, and the system accepts it.

That URP clarification matters more than it might appear. When the requirement was first announced, a good deal of alarm came from businesses whose consignees genuinely hold no registration: small retailers, individual buyers, unregistered project sites, certain government warehouses. GSTN addressed the point directly rather than leaving it to interpretation.

The validations you will actually meet

Alongside the mandatory field come system checks that will reject data your existing process may have tolerated for years:

• The Ship-To GSTIN is validated for authenticity against the registration database.
• The state code must be consistent with both the GSTIN and the PIN code supplied.
• The same GSTIN cannot appear in both the Bill-To and the Ship-To fields.
• For business-to-business and SEZ transactions, the Ship-To GSTIN is fixed at IRN generation and cannot be overridden when the e-Way Bill is created afterwards.
• Export transactions are excluded from the requirement.

The fourth point reverses a widespread operational habit. Many dispatch desks have treated the e-Way Bill stage as the place to correct consignee details discovered late. That window is closing. Whatever is locked in at IRN generation governs the movement.

There is a second exposure beyond generation failure, and it is the more expensive one. Once the field is populated, any mismatch between the Ship-To GSTIN on the e-Way Bill and the recipient’s GSTIN on the tax invoice becomes a visible discrepancy in departmental data. That can attract detention under Section 129 of the CGST Act or confiscation proceedings under Section 130 — and both begin at a roadside check post.

The Voluntary E-Way Bill Closure Facility

The second change is gentler, and genuinely useful. Once goods have been delivered, the e-Way Bill can now be formally closed.

Closure is not cancellation

These two words describe opposite situations, and conflating them causes real errors in practice.

Cancellation means the e-Way Bill should never have existed. The document was raised in error, or the movement never happened. It must be done within 24 hours of generation, and it voids the document.

Closure means the opposite: the movement happened and finished successfully. It records completion rather than erasing the record. Closure is permitted on the day of delivery or the immediately succeeding day.

Who can close, and what the system needs

Closure can be initiated by the supplier, the recipient, the transporter, the driver, or any authorised person whose mobile number is recorded against the document. That breadth is deliberate; the person who knows delivery is complete is often the driver, not the accounts team.

The closure API takes three inputs: the e-Way Bill number, the closure date, and remarks.

Why bother with an optional step

A fair question, given nothing compels you. Three reasons make it worth building into your process.

First, an open e-Way Bill sitting in the system long after the goods arrived is an unexplained data point. In an environment where the department increasingly reads patterns rather than individual documents, unexplained data points invite questions.

Second, closure completes the digital trail from dispatch to receipt. That converts your logistics record into something defensible during an audit rather than something you reconstruct from delivery challans and email.

Third, it costs a few seconds per consignment. Few compliance improvements offer that ratio.

The Rules from 2025 That Still Govern Every Dispatch

A guide to the e-way bill new rules 2026 would be incomplete if it covered only August. Three earlier changes remain fully in force, and in day-to-day operations they cause more disruption than the new ones, precisely because businesses have stopped thinking about them.

The 180-day document rule

Since 1 January 2025, an e-Way Bill cannot be generated against any document — invoice, credit note or delivery challan — dated more than 180 days before the generation date. The portal blocks the attempt and returns error code 820.

The rule was introduced through a GSTN advisory dated 17 December 2024, and its purpose is to stop backdated or stale documents being used to paper over movements after the fact.

Where does this bite in practice? Goods returned and re-dispatched much later. Long-running project supplies invoiced early. Warehouse stock moved against an old challan. Any process where paperwork and physical movement drift apart by six months will now fail, and the failure comes with no warning until someone tries to generate.

The 360-day extension cap

A related limit applies to extensions. Total extension cannot run beyond 360 days from the original date of generation. An e-Way Bill generated on 1 April 2026 cannot be extended past late March 2027.

This affects a narrow group — typically project cargo, plant relocation and consignments held up in prolonged disputes — but for that group it is absolute.

Multi-factor authentication

MFA is now mandatory for every user at every turnover level. Logging in requires a username, a password, and an OTP delivered to the registered mobile number or through the Sandes app.

The rollout was gradual, which is why some businesses were caught late. It applied to taxpayers above ₹100 crore turnover from August 2023, became optional above ₹20 crore from September 2023, was reduced to ₹20 crore in January 2025 and ₹5 crore in February 2025, and finally became mandatory for all remaining taxpayers and users from 1 April 2025.

The E-Way Bill 2.0 portal

Launched in July 2025 at ewaybill2.gst.gov.in, this second portal runs in parallel with the original rather than replacing it, with data synchronised between the two.

Its practical value is continuity. Part B can be updated and validity extended from either portal, and transporter details sync automatically. When one portal has an outage — which historically has happened at the worst possible moments — dispatch need not stop. Make sure your team knows the second address exists and has working credentials for it.

Which Businesses Are Most Exposed

The Ship-To GSTIN requirement does not land evenly. Three business models carry Bill-To / Ship-To transactions as a structural feature rather than an occasional exception, and they should treat this as a priority.

Construction and infrastructure

Materials are ordered by a head office and delivered to project sites, and project sites are frequently unregistered. This sector will lean heavily on the URP value.

The practical risk here is not the rule itself but inconsistency: a site that has a GSTIN in one system and is treated as URP in another will produce mismatches between the e-Way Bill and the invoice. Decide the treatment for each site once, record it in the master, and apply it uniformly.

Manufacturing and wholesale

The buyer’s head office places the order and receives the invoice; the factory, depot or warehouse receives the goods. This is the classic pattern, and it is usually high volume.

The exposure scales with the number of delivery locations. A wholesaler serving 300 dealer warehouses needs 300 correct GSTINs in the master, and any one of them being wrong stops that consignment.

E-commerce, logistics and drop-ship models

Goods travel directly from the seller to an end consumer or to a fulfilment centre, while the invoice moves through the platform. Volumes are high, individual consignment values are low, and the consignee is frequently unregistered.

For this group, the operational answer is almost always automation. Manual entry at these volumes is not viable, which means the ERP or the platform integration must handle the field correctly or the model breaks.

Generating an E-Way Bill Under the New Rules

The generation process itself has not been redesigned. What follows is the sequence with the new checkpoints built in.

1. Log in with MFA. Username, password and OTP at the e-Way Bill portal. Confirm the registered mobile number is one you actually control.
2. Check the document date. Before anything else, confirm the invoice or challan falls within 180 days. If it does not, no amount of correct data downstream will help.
3. Select the correct transaction sub-type. Choose Bill-To / Ship-To where the invoice party and delivery party differ. Choosing the wrong sub-type is the most common cause of a downstream mismatch.
4. Complete Part A, including both GSTINs. In the TO section, the billing party’s GSTIN goes on the left and the actual delivery location on the right. Enter URP on the right where the consignee is unregistered.
5. Let the validations run. The system checks GSTIN authenticity, state code against PIN code, and that the same GSTIN does not appear on both sides.
6. Enter Part B. Add the vehicle number or transport document number. Remember that validity starts here, not at Part A, so do not enter Part B hours before the vehicle actually leaves.
7. Generate and record the EBN. Capture the 12-digit number against the consignment in your own system.
8. Close after delivery. Use the voluntary closure facility on the day of delivery or the next day, with the EBN, closure date and remarks.

If you generate through an ERP rather than the portal, the same checkpoints apply at the API layer. The official GST portal tutorials walk through the screens, and the e-Way Bill portal hosts the current user manuals and API documentation.

Common E-Way Bill Errors in 2026 and How to Fix Them

Most e-Way Bill failures are not disputes about law. They are error messages on a screen at seven in the morning, and the person facing them usually has a driver waiting. The table below covers the failures that will account for the great majority of your problems this year.

The habit that prevents most of these

Almost every row above traces back to master data rather than to the transaction itself. A GSTIN that was correct when it was recorded in 2023 may have been cancelled since. An address captured from an email may carry a PIN code from the head office rather than the warehouse.

A quarterly master-data review, taking perhaps two hours, prevents more dispatch failures than any amount of care at the point of generation. Verify GSTIN status for your top delivery locations, check PIN codes against states, and remove records for customers you no longer serve.

If goods are detained in transit

Should a consignment be stopped, the practical sequence matters. Establish first whether the objection is a documentation defect or an allegation of evasion, because the two follow different paths.

Have the e-Way Bill number, the invoice and the transport document available immediately, ideally accessible to the driver on a phone rather than only in an office. Detention proceedings under Section 129 require an order, and the goods and conveyance are released against payment of the applicable penalty.

Where the defect is genuinely clerical — a transposed digit in a vehicle number, for instance — that has historically been treated differently from a substantive failure to generate. Document the position at the time rather than reconstructing it later, and take professional advice before making any payment that could be read as an admission.

Penalties, Detention and What Non-Compliance Costs

The financial consequence of moving goods without a valid e-Way Bill is set out in two places, and they operate independently of each other.

Under Section 122 of the CGST Act, transporting taxable goods without the prescribed documents attracts a penalty of ₹10,000 or the amount of tax sought to be evaded, whichever is higher.

Under Section 129, the goods and the conveyance carrying them may be detained or seized, with release conditional on payment of the applicable penalty. Where matters escalate, Section 130 provides for confiscation.

Two observations are worth drawing out. First, the direct penalty is rarely the largest number; the cost of a stopped truck and a missed delivery window usually exceeds ₹10,000 comfortably. Second, several of these failures are detected by a person at a check post rather than by a system at month end, which means they are disruptive at exactly the moment you can least afford disruption.

E-Way Bill New Rules 2026: Your Readiness Checklist

Seven steps, in the order they should be done. Most businesses can complete the whole list inside a week if they start now.

One addition that is not on the graphic but belongs in your process: run a duplicate-GSTIN query across your customer master before the cut-over. Any record where the billing and delivery GSTIN are identical will now fail validation, and that query surfaces the problem in minutes.

Key Takeaways

• 1 August 2026 is a hard cut-over. Mandatory Ship-To GSTIN in Bill-To / Ship-To transactions, with no further deferral signalled after the move from 15 June.
• The field is not new; the obligation is. Your work sits in master data and ERP mapping, not in learning a new screen.
• URP is the answer for unregistered consignees. Construction sites, small retailers and individual buyers are covered, and the portal accepts it.
• A blank field fails the API call. No IRN means no valid tax invoice and no lawful movement.
• The same GSTIN cannot sit on both sides. A habit many dispatch teams fell into now fails validation outright.
• Closure is voluntary but worth adopting. It completes the digital trail and costs seconds per consignment.
• The 2025 rules still bite. The 180-day document limit, the 360-day extension cap and mandatory MFA cause more day-to-day disruption than either August change.

Frequently Asked Questions

What are the e-way bill new rules 2026?

Two changes take effect from 1 August 2026. First, the Ship-To GSTIN becomes mandatory wherever Ship-To details are furnished and an e-Way Bill is generated, with the value URP used for unregistered consignees. Second, a voluntary e-Way Bill closure facility allows delivery completion to be recorded. Three earlier rules also remain in force: the 180-day document limit, the 360-day extension cap and mandatory multi-factor authentication.

When exactly does the mandatory Ship-To GSTIN rule start?

1 August 2026. GSTN first announced the requirement in an advisory dated 21 May 2026 with a proposed rollout of 15 June 2026, then deferred it to 1 August 2026 after representations from trade bodies, ERP vendors and service providers. A further advisory dated 17 June 2026 set out the detailed API specifications.

What do I enter if the consignee is not registered under GST?

Enter URP, meaning Unregistered Person, in the Ship-To GSTIN field. GSTN addressed this specifically because many consignees such as small retailers, project sites, individual buyers and certain government warehouses hold no GST registration. The portal accepts URP and the e-Way Bill generates normally.

Is the Ship-To GSTIN a brand new field on the portal?

No. The e-Way Bill portal already has a dedicated Bill-To / Ship-To transaction type, where the TO section captures the billing party on one side and the actual delivery location on the other. The field existed. What changes from 1 August 2026 is that completing it becomes compulsory rather than optional.

What is the difference between closing and cancelling an e-way bill?

Cancellation means the e-Way Bill should never have existed, for example it was raised in error, and it must be done within 24 hours of generation. Closure means the movement happened and finished successfully. Closure is the new voluntary facility available from 1 August 2026 and can be done on the day of delivery or the immediately succeeding day.

Who is allowed to close an e-way bill?

The supplier, the recipient, the transporter, the driver, or any authorised person whose mobile number is recorded against the document. The closure API requires three inputs: the e-Way Bill number, the closure date and remarks.

Can I still generate an e-way bill against an old invoice?

Only if the document is dated within 180 days. Since 1 January 2025, an e-Way Bill cannot be generated against any invoice, credit note or delivery challan older than 180 days from the generation date. The portal blocks the attempt and returns error code 820.

What is the penalty for moving goods without a valid e-way bill?

Under Section 122 of the CGST Act the penalty is ₹10,000 or the amount of tax sought to be evaded, whichever is higher. Separately, Section 129 permits detention or seizure of both the goods and the conveyance, and release is conditional on payment of the applicable penalty.

Do the new rules apply to export consignments?

Export transactions are excluded from the mandatory Ship-To GSTIN requirement. All other e-Way Bill obligations, including the 180-day document rule and multi-factor authentication, continue to apply to exporters in the normal way.

What is the e-Way Bill 2.0 portal and do I have to use it?

E-Way Bill 2.0 launched in July 2025 at ewaybill2.gst.gov.in and runs in parallel with the original portal, with data synchronised between them. It is not a replacement. Its practical value is continuity: Part B can be updated and validity extended from either portal, so a technical outage on one need not stop dispatch.

Conclusion

The e-way bill new rules 2026 are, in one sense, modest. A single mandatory field and an optional closure button do not amount to a redesign of the system. In another sense they are the sharpest kind of change, because compliance is binary and enforcement is automatic. Either the payload carries a valid Ship-To GSTIN or the document does not exist, and the consequence lands on a loading bay rather than in a notice three months later.

The businesses that will find 1 August uneventful are the ones treating this as a master-data project rather than a tax project. Map your Bill-To / Ship-To routes, populate the GSTINs, confirm the ERP release, test in the sandbox, and run that duplicate-GSTIN query. None of it is difficult. All of it takes longer than the morning you discover the problem.

Verify every requirement against the official e-Way Bill portal, gst.gov.in and cbic.gov.in before you rely on it, because advisories continue to be issued and dates have already moved once.

For the wider compliance picture, our August 2026 compliance calendar places this change alongside every other deadline in the month, the e-invoicing guide covers IRN generation in depth, and GST changes in 2026 sets out the reform programme these rules belong to. If your own dispatch pattern does not fit the standard cases here, get in touch.