, home
Customer access Request an enterprise demo
Request an enterprise demo Customer access

Banking & financial services / APPLICATION BLUEPRINT

Customer Due Diligence & Review

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

Start generatingExplore illustrative interface

12 workspace menus · 12 business workflows · 5 role profiles

Application blueprint only. This is a proposed design, not a deployed or production-tested system. Screens and sample figures are illustrative; workflows, business rules, approvals, permissions and integrations require confirmation before build.

Designed for Customer onboarding director

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

Explore an illustrative interface.

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

Customer Due Diligence & Review workspace interface preview; illustrative records and figures.
Customer Due Diligence & Review — operational workspaceIllustrative interface · Sample dataView full interface →
Customer Due Diligence & Review record interface preview; illustrative records and figures.
Customer Due Diligence & Review — record and workflow reviewIllustrative interface · Sample dataView full interface →

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.

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.

Business workflows

Select a workflow to review the steps, responsibilities, approval and exception handling.

01 · Coordinate customer intake

Coordinate customer intake within Customer due diligence onboarding and periodic review.

Trigger
Customer intake requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register customer intake and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

02 · Coordinate identity and ownership evidence

Coordinate identity and ownership evidence within Customer due diligence onboarding and periodic review.

Trigger
Identity and ownership evidence requires a new record, an agreed review or a controlled change.

Responsible role
Compliance approver

  • Register identity and ownership evidence and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

03 · Coordinate verification task tracking

Coordinate verification task tracking within Customer due diligence onboarding and periodic review.

Trigger
Verification task tracking requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register verification task tracking and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

04 · Coordinate risk-review routing

Coordinate risk-review routing within Customer due diligence onboarding and periodic review.

Trigger
Risk-review routing requires a new record, an agreed review or a controlled change.

Responsible role
Compliance approver

  • Register risk-review routing and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

05 · Coordinate relationship approval

Coordinate relationship approval within Customer due diligence onboarding and periodic review.

Trigger
Relationship approval requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register relationship approval and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

06 · Coordinate periodic refresh

Coordinate periodic refresh within Customer due diligence onboarding and periodic review.

Trigger
Periodic refresh requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register periodic refresh and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

07 · Coordinate review exception reporting

Coordinate review exception reporting within Customer due diligence onboarding and periodic review.

Trigger
Review exception reporting requires a new record, an agreed review or a controlled change.

Responsible role
Compliance approver

  • Register review exception reporting and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

08 · Register the operating requirement

Coordinate operating requirement within Customer due diligence onboarding and periodic review.

Trigger
Operating requirement requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register operating requirement and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

09 · Resolve operating exceptions

Coordinate operating exceptions within Customer due diligence onboarding and periodic review.

Trigger
Operating exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register operating exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

10 · Verify completion and follow-up

Coordinate completion and follow-up within Customer due diligence onboarding and periodic review.

Trigger
Completion and follow-up requires a new record, an agreed review or a controlled change.

Responsible role
Compliance approver

  • Register completion and follow-up and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

11 · Review controlled operating changes

Coordinate controlled operating changes within Customer due diligence onboarding and periodic review.

Trigger
Controlled operating changes requires a new record, an agreed review or a controlled change.

Responsible role
Compliance approver

  • Register controlled operating changes and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

12 · Prepare scoped operational reports

Coordinate scoped operational reports within Customer due diligence onboarding and periodic review.

Trigger
Scoped operational reports requires a new record, an agreed review or a controlled change.

Responsible role
Onboarding officer

  • Register scoped operational reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Relationship owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

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.
Operating rules by business workflow
  • For customer intake, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For identity and ownership evidence, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For verification task tracking, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For risk-review routing, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For relationship approval, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For periodic refresh, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For review exception reporting, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For operating requirement, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For operating exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For completion and follow-up, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For controlled operating changes, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For scoped operational reports, the record retains an accountable owner, its supporting evidence and accepted outcome.

Data, interfaces and operating requirements.

Core records

Obligation / ruleSubject / entityAssessmentAlert / issueReviewDecisionRemediationEvidence
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Service / branch — Business scope used for responsibility and reporting.
  • Operating subject — The request, commitment or work item being handled.
  • Accountable owner — Named responsibility for the next action.
  • Workflow stage — Current position in the agreed business journey.
  • Review requirement — Required review and outstanding decision.
  • Due or review date — Agreed action window or review trigger.
  • Linked evidence — Source records supporting the operating decision.
  • Decision authority — The delegated authority relevant to the accepted outcome.
  • Accepted outcome — Recorded decision and its business consequences.
  • Follow-up obligation — Remaining responsibilities after an accepted action.
  • Revision history — Trace of accepted changes and their evidence.
  • Customer intake reference — Link the relevant customer intake to the operating transaction and its decision evidence.
  • Identity and ownership evidence reference — Link the relevant identity and ownership evidence to the operating transaction and its decision evidence.
  • Verification task tracking reference — Link the relevant verification task tracking to the operating transaction and its decision evidence.
  • Risk-review routing reference — Link the relevant risk-review routing to the operating transaction and its decision evidence.
  • Relationship approval reference — Link the relevant relationship approval to the operating transaction and its decision evidence.

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.

Apple App Store ↗Google Play ↗

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

What to validate in a scoped demonstration.

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
Discuss this solution

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.