For businesses that transport goods across India, generating an e-Way Bill is only one part of GST compliance. Ensuring that every shipment complies with the latest regulations is equally important to avoid penalties, shipment delays, and unnecessary scrutiny from tax authorities. As GST compliance becomes increasingly digital and real-time, finance, tax, logistics, and warehouse teams must work together to ensure every movement of goods is backed by accurate documentation. This e-Way Bill Compliance checklist will help businesses strengthen their compliance framework, reduce operational risks, and prepare for GST audits and e way bill new rules August 2026.
Zone 1: Registration & Portal Access (Points 1–4)
Point 1 — MFA Is Active for All E-way bill Portal Users
The rule: Multi-Factor Authentication (MFA) has been mandatory for all taxpayers and transporters on the e-way bill portal since April 1, 2025 under the e-way bill compliance. Every login requires a username, password, and a one-time password (OTP) sent to the registered mobile number or via the Sandes messaging app.
Why it matters: Portal access without MFA is blocked. If a team member’s MFA is not configured — or if their registered mobile number is wrong — they cannot log in, which means they cannot generate, update, or extend an e-way bill. A delivery held up because the accounts executive cannot log in at 6 AM is a real operational failure.
What to check:
- All sub-users on your GSTIN have MFA enabled
- Registered mobile numbers are current for all users and sub-users
- Backup access procedures exist for when the primary user is unavailable
- Transporter partners who generate Part B on your behalf have MFA configured on their own logins
Quick action: Log in to ewaybillgst.gov.in → Registration → Sub-User Management → verify all active users have MFA enabled and correct mobile numbers.
Simplify E-Way Bill Compliance with GSTrobo
Automate E-Way Bill generation and validation to reduce manual errors, speed up dispatches, and stay GST compliant.
Point 2 — GSTIN Is Active and GST Returns Are Filed
The rule: In 2026, the E-way bill portal automatically blocks generation if your GSTIN is inactive, cancelled, or suspended — or if GST returns are pending.
Why it matters: A single missed GSTR-3B or GSTR-1 filing can halt your entire logistics operation. The system does not send a warning — it simply refuses to generate the E-way bill when the request is submitted.
What to check:
- GSTR-1 and GSTR-3B are filed on time every month (or quarter)
- Your GSTIN status is active — verify at the GST portal: Services → Know Your Taxpayer
- Transporter GSTINs you rely on are also active and in good standing
Quick action: Set a monthly calendar reminder 3 days before the GSTR-1 deadline (11th of the month for monthly filers). A missed return the week before a major dispatch can strand your goods.
Point 3 — Transporter Is Enrolled on the E-way Bill Portal
The rule: Transporters who are not registered under GST must enroll on the e-way bill portal (as a “Transporter”) before they can generate or update e-way bills. Without enrolment, they cannot enter Part B details or generate consolidated e-way bills.
Why it matters: If your transporter cannot access the portal, Part B cannot be filled and the E-way bill is incomplete. Goods cannot legally move on an e-way bill with only Part A filled.
What to check:
- All regular transporters have a valid Transporter ID (TRANSIN) — a 15-digit number issued on e-way bill portal enrolment
- New transporter partners are enrolled before their first dispatch
- You have the TRANSIN of each transporter stored in your dispatch system
Quick action: Ask transporters for their TRANSIN before onboarding. Verify it by entering it on the e-way bill portal: Tools → Search Transporter.
Point 4 — E-way Bill 2.0 Portal Familiarity
The rule: GSTN operates two parallel e-way bill portals — ewaybillgst.gov.in (Portal 1.0) and ewaybill2.nic.in (Portal 2.0), launched July 2025. Data syncs in real time between both.
Why it matters: During high-traffic periods, Portal 1.0 can experience downtime. If your team does not know that Portal 2.0 exists, a portal outage can result in missed dispatch windows and expired documents.
What to check:
- Your dispatch team knows both portal URLs
- Your ERP API integration has a fallback configuration to Portal 2.0 if Portal 1.0 is unavailable
- Login credentials work on both portals
Quick action: Bookmark ewaybill2.nic.in alongside the primary portal. Test login on both portals for all active users.
Zone 2: Pre-Dispatch — Generation & Data Accuracy (Points 5–12)
Point 5 — E-way Bill Is Generated Before Goods Move
The rule: Under Rule 138 of the CGST Rules, 2017, an e-way bill must be generated before goods are dispatched. There is no grace period for generating it after movement begins as per e-way bill compliance.
Why it matters: An E-way bill generated after departure is legally treated the same as no e-way bill at all. The timestamp of generation is recorded on the portal — tax officers can and do check this against vehicle GPS and toll data.
What to check:
- Your dispatch SOP requires e-way bill generation before loading begins
- The EBN (e-way bill number) is confirmed and attached to the dispatch before the truck leaves
- No dispatch happens on a verbal “we’ll generate it on the way” basis
Quick action: Make EBN confirmation a mandatory field in your dispatch sign-off form. No EBN = gate does not open.
Point 6 — Document Date Is Within 180 Days
The rule: Effective January 1, 2025, an e-way bill cannot be generated for any invoice, delivery challan, or credit note dated more than 180 days before the generation date. The portal blocks this with Error Code 820 (Error 4043 via e-invoice API).
Why it matters: Businesses with slow-moving inventory, seasonal goods, or delayed dispatch cycles frequently hit this block. There is no override — recovery requires a fresh document, which has GSTR and accounting implications.
What to check:
- No open invoices or delivery challans are more than 150 days old without an e-way bill generated
- Your ERP flags invoices approaching 150 days without Part B entry
- Part-A slips awaiting Part B are cleared well within the 180-day window
Quick action: Run a monthly report in your ERP: all open invoices / delivery challans older than 120 days with no e-way bill. Action each one before it hits 180 days.
Point 7 — GSTINs Are Correct and Active for Both Parties
The rule: Part A of the E-way bill must contain the correct GSTINs of both the supplier and recipient. The portal validates GSTIN format (15 characters) but does not always catch a valid-format-but-wrong GSTIN at the time of generation.
Why it matters: A wrong GSTIN creates a mismatch between the E-way bill and the tax invoice. At a checkpoint, a discrepancy between the GSTIN on the invoice and the E-way bill is sufficient grounds for detention under Section 129.
The rule: Part A of the E-way bill must contain the correct GSTINs of both the supplier and recipient. The portal validates GSTIN format (15 characters) but does not always catch a valid-format-but-wrong GSTIN at the time of generation.
Why it matters: A wrong GSTIN creates a mismatch between the E-way bill and the tax invoice. At a checkpoint, a discrepancy between the GSTIN on the invoice and the E-way bill is sufficient grounds for detention under Section 129 as per e-way bill compliance.
What to check:
- Recipient GSTINs in your customer master are verified against the GST portal
- GSTINs of one-time or infrequent buyers are verified before dispatch — not assumed
- Your ERP validates GSTIN format before submitting the E-way bill request
- You run periodic checks on your customer master for cancelled or suspended GSTINs
Quick action: Use the GSTIN search tool on the GST portal (gst.gov.in → Search Taxpayer) to batch-verify your top 20 customers’ GSTINs this week.
Point 8 — HSN Code Is Correct and at the Right Digit Level
The rule: HSN code accuracy is enforced on the E-way bill portal. Businesses with AATO above ₹5 crore must use at least 6-digit HSN codes. All others must use at least 4-digit codes.
Why it matters: An incorrect HSN code changes the apparent tax classification of the goods. At a checkpoint, if the physical goods do not match the HSN description on the E-way bill, officers can treat it as misrepresentation — attracting penalties beyond the standard ₹10,000 minimum. It also creates mismatches in GSTR-1 reconciliation.
What to check:
- Your item/product master in the ERP has validated HSN codes at the correct digit level
- HSN codes in the E-way bill match the codes on the tax invoice (they must be identical)
- Your HSN master is reviewed at least annually — classification can change with budget notifications
Quick action: Cross-check your 10 highest-volume SKUs: verify the HSN code used in your ERP against the CBIC HSN classification tool at cbic-gst.gov.in.
Point 9 — Invoice Value and E-way Bill Value Match Exactly
The rule: The consignment value on the E-way bill (taxable value + applicable GST) must exactly match the corresponding tax invoice.
Why it matters: A value mismatch between the E-way bill and invoice is one of the most common triggers for checkpoint scrutiny. Even a ₹1 difference — caused by a rounding error or a partial-delivery scenario — can attract detention under Section 129 of e-way bill compliance.
What to check:
- Your ERP auto-populates E-way bill values from the invoice (not manual re-entry)
- For partial dispatches against a single invoice, a new invoice or delivery challan is raised for the actual dispatch quantity — the E-way bill matches that document, not the original full-order invoice
- Tax components (CGST/SGST/IGST) are correctly calculated and reflected
Quick action: If your team manually enters E-way bill values separately from invoices, move to an ERP workflow where invoice data flows directly into the E-way bill form. Manual re-entry is the primary cause of value mismatches.
Point 10 — Part B Is Filled Before Goods Move
The rule: Part B of Form E-way bill-01 — containing vehicle number or transport document number — must be filled before goods leave the premises. Eway bill validity begins from the time Part B is first entered.
Why it matters: An E-way bill with only Part A is legally incomplete. Moving goods on a Part-A-only E-way bill is treated as moving goods without any E-way bill — full penalties apply under Section 129.
What to check:
- Your dispatch process requires Part B confirmation before vehicle departure
- For API-integrated systems, Part B submission is confirmed (not just Part A)
- Vehicle numbers are entered in the correct format (state code + number, e.g., MH12AB1234)
Quick action: Build a two-step confirmation into your dispatch workflow: (1) E-way bill generated with Part A, (2) Part B confirmed with vehicle number → only then dispatch cleared.
Point 11 — Ship-To GSTIN Is Captured for Bill-To/Ship-To Transactions
The rule: Effective August 1, 2026, the Ship-To GSTIN is mandatory for all Bill-To/Ship-To E-way bill transactions. If the delivery location is unregistered, enter “URP“. The field cannot be blank.
Why it matters: From August 1, any API call or manual E-way bill generation for a Bill-To/Ship-To transaction without a valid Ship-To GSTIN (or “URP”) will be rejected. No E-way bill = no movement. Additionally, a mismatch between Ship-To GSTIN on the E-way bill and the recipient on the invoice attracts Section 129 scrutiny.
What to check:
- Your customer master stores GSTINs at the delivery location level (not just billing level)
- The Ship-To GSTIN field is mandatory in your ERP’s sales order/invoice form
- Your ERP vendor has deployed the updated API specifications
- “URP” is configured as the default for unregistered delivery locations
Quick action: Audit your Bill-To/Ship-To customer list. For each customer with multiple delivery points, collect and verify the GSTIN for every location before August 1.
Point 12 — Consolidated E-way Bill Used for Multi-Consignment Vehicles
The rule: When a single vehicle carries multiple consignments with individual E-way bills, a Consolidated E-Way Bill (Form GST E-WAY BILL-02) must be generated to link all individual E-way bills under one document.
Why it matters: A transporter carrying five consignments with five individual E-way bills but no consolidated E-WAY BILL creates confusion at checkpoints. Officers may treat each unlinked E-way bill as a separate movement — potentially flagging the vehicle for carrying goods without proper documentation for some consignments.
What to check:
- Your transporter generates consolidated E-way bills for multi-consignment trips
- The consolidated E-way bill is updated when consignments are added or removed at intermediate stops
- Your dispatch team provides all individual EBNs to the transporter before departure
Quick action: Instruct your regular transporters: any vehicle carrying goods for more than one consignor/invoice must have a consolidated E-way bill generated before departure under the e-way bill compliance.
Zone 3: In-Transit — Validity & Updates (Points 13–16)
The rule: E-way bill validity is calculated as 1 day per 200 km for regular cargo (1 day per 20 km for over-dimensional cargo), starting from the time of first Part B entry. Validity expires at midnight on the last day.
Why it matters: An expired E-way bill at a checkpoint is treated identically to no E-way bill — full Section 129 penalties apply. Delays from traffic, weather, road conditions, or breakdowns can cause validity to lapse faster than expected.
What to check:
- Your logistics team tracks E-way bill expiry times for all active shipments
- Long-distance dispatches have a validity buffer — the actual travel time estimate vs. the E-way bill validity is reviewed before departure
- The driver/transporter has a clear process for requesting validity extension before expiry
Quick action: For any shipment with a travel time within 20% of the e-way bill validity period, proactively generate the extension before departure if allowed — or flag it for monitoring during transit.
Prevent E-Way Bill Errors Before Dispatch
Keep GSTINs, HSN codes, invoice values, Part B details, and E-Way Bill validity aligned with your shipment data.
Point 14 — Extensions Are Requested Within the 8-Hour Window
The rule: Eway bill validity rule can be extended by the generator or transporter. Extensions must be requested within 8 hours before or 8 hours after the expiry time. The total validity of all extensions combined cannot exceed 360 days from original generation (Error Code 821).
Why it matters: Missing the 8-hour extension window means the E-way bill cannot be extended at all. A new E-way bill must be generated — which requires a fresh invoice dated within 180 days and raises audit questions about why the original movement was interrupted.
What to check:
- Your transporter knows the exact expiry time and date of the E-way bill for each trip
- There is a clear escalation path if the transporter cannot reach a team member within the 8-hour window
- Extensions are not left as last-minute actions during odd hours or weekends
Quick action: Configure an alert in your dispatch system: notify logistics manager and transporter 4 hours before E-way bill expiry for any active shipment.
Point 15 — Vehicle Change Is Updated in the Portal
The rule: If the conveyance changes mid-transit — due to breakdown, transhipment, or any other reason — the new vehicle number must be updated in Part B of the E-way bill before goods resume movement in the new vehicle.
Why it matters: Moving goods in a vehicle whose number is not recorded in the E-way bill is a compliance violation, regardless of whether the original E-way bill exists. The E-way bill is vehicle-specific from the moment Part B is entered.
What to check:
- Your transporter knows to report vehicle changes immediately
- There is a clear procedure for your logistics team to update Part B when a vehicle change is reported
- Drivers are briefed: new truck = new Part B entry = before loading, not after
Quick action: Include vehicle-change reporting as an explicit clause in your transporter agreement. Define who updates Part B (transporter login vs. supplier login) and within what timeframe.
Point 16 — Physical Documents Are Available With the Conveyance
The rule: The person in charge of the conveyance must carry the EBN (print or digital) and the original tax invoice or delivery challan throughout transit. Tax officers at any checkpoint can demand these documents.
Why it matters: A valid E-way bill on the portal is of no use if the driver cannot produce it or the EBN when stopped. The physical or digital copy is the proof of compliance at the point of inspection.
What to check:
- Drivers carry either a printout of the E-way bill or have the EBN accessible digitally
- The tax invoice / delivery challan accompanies the goods at all times
- For e-invoice-mandated businesses, the IRN-stamped invoice (with QR code) is the document in transit
Quick action: Add an E-way Bill/document handover step to your dispatch gate checklist: confirm driver has EBN + invoice before departure is signed off.
Zone 4: Post-Delivery (Points 17–18)
Point 17 — Cancelled E-way Bills Are Closed Within 24 Hours
The rule: An E-way bill can be cancelled within 24 hours of generation if goods have not been transported or if incorrect details were entered. After 24 hours, cancellation is not possible — the E-way bill remains on record permanently.
Why it matters: An uncancelled E-way bill for a cancelled shipment creates a mismatch with your GSTR-1 and the recipient’s GSTR-2B. It can appear as a completed supply that wasn’t, affecting reconciliation and ITC claims.
What to check:
- Cancelled dispatches trigger an immediate E-way bill cancellation request (within 24 hours)
- There is a daily reconciliation step comparing E-way bills generated vs. dispatches confirmed
- The accounts team is notified of cancelled dispatches on the same day, not weekly
Quick action: Set a daily dispatch reconciliation: E-way bills generated yesterday vs. vehicles confirmed dispatched. Any E-way bill with no confirmed dispatch is cancelled the same day.
Point 18 — E-way Bill Closure Used for Delivered Consignments (Voluntary, August 2026+)
The rule: GSTN introduced a voluntary E-way bill Closure Facility (effective August 1, 2026) allowing the supplier, recipient, transporter, or authorised driver to officially record delivery completion against an active E-way bill.
Why it matters: Currently voluntary with no penalty for non-use — but expected to become mandatory. Using it now builds process discipline and eliminates the pool of open E-way bills for completed deliveries, which simplifies reconciliation and reduces audit exposure.
What to check:
- Your team is aware of the closure facility and how to use it
- You have identified who in your workflow (supplier, transporter, or recipient) will be responsible for closing E-way bills on delivery
- Your ERP vendor has incorporated the closure API if you use API-based E-way bill generation
Quick action: Start using the closure facility under e-way bill compliance for your top 5 regular delivery routes from August 1. Build the habit before it becomes mandatory.
Zone 5: System, ERP & Periodic Compliance (Points 19–20)
Point 19 — ERP/API Integration Is Updated for 2026 Rule Changes
The rule: Three system-level changes require ERP updates in 2025-26: the 180-day document date validation, mandatory Ship-To GSTIN for Bill-To/Ship-To transactions (August 1, 2026), and MFA for all portal users (April 1, 2025).
Why it matters: An ERP that is not updated will submit API calls that fail silently — or worse, generate E-way bills with incorrect data that creates compliance exposure later. The August 1, 2026 Ship-To GSTIN change in particular will cause all Bill-To/Ship-To API submissions without the Ship-To GSTIN field to fail.
What to check:
- Your ERP vendor has deployed the updated NIC API specifications (test in sandbox before August 1)
- The Ship-To GSTIN field is mandatory in your ERP’s E-way bill API payload
- Document date validation (180-day check) is implemented in your ERP’s pre-submission logic
- Error codes 820 (180-day block), 821 (360-day extension cap), and 4043 (e-invoice API path, 180-day block) are surfaced clearly to your operations team
Quick action: Schedule a call with your ERP vendor this week. Confirm: (1) Ship-To GSTIN field update deployed before August 1, (2) 180-day date validation in pre-submission logic, (3) error code handling is descriptive (not generic “API error”).
Point 20 — Periodic E-WAY BILL Data Reconciliation With GST Returns
The rule: E-way bill data is cross-verified by GSTN against GSTR-1 and GSTR-3B. Mismatches between E-way bills generated and supplies declared in returns are an audit trigger.
Why it matters: In 2026, GSTN’s automated matching detects discrepancies between E-way bill data (which records every movement above ₹50,000) and return data. A pattern of E-way bills without corresponding GSTR-1 entries — or GSTR-1 entries without E-way bills — attracts scrutiny and can result in notices under Section 61 or 65 of the CGST Act.
What to check:
- Monthly reconciliation: E-way bills generated in the period vs. outward supplies declared in GSTR-1
- Any E-way bill generated but corresponding supply not yet invoiced is cleared before GSTR-1 filing
- Inward E-way bills (received goods) are reconciled with purchase records and GSTR-2B
Quick action: Add an E-way bill GSTR-1 reconciliation step to your monthly GST close process. Most GST filing software can pull E-way bill data for comparison making them also e-way bill compliance software India. If yours doesn’t, export E-way bill data from the portal monthly.
Make E-Way Bill Compliance Easier with GSTrobo
Manage E-Way Bills, GST compliance, and reconciliation with automation designed to reduce operational risks and simplify compliance.
Penalty for E-Way Non-Compliance
| Violation | Penalty |
|---|---|
| No E-way bill / expired E-way bill during transit | ₹10,000 or 200% of tax evaded, whichever is higher (Section 129) |
| Goods and vehicle detention | Until tax + penalty paid (Section 129) |
| Goods confiscation (intentional evasion) | Section 130 proceedings |
| Minor clerical error (wrong PIN, spelling) | ₹1,000 under Section 125 read with Section 126 |
| Incorrect documentation (value/HSN mismatch) | ₹10,000 or tax amount under Section 122(1)(ii)/(iii) |
| Exempted goods moved without E-way bill | 2% of cargo value or ₹25,000, whichever is less (owner comes forward) |
Conclusion
E-way bill compliance checklist in 2026 is no longer about knowing the rules. The e-way bill rules 2026 are largely settled. What trips businesses up now is execution — a Part B not filled before the truck leaves, an invoice that crossed 180 days while sitting in a queue, an ERP that wasn’t updated before the August 1 Ship-To GSTIN deadline.
This checklist exists to close e-way bill compliance gaps before they become detention orders.
Work through it zone by zone. Fix the systemic issues first — MFA, return filing discipline, ERP configuration — because those are the ones that can silently block your entire logistics operation overnight. Then build the pre-dispatch checks into your dispatch SOP so they happen automatically, not because someone remembered.
The businesses that stay compliant in 2026 aren’t the ones with the most compliance knowledge. They’re the ones who converted that knowledge into process.
