Skip to content

Service Provider Task Workflows

These workflows reflect the current admin-console route tree and the refreshed agent-hierarchy documentation.

A. Session and Core Oversight

SPF-01 Sign in and confirm the admin dashboard

Route: /login -> /app

  1. Open the admin portal.
  2. Complete the identity handoff and sign in with an admin or service-provider account.
  3. Confirm the dashboard renders and the main operations navigation is present.

Expected result: the session resolves into the admin dashboard without a forbidden redirect.

SPF-02 Investigate a transaction from the main queue

Route: /app/transactions -> /app/transactions/:receiptNumber

  1. Search or filter transactions.
  2. Open a specific receipt route.
  3. Review the timeline, amounts, counterparties, and any linked operational evidence.

Expected result: transaction monitoring and receipt-level investigation stay connected.

B. Customer, Organization, and Agent Operations

SPF-03 Review a customer profile

Route: /app/customers -> /app/customers/:customerId

  1. Open the customer directory.
  2. Search for the target customer.
  3. Open the detail route and review profile, controls, and operational history.

Expected result: customer lookup and customer detail are consistent and auditable.

SPF-04 Use the organizations route as the canonical entry for agent oversight

Route: /app/agents -> /app/organizations

  1. Open /app/agents.
  2. Confirm the app redirects to /app/organizations.
  3. Use the resulting organization workspace as the main entry for organization and agent oversight.

Expected result: operators understand that the old standalone agents entry is now an alias.

SPF-05 Open a direct agent detail route

Route: /app/agents/:agentId

  1. Start from a known live agent ID.
  2. Open the direct detail route.
  3. Review the agent's status, tills, shortcodes, and other operational identifiers.

Expected result: direct agent detail remains valid even though the list alias redirects elsewhere.

SPF-06 Review a super-agent hierarchy

Route: /app/agents/:agentId/children

  1. Open a super-agent ID such as an agent returned by the tier=SUPER admin query.
  2. Load the child-agent route.
  3. Review child count, total child float, till coverage, and the child rows themselves.

Expected result: the hierarchy page summarizes the super-agent network in one admin surface.

SPF-07 Validate super-agent share context

Route: /app/agents/:agentId and /app/agents/:agentId/children

  1. Open the agent detail or hierarchy route for a known super-agent relationship.
  2. Review superAgentShareRate and the current child-agent attachment.
  3. Use that context when interpreting downstream commission or payout investigations.

Expected result: super-agent share behavior is documented and not treated as hidden backend-only logic.

C. Finance and Ledger Review

SPF-08 Reconcile ledger and journal evidence

Route: /app/ledger, /app/journals

  1. Open the ledger account list or journal list.
  2. Drill into the specific GL, account, or journal transaction route you need.
  3. Compare ledger evidence with the operational transaction or settlement you are investigating.

Expected result: finance evidence routes stay usable for traceability.

SPF-09 Review settlement and disbursement routes

Route: /app/settlements, /app/disbursements, /app/commissions

  1. Open the settlement or disbursement surface.
  2. Review the batch or disbursement state.
  3. Use the detail route where a batch ID is already known.

Expected result: settlement and disbursement routes remain navigable even where multiple menu items currently map to the same underlying page surface.

SPF-10 Investigate reconciliation mismatches

Route: /app/reconciliation/runs, /app/reconciliation/mismatches

  1. Open a reconciliation run or mismatch list.
  2. Drill into a known run or mismatch detail route.
  3. Compare the mismatch with the underlying operational or ledger evidence.

Expected result: reconciliation review spans list and detail routes cleanly.

D. Governance, Lending, and Platform Controls

SPF-11 Work an approval from queue to decision

Route: /app/approvals -> /app/approvals/:taskId

  1. Open the approvals queue.
  2. Select the target task.
  3. Review the task detail and record the decision.

Expected result: approval workflow remains explicit and auditable.

SPF-12 Review lending governance routes

Route: /app/loans/rules, /app/loans/products, /app/loans/lenders, /app/loans/operations

  1. Open the lending governance area relevant to your task.
  2. Review rules, products, lenders, or specific loan-operation detail as needed.
  3. Use these routes together when tracing a customer-loan behavior back to platform configuration.

Expected result: lending operations and configuration routes can be used together for platform-level investigation.

SPF-13 Review platform configuration and partner surfaces

Route: /app/developer-integrations, /app/ussd-registry, /app/system-settings

  1. Open the relevant integration or system route.
  2. Review request details, registry data, or configuration state.
  3. Use approval or audit routes alongside these pages for governance evidence when required.

Expected result: admin configuration work stays inside the documented service-provider route tree.