Purchase Requisitions is where ERP discipline either begins or breaks.
Purchase Requisition Submission and Approval Workflow 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: Every purchase request above threshold receives documented multi-level approval before any commitment is made; average approval cycle time is measurable and reportable; zero unauthorized spend commitments.
The control flow a finance team actually needs.
Step 1
Approval Routing Rules At Least Three...
Step 2
Partial Approval Of Individual Lines Be...
Step 3
Timeout Escalation Re-Route After A...
Step 4
Rejected Lines Carry Rejector ID,...
Step 5
Requisition-Level Budget Pre-Check Run...
The ERP surface involved.
Module
Purchase Requisitions
Actors
Requester, Department Manager, Finance Controller, Procurement System
Tier
Tier 1
Finance area
Procurement & Supplier Management
Region lens
US and UK finance teams
Publication date
April 21, 2026
Approval routing rules must support at least three tiers (line manager → department head → finance controller) with configurable threshold amounts per tier; partial approval of individual lines must be supported; timeout escalation must re-route after a configurable number of business hours; rejected lines must carry rejector ID, timestamp, and reason; requisition-level budget pre-check must run at submit time and again at each approval step.
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 | Approval routing rules must support at least three tiers (line manager → department head → finance controller) with configurable threshold amounts per tier | Given a requester with a valid GL account and cost-center budget headroom |
| Control 2 | partial approval of individual lines must be supported | when a requisition is submitted with item description, quantity, estimated_unit_cost_minor, currency_code, required_by_date, cost_center_id, and gl_account_id |
| Control 3 | timeout escalation must re-route after a configurable number of business hours | then system validates GL and budget, routes to tier-appropriate approver, sends in-app and email notification, and requisition moves to PENDING_APPROVAL |
| Control 4 | rejected lines must carry rejector ID, timestamp, and reason | negative) when GL account does not exist then POST returns 422 with problem+json code INVALID_GL_ACCOUNT. |
| Control 5 | requisition-level budget pre-check must run at submit time and again at each approval step. | Every purchase request above threshold receives documented multi-level approval before any commitment is made; average approval cycle time is measurable and reportable; zero unauthorized spend commitments. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A requester submits a purchase requisition specifying item description, quantity, estimated unit cost, required-by date, cost center, and GL account; the system validates GL account existence and cost-center budget headroom and routes the requisition to the appropriate approver tier based on monetary threshold rules (configurable per entity). Each approver receives an in-app and email notification with a one-click approve/reject action; rejections require a mandatory comment. On full approval the requisition status moves to Approved-Pending-PO and the requester is notified. |
| Control rules | Approval routing rules must support at least three tiers (line manager → department head → finance controller) with configurable threshold amounts per tier; partial approval of individual lines must be supported; timeout escalation must re-route after a configurable number of business hours; rejected lines must carry rejector ID, timestamp, and reason; requisition-level budget pre-check must run at submit time and again at each approval step. |
| Acceptance proof | Given a requester with a valid GL account and cost-center budget headroom; when a requisition is submitted with item description, quantity, estimated_unit_cost_minor, currency_code, required_by_date, cost_center_id, and gl_account_id; then system validates GL and budget, routes to tier-appropriate approver, sends in-app and email notification, and requisition moves to PENDING_APPROVAL; (negative) when GL account does not exist then POST returns 422 with problem+json code INVALID_GL_ACCOUNT. |
| 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
`purchase_requisition` { id: string, entity_id: string, requester_id: string, status: enum, submitted_at: timestamp, external_id: string }; `requisition_line` { id: string, requisition_id: string, description: string, quantity: int, estimated_unit_cost_minor: int64, currency_code: char(3), gl_account_id: string, cost_center_id: string, status: enum }; `approval_step` { id: string, requisition_id: string, approver_role: string, threshold_minor: int64, currency_code: char(3), decision: enum, decision_at: timestamp, rejector_id: string, reason: string, escalated_at: timestamp }; (reference, product may differ).API and events
`POST /v1/purchase-requisitions` { lines[{description, quantity, estimated_unit_cost_minor, currency_code, required_by_date, cost_center_id, gl_account_id}] } -> 201 { id, status, approval_route }; `POST /v1/purchase-requisitions/{id}/approve` { line_ids[] } -> 200; `POST /v1/purchase-requisitions/{id}/reject` { line_id, reason } -> 200; emits `procurement.requisition_submitted`, `procurement.requisition_approved`, `procurement.requisition_rejected` events; idempotent via `external_id`.State transitions
`DRAFT -> PENDING_APPROVAL -> PARTIALLY_APPROVED -> APPROVED_PENDING_PO`; terminal `REJECTED`, `CANCELLED`; guard: APPROVED_PENDING_PO requires all required approval tiers satisfied; rejection requires non-empty reason; timeout escalation re-routes after configurable business hours.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.