Maker-Checker Workflow — Engine, User/Role, Product & Programme Approvals

Banks with a regulatory requirement for segregation of duties on administrative actions can now enforce four-eyes control natively within the platform. No out-of-band approval process is needed. Checkers are notified automatically and can approve or reject from within the platform.

The implementation covers five stories:

(1) Core engine — the approval workflow engine, state machine, and audit trail infrastructure;

2) User & Role Management — creating, editing, and deactivating users and roles requires a Checker to approve before taking effect;

(3) Portal Governance — portal-level admin actions are subject to maker-checker controls;

(4) Product & Programme Approvals — creating and modifying products and programmes requires dual approval;

(5) Notifications — email and in-app notifications are sent to Checkers when a Maker submits an action for approval, and to Makers when approved or rejected. All approved and rejected actions are recorded in the audit trail with full detail.