# 1. Financial Dashboard

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

---

## 1. Financial Dashboard

### 1.1 Total Revenue Overview
**What it does:** Shows the total revenue overview: the total revenue (the revenue, the amount, the period, the source) is shown on the dashboard, so the revenue is visible at a glance (the overview is the summary). The Super Administrator views the total revenue overview (the revenue, the amount, the period, the source) so the viewing is structured and the overview is explicit.

**Sub-features:**
- Total revenue: the revenue (the total revenue, the amount, the period)
- Revenue amount: the amount (the amount of the revenue, the currency)
- Revenue period: the period (the period of the revenue, e.g., the monthly, the quarterly, the annual)
- Revenue source: the source (the source of the revenue, e.g., the subscription, the one-time)
- Revenue trend: the trend (the trend of the revenue, the period, the change)
- Revenue comparison: the comparison (the comparison of the revenue, the periods)
- Dashboard view: the view (the revenue, the amount, the period, the source)
- Audit logging of the revenue overview viewing

**Super Administrator User Journey:**
1. Super Admin views the total revenue overview: the revenue (the total revenue, the amount, the period), the source (the source of the revenue, e.g., the subscription, the one-time), and the period (the period of the revenue); the overview is explicit.
2. Views the revenue amount: the amount (the amount of the revenue, the currency); the amount is the value.
3. Sets the revenue period: the period (the period of the revenue, e.g., the monthly, the quarterly, the annual); the period is the scope.
4. Views the revenue source: the source (the source of the revenue, e.g., the subscription, the one-time); the source is the origin.
5. Views the revenue trend: the trend (the trend of the revenue, the period, the change); the trend is the direction.
6. Compares the revenue: the comparison (the comparison of the revenue, the periods); the comparison is the analysis.
7. The revenue is visible: the revenue, the amount, the period, the source, so the overview is complete.
8. The revenue overview viewing is audit-logged with the revenue, the period, and the timestamp.

**Rules & Edge Cases:**
- The total revenue is the summary (the total revenue, the amount, the period); the revenue is the value.
- The revenue amount is the measure (the amount of the revenue, the currency); the amount is the value.
- The revenue period is the scope (the period of the revenue, e.g., the monthly, the quarterly, the annual); the period is the control.
- The revenue trend is the direction (the trend of the revenue, the period, the change); the trend is the insight.
- The revenue is visible (the revenue, the amount, the period, the source); the viewing is managed.
- Revenue overview viewing is audit-logged with the revenue, period, and timestamp.

### 1.2 Active Subscriptions and Revenue
**What it does:** Shows the active subscriptions and their revenue: the active subscriptions (the subscription, the user, the plan, the amount, the date) and their revenue (the revenue, the amount, the period) are shown on the dashboard, so the subscriptions are visible (the overview is the summary). The Super Administrator views the active subscriptions and revenue (the subscription, the plan, the amount, the period) so the viewing is structured and the overview is explicit.

**Sub-features:**
- Active subscription: the subscription (the active subscription, the user, the plan, the amount, the date)
- Subscription count: the count (the count of the active subscriptions)
- Subscription revenue: the revenue (the revenue of the active subscriptions, the amount, the period)
- Subscription plan: the plan (the plan of the subscription, e.g., the monthly, the annual)
- Subscription period: the period (the period of the subscription, e.g., the monthly, the quarterly)
- Subscription view: the view (the subscriptions, the plans, the amounts, the period)
- Subscription export: the export (the subscriptions, the format, the period)
- Audit logging of the active subscription viewing

**Super Administrator User Journey:**
1. Super Admin views the active subscriptions: the subscriptions (the active subscription, the user, the plan, the amount, the date), the count (the count of the active subscriptions), and the period (the period of the subscriptions); the overview is explicit.
2. Views the subscription count: the count (the count of the active subscriptions); the count is the measure.
3. Views the subscription revenue: the revenue (the revenue of the active subscriptions, the amount, the period); the revenue is the value.
4. Views the subscription plans: the plan (the plan of the subscription, e.g., the monthly, the annual); the plan is the tier.
5. Sets the subscription period: the period (the period of the subscription, e.g., the monthly, the quarterly); the period is the scope.
6. Exports the subscriptions: the export (the subscriptions, the format, the period); the export is the record.
7. The subscriptions are visible: the subscriptions, the plans, the amounts, the period, so the overview is complete.
8. The active subscription viewing is audit-logged with the subscription, the period, and the timestamp.

**Rules & Edge Cases:**
- The active subscription is the ongoing (the active subscription, the user, the plan, the amount, the date); the subscription is the state.
- The subscription count is the measure (the count of the active subscriptions); the count is the volume.
- The subscription revenue is the value (the revenue of the active subscriptions, the amount, the period); the revenue is the income.
- The subscription plan is the tier (the plan of the subscription, e.g., the monthly, the annual); the plan is the level.
- The subscriptions are visible (the subscriptions, the plans, the amounts, the period); the viewing is managed.
- Active subscription viewing is audit-logged with the subscription, period, and timestamp.

