Approvals & controls
Any document type in Bebaak can need approval before it is submitted — bills, payments, purchase orders, journals, expense claims, society requests and more. An authority matrix routes each document to the right approver by role, amount and entity, and every decision is recorded.
Finding your way around
- Settings → Approvals: workflows, authority matrix, delegation and segregation rules (admins).
- Your approval inbox: the bell, the Approvals page, the installable phone app or the email Approve / Reject buttons.
In this area
8 step-by-step guides
How to make a document type need approval
Turn on approval for any document type and choose when it applies.
How to set up the approval authority matrix
Delegation of financial powers: who can approve what, by role, amount band and entity, with automatic routing up the hierarchy.
How to delegate approvals
Hand your approvals to someone else for a period (leave) or permanently; their decisions are recorded as "approved on behalf of" you.
How segregation of duties is enforced
The person who creates a document cannot approve it, and conflicting roles can be kept apart.
How to use your approvals inbox
Everything waiting for your decision, raised by you, overdue or closed — approve one at a time or in bulk.
How to decide one approval request
One request: summary, approvers, message thread, and approve / reject / send back / withdraw / reopen.
How to approve from an email
Approval emails carry Approve and Reject buttons. Each opens a signed, one-time link to confirm your decision.
How reminders, escalation and the daily digest work
Pending approvals don't sit forever: reminders, escalation after a set time, a daily digest and a defined closure.
Can't find it?
Search all guides or ask our team.