Full reasoning chain
Every conclusion carries its reasoning and a citation to the source document, with agent actions and human overrides recorded in sequence.
Solution · Onboarding
Onboarding is an investigation. We run it like one.
Commercial and capital markets files, from first request through approval. One mandate can arrive as dozens of funds, feeders and vehicles across domiciles — each with its own ownership chain and its own document set.
ScopeEvidenceFinding
The work
What the file
actually takes.
Onboarding delay is rarely analysis. It is the loop of asking a client for documents, chasing them, and re-keying what arrives. RiskPulse runs that loop as part of the case.
01
Request
The file is classified by entity type, domicile and product scope, and the applicable regime is determined.
02
Documentation
The required document set is derived, requested from the client, and tracked to completion.
03
Verification
Documents are validated, key fields extracted with citations, and ownership resolved to the ultimate beneficial owner.
04
Risk assessment
Each dimension is scored against your policy, with override rules applied where they bind.
05
Approval
The file is assembled with conditions precedent stated, ready for the reviewer who signs it off.
Where the agents run
Plan. Examine. Report.
The same three agents run this case type as run every other. What differs is the policy behind them — the plan template, the dimensions scored, the tools available, and the report that comes out.
The precondition tollgate.
The plan opens with a gate. RiskPulse derives the full document set the entity requires, then holds the rest of the plan until those documents are in and successfully processed — so no analyst time is spent on a file that cannot complete, and no client is asked for step-two items before step-one documents exist.
- Client RFI workspace — the required list, live processing status, outstanding questions and drafted emails in one tab
- Secure client portal — a one-time-password link per client; upload, answer and see status without an account to provision
- Dynamic questions — generated from the gaps in the file rather than a static form
- Conditions precedent — what remains outstanding, grouped and gated by product line
Product screenshotCase record
Placeholder — case record
Policy for this case type
Configured,
not hardcoded.
Nothing on this page is fixed in the product. Every element below is a policy setting you define, which is why the same platform runs this case type and the four others.
- Domain
- Commercial banking or capital markets — each with its own client categories and document requirements.
- Risk dimensions
- Sanctions and PEP, beneficial ownership, regulatory standing, source of capital, operational conduct — weighted to your model.
- Plan template
- Entity type, domicile and product scope drive which tasks the Plan Agent may generate.
- Review gates
- Standard files can run to sign-off; enhanced and high-risk tiers can require review at every stage.
Controls
Defensible
after the fact.
The same governance and quality controls apply to this case type as to every other — because an examiner does not lower the standard for the harder files.
Quality control
Sampling built in
A sampling methodology sits behind this case type, so your quality team can assess a representative sample rather than reviewing at random.
Quality assurance
Independent assessment
A separate set of agents assesses case quality end to end against your methodology — a second opinion on the work.
See it on your own file
Bring a case.
We will run it.
Pick a real file or a closed case and see how RiskPulse plans it, evidences it, and writes it up under your policy.
Request a Demo