Delivery Challan | Optiwise
Learn what a delivery challan is, when manufacturers use it, GST document details, and how Optiwise helps manage challans and dispatch traceability.
Delivery Challan: Meaning, GST Use, and Dispatch Workflow for Manufacturers
Goods do not always move because they are sold.
A manufacturer may send material for job work. A machine part may go for repair. A sample may go to a customer for approval. Goods may move to another warehouse. Tools or dies may be sent temporarily. In these cases, an invoice may not be the right document at the time of movement.
A delivery challan is used to document movement of goods in such situations.
Under GST, Rule 55 of the CGST Rules covers delivery challans in prescribed cases. CBIC material also explains that where goods are transported on a delivery challan in lieu of an invoice, the details are to be declared as specified in rule 138, and where goods are transported for supply but tax invoice could not be issued at removal, a tax invoice is issued after delivery as applicable.
This article explains practical use for manufacturers. It is not tax advice. For specific cases, consult your accountant or GST advisor.
AICAN Optiwise helps manufacturers manage delivery challans, inventory movement, job work, dispatch, and invoices in one connected workflow.
What Is a Delivery Challan?
A delivery challan is a document that records the movement of goods from one place to another when an invoice is not issued at that moment.
It does not always represent sale. It may represent transfer, job work, repair, return, sample movement, or another reason.
A delivery challan helps answer:
- What goods moved?
- From where did they move?
- To whom were they sent?
- Why were they sent?
- What quantity moved?
- Are the goods expected to return?
- Is an invoice required later?
For manufacturers, these questions matter because material movement affects stock accuracy, production planning, compliance, and customer coordination.
When Is a Delivery Challan Used?
Manufacturers commonly use delivery challans for:
- Job work material movement
- Sending goods for repair
- Sending samples for approval
- Moving goods for testing or inspection
- Sending tools, dies, moulds, or fixtures
- Branch or warehouse transfers where applicable
- Sending goods in parts or lots
- Returning rejected material to suppliers
- Moving goods where quantity is not known at removal
The reason should be clearly captured. A delivery challan without a reason creates confusion later.
Key Details in a Delivery Challan
CBIC invoice rules list particulars that a delivery challan should contain. In practical manufacturing use, the document should include:
- Date and challan number
- Supplier or sender name, address, and GSTIN
- Recipient name, address, and GSTIN or UIN where applicable
- HSN code where applicable
- Description of goods
- Quantity
- Taxable value where relevant
- Tax rate and tax amount where transportation is for supply
- Place of supply in interstate movement where applicable
- Transport details
- Reason for movement
- Signature or digital authentication where required
The delivery challan is generally prepared in multiple copies for consignee, transporter, and consignor as prescribed for supply of goods.
Delivery Challan vs Invoice
A delivery challan records movement. An invoice records billing.
If goods are moving for job work, repair, or sample approval, the delivery challan explains movement without treating it as a sale. If goods are sold and billed, the invoice records the commercial and tax value.
In many cases, both documents may become connected. For example, goods may first move under a delivery challan and later be invoiced after quantity confirmation or delivery.
The important thing is traceability. The invoice should not appear disconnected from the movement, and the challan should not remain open forever.
Delivery Challan Workflow in a Factory
A good delivery challan workflow begins before dispatch.
First, confirm the reason for movement. Job work, repair, sample, transfer, return, or sale-related movement all need different handling.
Second, verify stock availability. The system should reduce or tag inventory correctly so teams do not assume the goods are still physically available.
Third, create the challan with complete details. Missing recipient, quantity, or item information causes trouble during transit and reconciliation.
Fourth, attach transport details and e-way bill details where applicable.
Fifth, track closure. If the goods are expected to return, the return should be recorded. If an invoice is required later, the challan should be linked to that invoice.
Common Mistakes with Delivery Challans
One mistake is treating delivery challans casually because they are not invoices. That is risky. They affect inventory and compliance.
Another mistake is not closing challans. Material sent for job work or repair may remain open in records even after return.
Some teams create manual challans outside the ERP. This breaks inventory visibility.
Some fail to mention the reason for movement. Later, accounts cannot decide whether invoicing is pending.
Some use delivery challans where invoice should have been issued. This can create GST and audit issues.
How Optiwise Helps with Delivery Challans
Optiwise by AICAN helps manufacturers connect delivery challans with inventory, job work, sales orders, dispatch, and invoices. This prevents the document from becoming a loose paper trail.
Teams can track which challans are open, which materials are pending return, which movements are linked to invoices, and which dispatches need follow-up.
AICAN builds Optiwise for practical manufacturing workflows where documents, material movement, and business decisions must stay connected.
Founder’s Note
A delivery challan may look like a simple dispatch document, but it represents control over physical goods. If a factory cannot trace why goods left and whether they returned, inventory accuracy will always suffer.
At AICAN, we believe document discipline should be simple enough for daily use and strong enough for audit confidence. Optiwise is built around that idea.
FAQs
What is a delivery challan?
A delivery challan is a document used to record movement of goods when an invoice is not issued at that moment.
Is a delivery challan an invoice?
No. A delivery challan records movement. An invoice records billing, tax, and payment obligation.
When is a delivery challan used in manufacturing?
It is used for job work, repair, samples, testing, transfers, returns, or cases where goods move before invoice issuance as permitted.
Does a delivery challan affect inventory?
Yes. Goods moved under a challan should be reflected correctly in inventory records so stock visibility remains accurate.
How does Optiwise help manage delivery challans?
Optiwise links delivery challans with inventory, job work, dispatch, invoices, and reports so manufacturers can maintain traceability.
Related Posts
Kanban System | Optiwise
Learn how a Kanban system works in manufacturing, where it helps, where it fails, and how Optiwise connects Kanban signals with inventory, purchase, and production planning.
Erp In Operations Management | Optiwise
Learn how ERP improves operations management by connecting planning, inventory, purchase, production, quality, dispatch, finance, and reporting.
ERP for FMCG Companies in India
A practical guide to ERP for FMCG companies in India, covering distributor orders, batch tracking, expiry, inventory, production, schemes, costing, and reporting.
What's the Difference Between Odoo, Acumatica, and Dynamics 365 for Small Businesses?
Compare Odoo, Acumatica, and Microsoft Dynamics 365 for small businesses across flexibility, cost, implementation, manufacturing fit, ecosystem, and support considerations.

