CPQ / Quote Management is where ERP discipline either begins or breaks.
Configure-Price-Quote (CPQ) Generation looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Quote generation time <5 minutes for standard configurations; 100% of quotes above discount threshold approved before send; accepted quotes auto-converted to orders with zero re-entry
The control flow a finance team actually needs.
Step 1
Product Configurator Enforces Valid...
Step 2
Pricing Engine Evaluates Multiple Price...
Step 3
Discount Approval Matrix By Discount...
Step 4
Quote Versioning With Comparison View
Step 5
PDF Template Configurable Per Business...
The ERP surface involved.
Module
CPQ / Quote Management
Actors
Account Executive, Product Catalog, Pricing Engine, Customer
Tier
Tier 2
Finance area
Sales, CRM & Customer Management
Region lens
US and UK finance teams
Publication date
May 21, 2026
Product configurator enforces valid combinations and mandatory options; pricing engine evaluates multiple price lists in priority order; discount approval matrix by discount depth and deal size; quote versioning with comparison view; PDF template configurable per business unit; e-signature integration (DocuSign or equivalent); quote expiry date enforced; accepted quote locks pricing and auto-creates sales order; multi-currency quote with functional currency equivalent displayed
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Product configurator enforces valid combinations and mandatory options | Given an opportunity with a customer account, active price list, and product catalog |
| Control 2 | pricing engine evaluates multiple price lists in priority order | when an AE creates a quote selecting products and requesting a discount above the threshold, then the discount approval routes to the configured approver and the quote status is PENDING_APPROVAL |
| Control 3 | discount approval matrix by discount depth and deal size | when approved, then a branded PDF is rendered and e-signature link sent to the customer |
| Control 4 | quote versioning with comparison view | when the customer accepts, then a sales order is auto-created with locked pricing |
| Control 5 | PDF template configurable per business unit | negative) when a quote is sent with a discount above threshold without approval, then the action is rejected with 403 and error code DISCOUNT_APPROVAL_REQUIRED. |
| Control 6 | e-signature integration (DocuSign or equivalent | Quote generation time <5 minutes for standard configurations; 100% of quotes above discount threshold approved before send; accepted quotes auto-converted to orders with zero re-entry |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | An AE initiates a quote against an opportunity and selects products from the catalog. The CPQ engine applies configurator rules to prevent invalid product combinations, calculates list prices from the active price list for the customer's currency and tier, and applies any pre-approved discount schedules. The AE requests additional discounts beyond threshold which route for approval. Once approved, the system renders a branded PDF quote and sends it to the customer via email with an e-signature link. Customer acceptance converts the quote to a sales order. |
| Control rules | Product configurator enforces valid combinations and mandatory options; pricing engine evaluates multiple price lists in priority order; discount approval matrix by discount depth and deal size; quote versioning with comparison view; PDF template configurable per business unit; e-signature integration (DocuSign or equivalent); quote expiry date enforced; accepted quote locks pricing and auto-creates sales order; multi-currency quote with functional currency equivalent displayed |
| Acceptance proof | Given an opportunity with a customer account, active price list, and product catalog; when an AE creates a quote selecting products and requesting a discount above the threshold, then the discount approval routes to the configured approver and the quote status is PENDING_APPROVAL; when approved, then a branded PDF is rendered and e-signature link sent to the customer; when the customer accepts, then a sales order is auto-created with locked pricing; (negative) when a quote is sent with a discount above threshold without approval, then the action is rejected with 403 and error code DISCOUNT_APPROVAL_REQUIRED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`quote` { id: string (qt_*), external_id: string, opportunity_id: string, version: int, status: enum, expiry_date: date, lines: array[{ product_id, quantity, unit_price_minor, currency_code, discount_pct }], total_amount_minor: int64, currency_code: char(3), functional_amount_minor: int64, functional_currency_code: char(3), esignature_url: string, pdf_checksum: string }; linked to `opportunity`, `sales_order`; (reference, product may differ).API and events
`POST /v1/quotes` { external_id, opportunity_id, lines: [{ product_id, quantity, discount_pct }] } -> 201 { id, status, total_amount_minor, currency_code }; `POST /v1/quotes/{id}/approve-discount` { approver_id, notes } -> 200; `POST /v1/quotes/{id}/send` -> 200 { esignature_url }; `POST /v1/quotes/{id}/accept` -> 201 { sales_order_id }; `GET /v1/quotes/{id}`; emits `quote.sent`, `quote.accepted` events; idempotent via `external_id`.State transitions
`DRAFT -> PENDING_APPROVAL -> APPROVED -> SENT -> ACCEPTED | EXPIRED`; terminal `ACCEPTED`, `EXPIRED`, `REJECTED`; guard: SENT requires discount approval if above threshold; ACCEPTED locks pricing and triggers sales order creation; EXPIRED enforced on expiry_date.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.