The quote-to-cash (Q2C) process is the end-to-end business process that runs from a customer's first quote request to the resolution of the final dispute. It has seven steps: quote, contract, order, fulfillment, invoice, cash, and dispute resolution. Quote-to-cash connects sales, operations, and finance, and it is the process that turns customer demand into revenue.

Most companies never look at it as one process. A quote request waits in a shared inbox. A purchase order arrives as a PDF and someone retypes it into SAP. A deduction notice shows up weeks after the invoice, and three people spend an afternoon working out what it refers to. Every one of those moments belongs to the same quote-to-cash process.

Quote-to-cash process steps at a glance

  1. Quote: a request for quote arrives, the product is configured and priced, and a quote goes out.
  2. Contract: the customer accepts and the terms are formalized and signed.
  3. Order: the purchase order is captured, validated, and entered into the ERP.
  4. Fulfillment: the goods are picked, shipped, and delivered.
  5. Invoice: the billing system generates and sends the invoice.
  6. Cash: the payment is received and matched to the open invoice.
  7. Dispute resolution: short payments, deductions, and invoice disputes are resolved.

Quote-to-cash process flow chart

The flow chart below shows the seven steps in order, the system that usually owns each step, and the three steps where the input arrives as unstructured email rather than system data.

Quote-to-cash process flow chart: quote, contract, order, fulfillment, invoice, cash and dispute resolution, with the system behind each step and the steps that arrive as unstructured email

The 7 steps of the quote-to-cash process, explained

1. Quote

A request for quote (RFQ) arrives, usually by email. The sales team gathers the requirements, configures the product or service, calculates the price, and sends a quote the customer can accept. Configure, price, quote (CPQ) software owns the configuration and pricing logic. The work around it, reading the RFQ, capturing requirements, and chasing acceptance, still runs largely on email. RFQ automation covers this step in detail.

2. Contract

Once the quote is accepted, the terms are formalized. Drafting, legal review, and signature typically live in contract lifecycle management (CLM) software. After signing, the contract keeps generating work: customers email change requests that have to be interpreted, approved, and reflected in the systems downstream.

3. Order

The purchase order (PO) arrives by email, PDF, or EDI. It is captured, validated against customer and product master data, acknowledged, and entered into the ERP. In most B2B companies this is the step with the highest volume and the most manual work. Then come the changes: customers adjust quantities, dates, and delivery addresses on orders already in flight, almost always by email. See sales order automation and order change management.

4. Fulfillment

The ERP, the warehouse management system, and the carriers take over: picking, packing, shipping, delivery. Around the physical flow runs a communication flow of shipment questions, delivery exceptions, and carrier updates that someone has to read and act on.

5. Invoice

The billing system generates the invoice from the order and contract data and sends it to the customer, increasingly in structured e-invoicing formats. Accuracy here decides much of what happens next: a wrong invoice becomes a late payment or a dispute.

6. Cash

The payment arrives at the bank. Finance matches it to open invoices (cash application), manages accounts receivable, and follows up on late payments. This step lives in banking and accounts receivable systems and is measured in days sales outstanding (DSO).

7. Dispute resolution

Customers short-pay, take deductions, or dispute an invoice. Each case has to be identified, classified, assigned to an owner, and backed with evidence before anyone can approve a resolution. Most disputes start as an error earlier in the process, so what gets resolved here should feed back upstream. Deduction management covers this step.

Quote-to-cash process example

A distributor emails an RFQ for 400 units of a product in three variants. Sales configures and prices it in the CPQ and sends a quote, which the customer accepts by reply. A week later the purchase order arrives as a PDF attachment, is entered into the ERP, and is confirmed. Two days later the customer emails to move half of the delivery to the following month. The warehouse ships the first half, billing invoices it, and the payment arrives short by a few hundred euros with a one-line remittance note about a pricing difference. Finance opens a deduction case, finds the price agreed in the quote, and resolves it.

Seven steps, at least five systems, and four moments where the input was an email that no system could read on its own: the RFQ, the purchase order, the change request, and the remittance note.

Quote-to-cash in SAP

In SAP, the quote-to-cash process runs mostly through Sales and Distribution (SD) and Financial Accounting (FI). A quotation is created in SD and converted into a sales order once the customer accepts. The sales order drives the outbound delivery and goods issue, the delivery drives the billing document, and the billing document posts an open item in accounts receivable. Incoming payments are cleared against those open items, and disputes and deductions are typically handled in SAP's dispute management functions in Financial Supply Chain Management (FSCM).

