Approvals: thresholds, approver, deputy, escalation
The approval rule is written down once and applied the same way every time: who says yes, up to how much, who covers when they are away, and what happens after 24 hours of silence.
The problem it solves
Most automation projects stall at the approval step because nobody has ever written the rule down. This one forces the four lines: threshold, named approver, named deputy, and what happens when both are unavailable.
What it does
- A request arrives from a form, the ERP or Slack. The policy picks the tier by type and amount: under AED 5,000 approved automatically, then manager, director, CEO.
- Checks who is out of office and routes to the named deputy. A requester can never approve their own request; it escalates instead.
- Sends the request to the approver on Slack or email and tells the requester where it went and why.
- A decision callback is validated: only the current approver can decide, and only once. Anyone else gets a 409.
- An hourly sweep escalates anything past the SLA to the deputy or the CEO and logs it.
How it was tested
- Auto approval under threshold, manager tier, director out of office routed to deputy, requester equals approver escalated, valid decision, decision by the wrong person refused, forced escalation sweep.
- 7 of 7 as expected.
Screens
Who it is for
Any company where invoices wait four days in an inbox for a yes.
See it running on a call → hamza.jamal@finamatik.com
Built and tested on sample data before any live credential is connected. Every system Finamatik ships is adapted to the client's own tools and owned by the client outright.