Multi-Level Approval Workflows
Route purchase requests through the right chain of approvers based on amount, department, and policy, with automatic escalation when an approval stalls.
The problem
Purchase requests stall because approval chains live in spreadsheets, email, and the heads of a few finance people. Nobody can see where a request is stuck, and escalation means chasing someone in a hallway or a chat thread. When auditors ask who approved what and under which policy, reconstructing the chain takes days.
How it runs on Neblex
A Neblex flow picks up new purchase requests from NetSuite and reads the approval matrix from Data Tables: amount thresholds, department chains, and category-specific policies in one editable place. Conditional branching builds the right approver sequence for each request, whether that is one manager or a multi-step chain ending at the CFO.
Each approval step pauses the run until a decision is made, with the request appearing in the approver task inbox and a Slack notification pointing to it. SLA timers with business-hours awareness send reminders and escalate to the next approver or a delegate when a step stalls, and tasks can be reassigned when someone is out. Rejections route back to the requester with the reason attached.
Every decision, reminder, and escalation is written to a tamper-evident, hash-chained audit trail, so the full chain is answerable in one place. Flow changes are governed too: edits move from dev to prod through environments with promotion approvals, and role-based access controls who can edit the approval matrix.
Step by step
Detect new requests
The flow watches NetSuite for new purchase requests using poll-based change detection.
Build the approval chain
The approval matrix in Data Tables maps amount, department, and category to an ordered list of approvers.
Request each approval
Approval steps pause the run at each level, with a task assigned in the inbox and a Slack notification to the approver.
Escalate stalled steps
SLA timers with business-hours awareness remind first, then escalate to the next approver or a named delegate.
Write back the outcome
Approved requests are updated in NetSuite for purchasing to act on, and rejections return to the requester with the reason.
Keep the audit trail
Every decision and escalation is recorded on a hash-chained audit trail for compliance review.
Platform capabilities used
- Poll-based change detection
- Data Tables approval matrix
- Approval steps that pause the run
- Task inbox with reassignment
- Business-hours SLA escalation
- Hash-chained audit trail
Common questions
Can the approval chain differ by department or amount?
Yes. The chain is derived per request from an approval matrix stored in Data Tables, keyed on amount, department, and category. Finance can edit the matrix directly without changing the flow.
What stops someone from bypassing an approval?
Approval steps pause the run, so downstream steps cannot execute until a recorded decision exists. Role-based access limits who can approve, and the hash-chained audit trail makes the history tamper evident.
How do requesters know where a request stands?
Each pending step is a visible task with an assignee in the task inbox, and Slack notifications go out at each stage. Escalations fire automatically, so a stalled request moves instead of waiting.
Related use cases
Expense Categorization and Approval
Categorize submitted expenses, check them against policy, and route each report to the right approver based on amount and type, all in one governed flow.
FinanceInvoice Three-Way Matching
Match incoming invoices to purchase orders and receipts on Neblex, post clean matches to NetSuite automatically, and route exceptions to a reviewer.
IT & DevOpsOnboarding and Offboarding Automation
Turn Workday status changes into same-day provisioning in Okta and Google Admin, and revoke access the moment someone leaves.
Want this running on your stack?
Neblex Integration Fabric is in beta: full platform, free while in beta. Bring this workflow and we will map it to your systems.