Glossary
Maker ≠ checker
The control that the person who drafts or configures something cannot be the person who approves it; cutovers and state-system-affecting changes require two different approvers.
Maker ≠ checker means no one approves their own work. For a store it applies where a mistake is costly: a reconciliation report is signed off by someone other than the person who made the adjustments, and pay runs need two approvers.
BudAlly builds it into approval routing by role. A controller approves bills, GMs approve prices, and a single approval queue filters by store, module and person. The security page lists maker ≠ checker on campaigns and cutovers, and there is no "approve all" anywhere in the product.
A POS switch is the clearest case. The cutover needs two approvers, drafts pause during the window, and a rollback plan is linked to the approval. The audit trail then records the reviewer and approver with names, roles and timestamps.
Where this comes up on budally.com
Related terms
- Approval queue
The single list of proposals waiting for a human decision, filtered by store, module and role. There is no 'approve all'. Executed items run under the approver's own POS or state-system credential and are logged.