Sales Pipeline is where ERP discipline either begins or breaks.
Opportunity Creation and Pipeline Progression 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: 100% of opportunities have close date, stage, and estimated value populated; win/loss analysis available with reason codes; average sales cycle length reportable by segment
The control flow a finance team actually needs.
Step 1
Pipeline Stages Configurable Per Sales...
Step 2
Fields Enforced Per Stage Transition
Step 3
Stage Duration Tracked Per Opportunity
Step 4
Automated Task Creation On Stage Entry
Step 5
Closed-Won Auto-Triggers Sales Order...
The ERP surface involved.
Module
Sales Pipeline
Actors
Account Executive, Sales Manager, CRM System
Tier
Tier 3
Finance area
Sales, CRM & Customer Management
Region lens
US and UK finance teams
Publication date
May 20, 2026
Pipeline stages configurable per sales team; required fields enforced per stage transition; stage duration tracked per opportunity; automated task creation on stage entry; closed-won auto-triggers sales order creation workflow; probability percentage auto-suggested by stage but overridable; historical stage progression preserved as timeline; win/loss reason mandatory on close
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 | Pipeline stages configurable per sales team | Given an opportunity created from a converted lead with stage Discovery and a close date |
| Control 2 | required fields enforced per stage transition | when the AE advances the stage to Demo, then a stage-entry task is auto-created, stage duration tracking begins, and probability is updated to the stage default |
| Control 3 | stage duration tracked per opportunity | when stage advances to Closed Won, then a sales order creation workflow is triggered and win reason is required |
| Control 4 | automated task creation on stage entry | negative) when the AE attempts to skip from Discovery directly to Closed Won without completing required fields for intermediate stages, then the transition is rejected with 422 and error code REQUIRED_FIELDS_MISSING. |
| Control 5 | closed-won auto-triggers sales order creation workflow | 100% of opportunities have close date, stage, and estimated value populated; win/loss analysis available with reason codes; average sales cycle length reportable by segment |
| Control 6 | probability percentage auto-suggested by stage but overridable | 100% of opportunities have close date, stage, and estimated value populated; win/loss analysis available with reason codes; average sales cycle length reportable by segment |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | |
| Control rules | Pipeline stages configurable per sales team; required fields enforced per stage transition; stage duration tracked per opportunity; automated task creation on stage entry; closed-won auto-triggers sales order creation workflow; probability percentage auto-suggested by stage but overridable; historical stage progression preserved as timeline; win/loss reason mandatory on close |
| Acceptance proof | Given an opportunity created from a converted lead with stage Discovery and a close date; when the AE advances the stage to Demo, then a stage-entry task is auto-created, stage duration tracking begins, and probability is updated to the stage default; when stage advances to Closed Won, then a sales order creation workflow is triggered and win reason is required; (negative) when the AE attempts to skip from Discovery directly to Closed Won without completing required fields for intermediate stages, then the transition is rejected with 422 and error code REQUIRED_FIELDS_MISSING. |
| 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
`opportunity` { id: string (opp_*), external_id: string, account_id: string, stage: enum, probability: int, estimated_value_minor: int64, currency_code: char(3), close_date: date, win_loss_reason: string, stage_history: array, created_at: timestamp, status: enum(OPEN, CLOSED_WON, CLOSED_LOST) }; linked to `account`, `contact`, `sales_order`; (reference, product may differ).API and events
`POST /v1/opportunities` { external_id, account_id, stage, estimated_value_minor, currency_code, close_date } -> 201 { id, probability, status }; `PATCH /v1/opportunities/{id}` { stage, win_loss_reason } -> 200; `GET /v1/opportunities/{id}`; emits `opportunity.stage_changed`, `opportunity.closed_won`, `opportunity.closed_lost` events; idempotent via `external_id`.State transitions
`OPEN(Discovery) -> OPEN(Demo) -> OPEN(Proposal) -> OPEN(Negotiation) -> CLOSED_WON | CLOSED_LOST`; terminal `CLOSED_WON`, `CLOSED_LOST`; guard: CLOSED_WON and CLOSED_LOST require win_loss_reason; each stage transition enforces required field validation; stage duration tracked per transition.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.