GST PRACTICAL GUIDE

GST E-Way Bill: Complete Practical Guide – Rules, Validity, Cancellation & Compliance

Understand when an e-Way Bill is required, who generates it, how Part A and Part B work, validity, vehicle updates, cancellation, job work, stock transfers, returns, bill-to/ship-to movements, e-Invoice interaction and practical controls for accounts and dispatch teams.

₹50,000Core Rule 138 threshold
Part A + BMovement information
200 kmOrdinary cargo validity basis
Control-focusedPractical accounting & dispatch approach

1. Quick answer — when do you need an e-Way Bill?

The starting point under Rule 138 is simple: when goods are transported and the consignment value exceeds the prescribed threshold, an e-Way Bill is generally required, subject to the rule's exceptions and the nature of the movement.

Do not stop at “invoice value is below ₹50,000”.
First identify why the goods are moving, who is causing the movement, whether an exception applies, whether the movement is interstate or intrastate, and whether any specific notification or state requirement changes the result.
1. Identify goods
2. Determine movement
3. Calculate consignment value
4. Generate / document

The safest operational approach is to make the e-Way Bill decision before the vehicle leaves the premises—not after dispatch.

2. What is an e-Way Bill?

An e-Way Bill is an electronic document generated for specified movement of goods. It connects the tax document with the movement of goods and captures information such as supplier, recipient, document details, value and transportation details.

For businesses, it should be treated as a tax-compliance and logistics-control document, not merely a portal form.

Tax team

Checks GSTINs, document type, value, tax details and applicability.

Dispatch team

Ensures vehicle and transport details are correctly reflected before movement.

Accounts team

Reconciles invoices, credit/debit notes, returns and movement records.

Transporter

Uses the e-Way Bill details during transportation and updates permitted transport information.

3. When is an e-Way Bill mandatory under GST?

Rule 138 generally applies when a registered person causes movement of goods of a consignment value exceeding ₹50,000 in relation to supply, or for reasons other than supply, or because of inward supply from an unregistered person, subject to the detailed rules and exceptions.

MovementTypical questionPractical treatment
SaleGoods sold to customer?Check Rule 138 applicability and consignment value.
PurchaseGoods coming from supplier?Determine who is causing transportation and applicable responsibility.
Stock transferGoods moved between GST registrations?Review supply treatment and e-Way Bill requirement separately.
Job workGoods sent to job worker?Check the job-work movement provisions and document trail.
ReturnGoods moving back?Identify whether it is sales return, purchase return or another movement.
Other reasonGoods moved for repair, exhibition etc.?Do not assume “not a sale” means “no e-Way Bill”. Rule 138 expressly covers specified movements other than supply.
Important: The ₹50,000 figure is not a universal “all movements below this are exempt” shortcut. Always test the movement against the actual Rule 138 conditions and applicable exemptions.

4. Understanding the ₹50,000 consignment-value threshold

The central Rule 138 framework uses ₹50,000 as the key threshold for specified movements. The practical difficulty is often not the arithmetic—it is determining what belongs in the consignment value and whether the movement falls within the rule.

Example

A company dispatches goods under an invoice containing taxable value of ₹48,000 and applicable tax of ₹8,640. The team should not automatically decide based on a single ledger amount. The applicable definition and system calculation should be followed while preparing the e-Way Bill decision.

Common mistake

Accounts sees a taxable value below ₹50,000 and tells dispatch “E-Way Bill not required.” Dispatch then moves goods without testing whether the movement is otherwise covered or whether the value of the consignment crosses the prescribed limit.

Better control: Make the ERP dispatch checklist ask for invoice/document value, movement reason, destination, GSTINs and transporter details before concluding that an e-Way Bill is unnecessary.

5. Supply is not the only movement covered

One of the most important practical points is that Rule 138 is not restricted to an ordinary sale invoice. The rule also addresses movement for reasons other than supply and inward movement from an unregistered person.

Movement for supply

Sale, transfer pursuant to a contract, exchange or other forms of supply should be tested.

Movement without a sale

Repair, job work, exhibition, testing or other business movements can still require documentation.

Inward supply from unregistered person

Do not assume the absence of a supplier GSTIN removes the movement-control requirement.

Delivery challan movement

