Use caseRetail banking

Customer onboarding and KYC

A customer applies for two accounts in the app at 10 p.m. His bill is too old and his $85,000 deposit has no proof. Each gap costs a day.

The checklist runs the moment the file arrivesBoth missing documents are asked for in one messageThe advisor approves, compliance clears the funds

Actions on this onboarding file
The verdict on the file

A document is missing or out of date · the AI says which

The assistantOnboarding checklist

Driver's license valid, name matches the application. The electric bill is dated Jul 18, 2026, older than three months. No proof of origin for the $85,000 deposit.

source · 4 documents on the file
01

Where it stalls today

The short version

Andre Wallace applies for a checking and a savings account at 10:18 p.m. His electric bill is from July, and nothing explains where his $85,000 deposit comes from. In most branches the advisor spots the bill first, asks for a new one, then finds the second gap a day later. Somewhere between the two requests, applicants like Andre stop answering.

This time the checklist runs at the door. The AI applies the rules your compliance team wrote as soon as the file arrives, names every gap at once and drafts the request. The advisor starts from a verdict and its reasons, and keeps the approval.

Electric bill.pdfViewer
Two gaps on one file. The bill dated in July, and the checklist of what Andre sent, with the deposit proof still missing.
Onboarding OB-26-11872Case management
Four days, one request. Both gaps asked for the first morning, funds cleared by compliance, accounts open on day four.

Any onboarding desk has a bill, a checklist and a queue. What saves Andre's application is the timing: the file arrives already checked, both gaps are chased the same morning, and the approval is given on a complete file. The acts below follow his file until both accounts are open.

02

The application

The applicant finishes in the app at night. By morning the file has its checklist and its gaps.

Step 1Intake

The application arrives through the API, with its documents

Andre Wallace, 34, applies on Nov 4 at 10:18 p.m. He uploads his driver's license, an electric bill, his 2025 tax return and a signed W-9, and states an $85,000 deposit expected in December.

The app calls the repository API: an onboarding case is created and each document is filed in its slot, with its type.

IdentityProof of addressIncomeTax certification
Onboarding OB-26-11872 · DocumentsCase management
The expected deposit is a field of the case. It decides which checks apply.
The file is whole from minute oneNo scans emailed to the branch. The application and its papers land together, typed, on one case.
Step 2AI check

The AI runs the onboarding checklist

Before anyone opens it, an AI agent runs the file against the checklist your compliance team wrote in plain language. It extracts names, dates and addresses and compares them across the documents.

Is the ID valid, and does the name match?Is the proof of address under three months old?Above $50,000, is the origin of funds documented?

The status written on the case is Attention required: the bill is dated Jul 18, and nothing documents the deposit.

Electric bill.pdfViewer
The warning points to the line and page it comes from.
Both gaps are found at the doorNobody discovers the second missing document after the first one arrives. The checklist names them together.
Step 3Workflow

The deposit adds a compliance stage

The routing rule reads the expected deposit. Above $50,000, the process adds a source of funds review, assigned to the compliance queue. The case goes to Sarah Lindqvist, advisor at the branch nearest the applicant's address.

ProcessCase management
Each stage is a workflow task with its owner and its SLA timer.
The right people are on the file before it is readThe advisor does not have to know the threshold. The process does, and routes on it.
03

The gaps

A stale bill and an undocumented deposit stand between Andre and his accounts. One message has to cover both.

Step 4Reporting

The queue arrives sorted by verdict

Sarah starts her day with five new applications. Her home page counts them by verdict, and the complete ones can be approved in a few minutes. Andre's file needs two documents, so she opens it first.

Complete: 2Attention required: 2Not eligible: 1
New customersCase management
The verdict is a column you can sort and filter on.
The time goes where a gap existsComplete files move fast. The advisor spends her morning on the two that need her.
Step 5Assistant

One message asks for both documents

Sarah asks the assistant for a request to Andre. The draft lists the two documents, says why each is needed and gives examples of accepted proofs. She adds that the closing statement is enough if the money comes from selling his condo, which he mentioned in the app.

The message goes to his inbox in the app. An SLA timer on the request escalates to Sarah if nothing arrives in three days.

Onboarding OB-26-11872Case management
The request is filed in the case history, with its date.
Look at last month's abandoned applications. How many went quiet after a second request for a document the bank could have named the first time?
The applicant hears about both the same morningOne message, with the reason for each piece. No second request two days later.
Step 6AI check

The documents arrive and the check runs again

Andre uploads an internet bill dated Oct 29 and the closing statement for his condo in St. Paul. Both are filed on the same case and the checklist runs again.

