Quote-to-cash explained: from enquiry to a paid invoice

A customer calls, asks for a price, and somewhere a sale begins. Three weeks later that same sale ends as a number on your bank statement. Everything in between — the quotation, the order, the material, the production, the dispatch, the invoice, the follow-up for payment — is the quote-to-cash cycle. In most growing manufacturers it is stitched together by hand: a quotation in one file, an order confirmation on email, a dispatch note in the stores register, an invoice re-typed into Tally, and a payment nobody links back to the order it settled. Run it that way and the numbers drift. Run it as one chain of documents and they cannot.

This guide walks the whole cycle the way a manufacturing ERP runs it — each step, what document it produces, and why the joins between steps matter more than the steps themselves. It uses the real screen names and document flow of Fast ERP Software, so it doubles as a demo script you can hold a vendor to. If you want the wider context first, our guide to what manufacturing ERP is covers how the sales cycle sits alongside purchase, inventory, production and accounts.

1. What quote-to-cash actually is

Quote-to-cash — sometimes written Q2C, and closely related to what other systems call order-to-cash — is the end-to-end sales process, from the first customer enquiry to the cash finally received against the invoice. In a manufacturing business it is not a straight line: the order it produces reaches back into production and purchase, and only returns to the sales side once goods are ready to ship. The stages are:

• Enquiry — a customer expresses interest; you capture and follow it up
• Quotation — you offer a price and terms, often as one of several revisions, and it is compared and approved
• Order Acceptance (OA) — the customer confirms; you create the sales order that becomes the hub of everything downstream
• Production — the released order drives the BOM and plan, and the item is made
• Pre-dispatch inspection — finished goods are checked before they leave
• Dispatch & delivery challan — goods ship and stock is decremented on a challan
• Invoice — a GST invoice with amount-in-words is raised from the dispatch and order
• Reconciliation & payment — order versus invoice is reconciled, and payment is received and posted

The difference an ERP makes is that each of these is a numbered, owned, dated document with a status trail, and each inherits its data from the one before. Nothing is memory-dependent, and nothing is re-typed at a boundary.

2. Enquiry and follow-up — where the cycle starts

A sale that is not written down is a sale that depends on one person remembering to call back. The first job of the cycle is simply to capture the enquiry as a record — who asked, for what, when, and what happens next — and to keep it moving. Fast ERP tracks enquiries through a follow-up screen with pre-sales statuses, from "enquiry received" through the stages up to "order received", so nothing sits silently in an inbox.

This is the CRM front of the cycle, and it is more than a to-do list. Because the enquiry, the customer (party master) and the items are already in the system, a quotation can be raised directly from the enquiry without re-entering the customer's details or the part numbers. When the enquiry converts, its history stays attached — useful when the customer later asks why a price changed, or when you review which enquiries convert and which stall. See Sales & CRM for the follow-up detail, including the telephony link that logs calls against the enquiry.

3. Quotation — raise, compare and approve

A quotation is a priced offer, and in real business it is rarely a single number. There are revisions as the customer negotiates, and often several quotations in play for different enquiries at once. The system's job is to hold each version, cost it consistently, and put an approval gate before a price goes out that shouldn't.

In Fast ERP a quotation carries its item lines, quantities, rates and terms, and can be compared — revision against revision, or quotation against quotation — before it is approved. A pending-quotation queue shows what is awaiting sign-off, and a quotation-comparison view helps the manager see the differences at a glance rather than opening three files side by side. Approval is a real status change, not a verbal nod, so there is a record of who released which price. When the customer confirms, the approved quotation becomes the basis for the Order Acceptance — the quantities and rates carry forward instead of being re-keyed.

4. Order Acceptance — the hub that drives BOM and plan

When the customer says yes, the quotation becomes an Order Acceptance (OA) — the sales order, the confirmed commitment to supply. This is the pivot of the whole cycle, and it earns a section of its own because so much hangs off it. An OA is born as a draft, checked, and then approved and released; only a released OA drives the machinery downstream.

Once released, the OA does three things at once:

• Drives the BOM. Production explodes the Bill of Materials against the OA — a BOM-against-order — so the exact material and sub-assemblies for this order are known. See Production & Planning.
• Drives the plan. The order feeds the material, component and raw-material plans, so planning knows what to make and buy, and by when. Shortages from that plan reach into the procure-to-pay cycle.
• Sets the baseline for billing. The OA's quantities and rates are the reference the final invoice is reconciled against — so over-billing or short-billing becomes visible rather than accidental.

