GST and input tax credit

What Is an E-Way Bill? GST Movement Rules and Flow

Direct answer

An e-way bill is the electronic GST document used for specified movements of goods. For a registered person, the general rule applies when consignment value exceeds ₹50,000, subject to mandatory cases and exemptions. Part A captures transaction details and Part B captures transport details; the bill must be valid for movement and supported by the underlying invoice or challan.

Acronym: EWB. Also known as: electronic way bill, GST movement document.

Key takeaways

  • Test movement purpose, value, goods and exemptions before deciding whether an e-way bill is required.
  • Part A is transaction data; Part B activates the transport details needed for movement, subject to limited exceptions.
  • Validity is distance-based and current official portal guidance uses one day for every 200 kilometres or part.
  • Prevent dispatch until invoice, e-way bill, vehicle and destination data agree.

When an e-way bill is generally required

Rule 138 requires a registered person causing movement of goods with consignment value exceeding ₹50,000 to furnish information before movement when it is related to a supply, for reasons other than supply, or due to inward supply from an unregistered person. The rule also contains mandatory below-threshold cases and an exemption annexure, while state-specific intra-state rules can matter.

Do not treat ₹50,000 as the only decision. Determine who causes movement, whether the item is goods, the movement reason, consignment valuation, origin and destination, transport mode, and whether a specific exemption or mandatory case applies. A stock transfer, job-work dispatch, return, exhibition movement or repair shipment can require analysis even when there is no sale.

The e-way bill supports movement control; it is not a substitute for the invoice, bill of supply, delivery challan or bill of entry. The person in charge must carry the prescribed underlying document and the e-way bill or its electronic number, subject to the rules.

Build the applicability decision into order and warehouse workflows instead of leaving it to a driver at the gate. A dispatch record should show the rule outcome even when no bill is generated: below threshold, exempt goods, non-movement transaction, or another documented reason. This negative evidence helps reviewers test completeness because an e-way-bill report alone shows only documents the system created, not shipments the system missed.

Coordinate movement controls with e-invoice requirements

Part A and Part B of the e-way bill

Part A and Part B of the e-way bill
ComponentWhat it capturesControl focus
Part ASupplier and recipient identifiers, dispatch and delivery places, document type, number and date, value, HSN, goods description, quantity, tax and reason for transport.Agree to the invoice or challan and the actual movement.
Part-A SlipTemporary reference when transaction data is saved before full transport details.Do not mistake it for a movement-ready e-way bill.
Part BVehicle number for road or transport-document details for rail, air or ship, with transporter information.Update before movement unless a specific rule exception applies.
EWB number and validityUnique generated number and validity based on mode, vehicle type, distance and generation time.Confirm active status and sufficient validity before gate release.

The NIC portal explains that without the vehicle number or other transport-document number the system shows only a Part-A Slip. Part B converts it into an e-way bill for movement.

How e-way bill validity works

Current official e-way bill portal guidance states that for a regular vehicle or transport mode, one day of validity is provided for every 200 kilometres or part of the movement. Notification No. 94/2020 changed the regular-distance interval from 100 kilometres to 200 kilometres with effect from 1 January 2021. Over-dimensional cargo and multimodal movement involving ship have different intervals under the amended rule.

Validity is a time window for completing movement, not permission to enter an unrealistic distance. Use the actual route and preserve the basis for distance. If exceptional circumstances prevent completion, extension is available only under the rule and portal workflow; it should not become a routine substitute for dispatch planning.

Before a long-haul dispatch, compare expected transit, handovers and stoppages with the valid-until timestamp. During transshipment, update vehicle details within the original validity. Monitor near-expiry bills and escalate before the allowed extension window rather than after the document has lapsed.

E-way bill movement workflow

  1. Classify the movement. Record supply, return, stock transfer, job work, repair or other reason and test applicability.
  2. Prepare the source document. Finalise invoice, bill of supply or delivery challan with correct legal entities, locations, item and value.
  3. Complete Part A. Transfer transaction details from the approved source without re-keying uncontrolled values.
  4. Assign transport. Enter transporter ID and Part B vehicle or transport-document data before movement, subject to the specific rules.
  5. Validate at the gate. Match goods, quantity, document, vehicle, destination, EWB number, status and valid-until time.
  6. Control transit changes. Update vehicle information for breakdown or transshipment and keep every update linked to the shipment.
  7. Close exceptions. Cancel a wrongly generated bill within the prescribed window if goods do not move or details do not describe the movement, provided it has not been verified in transit.
  8. Reconcile delivery. Link proof of delivery and any voluntary closure functionality applicable at the time to the dispatch record.

