Platform - Approval Workflow is where ERP discipline either begins or breaks.
Approval Workflow Engine with Delegation and Escalation 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 payments above policy threshold have documented approval; audit evidence for every approval collected automatically; escalations reduce approval SLA breaches by 80%.
The control flow a finance team actually needs.
Step 1
Multi-Level Sequential And Parallel...
Step 2
Threshold-Based Routing Configurable...
Step 3
Delegation Is Date-Bounded And Audited
Step 4
Escalation Triggers After Configurable SLA
Step 5
Approval Action Creates An Immutable...
The ERP surface involved.
Module
Platform - Approval Workflow
Actors
Requestor, Approver, Delegate, Finance Manager, Workflow Engine
Tier
Tier 1
Finance area
Platform, Integration, Security, Administration & Analytics
Region lens
US and UK finance teams
Publication date
June 23, 2026
Multi-level sequential and parallel approval chains; threshold-based routing configurable per document type, amount range, cost center, and entity; delegation is date-bounded and audited; escalation triggers after configurable SLA (default 48 h); approval action creates an immutable audit event; a single approval task cannot be self-approved by the requestor; workflow engine runs as a Temporal workflow for durability; API to programmatically approve/reject for system integrations; approval history visible on every document.
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 | Multi-level sequential and parallel approval chains | Given an approval policy routing bills >$10,000 to CFO |
| Control 2 | threshold-based routing configurable per document type, amount range, cost center, and entity | when a bill is submitted with amount_minor = 1500000 (USD), then an approval task is created for the CFO and a notification sent |
| Control 3 | delegation is date-bounded and audited | when CFO approves, the bill transitions to APPROVED |
| Control 4 | escalation triggers after configurable SLA (default 48 h | when CFO rejects with comment, the bill returns to DRAFT with the rejection comment visible |
| Control 5 | approval action creates an immutable audit event | negative) when the requestor attempts to self-approve their own bill, then 403 SELF_APPROVAL_FORBIDDEN is returned |
| Control 6 | a single approval task cannot be self-approved by the requestor | 100% of payments above policy threshold have documented approval; audit evidence for every approval collected automatically; escalations reduce approval SLA breaches by 80%. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | |
| Control rules | Multi-level sequential and parallel approval chains; threshold-based routing configurable per document type, amount range, cost center, and entity; delegation is date-bounded and audited; escalation triggers after configurable SLA (default 48 h); approval action creates an immutable audit event; a single approval task cannot be self-approved by the requestor; workflow engine runs as a Temporal workflow for durability; API to programmatically approve/reject for system integrations; approval history visible on every document. |
| Acceptance proof | Given an approval policy routing bills >$10,000 to CFO; when a bill is submitted with amount_minor = 1500000 (USD), then an approval task is created for the CFO and a notification sent; when CFO approves, the bill transitions to APPROVED; when CFO rejects with comment, the bill returns to DRAFT with the rejection comment visible; (negative) when the requestor attempts to self-approve their own bill, then 403 SELF_APPROVAL_FORBIDDEN is returned; when approval SLA of 48 h elapses without action, the system escalates to the next configured level and notifies the approver's manager. |
| 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
`approval_policy` { policy_id: string, entity_id: string, document_type: string, threshold_minor: int64, currency_code: char(3), approver_role_id: string, escalation_hours: int, external_id: string }; `approval_task` { task_id: string, document_type: string, document_id: string, assignee_id: string, status: enum(PENDING,APPROVED,REJECTED,ESCALATED,DELEGATED), due_at: timestamp, external_id: string }; `approval_audit` { task_id: string, action: string, actor_id: string, comment: string, timestamp: timestamp }; (reference, product may differ).API and events
`POST /v1/approval-tasks/{id}/approve` { comment } -> 200 { status: APPROVED }; `POST /v1/approval-tasks/{id}/reject` { comment } -> 200 { status: REJECTED }; `POST /v1/approval-tasks/{id}/delegate` { delegate_id, until_date } -> 200; `GET /v1/approval-tasks?assignee_id=&status=`; emits `approval.task_created`, `approval.approved`, `approval.rejected`, `approval.escalated` events; idempotent via `external_id`.State transitions
`PENDING -> APPROVED | REJECTED | ESCALATED`; delegated state `DELEGATED -> PENDING(delegate)`; terminal `APPROVED` or `REJECTED`; guard: self-approval blocked; SLA escalation after configurable hours; approval history immutable.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.