E way bill applicability

Begin with the movement, not only the sale

The official e-way bill system describes the general requirement for consignments exceeding ₹50,000, including movement for supply, reasons other than supply and specified inward supplies. Check the operative rule, special cases and state notifications before relying on that general threshold.

Stock transfers, job-work movements, returns and other non-sale movements need assessment too. Conversely, an invoice for a service without goods movement does not become an e-way bill case merely because its value is high.

Check exceptions and state treatment

Record the goods, consignment value, origin, destination, transport mode and reason for movement. Assess exemptions, special mandatory cases and intrastate notifications for the actual route and period. A short journey or a low invoice value should not be treated as an automatic exemption without checking the relevant condition.

Determine who must generate the record and who must update transport details. Allocate responsibility between the consignor, consignee and transporter before dispatch rather than assuming another party will handle it.

Prepare the dispatch data

• Invoice, bill of supply or delivery challan appropriate to the movement.
• Supplier and recipient identifiers and actual dispatch and delivery addresses.
• Goods description, classification, quantity, value and tax details.
• Reason and type of movement, including returns or job work where relevant.
• Transporter identity, transport document and vehicle or mode details as required.
• Distance and other inputs used to determine the applicable validity.

Validate the generated record

Compare the e-way bill with the underlying document and actual vehicle or transport arrangement. Check that the required parts are complete and the status permits the planned movement. A saved draft or partial data entry is not necessarily a valid dispatch record.

Where an e-invoice system also generates an e-way bill, verify the transport information and result. An IRN alone does not prove that an e-way bill exists or that its details are correct.

Manage changes during transport

For example, goods are transferred to a replacement vehicle after a breakdown. The dispatch and transport teams should follow the applicable update process, retain the reason and check the remaining validity. A handwritten change on a printout does not necessarily update the portal record.

Assess extensions, cancellations and rejected records through the current rules and portal instructions. Do not assume every field can be edited or that a fresh record automatically cures an expired or incorrect earlier movement. Preserve both the original and corrective records.

Reconcile delivery and accounting

Link dispatch, e-way bill, transport documents and delivery acknowledgement to the invoice or challan. Record cancelled movements, goods returned and quantity differences. Investigate records that have no corresponding movement or accounting entry.

For split consignments or multiple vehicles, establish the appropriate document and e-way bill treatment rather than reusing one record without review. Keep consolidated transport records distinct from the underlying individual consignment records.

Build a practical dispatch control

Give dispatch staff a short checklist and an escalation contact for uncertain applicability, blocked generation or changed transport details. Review exceptions regularly with accounts so errors are corrected at source.

Bring sample movements, invoices and challans, transport arrangements, existing e-way bills and notices to Kosha.Services. We can organise the applicability matrix and reconciliation workflow, with current special cases and state rules checked for the business.