Activate two-person rules

The two-person rule is the single most important compliance control in the MFI Suite. Without it, a single corrupt officer can disburse a fictitious loan, lift a blacklist, and reverse the ledger entry in the same session. With it, every sensitive action needs two independent users — and the audit trail proves it.

What the engine does

The mfi_two_person module registers a generic Python hook that any other module can call via self.env['mfi.two.person'].require(rule_code, record, payload). The hook:

1. Checks the rule definition in mfi.two.person.rule.
2. If the action exceeds a threshold or matches a category, blocks the immediate commit and creates a mfi.two.person.request in state pending_concurrence.
3. Emails / app-notifies the eligible approvers (filtered by group + branch).
4. On concurrence, runs the original action with the original user as create_uid and the concurring user as concurrence_uid.
5. Writes both legs to the audit log, immutable.

Shipped rules

Eleven rules ship with the suite. Review them and adjust thresholds to your institution's policy.

Configure a rule

Open MFI → Configuration → Two-person rules → LOAN_APPROVE_B2 → Edit:

• Threshold expression: a Python expression evaluated on the record. Default for band 2 is record.approved_amount > 50000 and record.approved_amount <= 250000.
• Concurrer domain: a domain on res.users. Default for band 2: [('groups_id', 'in', ref('mfi_base.group_supervisor').id), ('id', '!=', record.create_uid.id), ('x_allowed_branch_ids', 'in', record.branch_id.id)] — excludes the originator and restricts to same branch.
• Quorum: 1 for most rules; 3 (of 5) for LOAN_APPROVE_B4 (Credit Committee).
• Time-to-live: hours before the pending request auto-expires. Default 24.
• Notification template: mail.template that fires to eligible concurrers.

# Sample custom rule — overriding band 2 to require Branch Manager (not Supervisor)
rule = self.env['mfi.two.person.rule'].browse(ref('LOAN_APPROVE_B2'))
rule.write({
    'concurrer_domain': "["
        "('groups_id', 'in', ref('mfi_base.group_branch_manager').id),"
        "('id', '!=', record.create_uid.id),"
        "('x_allowed_branch_ids', 'in', record.branch_id.id)"
    "]",
    'time_to_live_hours': 4,
})

The concurrence flow

1. Officer clicks Approve on a KES 200K loan.
2. Hook fires, creates a pending request, blocks the commit.
3. Officer sees an in-app banner: 'Pending concurrence from Supervisor — request ID 4471'.
4. Eligible supervisors receive an email and an app notification.
5. Supervisor opens the request, reviews the loan record, clicks Concur or Reject.
6. On Concur, the original action runs and the loan moves to state approved.
7. On Reject, the loan returns to under_appraisal with a comment.
8. On TTL expiry, the request auto-rejects.

Credit Committee quorum

Band 4 (KES 1M–5M) requires 3-of-5 concurrence from the Credit Committee group. The engine waits until three independent users have concurred — partial concurs are visible to all committee members so they can see the running tally.

• All five members receive the notification simultaneously.
• Each member must log in independently — no shared sessions.
• Each member can attach a comment (visible to others) before concurring.
• Once the third concur posts, the loan auto-approves and the remaining two members see 'closed — quorum reached'.
• Any committee member can issue a Veto, which blocks the loan regardless of partial concurs.

Worked scenarios

Reference

Fields on mfi.two.person.rule

States on mfi.two.person.request

Troubleshooting

See also

• Roles
• Branches
• Audit
• Approvals