My App

Head Workflows

Practical workflows for Head users.

Workflow 1 - Set or Update Global Risk Threshold

Prerequisites

  • Head role access
  • Branches are active in system

Steps

  1. Open Risk Settings.
  2. Enter the new threshold value (default reference is 110%).
  3. Save changes.
  4. Verify alert behavior on the Risk Monitoring screen.

Decision Points

  • If branch-level threshold exceptions are allowed, confirm policy before forcing global standard.

Notes and Warnings

  • Changing the threshold changes which loans appear as at-risk; confirm the numeric convention with head office (e.g. default 110%) before rolling changes to all branches.
  • Changes impact branch monitoring behaviour as soon as valuations and alerts are recalculated.

Workflow 2 - Review Cross-Branch Settlement Risk

Prerequisites

  • Cross-branch payments exist for the period

Steps

  1. Open Cross-Branch Settlement Report.
  2. Filter by date range and branch pair if needed.
  3. Review payment branch vs owning branch totals.
  4. Identify delayed or unmatched settlement entries.
  5. Escalate mismatches to relevant branch managers.

Decision Points

  • If payment appears to close transaction from non-owning branch, raise compliance issue and validate rejection controls.

Notes and Warnings

  • Non-owning branches can collect payments, but closure must be done by owning branch.

Workflow 3 - Monitor Enterprise Risk Exposure

Prerequisites

  • Daily gold rate updates are available
  • Active transactions exist

Steps

  1. Open Risk Exposure Report.
  2. Sort by lowest coverage ratio first.
  3. Open high-risk transactions and check branch actions.
  4. Verify if threshold, payment, or status action is required.
  5. Track unresolved alerts via notification panel.

Decision Points

  • If coverage ratio is below threshold and no branch action is recorded, issue immediate follow-up.

Notes and Warnings

  • Coverage compares collateral value to debt the system computes for risk (Outstanding is not “principal only”—accrued interest is included in that debt picture where the engine applies it), so low coverage is a real early warning.

Workflow 4 - Governance Review for Discounts

Prerequisites

  • Discounts were applied in selected period

Steps

  1. Open Discount Usage report.
  2. Filter by branch and staff user.
  3. Check reason quality and discount patterns.
  4. Use Export to Excel when you need a spreadsheet for audit or management review.
  5. Investigate unusual frequency or amount clusters.
  6. Record findings for audit readiness.

Decision Points

  • If discounts are missing reasons, flag as policy violation and request correction process.

Workflow 5 - Master Data (Currencies and Categories)

Prerequisites

  • Head (Super Admin) access

Steps

  1. Open Currencies to add or manage active currency codes used by branches and customers.
  2. Open Categories to maintain gold item types used when creating transactions.
  3. After changes, confirm staff can still create transactions without validation errors.

Notes

  • Deleting a currency may be blocked when it is still referenced—resolve references first.

On this page