Customer Onboarding and KYC

Why do two similar customers take completely different paths to the same account?

Application receivedThe customer commits
Account liveThe relationship is usable

Why this process resists visibility

Onboarding is the first thing a customer experiences and the last thing an enterprise can see clearly.

  • Turnaround time records the verdict

    It tells you the account took a fortnight. It cannot tell you which of the fourteen days were spent working and which were spent waiting on a document that went unchased.

  • The journey crosses front, middle and back office

    CRM, workflow, screening, document management and the core system each hold a fragment, each with its own clock and its own idea of when the case began.

  • Rework is treated as normal practice

    Asking a customer twice for the same document is routine enough that it often goes uncounted, and it can be one of the largest contributors to elapsed time.

  • Diligence depth is applied by judgement

    Two customers of the same risk profile take different routes depending on who assessed them, and the variation is rarely visible or governed.

  • Abandoned applications rarely have an owner

    Customers who drop out are recorded as inactive rather than investigated, so the point at which the relationship was lost is seldom identified.

Where time and effort accumulate

The process is normally drawn as six clean stages. Execution data shows what actually collects at each one, and how much of the cycle is spent waiting rather than working.

  1. Stage 1

    Application and capture

    • Submissions arriving incomplete
    • Re-entry between channel and core system
    • Duplicate applications for one customer
    • Missing entity and ownership data
  2. Stage 2

    Document collection

    • The same document requested more than once
    • Documents expiring before the case completes
    • Poor-quality uploads rejected late
    • Customers chased across several channels
  3. Stage 3

    Screening and due diligence

    • Screening re-run after every data change
    • Alerts sitting unassigned in a queue
    • False positives cleared manually
    • Enhanced diligence triggered late in the case
  4. Stage 4

    Risk and credit assessment

    • Assessments reworked as new information arrives
    • Referrals routed by relationship, not by rule
    • Limits and conditions revised repeatedly
    • Approvals waiting on a committee cycle
  5. Stage 5

    Approval and account setup

    • Approvals split across several systems
    • Account structures rebuilt after error
    • Product and pricing configured by hand
    • Mandates and signatories captured late
  6. Stage 6

    Activation and first use

    • Credentials and access delayed after approval
    • Funding blocked at the first transaction
    • Servicing handoffs missed at go-live
    • Accounts live on paper but not yet usable

What runs underneath all six

These four behaviours recur across the stages and often account for a large share of the cycle: work waiting in a queue without a clear owner, work looping back to a stage it already passed, work changing hands between teams with little record of the handoff, and the same application type running through materially different routes depending on who touched it.

How RE-ViVE observes it

No process remodeling. No new workflow instrumentation. Read-only source access.

You provide the relevant source records and limited subject-matter support. RE-ViVE does the reconstruction and the analysis.

  1. Step 1

    Read-only extracts

    Application, document, screening and account records from the systems that already hold them. Nothing is written back.

  2. Step 2

    Execution reconstructed

    RE-ViVE maps source records into its Execution Data Model, allowing each application to be reconstructed across the systems involved.

  3. Step 3

    Followed end to end

    Each application can then be followed from application received to account live, with dwell time, loops and handoffs measured rather than estimated.

  4. Step 4

    Kept current

    The view refreshes as new applications are recorded, so the effect of any change is visible in the same measure.

What you are left holding

Evidence specific enough to act on, and traceable back to the individual application behind it.

  • The routes applications actually take

    Every path present in the data, from receipt to activation, ranked by volume and by the effort it consumes, against the journey the process was designed around.

  • Where the days sit

    Elapsed time broken down by stage and split between work in progress and work waiting on the customer, a third party or an internal queue.

  • Rework made countable

    Repeat document requests, re-screening, re-keyed data and reworked assessments, counted and costed rather than assumed.

  • Cause attributed

    Delay and rework attributed by segment, product, channel, jurisdiction, risk rating and team.

  • Conduct and service exposure

    Where cases breach internal standards or customer commitments, and what created the breach rather than which team reported it.

  • A monitored process

    Continuous visibility once the first view is built, giving a baseline that simplification and automation can be measured against.

Where the evidence lives

Customer Onboarding and KYC leaves a record in systems you already run.

  • CRM
  • Onboarding workflow
  • Document management
  • Screening and sanctions
  • Credit and risk assessment
  • Core banking or policy administration
  • Electronic signature
  • Servicing and access provisioning

RE-ViVE works with the systems an enterprise already runs, including platforms such as Salesforce, Pega, Appian and Temenos, along with other CRM, workflow and core platforms, screening tools, document repositories, portals and custom applications. Where execution moves outside the available system evidence, RE-ViVE makes the unexplained interval visible for investigation.

Processes next door

Onboarding shares its evidence with the processes that follow the customer.

See how your onboarding actually executes

Give us read-only access to the application data you already hold, and we will show you the routes, the waiting and the rework inside it.

See all processes