Pricing Engine is where ERP discipline either begins or breaks.
Pricing and Discount Management 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: Zero quotes sent with unapproved discounts above threshold; pricing manager can publish new price list on effective date without engineer involvement; full discount approval audit trail available for deal review
The control flow a finance team actually needs.
Step 1
Multiple Concurrent Price Lists With...
Step 2
Effective-Date Publishing With Rollback...
Step 3
Discount Schedule Enforces Approval...
Step 4
Approval Requests Include Deal Context
Step 5
Price List Changes Versioned With Diff...
The ERP surface involved.
Module
Pricing Engine
Actors
Pricing Manager, Sales Rep, Approval Workflow Engine
Tier
Tier 1
Finance area
Sales, CRM & Customer Management
Region lens
US and UK finance teams
Publication date
May 22, 2026
Multiple concurrent price lists with priority ordering and customer-tier assignment; effective-date publishing with rollback capability; discount schedule enforces approval routing by discount tier (e.g., >10%→manager, >20%→VP); approval requests include deal context (ARR, strategic value, competitive notes); price list changes versioned with diff view; currency exchange rates applied from configured rate table; audit log of every price override with who approved and when; price list import via CSV
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 | Multiple concurrent price lists with priority ordering and customer-tier assignment | Given a pricing manager with an active price list and discount schedules |
| Control 2 | effective-date publishing with rollback capability | when a price list is created with effective date, tier, and discount approval matrix, then it activates on the effective date and the CPQ engine uses it for new quotes |
| Control 3 | | when a sales rep requests a discount above threshold, then the request routes to the configured approver with deal context |
| Control 4 | approval requests include deal context (ARR, strategic value, competitive notes | when approved, the discount is logged with approver identity and timestamp |
| Control 5 | price list changes versioned with diff view | negative) when a quote is submitted with an unapproved discount above the threshold, then it is rejected with 403 and error code UNAPPROVED_DISCOUNT. |
| Control 6 | currency exchange rates applied from configured rate table | Zero quotes sent with unapproved discounts above threshold; pricing manager can publish new price list on effective date without engineer involvement; full discount approval audit trail available for deal review |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A pricing manager creates or updates a price list defining list prices by product SKU and currency, effective date, and customer tier. Discount schedules are created specifying maximum discounts by product category and deal size band, each requiring a configured approval chain above a threshold. When a sales rep requests a custom discount, the request routes through the approval chain with deal context attached. Approved discounts are applied to the quote and logged with approver identity and timestamp. Pricing changes publish to the CPQ engine on effective date without requiring application restart. |
| Control rules | |
| Acceptance proof | Given a pricing manager with an active price list and discount schedules; when a price list is created with effective date, tier, and discount approval matrix, then it activates on the effective date and the CPQ engine uses it for new quotes; when a sales rep requests a discount above threshold, then the request routes to the configured approver with deal context; when approved, the discount is logged with approver identity and timestamp; (negative) when a quote is submitted with an unapproved discount above the threshold, then it is rejected with 403 and error code UNAPPROVED_DISCOUNT. |
| 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
`price_list` { id: string (pl_*), external_id: string, name: string, currency_code: char(3), effective_date: date, status: enum(DRAFT, ACTIVE, ARCHIVED), customer_tier: string, lines: array[{ product_id, unit_price_minor }], version: int }; `discount_approval` { id, price_list_id, opportunity_id, discount_pct, approver_id, status: enum, approved_at: timestamp }; (reference, product may differ).API and events
`POST /v1/price-lists` { external_id, name, currency_code, effective_date, customer_tier, lines } -> 201 { id, status }; `POST /v1/price-lists/{id}/activate` -> 200; `POST /v1/discount-approvals` { opportunity_id, discount_pct, deal_context } -> 201 { id, status }; `POST /v1/discount-approvals/{id}/approve` { approver_id } -> 200; `GET /v1/price-lists/{id}`; emits `price_list.activated`, `discount.approved` events; idempotent via `external_id`.State transitions
Price list: `DRAFT -> ACTIVE -> ARCHIVED`; discount approval: `PENDING -> APPROVED | REJECTED`; guard: ACTIVE requires effective_date reached; ARCHIVED price list not selectable for new quotes; APPROVED discount logged with approver_id and timestamp.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.