Banking & financial services

Customer Due Diligence & Review

Coordinate identity and ownership evidence, approved verification, risk-based review, relationship approval and periodic refresh.

12 workspace menus · 5 role profiles · Connected records

Designed for customer onboarding directors

Customer Due Diligence & Review workspace interface preview; illustrative records and figures.
Customer Due Diligence & Review — operational workspaceInterface preview · Illustrative dataView full interface →

Explore the system interface.

Operational workspace and record review. Select a screen to inspect it in full.

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Service / branchPeriodAssigned teamReview state

Dashboard measures

  • Active application records
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Coordinate identity and ownership evidence, approved verification, risk-based review, relationship approval and periodic refresh. Onboarding teams need to understand both the customer evidence and the decision that permitted a relationship to begin. The system maintains that connection through verification, exception review and periodic refresh, giving compliance and business owners a common, accountable review record.

Operational visibility

  • Due diligence reviews completed within service targets
  • Risk and obligation dashboard
  • Open issues / alerts
  • Periodic review due list
  • Decision and remediation audit

Operations

Operational overview

Review the work position and priority actions.

Customer intake

Coordinate customer intake with assigned responsibilities, linked records and review history.

Identity and ownership evidence

Coordinate identity and ownership evidence with assigned responsibilities, linked records and review history.

Verification task tracking

Coordinate verification task tracking with assigned responsibilities, linked records and review history.

Risk-review routing

Coordinate risk-review routing with assigned responsibilities, linked records and review history.

Relationship approval

Coordinate relationship approval with assigned responsibilities, linked records and review history.

Periodic refresh

Coordinate periodic refresh with assigned responsibilities, linked records and review history.

Review exception reporting

Coordinate review exception reporting with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Collect identity evidence

Collect customer identity and ownership evidence.

02

Perform approved checks

Perform approved verification checks.

03

Review the risk

Route risk-based human review.

04

Approve and refresh

Activate approved relationship and schedule refresh.

Governance and control

  • Authoritative obligations and thresholds must be version-controlled.
  • High-risk cases require designated reviewer approval.
  • Automated alerts may prioritise but must not silently make accountable regulatory decisions.
  • Evidence and decision rationale must be retained.
  • Periodic reviews must be scheduled from risk and policy rules.
  • Jurisdiction-, regulator- or authority-specific rules must be configurable and validated by an authorised domain owner before production use.

Accountable roles

Onboarding officer
Verification reviewer
Compliance approver
Relationship owner
Audit reviewer

Permissions are configured and tested for the agreed responsibilities.

Data, interfaces and operating requirements.

Core records

Obligation / ruleSubject / entityAssessmentAlert / issueReviewDecisionRemediationEvidence

Systems and interfaces

  • Identity verification services
  • Approved screening providers
  • Customer and relationship records

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Requires jurisdiction-specific requirements, identity verification services, screening integrations and accountable compliance approval of exceptions.

Mobile and tablet access

Support permitted evidence submission and review actions through controlled responsive views.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

AI extensions

Extract document fields and organise evidence for reviewer confirmation. Approval and exception decisions remain accountable human actions.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

An example operating scenario

See the process, its exception and the evidence.

A business customer submits incomplete ownership evidence. The reviewer requests clarification and an approved verification check creates an exception. An accountable compliance reviewer records the decision before relationship activation and schedules the next review.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report

Questions before implementation.

How is this system adapted to our organisation?

Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.

How are approvals and responsibilities defined?

Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.

Can it connect with our existing systems?

Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.

What will we review in a solution walkthrough?

Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.