Where goods move without a tax invoice, use the correct supporting document and test e-Way Bill applicability.

6. Who should generate the e-Way Bill?

The person causing movement has the primary responsibility framework under Rule 138. Depending on the transaction and the role of the parties, the supplier, recipient or transporter may be involved in generation or transport-detail updates.

PartyTypical responsibility
SupplierGenerate where the supplier is causing movement and the rule requires it; provide correct invoice/document details.
RecipientMay have responsibility where the recipient causes movement or in specified circumstances.
TransporterEnrolled transporters can generate/update permitted details in the e-Way Bill system as applicable.

For internal control, assign a named role: “Who is responsible for EWB generation?” should never be answered with “someone from dispatch will do it.”

7. Part A and Part B — what do they actually mean?

Part A — document and transaction information

Part A broadly captures the commercial/tax transaction information: supplier, recipient, invoice or document number/date, value, HSN and related details.

Part B — transportation information

Part B carries the transport-related information such as mode and vehicle or transport document details required by the system.

ControlWhat to verify
Supplier GSTINCorrect GST registration and legal identity.
Recipient GSTINCorrect destination registration, where applicable.
Document number/dateExactly matches invoice, delivery challan or other document.
ValueMatches the source document and system calculation.
HSNAppropriate classification in the transaction record.
Vehicle/transporterMatches the actual movement and gets updated when transport changes.
High-risk mismatch: An e-Way Bill can exist and still be wrong. Generation itself is not proof that the data is compliant.

8. e-Way Bill validity — the practical calculation

For ordinary cargo, the validity framework is generally based on 200 km per day or part thereof. The rules provide a different distance basis for over-dimensional cargo.

MovementPractical validity basis
Ordinary cargoOne day for every 200 km or part thereof.
Over-dimensional cargoOne day for every 20 km or part thereof.

The validity clock is therefore not simply “24 hours from invoice date.” Dispatch teams must look at the e-Way Bill date/time and the permitted validity under the rules.

Example

If an ordinary-cargo movement covers 350 km, the distance basis works through the 200-km-per-day rule: the first 200 km consumes the first day and the remaining distance falls into the next day.

Operational point: Delays caused by vehicle breakdown, accident, trans-shipment or other permitted circumstances should be handled through the applicable extension mechanism rather than allowing the EWB to silently expire.

9. Vehicle changes, trans-shipment and transport updates

Real-world logistics rarely follow the original vehicle plan. A truck may break down, a transporter may change the vehicle, or goods may move through trans-shipment.

Use the permitted update process

  1. Identify why the original vehicle/transport details changed.
  2. Ensure the actual document and movement remain consistent.
  3. Update the permitted transport details in the e-Way Bill system.
  4. Retain evidence of the change in the transport/dispatch record.
Do not overwrite the problem in accounting. If the physical vehicle changed, the EWB transport information must also reflect the actual movement through the permitted system process.

10. Can an e-Way Bill be cancelled?

Yes, cancellation is possible within the prescribed period when the goods are not transported or are not transported as declared, subject to the rules and system restrictions.

Example

An invoice is generated and an EWB is created, but the customer cancels the dispatch before the goods leave the warehouse. The tax team should not simply leave the EWB open. The transaction should be corrected in the books and the EWB cancellation process considered within the permitted window.

Verification matters: Once an e-Way Bill has been verified in transit, cancellation is not available in the ordinary manner. This is why dispatch cancellation controls must operate quickly.

11. Practical business scenarios — what should the team do?

ScenarioPractical approach
Sale to customerCheck threshold, invoice, destination and transport details before dispatch.
Branch transferIdentify whether registrations are distinct and determine supply/document treatment before movement.
Stock movement between sitesDetermine the reason for movement and applicable document/EWB requirement.
Purchase returnUse the correct return documentation and assess EWB applicability for the movement back.
Sales returnLink the return movement to the original sale and ensure the supporting document is clear.
Job workMaintain challan/job-work records and test EWB requirement based on the movement.
Repair movement“No sale” does not automatically mean “no EWB”; test Rule 138.
Exhibition/demo goodsDocument why goods are moving and maintain return/movement evidence.
Goods sent for testingUse appropriate documentation and maintain traceability from dispatch to return.
Interstate movementPay particular attention to destination GSTIN, place of movement and transport details.
Inward supply from unregistered personAssess Rule 138 applicability even though supplier may not have a GSTIN.
Vehicle breakdownUpdate permitted transport details rather than moving with stale vehicle information.
Multiple vehiclesFollow the permitted system process for movement/trans-shipment and maintain the document trail.
Invoice cancelled before dispatchCorrect the commercial record and consider timely EWB cancellation.
Delivery challan movementUse the correct document and test whether EWB is required for the movement.

