Important Transactions Shouldn't Happen Without Oversight.
Put controlled authorisation around purchasing, stock changes and selected master-data actions, with clear decision history and role-based access.
How Approvals Work.
Transaction submitted
A user creates a transaction — a requisition, purchase order, stock adjustment or stock count — and submits it for approval.
Pending review
The transaction enters a pending state. The approver is notified and can review the details before making a decision.
Approved or rejected
The approver approves or rejects the transaction. A rejection reason is recorded. The decision is logged against the transaction.
Transaction completed
Approved transactions proceed to completion. Rejected transactions are returned to the originator for correction or cancellation.
What Can Require Approval.
Purchase requisitions & purchase orders
Control purchasing before commitments are made by routing purchasing documents to authorised reviewers.
Stock receipts
Require review of manual stock receipts where your process needs an additional control before inventory is affected.
Stock adjustments
Prevent unauthorised corrections by requiring approval before stock adjustments are posted.
Stock transfers
Control transfers between warehouses or locations before quantities move between operational areas.
Stock counts
Review count results and variances before approved counts are posted to inventory.
Products, suppliers, warehouses & locations
Use approval workflows around selected master-data changes where stronger governance is required.
What's Included.
Configurable workflows
Choose which transaction types require approval. Configure approval requirements to match your operational controls.
Role-based approvers
Approval permissions are tied to user roles. Only users with the appropriate role can approve transactions.
Approval history
Every approval decision is recorded — who approved or rejected, when and with what reason.
Audit trail
Approvals form part of the broader audit trail, giving you a complete record of who authorised what and when.
Rejection reasons
When a transaction is rejected, the approver records a reason. The originator can see why and take corrective action.
Central approvals queue
Review pending requests from one approvals area instead of tracking authorisation through messages, calls or spreadsheets.