Maker–checker approvals
The person who does the work is never the one who approves it
CLEX Legal enforces the maker–checker principle: whoever submits an obligation, closes a month, raises an exception or prepares a contract cannot approve it. A second person reviews, approves or sends it back with a reason, and every step is written to the audit trail.
What it does
How maker–checker approvals works
- 1
A rule the system enforces
Separation of duties is not a policy document. The product will not let the same person make and check the same thing.
- 2
One list of what is waiting
Everything waiting on a checker — submissions, closing requests, contracts, exceptions, vendor checks — is in a single Approvals list, each decided on its own page.
- 3
Send back with a reason
A checker who is not satisfied returns the work with a reason the maker sees. The maker can take a request back before it is decided.
- 4
Roles you can shape
Admin, Maker, Checker and a person who is both come ready-made. Add custom roles with exactly the permissions a job needs; a checker can be limited to one organisation, unit or vendor.
Illustration of the screen. Figures shown are examples.
Questions
About maker–checker approvals
Used by
What is the maker–checker principle?
It is the control that requires two different people for one action: a maker prepares or submits it and a checker independently reviews and approves it. It reduces error and fraud because no one person can complete the whole action alone.
What if there is only one person in the workspace?
A workspace with a single approver can allow that person to approve a closing request they raised. The setting is explicit, and the approval is still recorded as theirs.
Keep exploring
The rest of the product
See your compliance in one calm place
Sign in to your workspace, or read what we publish for free.