Skip to content

Financial services

Customer onboarding with a record you can explain to auditors

Banks, insurers, credit providers and financial advisers need to know who they are dealing with. Yimi brings the purpose, consent, checks and decision into one record that supports your own onboarding procedures.

New request

Example Financial Services would like to verify your identity for account opening.

Business console

Account opening · SIM-2290

Awaiting applicant
  • Consent recorded
  • Document data extraction
  • Identity data match

Audit record

  1. 09:40Verification requested · account opening
Demonstration with a fictitious business and a synthetic person.

The challenge

Financial services firms must show not only that a customer was verified, but how and on what basis.

  • Onboarding evidence is spread across branch files, email attachments and core systems.
  • Customers expect to open accounts and take out policies remotely, without visiting a branch.
  • Reviewing a file months later means reconstructing who checked what, and why.

Who you onboard

The people financial services businesses need to verify

  • Account holders

    Individuals opening transactional, savings or investment accounts.

  • Policyholders and beneficiaries

    People taking out insurance cover or claiming against a policy.

  • Credit applicants

    Customers applying for personal loans, credit cards or store accounts.

Example workflow

How it works with Yimi

A typical onboarding journey for this industry, configured with Yimi.

  1. 1

    Open with a stated purpose

    Each verification records the product and the reason, such as account opening, so the check can be justified later.

  2. 2

    Customer consent

    The customer agrees on their phone to the specific check before any details are processed.

  3. 3

    Document data extraction

    Reading the identity document's fields to reduce manual capture by branch and contact-centre staff.

  4. 4

    Identity data matching

    Authorised, provider-backed matching of the customer's identity details.

  5. 5

    Decision and audit trail

    Compliance and operations teams see the outcome, the reason and a time-stamped trail of each step.

Business outcomes

What it means for your business

  • Onboarding files are complete by default, instead of being assembled after the fact.
  • Branch, contact-centre and remote onboarding follow the same verification steps.
  • Reviewers can see exactly which checks ran for any customer without searching several systems.

Capabilities

Capabilities for this workflow

Yimi is designed to support your own customer due diligence procedures. Responsibility for meeting FICA and other regulatory obligations remains with your institution.

  • Purpose-bound verification requests
  • Customer consent on mobile
  • Outcome and audit record
  • Scheduled retention and redaction
  • Document data extraction
  • Identity data matching

Explore Yimi for financial services

Request a demo to see Yimi configured for your onboarding journey, volumes and markets.