# 3. Payout Configuration

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Payout Configuration

### 3.1 Configure Payout Thresholds
**What it does:** Configures the payout thresholds: the minimum amount the affiliate must earn before the payout is made (the threshold, e.g., 1000) is set, so the payouts are controlled (the payout is made only when the threshold is met). The Super Administrator defines the payout thresholds (the threshold, the scope) so the payouts are structured and the thresholds are explicit.

**Sub-features:**
- Payout threshold: the threshold (the minimum amount, e.g., 1000)
- Threshold scope: the scope (the threshold applies to the affiliate's earnings)
- Threshold definition: the threshold defined by the Super Admin (the threshold, the scope)
- Threshold enforcement: the threshold enforced (the payout is made only when the threshold is met)
- Threshold record: the threshold recorded (the affiliate, the threshold, the earnings)
- Threshold change: the threshold changed (the threshold updated)
- Audit logging of the threshold definition and the enforcement

**Super Administrator User Journey:**
1. Super Admin defines the payout threshold: the threshold (the minimum amount, e.g., 1000) and the scope (the threshold applies to the affiliate's earnings); the threshold is explicit.
2. Sets the payout threshold: the threshold (the minimum amount, e.g., 1000); the threshold is the minimum.
3. Sets the threshold scope: the scope (the threshold applies to the affiliate's earnings); the scope is the application.
4. Saves; the payout threshold is live, and the payout is made only when the threshold is met.
5. An affiliate's earnings are evaluated; the threshold is enforced (the earnings meet the threshold, the payout is made); the payout is recorded.
6. For a threshold change (the threshold updated), Super Admin changes the threshold (the new threshold, the time); the change is recorded.
7. Reviews the thresholds: the affiliates, the thresholds, the earnings, so the payouts are visible.
8. The threshold definition and the enforcement are audit-logged with the affiliate, the threshold, and the timestamp.

**Rules & Edge Cases:**
- The payout threshold is the minimum (the minimum amount, e.g., 1000); the threshold is the gate.
- The threshold scope is the application (the threshold applies to the affiliate's earnings); the scope is the control.
- The threshold enforcement is the control (the payout is made only when the threshold is met); the enforcement is the gate.
- A threshold change (the threshold updated) is recorded (the new threshold, the time); it is auditable.
- The payout thresholds are visible (the affiliates, the thresholds, the earnings); the payouts are managed.
- Threshold definition and enforcement are audit-logged with the affiliate, threshold, and timestamp.

### 3.2 Configure Payout Schedules
**What it does:** Configures the payout schedules: the schedule for the payouts (the frequency, e.g., the monthly, the quarterly) is set, so the payouts are timed (the payout is made per the schedule). The Super Administrator defines the payout schedules (the frequency, the date, the scope) so the schedules are structured and the timing is explicit.

**Sub-features:**
- Payout frequency: the frequency (the monthly, the quarterly)
- Payout date: the date (the date of the payout, e.g., the 1st of the month)
- Schedule scope: the scope (the schedule applies to the affiliates' payouts)
- Schedule definition: the schedule defined by the Super Admin (the frequency, the date, the scope)
- Schedule enforcement: the schedule enforced (the payout is made per the schedule)
- Schedule record: the schedule recorded (the affiliate, the frequency, the date, the payout)
- Audit logging of the schedule definition and the enforcement

**Super Administrator User Journey:**
1. Super Admin defines the payout schedule: the frequency (the monthly, the quarterly), the date (the date of the payout, e.g., the 1st of the month), and the scope (the schedule applies to the affiliates' payouts); the schedule is explicit.
2. Sets the payout frequency: the frequency (the monthly, the quarterly); the frequency is the timing.
3. Sets the payout date: the date (the date of the payout, e.g., the 1st of the month); the date is the day.
4. Sets the schedule scope: the scope (the schedule applies to the affiliates' payouts); the scope is the application.
5. Saves; the payout schedule is live, and the payout is made per the schedule.
6. The payout date arrives; the schedule is enforced (the payout is made per the schedule, the threshold is met); the payout is recorded.
7. For a schedule change (the frequency, the date, the scope updated), Super Admin changes the schedule (the new frequency, the new date, the new scope, the time); the change is recorded.
8. The schedule definition and the enforcement are audit-logged with the affiliate, the frequency, and the timestamp.

**Rules & Edge Cases:**
- The payout frequency is the timing (the monthly, the quarterly); the frequency is the schedule.
- The payout date is the day (the date of the payout, e.g., the 1st of the month); the date is the control.
- The schedule scope is the application (the schedule applies to the affiliates' payouts); the scope is the control.
- A schedule change (the frequency, the date, the scope updated) is recorded (the new frequency, the new date, the new scope, the time); it is auditable.
- The payout schedules are visible (the affiliates, the frequencies, the dates, the payouts); the schedules are managed.
- Schedule definition and enforcement are audit-logged with the affiliate, frequency, and timestamp.

### 3.3 Payment Request Approval Workflow
**What it does:** Configures the payment request approval workflow: the workflow for the payment requests (the request, the approval, the payout) is set, so the payouts are approved (the request is approved before the payout). The Super Administrator defines the approval workflow (the request, the approval steps, the approver) so the workflow is structured and the approvals are explicit.

**Sub-features:**
- Payment request: the request (the affiliate's request for the payout)
- Approval steps: the steps (the steps for the approval, e.g., the review, the approval)
- Approver: the approver (the one who approves the request, e.g., the Super Admin)
- Workflow definition: the workflow defined by the Super Admin (the request, the steps, the approver)
- Request submission: the submission (the affiliate submits the request)
- Request approval: the approval (the approver approves the request)
- Audit logging of the workflow definition and the approvals

**Super Administrator User Journey:**
1. Super Admin defines the approval workflow: the request (the affiliate's request for the payout), the approval steps (the steps for the approval, e.g., the review, the approval), and the approver (the one who approves the request, e.g., the Super Admin); the workflow is explicit.
2. Sets the payment request: the request (the affiliate's request for the payout); the request is the trigger.
3. Sets the approval steps: the steps (the steps for the approval, e.g., the review, the approval); the steps are the process.
4. Sets the approver: the approver (the one who approves the request, e.g., the Super Admin); the approver is the authority.
5. Saves; the approval workflow is live, and the payouts are approved (the request is approved before the payout).
6. An affiliate submits a payment request; the workflow is enforced (the request is reviewed, the approver approves); the approval is recorded.
7. For a workflow change (the steps, the approver updated), Super Admin changes the workflow (the new steps, the new approver, the time); the change is recorded.
8. The workflow definition and the approvals are audit-logged with the affiliate, the request, and the timestamp.

**Rules & Edge Cases:**
- The payment request is the trigger (the affiliate's request for the payout); the request is the start.
- The approval steps are the process (the steps for the approval, e.g., the review, the approval); the steps are the workflow.
- The approver is the authority (the one who approves the request, e.g., the Super Admin); the approver is the control.
- A workflow change (the steps, the approver updated) is recorded (the new steps, the new approver, the time); it is auditable.
- The approval workflow is visible (the requests, the steps, the approvers, the approvals); the workflow is managed.
- Workflow definition and approvals are audit-logged with the affiliate, request, and timestamp.