SAP handles the structured steps well once the data is inside it. The gaps sit where the input arrives from outside: the RFQ before the quotation exists, the emailed purchase order before the sales order exists, the change request on an order already in flight, and the remittance note that explains a short payment. Those are the points where teams retype, look up, and forward, and where SAP order automation applies.

Quote-to-cash metrics to track

  • Quote turnaround time: the time from RFQ received to quote sent.
  • Order cycle time: the time from purchase order received to order confirmed in the ERP.
  • Touchless order rate: the share of orders entered without manual intervention.
  • Order change volume: how many in-flight orders change, and how long each change takes.
  • Invoice accuracy: the share of invoices issued without correction.
  • Days sales outstanding (DSO): the average number of days from invoice to payment.
  • Deduction rate and resolution time: how much invoice value is deducted, and how long each case stays open.

Most of these are measured inside one system. The delays between systems, for example how long an order email waits before anyone opens it, only become visible when the email traffic is part of the measurement. That is where process intelligence adds to classic reporting.

Quote-to-cash vs order-to-cash

The difference between quote-to-cash and order-to-cash is the starting point. Quote-to-cash starts at the quote request and includes the CPQ and contract steps; it is the term used in the sales technology world. Order-to-cash starts when the order is received and is the native term in ERP and finance. In practice both describe the same end-to-end revenue process. The full comparison of quote-to-cash and order-to-cash goes into the details.

Quote-to-cash vs CPQ

CPQ is one component of quote-to-cash, not a synonym for it. CPQ software handles the configure, price, and quote logic at the start of the process. Quote-to-cash is the full process that CPQ feeds into: contracts, orders, fulfillment, invoicing, cash, and disputes.

Why the quote-to-cash process still runs on email

Every step of quote-to-cash already has dedicated software: CRM and CPQ for the quote, CLM for the contract, the ERP for orders and fulfillment, billing for the invoice, and banking and accounts receivable systems for cash. None of these systems is the problem, and none of them needs replacing.

The problem sits between them. The inputs that drive the process, a quote request, an order change, a deduction notice, arrive as unstructured communication that no ERP, CPQ, or billing system can read. So people read them. They interpret the email, look up the account, retype the data, and forward it to the next team. Smart, expensive people working as the integration layer between systems, the Human API. The process is only as fast as their inbox.

That is why improving quote-to-cash rarely means buying another system of record. It means adding an intelligence layer, the role Tekst plays, that reads the communication between the steps and executes the outcome into the systems already in place. How that works step by step is covered in quote-to-cash automation.

Automating the quote-to-cash process

Automation adds the most value in the steps where the input arrives as email: quote, order, and dispute resolution. The order step is the most proven, because it combines the highest volume with the most manual work. Dossche Mills automated order routing and entry into SAP with Tekst across its EMEA customer service operation, reaching over 95% classification accuracy and €100k in net annual savings. At Mitsubishi Chemical Group, 60% of orders required manual entry that took 20% of inside sales time, and a template-based OCR tool handled only 4% of orders; AI-driven order entry into the ERP replaced it. Asteria automated order intake across more than 33 subsidiaries in 10 countries, each with its own processes and languages.

The direction of travel is agentic AI: software that completes work instead of only flagging it. Gartner predicts that 40% of enterprise applications will include task-specific AI agents by the end of 2026, up from less than 5% in 2025. For quote-to-cash, that means quote requests, orders, changes, and disputes increasingly get read, structured, and executed by AI, with people supervising the outcomes and keeping the judgment calls.

Other blog you might like
Deduction Management in B2B: Best Practices and How to Automate It

Deduction management explained: the types of B2B deductions, why the process fails at scale, best practices, and what AI can automate.

Process Intelligence vs Process Mining: The Difference

Process intelligence vs process mining: process mining reconstructs workflows from event logs, process intelligence also reads the unstructured work between systems.

Context Graph vs Knowledge Graph: The Enterprise AI Distinction That Actually Matters

A knowledge graph tells AI what exists. A context graph tells AI how your enterprise actually runs. The difference matters.

Discover the impact of AI on your enterprise. We're here to help you get started.

Get AI into your operations

Talk to our experts
Name Surname
Automation Engineer @ Tekst