### 1.3 Pending and Failed Payments
**What it does:** Shows the pending and failed payments: the pending payments (the payment, the user, the amount, the date) and the failed payments (the payment, the user, the amount, the date, the reason) are shown on the dashboard, so the payments are visible (the overview is the summary). The Super Administrator views the pending and failed payments (the payment, the user, the amount, the date, the reason) so the viewing is structured and the overview is explicit.

**Sub-features:**
- Pending payment: the payment (the pending payment, the user, the amount, the date)
- Failed payment: the payment (the failed payment, the user, the amount, the date, the reason)
- Payment count: the count (the count of the pending and failed payments)
- Payment amount: the amount (the amount of the pending and failed payments)
- Payment reason: the reason (the reason for the failed payment, e.g., the card declined)
- Payment view: the view (the payments, the users, the amounts, the period)
- Payment export: the export (the payments, the format, the period)
- Audit logging of the pending and failed payment viewing

**Super Administrator User Journey:**
1. Super Admin views the pending and failed payments: the payments (the pending payment, the failed payment, the user, the amount, the date), the count (the count of the payments), and the period (the period of the payments); the overview is explicit.
2. Views the pending payments: the payment (the pending payment, the user, the amount, the date); the payment is the in-progress.
3. Views the failed payments: the payment (the failed payment, the user, the amount, the date, the reason); the payment is the error.
4. Views the payment count: the count (the count of the pending and failed payments); the count is the measure.
5. Views the payment amount: the amount (the amount of the pending and failed payments); the amount is the value.
6. Exports the payments: the export (the payments, the format, the period); the export is the record.
7. The payments are visible: the payments, the users, the amounts, the period, so the overview is complete.
8. The pending and failed payment viewing is audit-logged with the payment, the period, and the timestamp.

**Rules & Edge Cases:**
- The pending payment is the in-progress (the pending payment, the user, the amount, the date); the payment is the state.
- The failed payment is the error (the failed payment, the user, the amount, the date, the reason); the payment is the state.
- The payment count is the measure (the count of the pending and failed payments); the count is the volume.
- The payment reason is the cause (the reason for the failed payment, e.g., the card declined); the reason is the explanation.
- The payments are visible (the payments, the users, the amounts, the period); the viewing is managed.
- Pending and failed payment viewing is audit-logged with the payment, period, and timestamp.

### 1.4 Refunds Processed
**What it does:** Shows the refunds processed: the refunds (the refund, the user, the amount, the date, the reason) are shown on the dashboard, so the refunds are visible (the overview is the summary). The Super Administrator views the refunds processed (the refund, the user, the amount, the date, the reason) so the viewing is structured and the overview is explicit.

**Sub-features:**
- Refund: the refund (the refund, the user, the amount, the date, the reason)
- Refund count: the count (the count of the refunds)
- Refund amount: the amount (the amount of the refunds)
- Refund reason: the reason (the reason for the refund, e.g., the cancellation)
- Refund period: the period (the period of the refunds, e.g., the monthly, the quarterly)
- Refund view: the view (the refunds, the users, the amounts, the period)
- Refund export: the export (the refunds, the format, the period)
- Audit logging of the refund viewing

**Super Administrator User Journey:**
1. Super Admin views the refunds processed: the refunds (the refund, the user, the amount, the date, the reason), the count (the count of the refunds), and the period (the period of the refunds); the overview is explicit.
2. Views the refund count: the count (the count of the refunds); the count is the measure.
3. Views the refund amount: the amount (the amount of the refunds); the amount is the value.
4. Views the refund reason: the reason (the reason for the refund, e.g., the cancellation); the reason is the cause.
5. Sets the refund period: the period (the period of the refunds, e.g., the monthly, the quarterly); the period is the scope.
6. Exports the refunds: the export (the refunds, the format, the period); the export is the record.
7. The refunds are visible: the refunds, the users, the amounts, the period, so the overview is complete.
8. The refund viewing is audit-logged with the refund, the period, and the timestamp.

**Rules & Edge Cases:**
- The refund is the return (the refund, the user, the amount, the date, the reason); the refund is the reversal.
- The refund count is the measure (the count of the refunds); the count is the volume.
- The refund amount is the value (the amount of the refunds); the amount is the measure.
- The refund reason is the cause (the reason for the refund, e.g., the cancellation); the reason is the explanation.
- The refunds are visible (the refunds, the users, the amounts, the period); the viewing is managed.
- Refund viewing is audit-logged with the refund, period, and timestamp.