Phase 1 of 6
Scoping & CIP/CDD Scope
Define onboarding channels, customer risk tiers, EDD triggers, and the jurisdictional perimeter that will govern every downstream agent decision.
0/8
Phase Progress
Required Recommended Optional Open-Source Proprietary Trinidy
Onboarding Channels & Customer Segments
Identify onboarding channels in scope for agentic CDD
Why This Matters
Channel is the largest single driver of both the CIP/CDD feature set and the regulatory control inventory — a corporate onboarding with a 5-tier UBO chain touches fundamentally different data sources and regulations than a retail digital applicant. Most agentic KYC programs underestimate how different the document, data, and verification primitives are across channels, and end up rebuilding the agent for each channel. Inventory every channel up front, including ones product is planning to add in the next 12 months, or the agent tooling will not transfer.
Note prompts — click to add
+ Which channels share enough document and verification overlap to run on a shared agent tool library?+ Which channels require human-in-the-loop review by policy vs. only on exception?+ Have we inventoried channels that are legally out of scope for autonomous decisioning under our risk appetite?
Required
Confirm every channel through which a customer can be onboarded and must be due-diligenced.
Select all that apply
Retail digital (mobile app / web self-serve)
Retail in-branch (assisted — document capture on-site)
Private / wealth (relationship-manager assisted)
Commercial / SMB (legal entity onboarding)
Corporate (complex ownership / multi-jurisdiction)
Correspondent banking (respondent institution DD)
Broker-dealer / introduced business
Payment institution / EMI applicants
Crypto / digital-asset customers
Third-party / partner API onboarding
required
✓ saved
Define customer risk tiers and CDD depth per tier
Why This Matters
FATF Recommendation 10 and the FinCEN CDD Rule both expect a risk-based approach — not a uniform treatment — and examiners increasingly test that CDD depth actually varies with risk tier rather than being a paper distinction. The agentic layer must encode the tier-to-tooling mapping explicitly: which data sources, which verification depth, which escalation gates. A uniform-depth agent is a regulatory finding waiting to happen once an EDD case slips through as standard CDD.
Note prompts — click to add
+ Is our tiering algorithm documented and model-risk-managed, or is it a static rules table?+ What proportion of our book falls into each tier today and does that match our risk appetite statement?+ When the agent disagrees with a tier assignment, what is the escalation path?
Required
Specify the risk-tiered CDD model the agent will execute — simplified, standard, or enhanced due diligence.
Select all that apply
SDD — simplified (low-risk retail, documented risk assessment)
CDD — standard (default tier, FinCEN CDD Rule baseline)
EDD — enhanced (high-risk geography / PEP / complex ownership)
Correspondent EDD (31 CFR 1010.610 — foreign respondent banks)
Private banking EDD (31 CFR 1010.620 — non-US persons, $1M+)
Uniform tier — no tiering applied today
required
✓ saved
Enumerate EDD triggers
Why This Matters
EDD triggers are where most agentic KYC programs either over- or under-fire. Under-firing means PEPs and high-risk geographies slip through as standard CDD — an examination finding and a material AML risk. Over-firing means the EDD queue balloons with false positives and the human review team becomes the actual bottleneck, defeating the agent. FATF R.12 on PEPs and R.19 on higher-risk countries expect these triggers to be explicit and documented; the agent's trigger logic must match the written CDD policy exactly.
Note prompts — click to add
+ Does our PEP list source cover domestic PEPs as well as foreign (required under FATF R.12 updates)?+ Are EDD triggers encoded in agent tooling, or hard-coded outside the agent where they cannot be audited?+ What percentage of our onboarding volume currently triggers EDD, and is that rate stable?
Required
Select every trigger that moves a case into enhanced due diligence.
Select all that apply
PEP hit (domestic / foreign / international organization)
PEP family member or close associate (RCA)
High-risk jurisdiction (FATF black/grey list)
Sanctions-adjacent geography or sectoral exposure
Correspondent banking relationship
Complex or opaque ownership structure
Bearer shares / nominee shareholders in chain
Shell-company indicators (no operations, mass-registered address)
Adverse media hit (financial crime / corruption / terrorism)
Cash-intensive business MCC
High transaction volume relative to stated profile
required
✓ saved
Define beneficial ownership (UBO) scope and threshold
Why This Matters
The FinCEN CDD Rule (31 CFR 1020.230) sets the baseline at 25% ownership plus a separate control prong — and the AML Act 2020 / Corporate Transparency Act layered on BOI reporting to FinCEN that reshapes the institutional BO picture (though CTA enforcement has been subject to litigation and a Treasury policy pivot in 2025 reducing domestic reporting scope for US companies). EU AMLD 5 and AMLD 6 align at 25% but give member states discretion to lower it in higher-risk sectors. The agent must encode the right threshold per jurisdiction and per customer type, and must unwind ownership through at least the intermediate legal entities — stopping at the first legal-entity layer is the most common UBO failure mode.
Note prompts — click to add
+ Does our agent unwind ownership through all intermediate entities or stop at the first legal-entity layer?+ Have we mapped the threshold variance across every jurisdiction we onboard in?+ How do we evidence control-prong analysis — not just ownership percentage — in the agent's output?
Required
Specify the UBO identification threshold and the ownership depth the agent must unwind.
Single choice
25% ownership threshold + control prong (FinCEN CDD Rule baseline)
10% threshold (enhanced — private banking / high-risk)
Corporate Transparency Act FinCEN BOI aligned (25% or substantial control)
EU AMLD 5/6 — 25% with member-state discretion to lower
Mixed — tier-dependent threshold
required
✓ saved
Confirm jurisdictional perimeter and data residency constraints
Required
Map customer identity and CDD data to residency rules before architecture is finalized.
Select all that apply
EU / UK GDPR — identity data must remain in EU/UK
GDPR Art. 9 — biometrics require on-prem / documented lawful basis
MAS Notice 626 (Singapore — AML/CFT)
HKMA AML/CFT Guideline (Hong Kong)
India RBI data localization + PMLA
UAE CBUAE + SCA AML rules
Brazil LGPD + BACEN Resolution 4.943
Switzerland FINMA + revised AMLO
Cross-border permitted under SCCs + approved vendors
requiredtrinidy
TrinidyGDPR Article 9 classifies biometrics as special-category data with a near-default prohibition on processing, and most regulators interpret cross-border LLM API calls as processing. Trinidy keeps document intelligence, face match, and agentic orchestration entirely on-premises — no customer identity data leaves the institutional perimeter for any step in the workflow.
✓ saved
Define agent autonomy envelope
Why This Matters
The EU AI Act treats AML/KYC decisioning as high-risk AI with Article 12 logging obligations taking full force in August 2026, and penalties of €15M or 3% of global revenue. Beyond compliance, the autonomy envelope is the single biggest lever on both ROI and regulatory defensibility: too narrow and the agent delivers no throughput gain; too wide and the institution is defending autonomous approvals of cases that turn out to be PEPs or sanctions adjacencies. The envelope should be defined in writing and encoded as explicit guardrails in the agent — not implicit in prompt wording.
Note prompts — click to add
+ Is our autonomy envelope documented as policy and encoded as hard guardrails in the agent?+ Where in the flow does the agent MUST hand off to a human under our own policy, even before regulation requires it?+ Have legal and BSA signed off on the autonomy envelope, or is it implicit in engineering decisions?
Required
Specify the scope of decisions the agent may take autonomously vs. must escalate.
Select all that apply
Approve low-risk standard-CDD cases autonomously
Clear confirmed-negative sanctions screening hits autonomously
Dispose false-positive PEP hits with documented reasoning
Compile EDD packages for human review (no autonomous approval)
Trigger periodic review events autonomously (perpetual KYC)
Decline / exit relationships — human approval required by policy
Any SAR-adjacent conclusion — escalate to BSA officer
requiredtrinidy
TrinidyEU AI Act Article 12 requires automatic event logging across the lifecycle of high-risk AI systems — agentic KYC decisions must carry a reconstructable audit trail. Trinidy logs every tool call, retrieved document, screening hit, and agent reasoning step by default, with 6-month minimum retention.
✓ saved
Specify ongoing vs. initial due diligence scope
Why This Matters
The FinCEN CDD Rule made ongoing monitoring an explicit fifth pillar of the AML program, and FATF R.10 requires ongoing DD including scrutiny of transactions to ensure consistency with the customer profile. Perpetual KYC — where sanctions, adverse media, and BO changes trigger reviews in real time — is rapidly becoming the expected operating model, and is where agentic architectures have the largest efficiency advantage over manual periodic refresh. Scoping this in at the start determines whether the agent needs event-driven triggers and persistent case state, or only one-shot onboarding orchestration.
Note prompts — click to add
+ Is our current model periodic refresh or perpetual KYC, and does our agent architecture match?+ What percentage of material customer risk changes do we currently catch at refresh vs. in real time?+ Have we sized the event volume that perpetual KYC would generate and the review capacity needed?
Required
Confirm whether the agent handles initial onboarding only, periodic review, or perpetual KYC.
Single choice
Initial onboarding only
Initial + scheduled periodic review (annual high-risk, 24mo medium, 36mo low)
Initial + event-driven trigger reviews
Perpetual KYC — continuous monitoring on sanctions / adverse media / BO changes
Not yet decided
required
✓ saved
Define latency and throughput targets
Why This Matters
Goldman Sachs reduced onboarding time by 30% through agentic CDD, and institutions targeting same-day retail onboarding are seeing meaningful revenue uplift from reduced applicant abandonment. But the SLA must be set against the depth-of-DD policy — a 30-minute target is incompatible with a real UBO unwind on a corporate applicant, and the right answer is tiered targets per customer type. A single uniform SLA will force the agent to short-cut either speed or depth, and neither is defensible.
Note prompts — click to add
+ What is our current measured time-to-decision by customer type, and where is the time actually spent?+ Have we quantified the abandonment cost of a one-day versus one-week onboarding for our highest-value segment?+ Is our SLA tiered to DD depth, or is it forcing the agent to compromise on one side?
Required
Specify end-to-end case SLA and step-level latency targets the agent must hit.
Single choice
Same-day onboarding (retail — under 30 min end-to-end)
3 business days (SMB / commercial)
5-10 business days (corporate with UBO unwind)
Tiered — varies by customer type and EDD status
Not yet defined at the case level
required
✓ saved