How to configure approval workflows in Auliq ERP
Design and configure approval chains: single and multi-step approvals, thresholds, delegation, and escalation.
Prerequisites
- Administrator role in Auliq ERP
- A written approval policy
Steps
Map the approval policy first
Write the policy before configuring: what gets approved, by whom, at what thresholds, and what happens on timeout or absence. Configuration mirrors the document; do not let the tool define the policy.
Define approval chains
In ERP settings, create the approval chains. A chain is an ordered list of approver roles with optional amount thresholds. Requests route through the chain in order and stop when every required approval is collected.
Set thresholds and routing rules
Attach thresholds so low-value requests skip senior approvers and high-value ones do not. Route by request type and organization where the same approval means different things in different units.
Configure delegation and escalation
For each approver role, configure delegation so absences do not stall requests, and set escalation timers so a request pending beyond your policy limit notifies the approver's manager.
Test with real scenarios
Before enabling broadly, run test requests through each chain: a standard case, a threshold boundary, a delegated approver, and a timeout escalation. Verify the routing and the notifications in each.
Enable and document
Enable the chains, then document them where users can see: who approves what, expected turnaround, and how to check a request's position. Approvals feel fair when the rules are visible.
Tips
- Review thresholds annually; approval chains set for last year's volumes quietly generate friction as the business grows.
- Every approval action is logged with who, when, and on which request; use the log, not memory, when auditing.