No separate portal login, no double data entry, no expired EWB surprises.
Raise a sales invoice that triggers EWB (value above ₹50,000, transport mode set), and Part-A is auto-generated. Vehicle number / transporter ID are the only remaining fields.
Every active EWB shows a countdown to expiry computed from distance and Part-B timestamp. Reminders before expiry so a stranded consignment never goes off-roster.
EWB about to expire mid-transit? Trigger the official extension flow with the reason code (transit, accident, road closure). Renewal time is updated on the EWB without losing the original IRN linkage.
Cancel an EWB with a single click if the consignment is delayed before dispatch. After the 24-hour window, the system blocks cancellation and routes the correction to a credit note flow.
Assign a transporter ID for hired transport. Switch vehicles mid-trip with the change-vehicle API. Consolidated EWB for multiple invoices on one vehicle is supported in one screen.
Intra-state EWB thresholds and exemption lists vary by state. ReadyBooks.ai applies the right threshold (or exemption) based on your registered state and the goods being shipped.
EWB is the same data your invoice already has — no double entry, ever.
Your invoice already has buyer GSTIN, place of supply, item HSN, value, and tax breakup. ReadyBooks.ai uses the same data to build Part-A — you only add the vehicle / transporter details.
Moving goods on an expired EWB attracts penalty equal to the tax payable or ₹10,000, whichever is higher (Section 129 CGST Act). ReadyBooks.ai alerts you 6 hours before EWB expiry — extend in time or hold the consignment.
Every EWB generation, Part-B update, extension, cancellation, and rejection is logged with timestamp, user, and the JSON sent to and received from the official portal. GST audits run in minutes.
If you have warehouses in multiple states, the system picks the right state code, the right state-specific intra-state threshold, and the right place-of-dispatch automatically.
E-way bill compliance is the GST area where Indian SMBs leak the most money — not because they don't know the rule, but because mid-transit changes (truck breakdown, route diversion, vehicle swap, extension) require fast portal action that operators rarely have time for. A truck stranded on an expired EWB attracts penalties under Section 129 and the goods can be detained or seized.
ReadyBooks.ai treats EWB as a live document, not a one-time generation. Every active EWB on your account is monitored — expiry timing, distance covered, validity remaining. Pre-expiry alerts fire on your phone. Extension and vehicle-change workflows are one tap. The cost of EWB compliance drops from a half-time admin role to a passive workflow.
When you save a sales invoice in ReadyBooks.ai for goods worth ₹50,000 or more, the system checks whether an EWB is required based on the destination (inter-state always; intra-state per the state threshold), the item type (some goods are exempt), and the supply type (sale, return, job work, exhibition). If EWB is required, Part-A is pre-built from the invoice — supplier and recipient GSTIN, supply type, document number, value, HSN, transport mode, and place of dispatch.
You then add the vehicle number (own transport) or the transporter ID (hired transport). Hit "Generate EWB" and the JSON is posted to the official EWB portal. NIC validates the supplier GSTIN, the recipient (if registered), the HSN-to-tax-rate mapping, and the distance computed from supplier to recipient PIN code. EWB number and validity timestamp are returned within seconds and embedded into the invoice PDF along with the QR code.
For hired transport, the workflow has two steps — you create Part-A and assign the transporter ID; the transporter then logs into the EWB portal (or uses their own software) and updates Part-B with the vehicle number before dispatch. ReadyBooks.ai notifies you as soon as Part-B is updated so you can track the consignment.
Vehicle change in transit is allowed unlimited times via the "Update Vehicle" API. Use cases include truck breakdown, route change for a multi-pickup consignment, and trans-shipment from a long-haul truck to a last-mile vehicle in a different state. Each update is logged on the EWB. ReadyBooks.ai supports vehicle change in one form — enter the new vehicle number and reason code, the EWB portal updates Part-B, and your books reflect the change.
Extension is allowed within 8 hours of expiry, or within 8 hours after expiry (the "extension window"). After that the EWB cannot be extended and the goods must move on a fresh EWB or be detained. Extension requires a reason code (vehicle breakdown, transhipment in progress, natural calamity, law-and-order issue, accident). ReadyBooks.ai walks you through the extension flow and posts the reason code per the official schema.
Consolidated EWB is for one vehicle carrying multiple consignments — useful for distributors. ReadyBooks.ai lets you bundle up to the official limit of EWBs into a single consolidated EWB so the driver carries one document instead of twenty.
Most common EWB mistake: moving goods on an EWB that expired in transit. The official penalty is the tax payable on the goods, or ₹10,000, whichever is higher — and the GST officer can detain the vehicle and seize the consignment. ReadyBooks.ai prevents this by alerting the user 6 hours and 1 hour before expiry, and by suggesting the next EWB or the extension flow.
Second most common: generating an EWB on the supplier portal but forgetting to mention it on the invoice (the EWB number and date must appear on the printed invoice). ReadyBooks.ai writes both onto the invoice PDF automatically the moment the EWB is generated.
Third: wrong vehicle category leading to a wrong validity period. Regular goods vehicle = 1 day per 200 km; over-dimensional cargo (ODC) = 1 day per 20 km. Using the wrong category understates the validity needed. ReadyBooks.ai sets the right category from the transport mode + vehicle type fields on the invoice.
Every invoice that crosses the EWB threshold gets Part-A generated automatically the moment it is saved. The dispatcher only adds vehicle number and clicks Generate — total time per invoice drops from 5 minutes to 30 seconds.
Vehicle-change workflow is a single form in ReadyBooks.ai — old vehicle out, new vehicle in, reason code selected, EWB updated. Two-minute task on the highway.
Pre-expiry alerts fire 6 hours and 1 hour before expiry. Extension flow is one tap with the right reason code. Both incidents would have been avoided with this alerting in place.