# Quote-to-Cash (QTC) — Standard Operating Procedure

> Source: https://b2bprocess.com/quote-to-cash
> Last updated: 2026-07-08. Adapt owners, tools, and thresholds to your organization.

## 1. Purpose

Quote-to-cash is the end-to-end process that turns a sales agreement into recognized revenue: configuring and pricing the quote (CPQ), negotiating and executing the contract, converting the signed order into provisioned product and a billing schedule, invoicing, collecting payment, handling amendments (upgrades, renewals, co-terms), and recognizing revenue correctly in the books. It spans sales, deal desk, legal, order management, billing, and accounting — which is exactly why it breaks: it is everyone's process and no one's.

## 2. Scope & prerequisites

Every B2B company runs QTC from its first invoice; formalize it when billing errors, invoice delays, or booking-vs-billing reconciliation pain become recurring — usually alongside multi-product pricing, usage-based components, or the first finance hire drowning in spreadsheets. Prerequisites: a price book, contract templates, and a defined handoff from closed-won to billing.

## 3. Roles & responsibilities

| Role | Responsibility |
| --- | --- |
| Revenue Operations | Owns the catalog, CPQ rules, and system integrations across the pipeline. |
| Deal Desk | Non-standard structures approved with billing and rev-rec consequences understood. |
| Legal | Contract templates, redlines, clause governance, executed-document custody. |
| Order Management / Billing Ops | Booking validation, billing schedules, invoicing, amendments. |
| Collections / AR | Dunning, disputes, cash application, aging management. |
| Accounting / Controller | Revenue recognition, deferred revenue, close reconciliation, audit readiness. |
| Customer Success / AM | Flags entitlement changes; first escalation path for billing-relationship issues. |

## 4. Procedure

### Step 1: Standardize the catalog and pricing

**Owner:** RevOps + Finance + Product

One product catalog with SKUs, price books, discount rules, and billing attributes (term, frequency, usage metrics, proration rules) shared by quoting, contracting, and billing systems. Every downstream QTC failure gets cheaper to prevent here: a clean catalog means quotes that bill correctly by construction.

- [ ] Define SKUs with billing behavior, not just price
- [ ] Encode discount bands and approval thresholds (see deal desk)
- [ ] Version price books; grandfathering rules explicit

### Step 2: Configure, price, quote

**Owner:** Sales (CPQ rules by RevOps)

Reps build quotes from the catalog with guardrails: valid product combinations, enforced discount authority, correct terms by segment. The quote object carries everything billing will need — start dates, ramps, usage tiers, PO requirements — so nothing is negotiated that can't be billed.

### Step 3: Contract and execute

**Owner:** Legal + Deal Desk

Order form generated from the quote (not retyped), non-standard terms through the approval matrix, redlines tracked in the CLM, signature via e-sign tied back to the final approved version. The executed contract is the single source of commercial truth downstream.

- [ ] Order form auto-generated from quote data
- [ ] Rev-rec-sensitive clauses flagged to finance pre-signature
- [ ] Executed documents and metadata stored in the CLM, linked to the CRM

### Step 4: Book the order and provision

**Owner:** Order Management / RevOps

Closed-won triggers a booking validation: contract vs. quote vs. CRM amounts reconciled, billing schedule created, provisioning kicked off, and the account handed to onboarding. Discrepancies bounce back to the desk now — not months later as a billing dispute.

- [ ] Three-way check: CRM opportunity = signed order = billing schedule
- [ ] Auto-provision entitlements from the order where possible
- [ ] Booking package archived for audit (quote, approvals, contract)

### Step 5: Invoice accurately, on time

**Owner:** Billing Operations

Invoices generate from the billing schedule with the customer's requirements honored: PO numbers, billing portal registration (Ariba, Coupa), entity and tax details, usage data pulled from metering for consumption components. The most common self-inflicted collections delay is an invoice the customer's AP system rejects on a technicality.

- [ ] Capture AP requirements (PO, portal, contacts) during onboarding, not at first overdue notice
- [ ] Reconcile usage metering to invoiced quantities each cycle
- [ ] First-invoice review for every new logo and every amended contract

### Step 6: Collect with a dunning discipline

**Owner:** Collections / Finance

A staged sequence from polite reminder through escalating contact to service-suspension policy, with aging reviewed weekly and disputes routed to a resolution owner with an SLA. Involuntary leakage (failed payments on card-based billing) gets automated retry and update flows.