12. Special movements that need extra care

Job work

Job-work movement is one of the most common areas where accounts and logistics teams misunderstand “no sale”. Goods can move to a job worker even though ownership or commercial treatment differs from a normal sale. The movement should be supported by the correct documentation and EWB analysis.

Stock transfers between GST registrations

Two registrations of the same legal entity can be distinct persons for GST purposes. Therefore, a “group company / branch transfer” label in ERP is not enough. Determine the GST supply treatment first and then apply the movement requirements.

Bill-to / Ship-to

Where the invoiced recipient and the physical delivery location differ, the tax invoice and transport information must be mapped carefully. Do not simply enter the delivery address as the recipient without considering the actual transaction structure.

Goods sent for repair

Movement for repair is a classic example showing why e-Way Bill analysis cannot be limited to sales invoices. Keep the repair document, original owner details, transporter information and return trail connected.

Import and port movement

Import logistics can involve multiple documents and movements. The team should map the customs document, delivery order, transporter and movement stage rather than treating every port movement as an ordinary domestic sale dispatch.

13. e-Invoice vs e-Way Bill — they are not the same

Pointe-Invoicee-Way Bill
Primary purposeInvoice reporting/authentication for covered taxpayers and transactions.Controls movement of goods.
Core dataInvoice and supply details.Supply/document plus transport details.
Replaces the other?No.No.
Practical controlEnsure invoice is correctly reported and IRN process is followed where applicable.Ensure movement is supported and transport details are accurate.
Best practice: Build one dispatch workflow where e-Invoice and EWB requirements are tested together, but keep their legal purposes distinct.

For related return reporting, see our GSTR-1 complete guide and GSTR-3B complete guide.

14. Common e-Way Bill errors

Wrong GSTIN

Supplier or recipient GSTIN entered incorrectly creates a serious document mismatch.

Wrong invoice number

EWB does not match the actual tax invoice or challan.

Wrong vehicle number

Vehicle changes without updating permitted transport details.

Expired validity

Goods continue moving after validity without handling the applicable extension process.

Wrong document type

Invoice, credit note, delivery challan or other document selected incorrectly.

Wrong movement reason

Repair/job work/return movement treated as ordinary sale or vice versa.

Value mismatch

Invoice value and EWB value differ without a valid reason.

Duplicate EWB

Multiple people generate documents for the same movement because responsibility is unclear.

15. Detention, inspection and penalty risk

An e-Way Bill problem can become a logistics problem when goods are intercepted during transit. The risk is not limited to a small portal error: the officer can compare the physical goods, invoice/challan, EWB and vehicle information.

What the inspection team should be able to establish

  • What goods are moving?
  • Who is the supplier and recipient?
  • What document supports the movement?
  • Why are the goods moving?
  • Does the EWB correspond to the actual vehicle and route?
  • Is the EWB valid at the time of movement?
Do not design compliance around “we will fix it if the truck is stopped.” The correct approach is preventive: invoice → EWB → vehicle → dispatch register → transporter record should agree before movement.

Penalty and detention consequences depend on the applicable statutory provision and facts. For a live dispute, the team should examine the actual notice/order and current law rather than relying on a generic penalty number copied from an old article.

16. Accounts + dispatch controls for companies

Recommended workflow

Invoice / Challan
EWB applicability
Vehicle validation
Dispatch release
ControlOwnerFrequency
Invoice vs EWB document number/dateAccountsEvery dispatch
GSTIN validationTax / AccountsEvery dispatch
Vehicle number confirmationDispatchBefore gate-out
EWB validity monitoringLogisticsDaily for open movements
Cancelled EWB reviewTax / AccountsWeekly
Duplicate EWB reviewTaxWeekly
Unbilled dispatch reviewAccountsDaily
Open delivery challansStores / AccountsMonthly
ERP idea: Do not allow a dispatch status to become “Released” until the system records the invoice/challan, EWB number where applicable, vehicle number and responsible user.

