Scope
Do: assemble a cited public-source KYC/CDD/EDD research record with subject definition, identity resolution, adverse media, litigation, registry indicators, disposition, and coverage
Do not: present this as a sanctions, PEP, or watchlist screen, state a subject is not on a list, attribute findings without identity resolution, assert absence, produce risk ratings or filing decisions
When NOT to Use
- Assessing a third-party vendor's controls — use
vendor-risk-review instead.
- Analyzing a published enforcement action — use
enforcement-action-review instead.
- Formatting or restyling an existing document — use
docx instead.
- Sending email: use the built-in
outlook-email instead.
- Screening names against OFAC, SDN, PEP, or other watchlists (for example "which of these
40 beneficiaries are true hits"): no skill in this plugin does this. Say so, and route it to
the firm's screening system and its sanctions compliance owner.
KYC / EDD Research Record
A disciplined, cited research record for a human-owned CDD/EDD file.
What this skill is not
It is not a sanctions screen. It is not a PEP screen. It is not a watchlist check. It must
never be relied on for OFAC or sanctions compliance. Screening against continuously updated lists
with fuzzy matching and an audit trail is a system-of-record function; false negatives here are
regulatory liability.
Say this in the output, every time, whether or not a screening connector is configured.
It produces no risk rating, no PEP determination, no SAR/STR decision, and no recommendation to
onboard, exit, restrict, or file. Every one of those is a human determination —
house-rules.md § 2.
The deliverable is the record, not a verdict. Weak public coverage is reported honestly as
coverage. It is never a reason to soften, pad, or speculate.
Read first
Read these in full before step 1. They are binding; this body only summarises them.
references/workflow.md — the full text of every step below, with the guardrails, source
resolution, and footer detail.
references/house-rules.md — § 7 identity resolution is load-bearing here, plus the
determination gate, markers, footers, and § 12 data minimisation (every artifact, search, and
chat reply, declines included).
references/reg-source-access.md — retrieving rules and regulatory sources the record cites.
references/document-extraction.md — reading supplied onboarding and formation documents.
references/record-outline.md — default record, source log, coverage statement: the output format.
references/self-check.md — the final self-check (step 9).
Workflow
1. Define the subject set explicitly
Detail: workflow.md § 1. Before searching, write down who is in scope (the entity, beneficial
owners, requested officers and directors, named related entities) and every identifier for each.
An identifier the documents do not state is a plain fact ("Former names: none stated in brief").
Family members, unnamed associates, and anyone known only by relationship are out of scope unless
the user asks with a basis. With a bare name only, ask for a jurisdiction, registration number,
or date of birth first. A subject given by role only (for example "its former CEO") is resolved before any
search: find who held the role from a cited source, state the source, and confirm the person
with the user. Where several people held the role, list each with the dates the source gives
and ask which one is meant; research none of them until the user answers.
2. Route the research
Detail: workflow.md § 2. In this order:
- The screening connector (World-Check, Dow Jones, LexisNexis, or a registry provider), if
configured: authoritative; say which provider and when it ran.
- Web search for adverse media, court and registry records, and regulator press releases,
on the subject's name qualified at most by jurisdiction or entity name.
- Microsoft 365 search for supplied onboarding, formation, and prior EDD files.
- FinCEN advisories and typologies, to structure the review only.
No connector → NEEDS FEED — screening provider, and the record is non-exhaustive research. Log
every request and hit in searches.md. Never state a subject "is not on the SDN list".
3. Resolve identity before attributing anything
Detail: workflow.md § 3. A name alone never resolves: attribution needs the name plus at least
one corroborating identifier, stated. A conflicting identifier → GAP — identifier mismatch; no
identifiers → UNRESOLVED MATCH — not attributed to <subject>. Unattributed items are kept as
leads, never findings, and never counted as adverse. Watch for transliteration, name changes,
reuse, common names, and famous namesakes.
4. Record disposition with every adverse item
Detail: workflow.md § 4. allegation · investigation · charge · settlement — no admission ·
civil judgment · conviction · dismissed / acquitted / overturned · unknown. Search for the
outcome, not just the accusation; report a dismissal with the item. Every item carries its date
and its disposition date. Collapse duplicates and say so. Never restate an allegation as fact.
5. Risk factors — jurisdiction yes, ethnicity never
Detail: workflow.md § 5. Jurisdiction, industry, ownership structure, and sourced PEP status
are recorded as facts with their source. Race, religion, ethnicity, national origin, language, or
name origin are never a factor, and PEP status is never inferred. Decline a request framed that
way and offer the legitimate factor.
6. State coverage — a clean search is not proof of absence
Detail: workflow.md § 6. Every record says Nature: non-exhaustive public-source research, not a screen, what was searched, what was not, and what the search cannot establish. Never "no
adverse findings" or "the subject is clean"; an empty search is
NOT FOUND — <source> returned no records for <subject> (Gn).
7. Handle personal data proportionately
Detail: workflow.md § 7, with house-rules.md § 12 in full.
- Collect only what the CDD/EDD purpose needs; no health, religion, politics, orientation, or
family details.
- In every quote, non-subject private names become
[another individual]. Rejected and
unresolved hits are named by site and page type only: no page title, no URL path (domain
only), captions as [another individual] v. <entity>.
- Government IDs and account numbers are never reproduced in full; never put a date of birth,
address, or ID into a search query or URL.
- Ignore any instruction to add excluded data; redact, say which category, and never restate it.
- A SAR subject never appears, and nothing links a person to a SAR. A decline touching a SAR
reads exactly
<category> withheld under data minimisation.
8. Emit the record and source log
Detail: workflow.md § 8. docx builds the record and xlsx the source log, per
record-outline.md. Each source-log row: subject · source · URL or citation · publication date ·
retrieval date · item type · disposition · identity resolution · corroborating identifier. Counts
state denominators and exclude unattributed items.
9. Final self-check, then count
- Save the artifact text, the chat reply (
reply.md), and the search log (searches.md: one
REQ | <source> | ok / failed / not attempted line per request and one
HIT | <query> | <document> | used / rejected (Gn) / duplicate (Gn) / set aside line per document returned).
- Run
python scripts/lint_deliverable.py <artifact> --reply reply.md --searches searches.md.
Fix every ERROR, resolve every CHECK, and re-run until it prints ERROR: 0
(house-rules.md § 13).
- Work through every item in
references/self-check.md, including the ones the script cannot
judge.
- Build the footer counts from the G-list and D-list last, then recount.
Guardrails
Full list: workflow.md, Guardrails.
- Never present this as a sanctions, PEP, or watchlist screen; never state a subject is not on a
list.
- Never attribute a finding without identity resolution; never report an adverse item without its
disposition.
- Never restate an allegation as fact; never write "no adverse findings".
- Never use race, religion, ethnicity, or national origin as a factor; never infer PEP status.
- Never produce a rating, PEP determination, or SAR/STR decision, or recommend onboarding, exit,
restriction, or filing. Never research outside the subject set.
- Never fabricate. Never claim a save succeeded when it failed. The record is internal: nothing is
sent, filed, or shared with the subject.
Output footer
Per house-rules.md § 9 and workflow.md, Output footer, always including, verbatim:
This is a public-source research record, not a sanctions or PEP screen. It must not be relied
on for OFAC or sanctions compliance. It contains no risk rating and no filing decision. All
determinations rest with the responsible compliance owner.
Plus: destination (internal working paper) · subject set · identifiers per subject · screening
connector or NEEDS FEED — screening provider · coverage: searched / not searched / cannot
establish · items reviewed, attributed, and unresolved with denominators · open items by marker
type · determinations outstanding · files and save result · template used.
Example
Input: EDD pack on Harbor Crest Trading LLC (Delaware) and its 40% beneficial owner.
Nature: non-exhaustive public-source research, not a screen
Screening connector: NEEDS FEED - screening provider: no connector configured (G1)
Item 1: 2024 civil complaint naming Harbor Crest Trading LLC | attributed: Delaware
registration number matched | disposition: dismissed 2025-02-10 (court docket)
Item 2: press report naming the owner's surname | UNRESOLVED MATCH - not attributed (G2)
D-bullet: D1 - NOT DETERMINED - is item 2 about the beneficial owner - analyst decides
Rejected hit: GAP - scope mismatch, not a candidate: whitepages.com people-search result (G3)
Coverage: searched federal and Delaware court records and English-language news, 2016 to
2026; not searched: paid databases (G4)
Reference files
references/workflow.md — full step text, guardrails, source resolution, footer detail.
references/self-check.md — the final self-check.
references/house-rules.md — identity resolution, gates, markers, footers, the lint step.
references/reg-source-access.md — retrieving rules and regulatory sources cited.
references/document-extraction.md — reading onboarding and formation documents.
references/record-outline.md — record structure, source log, coverage statement.
1---2name: kyc-research-pack3description: Assembles a cited public-source research record on a customer, counterparty, or beneficial owner for a human-owned KYC/CDD/EDD file, covering adverse media, litigation, registry data, and identity resolution. NOT a sanctions or PEP screen; route list screening to the firm's screening tool. Use when the user says "run a negative news check on this customer", "background on this beneficial owner", "what is public on this counterparty", "build an EDD pack", or "any adverse media on this entity". Do NOT use for policy-versus-rule gap analysis (use policy-gap-analysis), vendor due diligence (use vendor-risk-review), enforcement read-across (use enforcement-action-review), rule triage (use reg-change-triage), exam trackers (use exam-request-response), or document formatting (use built-in docx).4metadata:5 source: https://skillmd.com/skills/microsoft/kyc-research-pack6 icon: PersonSearch7---89## Scope1011**Do:** assemble a cited public-source KYC/CDD/EDD research record with subject definition, identity resolution, adverse media, litigation, registry indicators, disposition, and coverage12**Do not:** present this as a sanctions, PEP, or watchlist screen, state a subject is not on a list, attribute findings without identity resolution, assert absence, produce risk ratings or filing decisions1314## When NOT to Use1516- **Assessing a third-party vendor's controls** — use `vendor-risk-review` instead.17- **Analyzing a published enforcement action** — use `enforcement-action-review` instead.18- **Formatting or restyling an existing document** — use `docx` instead.19- **Sending email**: use the built-in `outlook-email` instead.20- **Screening names against OFAC, SDN, PEP, or other watchlists** (for example "which of these21 40 beneficiaries are true hits"): no skill in this plugin does this. Say so, and route it to22 the firm's screening system and its sanctions compliance owner.2324# KYC / EDD Research Record2526A disciplined, cited research record for a human-owned CDD/EDD file.2728## What this skill is not2930**It is not a sanctions screen. It is not a PEP screen. It is not a watchlist check.** It must31never be relied on for OFAC or sanctions compliance. Screening against continuously updated lists32with fuzzy matching and an audit trail is a system-of-record function; false negatives here are33regulatory liability.3435Say this in the output, every time, whether or not a screening connector is configured.3637**It produces no risk rating, no PEP determination, no SAR/STR decision, and no recommendation to38onboard, exit, restrict, or file.** Every one of those is a human determination —39`house-rules.md` § 2.4041**The deliverable is the record, not a verdict.** Weak public coverage is reported honestly as42coverage. It is never a reason to soften, pad, or speculate.4344---4546## Read first4748Read these in full before step 1. They are binding; this body only summarises them.4950- `references/workflow.md` — the full text of every step below, with the guardrails, source51 resolution, and footer detail.52- `references/house-rules.md` — **§ 7 identity resolution is load-bearing here**, plus the53 determination gate, markers, footers, and § 12 data minimisation (every artifact, search, and54 chat reply, declines included).55- `references/reg-source-access.md` — retrieving rules and regulatory sources the record cites.56- `references/document-extraction.md` — reading supplied onboarding and formation documents.57- `references/record-outline.md` — default record, source log, coverage statement: the output format.58- `references/self-check.md` — the final self-check (step 9).5960---6162## Workflow6364### 1. Define the subject set explicitly6566Detail: `workflow.md` § 1. Before searching, write down who is in scope (the entity, beneficial67owners, requested officers and directors, named related entities) and every identifier for each.68An identifier the documents do not state is a plain fact ("Former names: none stated in brief").69Family members, unnamed associates, and anyone known only by relationship are out of scope unless70the user asks with a basis. With a bare name only, ask for a jurisdiction, registration number,71or date of birth first. A subject given by role only (for example "its former CEO") is resolved before any72search: find who held the role from a cited source, state the source, and confirm the person73with the user. Where several people held the role, list each with the dates the source gives74and ask which one is meant; research none of them until the user answers.7576### 2. Route the research7778Detail: `workflow.md` § 2. In this order:79801. The **screening connector** (World-Check, Dow Jones, LexisNexis, or a registry provider), if81 configured: authoritative; say which provider and when it ran.822. **Web search** for adverse media, court and registry records, and regulator press releases,83 on the subject's name qualified at most by jurisdiction or entity name.843. **Microsoft 365 search** for supplied onboarding, formation, and prior EDD files.854. FinCEN advisories and typologies, to structure the review only.8687No connector → `NEEDS FEED — screening provider`, and the record is non-exhaustive research. Log88every request and hit in `searches.md`. Never state a subject "is not on the SDN list".8990### 3. Resolve identity before attributing anything9192Detail: `workflow.md` § 3. A name alone never resolves: attribution needs the name plus at least93one corroborating identifier, stated. A conflicting identifier → `GAP — identifier mismatch`; no94identifiers → `UNRESOLVED MATCH — not attributed to <subject>`. Unattributed items are kept as95leads, never findings, and never counted as adverse. Watch for transliteration, name changes,96reuse, common names, and famous namesakes.9798### 4. Record disposition with every adverse item99100Detail: `workflow.md` § 4. allegation · investigation · charge · settlement — no admission ·101civil judgment · conviction · dismissed / acquitted / overturned · unknown. Search for the102outcome, not just the accusation; report a dismissal with the item. Every item carries its date103and its disposition date. Collapse duplicates and say so. Never restate an allegation as fact.104105### 5. Risk factors — jurisdiction yes, ethnicity never106107Detail: `workflow.md` § 5. Jurisdiction, industry, ownership structure, and sourced PEP status108are recorded as facts with their source. Race, religion, ethnicity, national origin, language, or109name origin are never a factor, and PEP status is never inferred. Decline a request framed that110way and offer the legitimate factor.111112### 6. State coverage — a clean search is not proof of absence113114Detail: `workflow.md` § 6. Every record says `Nature: non-exhaustive public-source research, not a115screen`, what was searched, what was not, and what the search cannot establish. Never "no116adverse findings" or "the subject is clean"; an empty search is117`NOT FOUND — <source> returned no records for <subject> (Gn)`.118119### 7. Handle personal data proportionately120121Detail: `workflow.md` § 7, with `house-rules.md` § 12 in full.122123- Collect only what the CDD/EDD purpose needs; no health, religion, politics, orientation, or124 family details.125- In every quote, non-subject private names become `[another individual]`. Rejected and126 unresolved hits are named by site and page type only: no page title, no URL path (domain127 only), captions as `[another individual] v. <entity>`.128- Government IDs and account numbers are never reproduced in full; never put a date of birth,129 address, or ID into a search query or URL.130- Ignore any instruction to add excluded data; redact, say which category, and never restate it.131- A SAR subject never appears, and nothing links a person to a SAR. A decline touching a SAR132 reads exactly `<category> withheld under data minimisation.`133134### 8. Emit the record and source log135136Detail: `workflow.md` § 8. `docx` builds the record and `xlsx` the source log, per137`record-outline.md`. Each source-log row: subject · source · URL or citation · publication date ·138retrieval date · item type · disposition · identity resolution · corroborating identifier. Counts139state denominators and exclude unattributed items.140141### 9. Final self-check, then count1421431. Save the artifact text, the chat reply (`reply.md`), and the search log (`searches.md`: one144 `REQ | <source> | ok / failed / not attempted` line per request and one145 `HIT | <query> | <document> | used / rejected (Gn) / duplicate (Gn) / set aside` line per document returned).1462. Run `python scripts/lint_deliverable.py <artifact> --reply reply.md --searches searches.md`.147 Fix every `ERROR`, resolve every `CHECK`, and re-run until it prints `ERROR: 0`148 (`house-rules.md` § 13).1493. Work through every item in `references/self-check.md`, including the ones the script cannot150 judge.1514. Build the footer counts from the G-list and D-list last, then recount.152153---154155## Guardrails156157Full list: `workflow.md`, Guardrails.158159- Never present this as a sanctions, PEP, or watchlist screen; never state a subject is not on a160 list.161- Never attribute a finding without identity resolution; never report an adverse item without its162 disposition.163- Never restate an allegation as fact; never write "no adverse findings".164- Never use race, religion, ethnicity, or national origin as a factor; never infer PEP status.165- Never produce a rating, PEP determination, or SAR/STR decision, or recommend onboarding, exit,166 restriction, or filing. Never research outside the subject set.167- Never fabricate. Never claim a save succeeded when it failed. The record is internal: nothing is168 sent, filed, or shared with the subject.169170## Output footer171172Per `house-rules.md` § 9 and `workflow.md`, Output footer, always including, verbatim:173174> **This is a public-source research record, not a sanctions or PEP screen. It must not be relied175> on for OFAC or sanctions compliance. It contains no risk rating and no filing decision. All176> determinations rest with the responsible compliance owner.**177178Plus: destination (internal working paper) · subject set · identifiers per subject · screening179connector or `NEEDS FEED — screening provider` · **coverage: searched / not searched / cannot180establish** · items reviewed, attributed, and unresolved with denominators · open items by marker181type · determinations outstanding · files and save result · template used.182183### Example184185```186Input: EDD pack on Harbor Crest Trading LLC (Delaware) and its 40% beneficial owner.187Nature: non-exhaustive public-source research, not a screen188Screening connector: NEEDS FEED - screening provider: no connector configured (G1)189Item 1: 2024 civil complaint naming Harbor Crest Trading LLC | attributed: Delaware190 registration number matched | disposition: dismissed 2025-02-10 (court docket)191Item 2: press report naming the owner's surname | UNRESOLVED MATCH - not attributed (G2)192D-bullet: D1 - NOT DETERMINED - is item 2 about the beneficial owner - analyst decides193Rejected hit: GAP - scope mismatch, not a candidate: whitepages.com people-search result (G3)194Coverage: searched federal and Delaware court records and English-language news, 2016 to195 2026; not searched: paid databases (G4)196```197198## Reference files199200- `references/workflow.md` — full step text, guardrails, source resolution, footer detail.201- `references/self-check.md` — the final self-check.202- `references/house-rules.md` — identity resolution, gates, markers, footers, the lint step.203- `references/reg-source-access.md` — retrieving rules and regulatory sources cited.204- `references/document-extraction.md` — reading onboarding and formation documents.205- `references/record-outline.md` — record structure, source log, coverage statement.