eWay Bill

Every time your business moves goods worth more than ₹50,000 across State lines — or above your State's intra-State threshold — you are required to carry an active eWay Bill. Section 68 of the CGST Act gives enforcement officers the power to stop, inspect, and detain any vehicle that cannot produce one. The difference between goods arriving on time and a penalty under Section 129 comes down to one digital document generated before the truck leaves your gate.

The eWay Bill (Form EWB-01) is generated on the NIC portal — or via API from your accounting system — and ties the invoice, the consignor, the consignee, the transporter, and the vehicle into one verifiable record. For FY 2026-27, the e-invoicing threshold sits at ₹5 crore, meaning Part A of your EWB-01 auto-fills from the IRN for most mid-size businesses. Part B entry and validity management still require active oversight on every dispatch day.

At a Glance

• Who must generate: Any registered person moving goods above ₹50,000 inter-State, or above the State-notified intra-State threshold — consignor, consignee, or transporter can generate it.
• Governing law: Section 68, CGST Act 2017; Rule 138, CGST Rules 2017; State-specific EWB notifications for intra-State movement.
• Validity window: 1 day per 200 km (or part thereof) for regular cargo; 1 day per 20 km for over-dimensional cargo. Extensions allowed within 8 hours of expiry only.
• e-Invoice link: Businesses above ₹5 crore aggregate turnover (any FY from 2017-18): IRN auto-populates Part A. Part B still requires manual or API input before dispatch.
• Portal: ewaybillgst.gov.in — web, API, SMS, and mobile app modes available for generation and updates.
• Movements covered: Sale, stock transfer, job-work, returnable packaging, export, import, and deemed export.
• Non-compliance risk: Detention under Section 129; penalty up to 200% of tax payable; confiscation under Section 130 in repeat or deliberate cases.

What's New for FY 2026-27

Three changes that took effect between FY 2024-25 and FY 2025-26 are now fully embedded in the compliance cycle. One of them — IMS cross-referencing — is already appearing in GST scrutiny proceedings.

• e-Invoice Part A auto-fill at ₹5 crore: Any business above this turnover threshold has Part A of EWB-01 auto-populated from the IRN. This removes double-entry errors but means an IRN mistake propagates directly into the EWB — making IRN accuracy more critical than ever.
• IMS cross-check on inward supplies: The Invoice Management System (live from October 2024) compares your inward EWB data with supplier GSTR-1 entries. Unresolved mismatches appear in your IMS dashboard and can mark GSTR-2B input tax credit as pending until cleared.
• GSTR-1A correction window: The GSTR-1A form (available from FY 2025-26) lets you amend outward supply data before GSTR-3B is filed. EWB-GSTR-1 mismatches caught in time can be corrected here instead of being deferred to next month's GSTR-1.
• FASTag cross-referencing at toll plazas: The EWB system now cross-references FASTag reads at national highway toll plazas against the vehicle number in Part B. A mismatch between your EWB and the toll read generates an alert that can trigger a physical inspection.
• Tighter EDPMS timelines for exporters: AD banks are enforcing BRC closure more strictly. The EWB-to-shipping-bill chain must be complete and consistent, or IGST refund claims stall at the RFD-08 stage.

Who Needs Managed eWay Bill Compliance

• Multi-State traders: Every State pair you move through may have a different intra-State threshold and exemption schedule. One wrong threshold call means unprotected movement — which the officer reads as suppression, not oversight.
• High-dispatch-volume businesses: Manually generating dozens of EWBs per day on the web portal is operationally unsustainable. API integration turns EWB generation into a by-product of your normal invoice workflow.
• Principals dispatching to job-workers: Inter-State job-work movement requires an EWB regardless of consignment value — the ₹50,000 threshold does not apply. Many principals miss this and expose their supply chain to interception.
• Exporters: EWB must be generated before goods reach the port or ICD. The shipping bill number links to the EWB, which feeds EDPMS. A gap in this chain delays or blocks your IGST refund.
• Third-party transporters: Where the consignor did not generate an EWB, the transporter must complete Part B before movement starts. Operating without a full EWB exposes the transporter to the same Section 129 risk as the goods owner.
• Businesses facing ASMT-10 scrutiny: Officers issue ASMT-10 notices when EWB data does not match GSTR-1 — mismatched HSN, invoice value, or counter-party GSTIN. Monthly reconciliation removes this exposure before the notice arrives.

