E-Way Bill Manager (India)

Key Features

`E-Way Bill` DocType linked to Sales Invoice, Delivery Note and Purchase Invoice, storing EWB number, generated date, valid-upto and the raw NIC acknowledgement JSON

Direct NIC e-way bill API integration (or via your GSP/e-invoice provider) through whitelisted methods with token caching and auth refresh

Part-A generation on document submit via `hooks.py` doc events, with payload validation before the call so malformed requests are caught locally

Part-B (transporter and vehicle) update from inside ERPNext when the assigned vehicle or transporter changes en route

Bulk e-way bill generation over a filtered list, run as Frappe background jobs with per-record success/failure capture

Consolidated e-way bill grouping multiple part-generated EWBs for a single vehicle and route into one consolidated number

Automatic distance resolution from consignor/consignee PIN codes with manual override, feeding validity-day calculation

Validity auto-calculation from distance and cargo type, with a computed expiry shown on the record

Cancellation handling within the NIC 24-hour window, with reason codes and state guards that hide the action once it is no longer legal

Validity extension flow capturing current location and remaining distance as required by NIC

Scheduler event that flags EWBs nearing expiry and can auto-attempt extension per your configured policy

`Transporter` and `Vehicle` masters with GSTIN/transporter-ID validation and a vehicle child table on the EWB record

Client scripts adding contextual Generate / Update Part-B / Cancel / Extend buttons on linked documents, state-aware per EWB status

Role profiles and DocType-level permissions separating generation, cancellation and master maintenance; every NIC API call written to an audit log

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Every GST-registered business in India that moves goods above the state threshold must carry a valid e-way bill, yet ERPNext core out of the box stops at generating the JSON payload you upload manually into the NIC portal or an external GSP. For a busy dispatch dock that is a bottleneck: no in-record EWB number, no Part-B vehicle update when the truck actually changes, no consolidated e-way bill for a multi-invoice trip, no way to cancel within the 24-hour window without leaving ERPNext, and validity that no one is tracking until a consignment is stopped at a checkpoint. Teams end up running a parallel spreadsheet and a second login, and the two systems drift.

ECOSIRE builds eway_bill_manager, a proper Frappe app installed on your bench, that closes that gap by talking to the NIC e-way bill API (directly or through your chosen GSP/e-invoice provider) from inside ERPNext. We add an E-Way Bill DocType that links to Sales Invoice, Delivery Note and, where relevant, Purchase Invoice, plus a Transporter master and a Vehicle child table. hooks.py doc events fire on submit to build and validate the EWB request, and whitelisted server methods (eway_bill_manager.api.generate, .update_part_b, .cancel, .extend_validity) handle the round-trip, storing the returned EWB number, generated date, valid-upto and the raw NIC acknowledgement against the source document. Distance is auto-resolved from consignor/consignee PIN codes with a manual override, and validity days are computed from distance and cargo type so the record shows exactly when the bill lapses.

The app is designed for real dispatch workflow, not just the happy path. Client scripts add "Generate E-Way Bill", "Update Part-B", "Cancel" and "Extend" buttons on the linked documents with contextual guards, so a dispatcher only sees the action that is legal for the current EWB state. Bulk generation and the consolidated e-way bill (single EWB grouping several part-generated bills for one vehicle and route) run as background jobs via the Frappe job queue with per-record error capture, so one rejected invoice never blocks the batch. A scheduler event flags bills nearing expiry and can auto-attempt extension where your policy allows. Role profiles and DocType permissions keep generation, cancellation and master maintenance separated across your dispatch, accounts and transport-desk roles, and every NIC call is logged for audit.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your exact flow — direct NIC vs GSP, which documents trigger EWBs, your distance and validity rules, and any state-specific handling — then build and configure the app against Frappe/ERPNext v15 or v16 on a staging copy of your site. You get UAT on staging, the full Git repository, install and configuration docs, a user guide and a live training session, and a post-go-live support window. Typical delivery is 2 to 4 weeks from confirmed scope. You own the source code and can extend it yourself, or keep ECOSIRE on for updates as the NIC API and GST rules evolve.

What you get

Installable source code for your configured version of the `eway_bill_manager` Frappe app

