Maker-Checker Feature

Overview

The maker-checker feature is a dual-control mechanism designed to add an extra layer of oversight to payment workflows. A maker initiates a payment request, and a checker reviews and approves or rejects it before it is processed — ensuring no single user can complete a sensitive action alone.

Note: The maker-checker feature must be enabled for your organisation before it can be used.

---

How It Works

1. A maker creates a payment request.
2. The request is sent for review instead of being processed immediately.
3. A checker reviews the request and either approves or rejects it.
4. Approved requests are then processed; rejected requests are returned.

Key Rule

A maker cannot review their own payment requests. This enforces the separation of duties that makes the feature effective. The only exception is users with admin privileges, who can review requests they initiated.

---

Roles & Permissions

Maker-checker roles are managed in Team Management Settings. There are two dedicated roles:

Payment Requester

• Can initiate payment creation requests.
• Cannot review their own requests.

Payment Reviewer

• Can review payment requests initiated by other users.
• Can approve or reject pending requests.

Combining Roles

A single user can be assigned both the Payment Requester and Payment Reviewer roles. This allows them to both initiate their own payment requests and review requests from other users (but still not their own).

---

Setting Up Maker-Checker Roles

1. Navigate to Team Management Settings.
2. Select the user you want to configure.
3. Assign the appropriate role(s):
   • Payment Requester — for users who will create payment requests.
   • Payment Reviewer — for users who will review and approve requests.
   • Both — for users who need to do both.
4. Save your changes.

---

Quick Reference