How It Actually Works

Here is how we manage the full eWay Bill lifecycle — from portal setup on day one to detention response when needed.

Step 1: Portal Setup & Master Data

Your GSTIN is registered on the e-Way Bill portal and sub-users are configured for your dispatch team. Consignor and consignee masters, HSN codes, vehicle numbers, and transporter TRANSIN enrolment are loaded. This base data is what the portal — and the officer scanning your QR code at a checkpoint — checks against.

Step 2: ERP / API Integration

An API key is generated and mapped to your accounting system — Tally, SAP, Zoho Books, or a custom ERP. Where e-invoicing applies, the IRN-to-Part-A auto-pull is configured so the EWB generates at invoice time with no separate portal login. Test dispatches verify HSN, value, and place-of-supply fields before go-live.

Step 3: Daily EWB Generation

At dispatch, EWB-01 is generated with both Part A (invoice details) and Part B (vehicle or transporter) complete. For multi-consignment vehicles, a consolidated EWB is generated. The EWB number and QR code are sent to the driver by SMS, and a copy attaches to the invoice set travelling with the goods.

Step 4: In-Transit Validity Tracking

Validity counts from the first movement entry. If a vehicle change is needed en route, Part B is updated before the original vehicle clears the next checkpoint. Where delay is genuine — breakdown, weather event, curfew — the extension is filed within 8 hours of expiry with reasons recorded and supporting evidence archived against the EWB number.

Step 5: Monthly Reconciliation

Each month, we run a three-way match: EWB register versus GSTR-1 outward supply data versus e-invoice IRN MIS (where applicable). HSN mismatches, value differences, and incorrect place-of-supply codes are corrected in GSTR-1A or the next GSTR-1. For exporters, EWBs are also matched against shipping bills to flag EDPMS gaps before BRC closure deadlines.

Step 6: Detention & Notice Response

When a vehicle is stopped and MOV-01 (interception memo) is issued, we respond with the full invoice-and-EWB set the same day. If detention proceeds to MOV-06, we calculate tax and penalty under Section 129(1)(a) or (b), arrange bond or bank guarantee for release pending adjudication where strategic, and file the MOV-07 reply. Excessive or factually incorrect penalty demands are challenged.

A Real Example: Pune to Chennai, ₹4.2 Lakh Consignment

A Pune-based auto-parts manufacturer ships goods valued at ₹4.2 lakh (IGST at 18% = ₹75,600) to a buyer in Chennai — a standard inter-State supply under GST.

• EWB trigger: Inter-State movement above ₹50,000 — EWB mandatory under Rule 138. No exemption applies to this category of goods.
• Part A source: Manufacturer's turnover exceeds ₹5 crore, so IRN is generated first. Part A of EWB-01 auto-populates from the IRN; only Part B (vehicle number) requires input.
• Validity: Pune to Chennai is approximately 1,400 km — giving 7 days of validity at the rate of 1 day per 200 km.
• In-transit event: Truck breaks down near Bellary on Day 6. Extension filed within 8 hours with a breakdown photograph and transporter's report. Validity extended by 1 day. Goods arrive without incident.
• Monthly check: EWB value of ₹4.2 lakh is cross-checked against GSTR-1 outward supply entry — values match. No ASMT-10 exposure created.

Without validity tracking, the Bellary breakdown would have produced movement on an expired EWB — triggering a Section 129 penalty of ₹1,51,200 (200% of IGST ₹75,600) on a ₹4.2 lakh consignment.

