Skip to content
Finance
Skill

/client-onboarding

Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity

From plugin
finance-skills
16491 skills
Install
$ npx -y skills add JoelLewis/finance_skills --skill client-onboarding --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/client-onboarding

Context preview

The summary Claude sees to decide when to auto-load this skill.

Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity

SKILL.md

client-onboarding.SKILL.md
name: client-onboarding
description: "Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity verification or CIP checks, reducing NIGO rejection rates, opening complex account types like trusts or entities, connecting to custodian APIs, designing suitability questionnaires, or comparing advisor-assisted vs self-service models. Also trigger when users mention 'new account opening', 'onboarding bottleneck', 'KYC integration', 'beneficial ownership', 'OFAC screening', 'account funding', or 'onboarding automation'."

Client Onboarding

Core Concepts

Onboarding Workflow Architecture

Client onboarding is an orchestrated, multi-stage process that transforms a prospect into a funded, investable account. The canonical stages are:

1. **Prospect intake** — capture contact information, establish CRM record, assign advisor 2. **Identity verification** — CIP/KYC checks (name, DOB, address, SSN/TIN, government ID) 3. **Suitability data collection** — investment objectives, risk tolerance, time horizon, financial situation 4. **Account type selection** — individual, joint, trust, IRA, entity, or other structure 5. **Document generation** — assemble the required document package based on account type and features 6. **E-signature** — execute new account forms, agreements, and disclosures electronically 7. **Custodian submission** — transmit the completed application to the custodian for account creation 8. **Funding** — ACH, wire, ACAT transfer, or check deposit to fund the new account 9. **Initial investment** — assign the funded account to a model portfolio or execute the initial trade

The two primary flow models are **advisor-assisted** and **self-service (digital-direct)**. In advisor-assisted onboarding, the advisor guides the client through each step, often in a meeting or screen-share, with the onboarding platform pre-populating data from the CRM. In self-service onboarding, the client completes a guided digital workflow independently, with the advisor reviewing and approving the completed application. Most firms support a hybrid model where self-service handles simple account types and advisor-assisted handles complex ones.

The onboarding platform acts as an orchestrator across multiple downstream systems: CRM (client master), KYC/AML vendor (identity verification), custodian (account opening API), document management (storage and retrieval), and portfolio management system (model assignment). The platform must manage state transitions, handle errors at each stage, and provide visibility to both the advisor and compliance.

Digital Identity Verification

Identity verification during onboarding must satisfy CIP requirements under USA PATRIOT Act Section 326 and, for legal entities, the FinCEN CDD Rule (31 CFR 1010.230). The onboarding workflow collects the following minimum identifying information:

  • **Individuals:** Full legal name, date of birth, residential address, Social Security Number (or TIN for non-citizens)
  • **Entities:** Legal name, formation date, principal place of business, EIN/TIN, formation documents

**Verification methods integrated into digital onboarding:**

  • **Database verification** — real-time API calls to identity verification vendors (LexisNexis Risk Solutions, Equifax, TransUnion, Alloy) that cross-reference provided data against credit bureau, public records, and government databases. This is the most common method for digital onboarding because it requires no document handling and provides a pass/fail result in seconds.
  • **Document verification** — the client uploads a photo of a government-issued ID (driver's license, passport), and optionally a selfie for facial comparison. OCR extracts data fields; liveness detection prevents spoofing. Used as a fallback when database verification is inconclusive or as a primary method for non-US persons.
  • **Knowledge-based authentication (KBA)** — the client answers challenge questions generated from their credit file (e.g., "Which of the following addresses have you lived at?"). KBA is declining in use due to data breach exposure but remains a supplementary method.
  • **Biometric verification** — fingerprint or facial recognition, typically used in mobile onboarding flows.

**OFAC and sanctions screening** is a mandatory gate before account opening. The onboarding platform must screen all individuals associated with the account (account holders, authorized signers, beneficial owners, trustees) against the OFAC SDN list, FinCEN 314(a) lists, and any firm-specific restricted lists. A match or potential match must halt the onboarding flow and route to compliance for manual review.

**Beneficial ownership collection for entity accounts** requires identification of every individual who directly or indirectly owns 25% or more of the equity interests in the legal entity, plus at least one individual with significant managerial control (the control person). The onboarding workflow must dynamically present beneficial ownership forms when the account type is an entity (LLC, corporation, partnership, certain trusts).

**Enhanced due diligence triggers** that the onboarding system should detect and flag: politically exposed persons (PEPs), connections to high-risk jurisdictions (per FinCEN advisories and FATF guidance), complex multi-layered ownership structures, and negative news screening results. When EDD is triggered, the onboarding flow should pause and escalate to the compliance team before proceeding.

Suitability and Risk Profiling

Onboarding is the primary data collection event for investment suitability. Before any investment recommendation can be made, the firm must gather sufficient information to satisfy FINRA Rule 2111 (suitability) for broker-dealers and Regulation Best Interest

Read more
Ships withfinance-skills

A collection of Claude Code skill plugins for financial services. 91 skills across 7 domain plugins teach Claude investment management, regulatory compliance, advisory workflows, trading operations, and more — so it can assist with finance questions, build

Get the whole plugin
Stats
170
Stars
34
Forks
Maintained
Maintenance
Python
Language
MIT
License
1mo ago
Last commit
6mo ago
Created

Repo: JoelLewis/finance_skills

Other skills on finance-skills.