Installation and environment configuration on your bench (NIC/GSP credentials, GSTIN, endpoints, staging then production)

Technical documentation: DocTypes, hooks, whitelisted methods, scheduler events and API mapping

User guide plus a live training session for your dispatch, accounts and transport-desk teams

UAT on a staging copy of your site with a documented rollback plan before go-live

Post-go-live support window for defect fixes and NIC-API adjustments

Full Git repository handover so you own and can extend the code

Compatibility validation against your Frappe/ERPNext v15 or v16 site

Who this is for

Dispatch / logistics supervisor

Runs the loading dock and needs to generate, update Part-B and cancel e-way bills for every outbound consignment without leaving ERPNext or logging into the NIC portal separately.

GST accounts / compliance lead

Owns EWB accuracy against invoices, cares about distance/validity correctness, the 24-hour cancellation rule and a clean audit trail of every NIC call for assessments.

Transport desk / fleet coordinator

Assigns trucks and transporters, manages consolidated e-way bills for multi-drop trips and updates vehicle details mid-transit when a vehicle breaks down or is swapped.

ERPNext administrator / IT owner

Wants a clean Frappe app on a supported bench (v15/v16), proper DocTypes, role permissions and Git handover — not spreadsheet macros or an unmaintainable one-off patch.

How E-Way Bill Manager (India) Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
NIC API integration	Built-in generate/update/cancel/extend via whitelisted methods	You build and maintain the NIC client yourself	Usually generation only, limited lifecycle	Produces JSON payload; upload done manually
Part-B / vehicle update	In-ERPNext Part-B update with state guards	Extra scope and build time	Often missing or bolt-on	Not available
Bulk & consolidated EWB	Background-job bulk + consolidated grouping	Requires job-queue work you design	Bulk sometimes; consolidated rare	One-at-a-time, manual
Distance & validity	PIN-based auto-distance and validity calc	You implement the rules	Partial, varies by vendor	Manual entry, untracked expiry
Fit to your workflow	Scoped to your exact dispatch flow	Fully bespoke but from zero	Fixed feature set, take it as-is	Generic, no EWB workflow
Version support	Built and tested on your v15/v16 site	Depends on your team	Whatever the listing targets	Ships with ERPNext
Delivery & effort	2-4 weeks, built and installed for you	Months of internal dev time	Instant install, then self-configure	Already present, limited
Code ownership & support	Full Git handover + support window	You own and support everything	Vendor-owned, subscription support	Community / Frappe support

Frequently Asked Questions about E-Way Bill Manager (India)

How long until it is live?

This is a build-to-order app, not an instant download. After a short scoping call to lock your exact flow, typical delivery is 2 to 4 weeks from confirmed scope — including build, UAT on your staging site and a training session before go-live.

What do I get support and updates on?

Every engagement includes a post-go-live support window for defect fixes and adjustments if the NIC e-way bill API or GST rules change. Because you receive the full Git repository, you can extend it in-house, or keep ECOSIRE on a maintenance arrangement for ongoing updates across v15/v16.

Does it connect directly to the NIC e-way bill system?

Yes. The app calls the NIC e-way bill API — either directly with your NIC API credentials or through your existing GSP / e-invoice provider — from whitelisted Frappe methods, and stores the EWB number, validity and raw acknowledgement against the source ERPNext document.

Which ERPNext versions does it support?

We build and validate against Frappe/ERPNext v15 or v16 on your bench. We confirm your exact version during scoping and test on a staging copy of your site before touching production.

Can it handle bulk and consolidated e-way bills?

Yes. Bulk generation runs over a filtered list as background jobs with per-record error capture so one rejected invoice never blocks the batch, and consolidated e-way bills group multiple part-generated EWBs for a single vehicle and route into one consolidated number.

Will it clash with ERPNext's built-in GST features?

No. It is a separate Frappe app that links to standard Sales Invoice, Delivery Note and Purchase Invoice documents via hooks rather than modifying core, so it upgrades cleanly and coexists with ERPNext's existing GST/e-invoice handling.

Who owns the code once it is delivered?

You do. We hand over the complete Git repository and installable source for your configured version, so there is no vendor lock-in — you can self-host, self-maintain or bring in any Frappe developer.