Latest position as of 3 August 2026

The official e-way bill API release notes show a 30 July 2026 update stating that recent changes related to e-way bill, including EWB Closure functionality and mandatory Ship-to GSTIN, have been kept on hold. The same release notes also preserve the earlier 22 May 2026 update describing mandatory capture of Ship-To GSTIN in Bill-To/Ship-To transactions and introduction of EWB Closure functionality.

This means founders should avoid half-implemented production changes based on old advisory timelines, but should not ignore the direction of travel. GSTN wants better traceability in bill-to/ship-to transactions and a cleaner way to close e-way bills after delivery. Both are operationally sensible.

Why founders should care

E-way bill compliance sits between finance, warehouse, ERP, transporter and customer operations. When it fails, the founder may see it as delayed shipments, blocked dispatches, GST notices, customer payment holds and poor enterprise delivery scores. For a product startup, logistics compliance is revenue infrastructure.

Mandatory Ship-To GSTIN proposal

The earlier GSTN update focused on mandatory capture of Ship-To GSTIN in Bill-To/Ship-To transactions. The business logic is clear: the party billed and the party receiving goods may differ. If the final recipient is registered, GSTIN mapping improves traceability. Where the consignee is unregistered, advisory material referred to use of URP in the relevant field.

Even while kept on hold, this proposal tells startups what to fix. Customer master data should distinguish legal billing entity, ship-to location, warehouse, branch, GSTIN, state code and PIN. Free-text addresses inside sales invoices are not enough for a scale business.

• Create separate bill-to, ship-to and dispatch-from fields.
• Validate GSTIN state code against delivery state.
• Map unregistered-person scenarios clearly.
• Prevent same-party misuse where bill-to/ship-to should be regular transaction.
• Train sales and warehouse teams on customer-location changes.

Voluntary EWB Closure proposal

The closure facility was designed to let eligible users close an e-way bill after delivery or in specified scenarios. Advisory/FAQ material described closure by supplier, recipient, transporter or authorised person, with portal and API routes. The concept is useful because open e-way bills create reconciliation clutter.

The founder control is evidence. Closing an e-way bill should be linked to delivery proof, cancellation record, stock movement, transporter confirmation or customer receipt. Without evidence, closure becomes another field teams can misuse.

API and ERP readiness

Companies using e-way bill APIs should treat the hold notice carefully. Do not push production changes that conflict with the current system. But keep sandbox testing, schema mapping and exception handling ready so the business can respond quickly when GSTN notifies a revised implementation date.

• Track official release notes before every deployment.
• Keep feature flags for Ship-To GSTIN and closure workflows.
• Test API failure messages before dispatch teams rely on them.
• Maintain rollback plan for ERP changes.
• Log manual overrides of GSTIN, distance, transporter and address fields.
• Reconcile generated, cancelled, expired and closed e-way bills.
• Train support teams on customer-facing shipment delays.

Founder control dashboard

A founder does not need to review every e-way bill. The founder should review exception numbers. Ask finance and operations to produce a weekly dashboard showing e-way bills generated, cancelled, expired, held, mismatched with invoice, missing delivery proof and manually overridden. If the team cannot produce the dashboard, the process is not mature.

Enterprise customers increasingly expect clean GST documents. A startup with frequent document mismatches may still deliver the product, but it collects late and looks operationally weak.

30-day readiness plan while changes are on hold

The Best CS Firm In India approach is to treat the current hold as preparation time. When GSTN gives a new date, the startup should be switching on tested controls, not discovering missing GSTINs.

FAQs for founders

Should ERP vendors remove all ship-to work?

No. They should avoid unsupported production enforcement but preserve tested configuration options for a future go-live.

Is voluntary closure mandatory?

The earlier material described it as voluntary. In any case, the current official release note says the recent changes are on hold.

Can dispatch continue under existing process?

Yes, follow the current portal position and existing e-way bill process while monitoring GSTN updates.

What should founders do this week?

Run a sample reconciliation of invoice, e-way bill, delivery proof and payment status for recent shipments. That will reveal whether master data is ready.