### Step 7: Recognize revenue correctly

**Owner:** Accounting

Contracts map to performance obligations and recognition schedules per ASC 606 / IFRS 15; deferred revenue tracks billing-vs-recognition timing; non-standard terms flagged at contracting land in the right treatment. Monthly close reconciles billed, collected, recognized, and deferred against the contract base — to the dollar.

### Step 8: Handle amendments as first-class events

**Owner:** Order Management + Billing

Upgrades, downgrades, co-terms, mid-term expansions, and renewals flow through the same quote→contract→order→billing pipeline with proration and rev-rec handled systematically. Amendment chaos — hand-edited invoices, side-letter pricing, orphaned entitlements — is where mature QTC processes quietly rot.

- [ ] Amendments quoted against the live contract state, never from memory
- [ ] Renewals generated from contract data with uplift rules applied
- [ ] Entitlement changes provisioned and billed from the same event

### Step 9: Audit for leakage quarterly

**Owner:** Finance + RevOps

Reconcile entitlements vs. billing (who uses what we never bill?), contracts vs. price increases applied, usage metered vs. invoiced, and bookings vs. billings vs. collections. Track error-driven credit memos as a quality signal. Feed systematic findings back into catalog rules and process fixes.

- [ ] Entitlement-to-billing reconciliation across the customer base
- [ ] Credit memo root-cause review
- [ ] Bookings→billings→collections waterfall reported to leadership

## 5. Metrics to monitor

| Metric | Definition | Formula | Target |
| --- | --- | --- | --- |
| Quote-to-invoice cycle time | Days from closed-won to accurate first invoice issued — the friction headline. | First-invoice date − close date | < 5 business days for standard deals |
| Billing accuracy | Invoices issued without error requiring correction or credit memo. | 1 − (corrected invoices ÷ invoices issued) | > 99% |
| Days sales outstanding (DSO) | Average time from invoice to cash — the collections health metric. | (AR ÷ revenue) × days in period | ≤ contractual terms + 15 days |
| Revenue leakage rate | Revenue entitled but never billed or collected, found via reconciliation. | Leaked revenue identified ÷ total revenue | < 1% and falling |
| Quote rework rate | Quotes requiring revision after submission — upstream friction and downstream error predictor. | Reworked quotes ÷ quotes issued | < 20% |
| Bad debt / write-off rate | Billed revenue ultimately uncollectable. | Write-offs ÷ billed revenue | < 0.5–1% |

## 6. Known failure modes

| Failure | Symptom | Corrective action |
| --- | --- | --- |
| Re-keying between systems | Quote in CPQ, contract in Word, order in email, invoice typed into the billing tool — each hop adds errors and days. | Integrate the object chain (quote → order → billing schedule) so data flows without human transcription; the catalog is the shared language. |
| Deals sold that can't be billed | Custom ramps, mid-term true-ups, or usage constructs agreed in contracts that the billing system can't represent; finance runs them in spreadsheets forever. | Billing-feasibility check inside deal desk review; product catalog defines the sellable-and-billable envelope; exceptions require finance sign-off. |
| First invoice rejected by AP | Net-30 becomes net-90 because the invoice lacked a PO number or wasn't in the customer's portal; collections chases a self-inflicted wound. | Capture AP requirements as an onboarding step with a checklist; validate the first invoice against them before sending. |
| Amendment spaghetti | Three upgrades and a co-term later, nobody can state the account's current entitlements or correct invoice amount; renewals negotiate against fiction. | All changes flow through the contract-order-billing pipeline; the billing system's contract state is authoritative and auditable. |
| Unbilled entitlements | Customers using seats, modules, or volume nobody invoices; discovered years later with awkward back-billing conversations. | Quarterly entitlement-to-billing reconciliation; automated provisioning tied to orders so access and billing share a source. |
| Rev-rec discovered at close | Accounting unwinds or restates because an acceptance clause, refund right, or bundled service changed recognition — weeks after signature. | Finance flags rev-rec-sensitive terms at contracting (deal desk checkpoint), not at month-end. |
| Dunning by mood | Collections happen when someone remembers; aging balloons quietly; write-offs arrive as surprises. | Automated staged dunning with defined escalation and suspension policy; weekly aging review with named owners per overdue account. |

---

This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.