17. Month-end e-Way Bill reconciliation checklist

  • Compare sales invoices with e-Way Bills generated.
  • Identify invoices above the threshold without corresponding movement documentation.
  • Review EWB cancellations and confirm the underlying invoice status.
  • Review expired EWBs against open deliveries.
  • Identify duplicate EWBs.
  • Match vehicle details for major/high-value dispatches.
  • Review delivery challans still open at month-end.
  • Check job-work movements pending return.
  • Check stock transfers and inter-registration movements.
  • Investigate dispatches recorded in ERP but not supported by the expected EWB trail.
  • Retain exception explanations with supporting evidence.

18. Frequently asked questions

Is an e-Way Bill mandatory above ₹50,000?

Generally, Rule 138 requires it for specified movements above the prescribed threshold, subject to exceptions and the detailed conditions.

Is an e-Way Bill required below ₹50,000?

The central threshold is ₹50,000, but businesses should not treat the threshold as the only test. Specific movement requirements, notifications and applicable state provisions must also be considered.

Is e-Way Bill required for stock transfer?

It can be. First determine the GST treatment of the stock movement and then test the movement under Rule 138.

Is e-Way Bill required for job work?

Job-work movement can require an EWB depending on the applicable provisions, value and movement. Maintain the job-work document trail.

Can an e-Way Bill be cancelled after the goods have moved?

Cancellation is subject to the prescribed window and restrictions, including verification in transit. It is not a general method to correct a movement after interception.

Can vehicle details be changed?

Permitted vehicle/transport details can be updated through the EWB system when the transport changes, subject to the applicable conditions.

What happens if an e-Way Bill expires during transit?

The team should evaluate the applicable extension provisions and circumstances immediately. Do not continue relying on an expired EWB without taking the permitted action.

Does an e-Invoice replace an e-Way Bill?

No. They serve different purposes. Where both requirements apply, both compliance processes need to be completed.

Is an e-Way Bill required for movement for repair?

It may be, because Rule 138 is not restricted to sales. Test the movement and applicable document requirements.

Who is responsible when the transporter generates the EWB?

The parties should still ensure the EWB data is accurate. Outsourcing generation does not remove the need to reconcile the EWB with the underlying transaction and physical movement.

Can one person generate duplicate EWBs for the same invoice?

Businesses should prevent duplicate generation through role-based controls. If duplicate documents are created, review the system status and underlying movement immediately.

How should accounts teams monitor EWB compliance?

Use a recurring reconciliation between invoices/challans, EWB numbers, vehicle details, cancellations, validity status and dispatch records.

19. Related GST guides and tools

GSTR-1

Understand how outward supplies and amendments are reported.

Read GSTR-1 guide →

GSTR-3B

Understand the return-level reporting connected with GST accounting.

Read GSTR-3B guide →

GST RCM

Review reverse-charge transactions and documentation.

Read RCM guide →

GSTR-2B

Understand purchase-side ITC data and reconciliation.

Read GSTR-2B guide →

ITC reconciliation

Compare purchase records and portal data systematically.

Open reconciliation tool →

GST knowledge centre

Explore more practical GST guides and compliance topics.

Browse GST articles →

20. Final takeaway — treat the e-Way Bill as a movement control

The strongest e-Way Bill process is not “generate an EWB whenever someone asks.” It is a controlled chain:

Correct document
Correct EWB data
Correct vehicle
Correct movement

If those four elements agree, the business has a much stronger compliance trail. If they do not, even a technically generated e-Way Bill may leave the company exposed.

A PRACTICAL NEXT STEP

Use this guide to build an internal dispatch checklist covering invoice/challan → EWB applicability → EWB generation → vehicle confirmation → gate-out → validity monitoring → cancellation/return reconciliation.

Explore GSTReconciliation.in for practical GST guides and reconciliation tools.

Disclaimer

This article is for educational and practical guidance. GST provisions, notifications, portal validations and procedural requirements can change. For a live transaction, notice, detention or litigation matter, verify the applicable law, notification, circular and portal procedure for the relevant facts before taking action.