Unified queue
Expenses, advances and leave in one list rather than three screens.
The problem
What this replaces today
Approvals happen over calls and messages. There is no record of who approved what, and requests stall because nobody knows they are waiting.
How it works
The workflow, end to end
01
Request is submitted
An expense, advance or leave request enters the queue.
02
It reaches the right approver
Routing follows your reporting structure and permissions.
03
Decision is recorded
Approve or reject with the decision and actor stored.
04
Downstream updates
Approved records flow into reports, dashboards and payroll inputs where relevant.
What you get
Built for the way the work actually happens
Consistent lifecycle
Draft, submitted, approved, rejected, processed and closed states across request types.
Server-side permissions
Only authorised approvers can act, enforced in the backend.
Decision history
Every decision is attributable and reviewable.
Connected
How this fits the rest of the platform
Information is captured once and reused wherever it is relevant.
- Expenses, advances and leave all use this engine rather than separate logic.
- Approval outcomes update dashboards and reports immediately.
- Future approval-based modules reuse the same flow.
Questions
Common questions
Can we have different approvers per location?+
Yes. Routing follows the reporting structure and permissions you configure per location and team.
Is there a record of approvals?+
Yes. Decisions are recorded with the actor and timestamp.