Common e-way bill exceptions

Common e-way bill exceptions
ExceptionRiskResponse
Wrong GSTIN or destinationMovement document does not represent the supply.Stop dispatch; cancel and regenerate where permitted.
Part A exists but Part B is missingTemporary slip is mistaken for a valid movement document.Enter required transport details before gate release.
Vehicle changes in transitPortal data no longer matches conveyance.Authorised party updates Part B within validity.
Bill nearing expiryJourney may continue without valid coverage.Assess delay reason and use only the prescribed extension workflow.
Goods do not moveActive EWB creates false movement history.Generator cancels within 24 hours if allowed and not verified.
Incorrect entry discoveredPortal FAQ says submitted values cannot simply be edited.Cancel and generate a correct bill when the rules permit.

Record cancellation reason and approver. A replacement should link to the original so reports do not count two dispatches.

Preserve movement evidence for input tax credit review

Dispatch control checklist

  • Confirm the consignor, consignee, dispatch-from and ship-to addresses against master data and the physical route.
  • Test ₹50,000 value, mandatory cases, exemptions and state-specific movement requirements.
  • Match document number, date, transaction type, reason, HSN, description, quantity, taxable value and tax to the approved source.
  • Verify transporter identity, vehicle-number format or rail, air or ship document data.
  • Confirm Part B is active, not merely a Part-A Slip, before loading exits.
  • Compare estimated distance with route evidence and verify the valid-until timestamp covers planned transit.
  • Scan for duplicates, cancelled status and accidental use of a prior shipment’s EWB.
  • Give the driver or carrier the required invoice or challan and electronic EWB reference.
  • Monitor transshipment, breakdown and near-expiry alerts; restrict updates to authorised users.
  • After delivery, connect proof of delivery, EWB history and the accounting movement.

Measure gate blocks prevented, aged Part-A Slips, cancellations, distance overrides and expired-in-transit events. These indicators reveal process weaknesses earlier than a compliance notice. Review them by location and transporter: repeated late vehicle assignment may indicate a planning problem, while frequent address cancellation may point to weak customer master data. Correct the source process instead of normalising repeated portal rework.

Connect dispatch data through business integrations

Frequently asked questions

What is the general e-way bill value threshold?

Rule 138 generally refers to consignment value exceeding ₹50,000 for specified movements caused by a registered person. Mandatory below-threshold cases, exemptions and state rules must also be checked.

Is a Part-A Slip enough to move goods?

No. The official portal says it is a temporary reference. Part B transport details are required to generate a movement-ready e-way bill, subject to limited rule exceptions.

How long is an e-way bill valid?

For regular transport, current portal guidance provides one day for every 200 kilometres or part. Other vehicle or multimodal categories can use different distance intervals under the rules.

Can an e-way bill be edited after generation?

The official FAQ says incorrect submitted entries cannot simply be corrected. Where permitted, cancel the bill and generate a new correct one; vehicle updates follow their separate facility.

When can an e-way bill be cancelled?

The generator can cancel within 24 hours when goods are not transported or movement does not match the furnished details, provided the bill has not been verified in transit.

Does an e-invoice replace an e-way bill?

No. The processes can share data and an e-way bill may be generated through an IRN workflow, but movement applicability, Part B and validity remain separate controls.

What should be checked before a vehicle leaves?

Confirm the physical goods, source document, legal parties, addresses, vehicle, Part B, active EWB status and valid-until time all agree. A gate check should stop a mismatch before movement starts.

Sources and further reading

Educational disclaimer: This material is general information, not legal, tax, or accounting advice. Check current official guidance and your facts with a qualified professional.

From definition to workflow

Apply this concept with connected finance operations

Finnoto connects source records, approvals, reconciliation evidence, and exception ownership so teams can move from knowing the rule to operating the control.

Explore GSTR-2B reconciliation
Read nextGSTR-2A