The AI extracts the net proceeds from the statement: $96,400 after the mortgage payoff, which covers the stated deposit. The status moves to Complete, pending the compliance stage.

Closing statement.pdfViewer
The earlier warnings stay in the history, with the document that cleared each one.
The file comes back readySarah does not reread everything. She sees the two rules that changed and the documents that changed them.
04

The approval

The file is complete. Compliance clears the funds first, then the advisor approves.

Step 7Viewer

Compliance reviews the source of funds

Tom Becker picks up the review stage. He opens the closing statement in the viewer, next to the case, and asks the assistant where the net proceeds and the payment date are stated. The answer points to the page. He adds a note on the passage and approves the stage.

Closing statement.pdfViewer
The note stays on the document, visible to whoever opens it next.
The review is done on the evidence itselfTom does not ask the branch for a copy. The closing statement is on the case, and his note travels with it.
Step 8Assistant

A summary to approve on the whole file

Sarah asks for a summary of the file. It says who the applicant is, what he stated, what was checked and what compliance cleared, each line with its source. She confirms the standard risk level the policy gives this profile and approves the opening.

Onboarding OB-26-11872AI console
The summary helps the reading. The risk level and the approval stay with the advisor.
The approval is given on all of itEvery line of the summary can be checked against its document before Sarah decides.
Step 9History

The accounts open and the file is kept

On approval, the workflow calls the core banking system through its API to open both accounts. The onboarding case closes, and the KYC file stays on the customer with its review date and the retention rule your BSA/AML policy sets.

Onboarding OB-26-11872 · HistoryCase management
The trail is part of the file, readable at the next periodic review.
The next review starts from a full fileWho checked what, when, and on which document: the periodic review opens on that record.
05

What comes out

The applicant is never scored. The file is read against your checklist, and lands in one of three states that set Sarah's next move.

Complete

Every rule passes

Identity, address, tax status, funds. Each check is recorded on the case with its source.

What follows: the advisor reads the summary and approves.
Attention required

A piece is missing or out of date

A bill older than three months, a deposit with no proof. The check names every gap at once.

What follows: the advisor sends one request; the check runs again when the pieces arrive.
Not eligible

A rule fails, and you know which

An expired ID, a country of residence the bank does not serve. The AI lists what passes first, then the rule that fails.

What follows: the advisor decides, and tells the applicant why.
What stays with people

It opens no account. It refuses nobody. It clears no deposit. Across the nine steps on this page, the approval belongs to the advisor and the funds review to compliance, each with their own rights and their own trace.

The AI reads, checks, drafts and summarizes. The control is in how the process is written, with its thresholds and its review stages.

06

Time back

Counted on Andre Wallace's application, two accounts and one large deposit. Your thresholds and your checklist will shift these counts.

0 fieldsretyped from the documents. Names, dates and addresses are extracted onto the case.
1 messageto ask for both missing documents, sent the morning after the application.
Day 4when the file is approved, with the compliance stage already cleared.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Three principles behind the figures

Zero wasted readingProductivityThe checklist runs before the advisor opens the file. She starts from a verdict and its reasons.
Zero second requestsApplicant experienceEvery gap is named at once, so one message is enough.
Decision supportA person decidesSummaries and answers cite their sources. Approval and clearance stay with people.
07

Built for

An advisor opens the accounts, a compliance analyst clears the funds, IT wires the app to the core. Three different reasons to look closer.

Business operations

Branch advisors

Papers get checked all day, and the customers you meet get what time is left.

  • The file arrives checked, with every gap already named.
  • One request covers all the missing documents.
  • The returned documents are checked again on arrival.
  • The summary lists every fact with its source.
Risk and compliance

Compliance analysts

Funds land on your desk for clearance with no view of how the file was built.

  • The threshold rule routes the file to you, every time.
  • The evidence opens in the viewer, next to the case.
  • Your note stays on the document for the next reader.
  • The checklist is yours, written in plain language.
IT and architecture

CIOs and architects

The app, the branch tools and the core banking system each hold a piece of the customer.

  • The application comes in through the API, from your existing app.
  • The checklist runs as one stage of the onboarding workflow.
  • The core banking system is called by API on approval.
  • Runs on your own servers or in a cloud your bank approves.

A good first step

With one rule. Take the proof of address check your advisors do by hand on every file, and move it to the door. A few hundred applications are enough to see what it changes.

Your app, your branch tools and your core banking system keep running. The onboarding case links them.

Let's talk

See it on your own files

Bring a few anonymized onboarding files and your checklist. We will check one with you at the door and leave the approval to your advisor.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.