The quote-to-cash process, enquiry to payment

The short answer

Quote-to-cash is the customer-facing spine of a manufacturing business: an enquiry becomes a quotation; the approved quotation becomes a confirmed sales order — the Order Acceptance (OA); the released order drives BOM explosion, planning and production; finished goods pass pre-dispatch inspection and ship on a delivery challan; a GST invoice is raised and posted to Tally; and the customer's payment closes the loop, reconciled order-versus-invoice. In an ERP, every one of those stages is a document created from the one before it, which is what makes the chain traceable and the totals honest.

This guide walks the chain as it actually runs in Fast ERP — not the CRM-flavoured version that stops at "deal won", but the manufacturing version where the middle stages involve making and moving real goods. It pairs with the procure-to-pay guide, which covers the supplier-facing spine the released order triggers, and both sit under the pillar, what is ERP software?

The whole chain in one table

Each stage, the document it produces, who owns it, and what it feeds:

Stage 1 — Enquiry and follow-up

The chain begins before there is an order. An enquiry is captured with its source and reference, and tracked through a pre-sales pipeline — from enquiry received through quotation and negotiation to order received — with follow-up screens that keep every open enquiry on someone's list rather than in someone's head. In the Sales & CRM module this pipeline is wired to telephony: KooKoo IVR and click-to-dial log calls against the enquiry automatically, so the follow-up history is real rather than remembered.

Why it matters commercially: most SMEs do not lose orders on price — they lose them on silence. A tracked pipeline converts more of the same enquiries simply because none go quiet.

Stage 2 — Quotation

The quotation turns the enquiry into a commercial offer: items from the item master, rates, taxes from the tax configuration, terms and validity. Because it binds to masters, the quote is consistent with every other document the customer will see. Fast ERP adds two disciplines that matter at scale: pending-quotation queues, so quotes awaiting approval or customer response are visible, and a quotation comparison dashboard, so management can compare offers and win rates rather than guessing.

A quotation is still a proposal — it commits nothing. The commitment happens at the next stage, which is why the two are separate documents with separate approvals.

Stage 3 — Order Acceptance: the hub of the system

When the customer says yes, the approved quotation becomes an Order Acceptance — the confirmed sales order and the single most important document in the ERP. It starts in draft, is checked, and is then approved to released by a role with the right to commit the factory. Until release, it drives nothing; after release, it drives everything:

• BOM against the OA — the multi-level bill of materials and resources for the ordered item is exploded from the order itself.
• The material plan — demand netted against stock, revealing what must be made and what must be bought.
• Work orders and the route — production knows what to run and in what sequence.
• The purchase spine — shortages become requisitions, starting procure-to-pay with the order as their reason.

Variants cover real-world shapes of demand — development OAs for new parts, component/child OAs for sets — but the principle holds: one released order, referenced by everything downstream. This hub-and-spoke structure is the heart of how the whole system works.

Stage 4 — BOM, plan and production

This is the stage CRM-centred tools skip entirely, and where a manufacturing ERP earns its keep. The exploded BOM feeds the planning module: sales, raw-material and component plans quantify demand; MRP nets it against stock; Gantt scheduling and machine-loading views sequence the work. On the floor, process sheets define the operations, work orders drive them, and production slips book completed quantities — good and rejected — through the route.

Materially, everything posts the store engine: raw material is reserved and issued against work orders, work-in-progress accumulates, and completed goods transfer from WIP to lot-tracked finished stock. Rework and rejection have their own flows, so scrap is a recorded fact with a cause, not a discrepancy discovered at year-end. By the time goods are ready to ship, stores, production and planning agree — because they were writing the same records all along.

Stage 5 — Pre-dispatch inspection and the delivery challan

Before anything leaves, quality stands at the gate. Pre-dispatch inspection checks the finished lot against its specification; only a pass releases it for dispatch. This single gate eliminates the most expensive category of quality failure — the one the customer finds.

Dispatch then records the physical event: a delivery challan lists what shipped against the order, and the store engine decrements stock as it goes. Partial dispatches accumulate against the order, so pending-to-ship is always ordered-minus-dispatched — a figure the dispatch team reads, not calculates. The challan also carries the consignment data an e-way bill needs.

Stage 6 — The GST invoice

The invoice is raised from the dispatch, which is the discipline that prevents billing disputes: quantity billed is quantity shipped, by construction. The accounts module applies GST from the tax configuration and the item-HSN mapping, adds amount-in-words for statutory format, and produces the printable document — with C-Form handling where legacy inter-state sales require it.

Posting is automatic: the invoice lands in Tally as a sales voucher, so the books and the operations describe the same event without anyone re-typing it. Summary and order-versus-invoice reports keep the commercial picture current as invoices accumulate.

Stage 7 — Payment, receipt and reconciliation

Cash closes the loop. Customer receipts are recorded against invoices, payment follow-up screens keep receivables visible, and order-versus-invoice reconciliation answers the question every owner asks — was everything we shipped billed, and everything we billed collected? — as a report over the chain rather than a month-end investigation.

This is the payoff of the document chain: because invoice descends from dispatch, dispatch from order, and receipt attaches to invoice, revenue leakage — shipped-but-not-billed, billed-but-not-collected — has nowhere to hide.

After the cash: complaints, service and the next order

Quote-to-cash does not quite end at payment. Complaints and service tickets — logged manually or via IVR — reference the customer and, where relevant, the order and dispatch that gave rise to them, with SLA-style follow-up and, for serious issues, an 8D corrective action anchored to the source. Feedback flows into the same customer record the next enquiry will open against. The loop from this order's end to the next order's beginning runs through one customer history, which is what a "customer 360" actually means when the underlying records are real.

Where quote-to-cash breaks without an ERP

Run the same chain across disconnected tools and each hand-off becomes a failure point: quotes tracked in one place and orders in another, so commitments are made against stale prices; production told about orders verbally, so the floor builds from memory; dispatch recorded on paper, so stock and pending-to-ship drift; invoices reconstructed from challans, so billing disputes multiply; and nobody able to say which orders were shipped but never billed. Each gap is small; together they are weeks of cycle time and percentage points of margin.

Frequently asked questions