What Your Documentation Stack Must Hold

Generating the EWB is one part of the obligation. What you retain after dispatch — and for how long — determines your ability to defend against scrutiny or a follow-up inspection at the destination.

• Original invoice set: Tax invoice, delivery challan, or bill of supply — whichever applies to the movement — must travel with the goods and be available for the officer's inspection at any checkpoint.
• EWB number and QR code: The driver carries the EWB number, printed or on a phone. Officers scan the QR at checkpoints; a mismatch with the invoice set triggers a detailed inspection.
• IRN acknowledgement: Where your turnover exceeds ₹5 crore, the IRN acknowledgement from the Invoice Registration Portal must also be available. Officers cross-check the IRN against Part A of the EWB.
• Extension records: Every validity extension must have the reason recorded on the portal. Archive the supporting document — breakdown report, photograph, FIR — against the specific EWB number.
• Reconciliation reports: The EWB register-versus-GSTR-1 reconciliation must be retained for 72 months (six years) under Section 36 of the CGST Act.

The officer's first question at an interception is not whether an EWB exists — it is whether the EWB matches the invoice in your hands. A value mismatch of even ₹1 is technically actionable under Section 129.

Where It Goes Wrong

• Part B blank at movement start: Generating Part A at invoice time but adding the vehicle number only after the truck has left is one of the most common interception triggers. Part B must be complete before the goods move.
• Wrong State threshold applied: Applying the inter-State ₹50,000 threshold to an intra-State corridor in a State where the threshold is ₹1 lakh results in a missed EWB. The reverse creates unnecessary filings. State-specific mapping is not optional.
• No EWB for job-work dispatch: Principals who send goods to inter-State job-workers without an EWB — reasoning there is no supply, so no EWB needed — are wrong. Section 68 covers movement of goods, not just taxable supply.
• Vehicle change with no Part B update: Transshipment to a different vehicle mid-route without updating Part B leaves the new vehicle unprotected. The officer sees a vehicle number in the EWB that does not match the truck in front of them.
• EWB value differs from tax invoice: Generating an EWB on a proforma at one value and then issuing the final invoice at a different value creates a GSTR-1 mismatch that generates an ASMT-10 notice from the officer.
• Extension filed after the 8-hour window: Extending validity more than 8 hours after expiry is not permitted. A fresh EWB must be generated for the remaining distance. Officers who intercept between expiry and the new EWB are entitled to detain.
• Export EWB not linked to shipping bill: An EWB generated for factory-to-port movement that is not matched to the shipping bill creates an EDPMS gap. The outcome is a delayed or rejected IGST refund, not just a compliance footnote.

What You Receive at the End

• Configured e-Way Bill portal account with sub-users, vehicle masters, and API key
• ERP / Tally / SAP API integration mapping document and test-run log
• EWB generation workflow SOP for your dispatch and accounts team
• Monthly three-way reconciliation report: EWB register vs. GSTR-1 vs. IRN MIS
• Validity tracker and extension log for each consignment, with supporting evidence filed
• Detention response file where applicable: MOV-01 through MOV-09, bond or BG calculation, adjudication record
• Export shipping-bill-to-EWB reconciliation report for EDPMS and IGST refund compliance
• Six-year document retention checklist per Section 36, CGST Act 2017

How to Get Started

Share your GSTIN, a recent set of invoices, and the list of States you dispatch to. We map your inter-State and intra-State threshold obligations within 24 hours, then begin portal setup and ERP integration within the same week. If you have an active detention or an imminent scrutiny notice, flag it at the start — urgent matters take priority over routine setup.

For businesses starting fresh with dispatch operations, setup is lighter and API integration is cleaner without legacy data. For established businesses moving from manual generation, we run a parallel cycle in the first month — your team and our system generate EWBs for the same dispatches and we compare outputs before switching over. You retain full control of the process throughout.