The quick difference between the three documents
A quotation is usually a pre-sale document. It tells the customer what you propose to supply, at what price, and for how long the offer remains valid. It helps the buyer decide whether to proceed, but it is not the billing document.
An invoice is the billing record. It is used when the sale is ready to be charged and the tax or total payable amount needs to be stated properly. A delivery challan sits in a different place. It is generally used when goods are moving but the movement is not being documented as a sale invoice in that moment.
Which document fits which stage
| Document | Primary use | What it should not be confused with |
|---|---|---|
| Quotation | Offer and pricing before order confirmation | Not a tax invoice or proof of dispatch |
| Invoice | Billing the customer for goods or services | Not a pre-sale quote and not just a transport record |
| Delivery challan | Movement of goods without using a tax invoice for that step | Not a quotation and not a normal billing substitute |
When a quotation is the right document
Use a quotation when the customer is still evaluating price, scope, item list, or validity period. This is common in service businesses, B2B supply, and custom-order work where the buyer wants a formal offer before approving the purchase.
A quotation is useful because it keeps pricing and scope clear without pretending the sale is already complete. It can include line items, subtotal, taxes if you choose to show them, and validity terms. But it is still a commercial offer, not the final billing record.
When an invoice is the right document
Use an invoice when the sale is ready to be billed. For GST workflows, that means seller and buyer details, item rows, taxable value, GST rate, and the correct split between CGST and SGST or IGST depending on the supply context.
The invoice is the document that should match the transaction being charged. If you use an invoice too early, before the buyer has really accepted the offer or before the commercial details are final, you make the workflow messier than it needs to be.
When a delivery challan is the right document
A delivery challan is usually the right fit when goods are being moved without that movement itself being represented as a standard tax invoice. Examples can include stock transfer, approval basis, job work, or other dispatch scenarios where goods move first and the final billing step is separate.
That is why a challan should look like a movement document, not a casual item list. Sender, receiver, date, item quantities, and transport details matter because the challan is serving a dispatch function rather than a pricing or billing function.
A simple workflow from enquiry to dispatch
The cleanest business-document sequence is often: quotation first, invoice when billing is ready, and delivery challan when the movement scenario genuinely needs one. Not every business uses all three on every transaction, but each one has a defined role and should be used for that role only.
For example, a service provider may use a quotation and then an invoice, with no challan at all. A goods supplier may use quotation, then invoice, and sometimes a challan when the movement context requires it. The key is that the document trail should tell a coherent commercial story.
- Use a quotation to win approval, not to mimic billing.
- Use an invoice when the sale is ready to be charged properly.
- Use a delivery challan only when the goods-movement scenario actually calls for it.
Where businesses usually get this wrong
The most common mistake is treating all business documents as interchangeable PDF templates. They are not. A quotation helps a buyer decide. An invoice records a billable transaction. A delivery challan tracks movement without pretending that movement is automatically the same thing as billing.
The second mistake is ignoring GST context. Tax treatment and supply context matter on invoices, and GSTIN validity matters when you are using registration details operationally. That is why quotation, invoice, challan, GST calculator, and GSTIN validation often belong in the same operational cluster.
Review basis and update approach
Reviewed by Atul Sharma · Updated 2026-04-04 · Sources and review basis are shown on this page for context and maintenance transparency.
Built and reviewed by Atul Sharma
These GST and document-workflow guides are maintained as practical explainers for Indian invoices, quotations, challans, and tax-split decisions. They are updated when workflow assumptions, common field patterns, or GST framing changes on the linked tools.
They are not official compliance manuals. Their job is to help a user understand the document or GST workflow before they rely on a generator or a calculator output.
Sources used for this guide
- GST rate and tax-split framing from official Indian GST materials
- India Toolbox workflow assumptions for invoice, quotation, challan, and validator pages
For the site-wide process behind this guide, see the review methodology and sources policy.
Related tools
If you want to run the scenario after reading, start with the Quotation Generator.
Related guides
Frequently asked questions
- Can I use a quotation instead of an invoice?
- No. A quotation is a pre-sale or offer document. An invoice is the billing document and should be used when the transaction is actually being charged.
- Is a delivery challan the same as an invoice?
- No. A delivery challan is used for goods movement in scenarios where that step is not being documented as a normal tax invoice.
- Do all businesses need all three documents?
- No. Some workflows use only quotation plus invoice. Others need delivery challans as well because goods move separately from final billing.
- When should I check GST split and GSTIN details?
- At the invoicing stage. That is when CGST, SGST, IGST, and GSTIN accuracy usually matter most in the document workflow.
- Which tools should I use together for this workflow?
- Use the quotation generator before approval, the GST invoice generator when billing is ready, and the delivery challan generator when the dispatch scenario calls for a challan instead of a normal invoice.