The one-sentence answer
The delivery challan moves goods; the tax invoice bills them. The challan is a movement document — it accompanies material in transit, lists what is moving and in what quantity, and carries the transport details an e-way bill needs. It charges no tax and creates no receivable. The tax invoice is a financial document — it attaches commercial value and GST to those goods, creates the customer's liability, and is what your books and GST returns are built on. Two events, two documents — and a link between them that matters as much as either one.
Everything confusing about this pair comes from the fact that in a simple cash-and-carry sale the two events happen together, so small businesses get used to one piece of paper doing both jobs. The moment shipping and billing separate — goods out today, invoice at week's end; one dispatch billed in parts; stock moved between branches with no sale at all — the two documents earn their separate existence. For the surrounding document family, see types of billing documents; for the concepts, the pillar guide what is GST billing software?
What a delivery challan is — and what it carries
A delivery challan (and the packing slip that often rides with it) is the paper — or the printout — that travels with goods. It typically shows: consignor and consignee, the items and their quantities, descriptions sufficient to identify the material, vehicle and transport details, and the date of movement. What it deliberately does not do is demand money: no taxable value presented as a bill, no GST computation, no payment terms. In a warehouse-linked system, the challan is also the moment stock actually leaves — the dispatch event that inventory records are built on.
That last point is the key to the whole design: stock moves at the challan, not at the invoice. Whatever billing happens later is a financial layer applied to a movement that has already occurred. The product side of this document is Delivery Challan & Packing Slip.
What a tax invoice is — and what it carries
The tax invoice is the GST-compliant commercial document: the parties with their GSTINs, item lines with HSN codes, quantities, rates and taxable values, the CGST/SGST or IGST split decided by the buyer's state, other charges such as freight and packing, rounding, and the total in figures and in words in Indian numbering. It is the document a business buyer claims input credit from, the document your GST returns summarise, and the document that creates the receivable you will collect against. It moves no stock — the goods already left on the challan. Full detail on the GST Tax Invoicing feature page, with the invoice-raising mechanics walked through in the billing process guide.
Side by side
| Aspect | Delivery challan | Tax invoice |
|---|---|---|
| Records | Movement of goods | Sale value and tax |
| Travels with the goods | Yes — that is its job | In a sale — accompanies or promptly follows, per the rules for your case |
| Moves stock | Yes — dispatch is the stock event | No — financial event only |
| Charges GST | No | Yes — CGST/SGST or IGST per line |
| Creates a receivable | No | Yes — the customer now owes you |
| Basis for input credit | No | Yes — with the buyer's GSTIN and HSN lines |
| Posts to the books as | Nothing financial by itself | A sales voucher with GST ledgers |
| Key discipline | Linked — the invoice is raised against the challan, and each dispatched quantity is billable exactly once | |
When goods move on a challan alone
Not every movement is a sale, and GST practice recognises movements where a challan travels without a tax invoice. The common categories:
- Job work — material sent to a job-worker for processing and due back; no sale has occurred, so no invoice is raised for the movement.
- Transfers between your own premises — stock moved from factory to warehouse or branch to branch within the same registration; a movement, not a supply.
- Goods on approval — material sent for the customer to inspect and accept; the invoice follows only if and when they do.
- Exhibitions, demonstrations and similar non-supply movements — goods out and back with no change of ownership.
Each category has conditions and timing rules attached, and inter-state variants have their own wrinkles — so treat this list as the map, not the law, and confirm your specific flows with your CA. The operating discipline, though, is universal: every challan should either be linked to an invoice or clearly belong to a recognised non-sale category. A challan that is neither is exactly where revenue leaks and audit questions begin.
Shipping on challans and billing later?
That is the exact flow Fast Billing Software is built around — challans out, invoices raised against them, every quantity billed once. See it live in 30 minutes.
The link between them — why it matters more than either document
A perfect challan and a perfect invoice, unlinked, still produce a broken billing system. The link — this invoice bills that challan — is what turns two documents into one auditable chain, and it enables the two guarantees manual billing cannot make:
- Nothing billed twice. With per-line quantity tracking on the challan, an invoice can only consume un-invoiced quantity. A 100-unit dispatch with 60 billed offers exactly 40 — the used-quantity guard that gets its own deep-dive in how billing software prevents double billing.
- Nothing shipped unbilled. The same link, read the other way, is a pending-to-bill report: challans whose quantities are not fully invoiced surface automatically instead of surfacing never.
Both directions of traffic are normal: one challan billed across several invoices, several challans consolidated onto one invoice. The quantity arithmetic holds either way, and corrections stay clean too — a sales return raises a credit note against the original dispatch, and a cancelled invoice releases its consumed quantity back to the challan for correct re-billing.
Where the e-way bill fits
The e-way bill rides with the movement, so its data comes from the challan-and-invoice pair: items and quantities from the dispatch, values from the invoice where a sale is involved, transport details from the challan. When your documents are linked in one system, that data is assembled rather than re-typed — one more error surface removed. Thresholds and validity rules change; the compliance surface is covered under GST, e-Way Bill & e-Invoice.
The mistakes that cost money
| Mistake | What happens | The fix |
|---|---|---|
| Treating the challan as the bill | Goods delivered against a quantity document; no tax invoice, no receivable, no input credit for the buyer | Always follow the challan with an invoice raised against it (or classify it as a non-sale movement) |
| Invoicing with no challan reference | Invoice and dispatch drift apart; disputes over what was actually delivered | Raise invoices from the dispatch, lines pre-filled, reference recorded |
| Billing the same challan twice | Angry customer, credit note, GST correction | Per-line used-quantity guard on the challan |
| Challans that never get billed | Silent revenue loss, found months later if at all | Pending-to-bill report over linked challans |
| Branch transfers billed as sales | Tax charged on your own stock movement | Classify the movement correctly — challan without invoice; confirm treatment with your CA |
How Fast Billing Software handles the pair
This distinction is not a feature of Fast Billing Software so much as its architecture. Dispatch and billing are separate events by design: the challan moves goods (and stock), the tax invoice is raised against that dispatch as a purely financial document, and the against-dispatch reference plus the used-quantity guard keep every dispatched unit billable exactly once. Returns raise credit notes against the original dispatch; cancellations release quantity for re-billing; and both documents feed Tally and the e-way/GST data surface automatically. It is the same discipline whether billing rides on Fast WMS dispatches or runs standalone — the pattern trading businesses in particular live by, as the trading & distribution page shows.
Frequently asked questions
What is the difference between a delivery challan and a tax invoice?
They record two different events. The delivery challan is a movement document: it accompanies goods in transit, lists items, quantities and transport details, charges no tax and creates no receivable. The tax invoice is a financial document: it attaches commercial value and GST — HSN codes, CGST/SGST or IGST — to the goods, creates the customer's liability, and is what your books and GST returns are built on. Goods can move on a challan today and be invoiced later; the invoice is then raised against that dispatch.
Can goods be sent on a delivery challan without an invoice?
Yes, in the situations GST rules recognise for movement without a sale — commonly job work, transfers between your own premises, goods sent on approval, and similar non-supply movements. In a normal sale, the tax invoice must accompany or promptly follow the goods as the rules require for your case. The safe pattern: every challan is either linked to an invoice or clearly belongs to a recognised non-sale category — and because the categories carry conditions, confirm your specific flows with your CA.
Does a delivery challan charge GST?
No. A delivery challan is not a tax document — it moves goods and shows quantities and descriptions, not a tax demand. GST is charged on the tax invoice, which carries the HSN codes, taxable values and the CGST/SGST or IGST split. The challan does supply the movement data an e-way bill needs when the consignment requires one, which is why good software generates challans and invoices from the same linked record.
How should challans and invoices be linked?
Every invoice should be raised against the challan or dispatch it bills, with the reference recorded on the invoice line. That link makes billing reconcilable: a used-quantity guard blocks quantities already invoiced, a pending-to-bill report shows challans not yet invoiced, and any audit query can walk the chain from movement to money. Unlinked challans and invoices are the root cause of most billing disputes.
Can one challan be billed on multiple invoices, or several challans on one invoice?
Both patterns are normal business. A large dispatch may be invoiced in parts across periods, and several challans to the same customer may be consolidated onto one invoice. What keeps either pattern safe is quantity tracking per challan line: each invoice consumes part of the dispatched quantity, the system offers only the un-invoiced remainder, and every dispatched unit ends up billed exactly once.