Fast ERP supports the variants real manufacturing needs — a standard OA, a development OA for new-product work, and component or child OAs where sub-assemblies are ordered in their own right. Because the OA lives on the same database as production, inventory and accounts, every downstream module reads the same confirmed order. This is the single biggest reason to run sales in an ERP rather than a standalone CRM: the CRM can win the order, but only the ERP can turn it into a BOM, a plan and an invoice without anyone re-typing it.

5. Produce, then pre-dispatch inspection

With the OA released, production takes over: the BOM is exploded, material is reserved and issued to work orders, operations run through their route sheets, and finished goods are transferred back into stock. That production story is a cycle in its own right — covered in the manufacturing ERP guide — but from the sales cycle's point of view, the important thing is that when the goods are ready, they are real stock against the order, not an assurance from the shop floor.

Before those goods leave, quality gets a gate. A pre-dispatch inspection checks the finished goods against the order and the control plan, and records an accept or reject decision. This matters commercially, not just for compliance: a rejected pre-dispatch inspection stops a bad shipment before it becomes a customer complaint and a credit note. In Fast ERP this inspection is part of the same quality module that handles receipt and in-process inspection, so the finished-goods check sits in one auditable quality record. See Quality & APQP.

6. Dispatch and the delivery challan

Once inspection passes, the goods ship. Dispatch is where stock actually leaves the building, and the document that records it is the delivery challan (DC). This is a genuine stock movement — a dispatch-out posting to the same store engine that inventory uses — so on-hand falls the moment goods go, and nobody is left guessing whether an order has shipped.

The challan carries the item lines and quantities being dispatched against the order, and becomes the bridge to invoicing. Because it references the OA, partial dispatches are handled cleanly: ship half the order now, and the system knows exactly how much of the order remains open and how much is ready to be billed. Handling challan transfers and dispatch this way — rather than as a manual gate-pass note — is what lets the later reconciliation actually work. See Inventory & Stores for how dispatch posts to stock.

7. The GST invoice and amount-in-words

Now the sale becomes a receivable. In Fast ERP the invoice is built from the dispatch and the order, not typed from a blank template. It pulls the item lines, quantities and rates already confirmed upstream, applies GST from the tax master and the item's HSN code, and renders the total in amount-in-words — the words-and-figures format Indian invoices require. Because the invoice is generated from documents that already exist on the same database, it cannot quietly disagree with what was ordered or shipped.

That single fact removes a whole class of errors. There is no re-keying of quantities from the challan, no mistyped tax rate, no invoice for goods that were never dispatched. And the invoice does not stop at the print: it posts to Tally ERP 9 or TallyPrime as a sales voucher, so the statutory books reflect the sale without a second round of entry. GST reports, party-wise, roll up from the same invoices. See Accounts, GST & Finance.

The invoice loops back to the order: reconciliation is what closes the cycle honestly, and it only works because the order and the invoice live on the same database.

8. Order-vs-invoice reconciliation and payment

The cycle is not finished when the invoice prints — it is finished when the money arrives and everything reconciles. Two checks close it out.

First, order-vs-invoice reconciliation. An order-vs-invoice report lines the Order Acceptance up against every invoice raised against it, so you can see which order lines are fully billed, which are part billed, and which are still open — and whether any invoice value or quantity has run ahead of the order. In a spreadsheet world this is a manual reconciliation somebody does at month-end, badly; in an ERP it is a live report, because the OA and the invoice are the same kind of document on the same database. This is where short-billing (revenue you forgot to raise) and over-billing (a dispute waiting to happen) surface early.

Second, payment. When the customer pays, a receipt is recorded against the invoice, posted to accounts and to Tally, and overdue amounts can be followed up from a payment-follow-up view. Because the receipt settles against a specific invoice, which references a specific order, you can always answer the question that a pile of spreadsheets cannot: which order did this payment settle, and what is still outstanding against this customer?

9. How Fast ERP Software implements quote-to-cash

Fast ERP runs the whole cycle above with real, named screens — the same ones you would see in a demo — and, crucially, with each document generated from the one before it on one SQL Server database.

10. Frequently asked questions