Delivery challan software with one-click invoicing
Issue GST delivery challans for goods movement, then convert to an invoice in one click — with e-way bill support — on an offline app.
Live product UI — sample data.
Compliant challans
Delivery challans for job work, transfers and approvals, in the right GST format.
One-click to invoice
Convert a challan into a GST invoice when the sale is confirmed, without re-typing.
e-Way bill ready
Generate e-way bill JSON from the challan with transport details.
What this actually means in practice
The whole point of a delivery challan is that goods are moving and no sale is happening. Material going to a job worker, stock going to your own branch, samples going out on approval — in none of these has a supply taken place, so a tax invoice would be the wrong document. Raise one anyway and you have created output tax on a sale you never made and inflated your turnover for the period.
The vehicle still needs paperwork. Where the consignment value crosses the notified threshold, an e-way bill is required whether or not the movement is a sale, and it is raised against the challan — challan number, date, value, transporter and vehicle. That is the reference an officer at the check post reads, so the number on the road and the number in your challan series must be the same one.
Then the challan has to be closed out. Material at a job worker must come back within the period notified for that class of goods, or the original movement is treated as a supply and taxed accordingly. Goods sent on approval must be invoiced or returned. LekhaPro tracks issued quantity against received quantity, so the balance still lying outside your premises is a number, not a worry.
| Reason for the movement | Document that travels | What must happen afterwards |
|---|---|---|
| Sale, price agreed | Tax invoice | Revenue, stock and GST all post at once |
| Material sent to a job worker | Delivery challan for job work | Processed goods return within the notified period |
| Goods on approval or sale-or-return | Delivery challan | Invoice only what the customer keeps |
| Transfer to your own godown or branch | Delivery challan; a tax invoice where registrations differ | Stock changes location; no sale is recorded |
| Exhibition or demonstration stock | Delivery challan | Return it, or invoice what was sold |
| One consignment across several vehicles | A challan per vehicle, invoice with the first | Each vehicle carries its own copy |
What’s included
- GST delivery challans
- Job work & transfer challans
- One-click convert to invoice
- e-way bill JSON
- Linked to stock & ledger
- Print / PDF / share
- Offline-first
What it does not do
- · A delivery challan is not a tax invoice: it carries no output tax, gives the recipient no input credit, and does not discharge the duty to invoice once the sale is confirmed.
- · The e-way bill payload is built from a tax invoice; for a challan-only movement such as a branch transfer, the bill is raised on the portal against the challan's own details.
- · Live portal actions need your own GST Suvidha Provider credentials; without them LekhaPro produces upload-ready JSON, and there is no payroll module.
Frequently asked
Can I convert a challan to an invoice?
Yes — convert a delivery challan into a GST invoice in one click when the sale is confirmed.
Does it support e-way bills?
Yes — generate e-way bill JSON from the challan with transport details.
Is it offline?
Yes — everything runs on your machine.
When should I raise a delivery challan instead of a tax invoice?
Whenever goods leave your premises without a supply taking place — job work, branch and godown transfers, goods on approval or sale-or-return, exhibition stock, and consignments moving in more than one vehicle. The moment the sale is confirmed, the challan converts into a tax invoice for the quantity the customer actually keeps, and the challan stays linked behind it.
Does a delivery challan still need an e-way bill?
Yes, where the consignment value crosses the notified threshold — the requirement follows the movement of goods, not the existence of a sale, so branch transfers and job-work despatches are caught just as a sale is. Note the practical limit: LekhaPro builds the e-way bill payload from a tax invoice, so a challan-only movement is raised on the portal against the challan.
What exactly is included in Delivery challan · dispatch?
GST delivery challans, job work & transfer challans, one-click convert to invoice, e-way bill JSON, linked to stock & ledger and print / PDF / share, and 1 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is delivery challan · dispatch handled differently here?
It rests on compliant challans, one-click to invoice and e-Way bill ready. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does Delivery challan · dispatch post to the real books?
Yes, and that is the whole reason it lives in this product rather than beside it. What compliant challans records lands in the same posted double-entry ledger the Trial Balance, P&L and GST returns are built from — so there is no second set of delivery challan · dispatch numbers to reconcile against the first.
Does Delivery challan · dispatch cost extra?
No. Delivery challan · dispatch is part of the accounting core rather than a paid add-on, so one-click to invoice is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Delivery challan · dispatch before committing?
Yes — 14 days, no card. Test delivery challan · dispatch against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.