Finance & compliance

Approvals, audit & security

The control layer behind consequential actions: independent approval, evidence and accountability.

Category
Finance & compliance
Status
Available
Platform
CoreVista CBS
Approval Path flow Step 1: Maker request; Step 2: Approver decision; Step 3: Audit evidence MODULE FLOW 1 Maker request A consequential action is proposed 2 Approver decision A different user approves or rejects 3 Audit evidence The decision and effect are recorded
Illustrative flow: approval path. Each step is controlled and audited.

What it covers

  • Consolidated queueOne approvals queue covers reversals, loan write-offs, restructures, originations, cash transfers, maturity instructions, period close and AML case decisions.
  • Maker-checkerA maker requests and a different user approves or rejects; self-approval is refused.
  • Approval recordsPersisted requests carry the threshold, status and decision audit, with encrypted approval configuration.
  • Audit trailWho, what, when, where and before-and-after values are written in the same transaction.
  • IdentityKeycloak OIDC/OAuth2 with TOTP MFA and role-based access.
  • RolesAdministrator, teller, compliance, auditor and approver roles.

How it works

  1. Raise a request

    The maker submits a consequential action with its business context.

  2. Review

    A distinct approver reviews the request in the consolidated queue.

  3. Decide

    Approval executes or dispatches the action; rejection records the decision.

  4. Keep evidence

    The decision and business effect are audited and emitted to the outbox.

Controls built in

  • A distinct approver is enforced for every maker-checker action.
  • Self-approval is refused.
  • Audit records are tamper-evident and written transactionally.
  • OIDC, TOTP MFA and role-based access protect the console.

Talk through this module.

Book a walkthrough and we will map this module to your products, approval rules and reporting needs.