Delivery challan format

A consignor uses the delivery challan to document qualifying movement of goods when Rule 55 permits transportation without issuing the tax invoice at that point.

This is a goods-movement document, not a traffic-penalty document, purchase order, receipt or automatic substitute for every tax invoice.

• Issued by: The consignor responsible for the qualifying movement
• Given to: The consignee and transporter copies required by the process
• Keep the source and approval with the final document.
• Confirm jurisdiction-specific requirements before issue.

Put this into practice with what is GST.

The downloadable HTML provides a printable starting structure. Complete every field that explains the parties, document identity, commercial basis and resulting amount or movement. Remove irrelevant prompts only after confirming that they are not required for the transaction.

A field list cannot determine classification, tax, authority or legal effect. Those decisions come from the underlying agreement, actual event and current applicable rules.

• Delivery challan date and controlled number
• Consignor name, address and GSTIN if registered
• Consignee name, address and GSTIN or UIN if registered
• HSN and description of goods
• Quantity, provisional where permitted
• Taxable value
• Tax rate and amount where movement is for supply
• Place of supply for inter-state movement
• Signature and copy marking

Put this into practice with what is an e-way bill.

Begin with the source record rather than typing from memory. Confirm the issuer, recipient, reference, date and currency or movement context, then complete the line detail and arithmetic. A second person should review material or regulated documents before release.

Keep the final issued version immutable in ordinary operations. If a fact changes, use the appropriate revision, cancellation, credit or replacement process instead of silently overwriting history.

• Confirm the Rule 55 reason for movement.
• Identify consignor, consignee and transporter context.
• Record goods, quantity and value accurately.
• Prepare and mark the required copies.
• Link the later invoice or return movement where applicable.

Put this into practice with GST invoice format.

The example below demonstrates how the fields relate. It is not a claim that the same tax, rate, wording or commercial treatment applies to another transaction.

Retain the calculation and evidence behind every total. A reader should be able to connect the final document to the authorised order, delivered item, accepted work or verified payment without reconstructing it from private messages.

• Movement: 40 machine parts sent for job work
• Quantity: 40 units
• Value for document context: ₹200,000
• Invoice at removal: not issued under the verified case
• Next control: retain return or subsequent invoice reference

Put this into practice with what is an HSN code.

Check identity, direction, date, reference, quantity, rate, amount, currency, tax treatment where applicable, delivery or payment evidence and authorised sign-off. Confirm that the document name matches the event it records.

A complete-looking template can still be wrong when it uses the incorrect issuer, duplicates an existing number, confuses a preliminary document with a final one or records intent as though the underlying event occurred.

• Using the document for a normal invoiced sale without basis
• Confusing it with a traffic challan
• Missing HSN, quantity or movement reason
• Failing to link the related invoice where required
• Ignoring e-way-bill or other movement requirements

Put this into practice with GST invoicing.