# 7. Billing History

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

---

## 7. Billing History

### 7.1 View Billing History per User
**What it does:** Views the billing history per user: the billing history of the users (the billing, the user, the amount, the date, the status) is viewable, so the billing is visible (the history is the record). The Super Administrator views the billing history (the user, the filters, the period) so the viewing is structured and the history is explicit.

**Sub-features:**
- Billing history: the history (the billing, the user, the amount, the date, the status)
- User billing view: the view (the billing per user, the period)
- Billing filter: the filter (the filter by the user, the amount, the date, the status)
- Billing search: the search (the search by the user, the billing ID)
- Billing export: the export (the billing, the format, the period)
- Billing record: the record (the billing, the user, the amount, the date, the status)
- Audit logging of the billing history viewing

**Super Administrator User Journey:**
1. Super Admin views the billing history: the billing (the billing, the user, the amount, the date, the status), the filters (the user, the amount, the date, the status), and the period (the period of the billing); the history is explicit.
2. Sets the billing filter: the filter (the filter by the user, the amount, the date, the status); the filter is the scope.
3. Views a user's billing: the view (the billing per user, the period); the view is the detail.
4. Searches a billing: the search (the search by the user, the billing ID); the search is the lookup.
5. Exports the billing: the export (the billing, the format, the period); the export is the record.
6. The billing is visible: the billing, the filters, the period, so the history is complete.
7. Reviews the billing history: the billing, the users, the period, so the billing is visible.
8. The billing history viewing is audit-logged with the billing, the user, and the timestamp.

**Rules & Edge Cases:**
- The billing history is the record (the billing, the user, the amount, the date, the status); the history is the timeline.
- The user billing view is the detail (the billing per user, the period); the view is the access.
- The billing filter is the scope (the filter by the user, the amount, the date, the status); the filter is the control.
- The billing search is the lookup (the search by the user, the billing ID); the search is the access.
- The billing is visible (the billing, the filters, the period); the viewing is managed.
- Billing history viewing is audit-logged with the billing, user, and timestamp.

### 7.2 Payment History and Statements
**What it does:** Manages the payment history and statements: the payment history (the payment, the user, the amount, the date, the status) and the statements (the statement, the period, the payments) are managed, so the payments are documented (the history is the record). The Super Administrator views the payment history and statements (the user, the period, the filters) so the management is structured and the history is explicit.

**Sub-features:**
- Payment history: the history (the payment, the user, the amount, the date, the status)
- Payment statement: the statement (the statement, the period, the payments)
- Statement generation: the generation (the statement is generated, the period, the payments)
- History filter: the filter (the filter by the user, the amount, the date, the status)
- History export: the export (the history, the format, the period)
- History record: the record (the payment, the user, the amount, the date, the status)
- Audit logging of the payment history and statement management

**Super Administrator User Journey:**
1. Super Admin views the payment history: the payments (the payment, the user, the amount, the date, the status), the filters (the user, the amount, the date, the status), and the period (the period of the payments); the history is explicit.
2. Sets the history filter: the filter (the filter by the user, the amount, the date, the status); the filter is the scope.
3. Generates a statement: the generation (the statement is generated, the period, the payments); the generation is the document.
4. Views a statement: the statement (the statement, the period, the payments); the statement is the record.
5. Exports the history: the export (the history, the format, the period); the export is the record.
6. The payments are visible: the payments, the filters, the period, so the history is complete.
7. Reviews the payment history: the payments, the users, the period, so the payments are visible.
8. The payment history and statement management is audit-logged with the payment, the user, and the timestamp.

**Rules & Edge Cases:**
- The payment history is the record (the payment, the user, the amount, the date, the status); the history is the timeline.
- The payment statement is the document (the statement, the period, the payments); the statement is the summary.
- The statement generation is the creation (the statement is generated, the period, the payments); the generation is the action.
- The history filter is the scope (the filter by the user, the amount, the date, the status); the filter is the control.
- The payments are visible (the payments, the filters, the period); the management is managed.
- Payment history and statement management is audit-logged with the payment, user, and timestamp.

### 7.3 License Usage and Available Seats View
**What it does:** Views the license usage and available seats: the usage of the licenses (the usage, the institute, the count, the seats) and the available seats (the seats, the institute, the count) are viewable, so the licenses are visible (the usage is the record). The Super Administrator views the license usage and available seats (the institute, the count, the seats) so the viewing is structured and the usage is explicit.

**Sub-features:**
- License usage: the usage (the usage, the institute, the count, the seats)
- Available seats: the seats (the seats, the institute, the count)
- Usage view: the view (the usage per institute, the period)
- Seat view: the view (the seats per institute, the period)
- Usage filter: the filter (the filter by the institute, the count, the period)
- Usage export: the export (the usage, the format, the period)
- Audit logging of the license usage and seat viewing

**Super Administrator User Journey:**
1. Super Admin views the license usage: the usage (the usage, the institute, the count, the seats), the available seats (the seats, the institute, the count), and the period (the period of the usage); the usage is explicit.
2. Sets the usage filter: the filter (the filter by the institute, the count, the period); the filter is the scope.
3. Views an institute's usage: the view (the usage per institute, the period); the view is the detail.
4. Views the available seats: the seats (the seats, the institute, the count); the seats are the availability.
5. Exports the usage: the export (the usage, the format, the period); the export is the record.
6. The usage is visible: the usage, the institutes, the period, so the viewing is complete.
7. Reviews the license usage: the usage, the institutes, the seats, so the licenses are visible.
8. The license usage and seat viewing is audit-logged with the institute, the usage, and the timestamp.

**Rules & Edge Cases:**
- The license usage is the record (the usage, the institute, the count, the seats); the usage is the measure.
- The available seats are the availability (the seats, the institute, the count); the seats are the capacity.
- The usage view is the detail (the usage per institute, the period); the view is the access.
- The usage filter is the scope (the filter by the institute, the count, the period); the filter is the control.
- The usage is visible (the usage, the institutes, the period); the viewing is managed.
- License usage and seat viewing is audit-logged with the institute, usage, and timestamp.