Onboarding & KYC remediation

Speed up onboarding work without letting an agent approve what a human should.

Typical agents
Onboarding, document-collection and remediation agents
Systems touched
Customer records, KYC case management, account opening
Who approves
Onboarding, compliance and financial-crime teams

The risk

What can go wrong

Agents that gather documents, update records and propose approvals take load off operations teams — but account approvals, limit changes and remediation decisions are exactly where examiners expect human judgment and a record.

Approvals without judgment

An agent that can draft an approval can often submit it. Account openings and limit raises then happen without the human review examiners expect.

Customer data leaving the boundary

A broad read or an export to the wrong place moves sensitive identity data where it should not go.

Remediation that cannot be evidenced

Cases are closed in bulk, but the file does not show who decided each one or why.

Typical decisions

How GREENLIGHT typically decides

Each action an agent proposes gets one of four outcomes, with a reason a reviewer and an auditor can read.

Agent action	Typical outcome	Why
Request missing documents	Allow	Requesting documents changes nothing consequential.
Update customer record from verified data	Allow	The update comes from data that has already been verified.
Approve a new account or raise a limit	Require human approval	Opening an account or raising a limit needs a person to decide.
Close a remediation case	Require human approval	Closing a remediation case is a judgment call for a reviewer.
Bulk export of customer data	Escalate	Bulk movement of customer data is unusual and goes to a person.

Illustrative. Outcomes follow your policies and thresholds.

One action, end to end

A limit raise during onboarding, end to end

What happens between the moment an agent decides to act and the moment your system changes. Figures are illustrative.

Agent

An onboarding agent has gathered documents and proposes raising a new customer’s daily limit.

GREENLIGHT

Raising a limit is consequential, so the decision is require human approval, with the customer context attached.

Reviewer

A compliance reviewer, not the person who owns the case, checks the file and approves it.

GREENLIGHT

The approved change is released once, and only that change.

Logbook

The file now shows who approved the limit, when, and under which rule.

How GREENLIGHT governs it

Four parts of the platform, working together

Each part of GREENLIGHT plays a role in this use case. Follow a link to see how that part works.

The difference

Without GREENLIGHT, and with it

	Without a decision point	With GREENLIGHT
Opening an account or raising a limit	Possible for any agent with write access	Always decided by a reviewer, with separation of duties
Bulk reads and exports	Invisible until someone audits access logs	Observed, flagged and escalated as they happen
Remediation evidence	Case notes and spreadsheets	A decision record for every file

Rollout

Start in shadow, enforce when you are ready

For this use case, as for every other, GREENLIGHT starts by watching. Nothing is blocked until you decide it should be.

Shadow

GREENLIGHT evaluates every action and records what it would have decided. Nothing is blocked, so you can measure before you change anything.

Advisory

Decisions are returned to the agent and to your teams as recommendations, and policies are tuned against real traffic.

Enforce

Holds and blocks are switched on workflow by workflow, starting where the risk is highest and the evidence is clearest.

More use cases

Get started

Start with this workflow.

Bring one Onboarding & KYC remediation workflow into GREENLIGHT in shadow mode. We will show you what it would decide on your real traffic, then agree with you when to enforce.

Apply for Pilot Access Request a Demo All solutions