Back to Details

str-report

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

STR Report

STR报告

When to Use

适用场景

  • Draft or restructure a suspicious transaction report (STR) or suspicious activity report (SAR) narrative for AML compliance filing or internal MLRO review
  • Build the who / what / when / where / why suspicion story with clear chronology and aggregated transaction facts
  • Map red flags and typologies (structuring, layering, trade-based ML, etc.) to observable facts—not conclusions without evidence
  • Compile subject and customer identification fields, related parties, accounts, and product/channel context for filing templates
  • Produce a supporting documentation checklist and exhibit index aligned to the narrative
  • Run quality review (completeness, consistency, tone, PII handling) before submission to MLRO or regulator-facing systems
  • Compare jurisdiction-agnostic structure with high-level US (FinCEN SAR), EU, and goAML field concepts (not legal filing advice)
  • Distinguish STR/SAR from internal case notes, management summaries, or law enforcement referral packages
  • Escalate and hand off to MLRO/compliance with a structured fact pack and open questions
  • 为AML合规申报或内部MLRO审核起草或重构**可疑交易报告（STR）或可疑活动报告（SAR）**的叙事内容
  • 结合清晰的时间线和汇总的交易事实，构建“何人/何事/何时/何地/为何可疑”的完整叙事
  • 将红旗指标和交易类型（拆分交易、多层转账、基于贸易的洗钱等）与可观测事实关联——不做无证据的结论
  • 为申报模板整理主体与客户识别字段、关联方、账户及产品/渠道背景信息
  • 生成与叙事内容匹配的支持文档清单及附件索引
  • 在提交给MLRO或监管系统前，进行质量审查（完整性、一致性、表述语气、个人身份信息（PII）处理）
  • 对比不受司法管辖区限制的通用结构与美国（FinCEN SAR）、欧盟及goAML的核心字段概念（不提供法律申报建议）
  • 区分STR/SAR与内部案件记录、管理层摘要或执法部门转介材料
  • 整理结构化事实包和待解决问题，上报并移交给MLRO/合规部门

When NOT to Use

不适用场景

  • Design transaction monitoring rules, thresholds, alert tuning, or TM scenario libraries → 
    aml-compliance
  • Build a full AML/CFT program, KYC/CDD policy, or enterprise risk assessment → 
    aml-compliance
    , 
    aml-cft
  • Determine legal obligation to file, statute of limitations, or regulator-specific filing deadlines as counsel → 
    commercial-counsel
  • Conduct internal or IT audit workpapers, SOC 2 testing, or control effectiveness sampling → 
    auditor
  • Implement technical controls, evidence automation, or screening system engineering → 
    compliance-engineer
  • Perform on-chain investigation, wallet tracing, or blockchain intelligence reports → 
    on-chain-investigator-agent
    , 
    solana-tracing-specialist
    , blockint skills
  • Draft law enforcement tactical packages, subpoena responses, or victim tracing narratives → route to investigation skills; keep STR factual and filing-oriented
  • CFT/TF-only typologies without broader STR narrative needs → 
    aml-cft
    (then return here for unified STR assembly)
  • 设计交易监控规则、阈值、警报优化或交易监控（TM）场景库 → 请使用
    aml-compliance
    Skill
  • 构建完整的AML/CFT程序、KYC/CDD政策或企业风险评估 → 请使用
    aml-compliance
    、
    aml-cft
    Skill
  • 作为法律顾问判定法定申报义务、诉讼时效或监管机构特定的申报截止日期 → 请使用
    commercial-counsel
    Skill
  • 开展内部或IT审计工作底稿、SOC 2测试或控制有效性抽样 → 请使用
    auditor
    Skill
  • 实施技术控制、证据自动化或筛查系统工程 → 请使用
    compliance-engineer
    Skill
  • 进行链上调查、钱包追踪或区块链情报报告 → 请使用
    on-chain-investigator-agent
    、
    solana-tracing-specialist
    及blockint类Skill
  • 起草执法部门战术材料、传票回复或受害者追踪叙事内容 → 请转用调查类Skill；STR需以事实为基础、聚焦申报需求
  • 仅涉及CFT/反恐融资交易类型，无完整STR叙事需求 → 请先使用
    aml-cft
    Skill，再返回此处进行STR整合

Related skills

相关Skill

NeedSkill
Full AML program, KYC/CDD, TM scenarios, alert triage
aml-compliance
Terrorist financing / proliferation financing STR angles
aml-cft
IT audit workpapers, control testing, sampling
auditor
SOC/ISO evidence pipelines, technical control automation
compliance-engineer
Legal interpretation, contracts, filing duty as counsel
commercial-counsel
FATF standardized terms (STR, CDD, etc.)
fatf-glossary-reference
Transaction screening UI and rescreen concepts
transaction-screening-workflow-concepts
Address screening and list policy concepts
address-screening-workflow-concepts
Behavioral monitoring heuristics (educational)
behavioral-risk-screening-concepts
Blockchain tracing and forensic reports
on-chain-investigator-agent
, 
solana-tracing-specialist
需求Skill
完整AML程序、KYC/CDD、交易监控场景、警报分流
aml-compliance
反恐融资/防扩散融资视角下的STR内容
aml-cft
IT审计工作底稿、控制测试、抽样
auditor
SOC/ISO证据流水线、技术控制自动化
compliance-engineer
法律解读、合同、作为法律顾问判定申报义务
commercial-counsel
FATF标准化术语（STR、CDD等）
fatf-glossary-reference
交易筛查UI及重新筛查概念
transaction-screening-workflow-concepts
地址筛查及清单政策概念
address-screening-workflow-concepts
行为监控启发法（教育类）
behavioral-risk-screening-concepts
区块链追踪及取证报告
on-chain-investigator-agent
, 
solana-tracing-specialist

Core Workflows

核心工作流程

1. Intake and scope

1. 需求接收与范围界定

  1. Confirm jurisdiction, entity, filing type (STR vs SAR vs internal referral), and case ID
  2. Collect alert source, investigation notes, and already-reviewed transactions (do not re-investigate beyond narrative needs)
  3. Identify subjects (customer, beneficial owners, counterparties, unknown parties) and reporting institution role
  4. Flag gaps requiring analyst follow-up before MLRO sign-off
See 
references/str_report_scope.md
.
  1. 确认司法管辖区、实体、申报类型（STR/SAR/内部转介）及案件ID
  2. 收集警报来源、调查记录及已审核的交易（无需超出叙事需求重复调查）
  3. 识别主体（客户、实际控制人、交易对手方、未知方）及申报机构角色
  4. 标记需分析师跟进、待MLRO签字确认的信息缺口
参考文件：
references/str_report_scope.md

2. Facts, aggregation, and chronology

2. 事实整理、汇总与时间线构建

  1. Normalize amounts, currencies, dates (UTC vs local—state assumption)
  2. Aggregate related transactions (account, counterparty, corridor, instrument)
  3. Build a chronological timeline with anchors (onboarding, profile change, alert, key txs)
  4. Separate verified facts from inference; label each suspicion element
See 
references/subject_and_transaction_detail.md
.
  1. 统一金额、货币、日期格式（UTC与本地时间需说明假设）
  2. 汇总关联交易（按账户、交易对手方、资金通道、工具分类）
  3. 构建带有关键节点（开户、资料变更、警报触发、核心交易）的时间线
  4. 区分已核实事实与推断内容；为每个可疑要素标注分类
参考文件：
references/subject_and_transaction_detail.md

3. Narrative and typologies

3. 叙事内容与交易类型匹配

  1. Open with summary suspicion in plain language (one short paragraph)
  2. Develop who / what / when / where / why sections with cross-references to exhibits
  3. Tie red flags to typologies and observable indicators—avoid legal conclusions
  4. Address innocent explanations considered and why rejected or unresolved
See 
references/narrative_structure_and_quality.md
and 
references/red_flags_and_typologies.md
.
  1. 以平实语言开篇，用简短段落概括可疑点摘要
  2. 展开“何人/何事/何时/何地/为何可疑”各章节，并添加附件交叉引用
  3. 将红旗指标与交易类型、可观测指标关联——避免法律结论
  4. 说明已考虑的合理解释，以及为何排除或暂未解决
参考文件：
references/narrative_structure_and_quality.md
及
references/red_flags_and_typologies.md

4. Format, review, and handoff

4. 格式调整、审查与移交

  1. Map narrative blocks to jurisdiction template fields at a high level (FinCEN SAR, goAML, etc.)
  2. Complete supporting documentation checklist and quality gates
  3. Run MLRO/compliance escalation pack: decision requested, risks, open items
  4. Record version, reviewers, and not legal advice disclaimer where appropriate
See 
references/jurisdiction_formats_and_filing.md
and 
references/review_escalation_and_handoff.md
.
  1. 从宏观层面将叙事模块映射到司法管辖区模板字段（如FinCEN SAR、goAML等）
  2. 完成支持文档清单及质量检查环节
  3. 准备MLRO/合规部门上报包：需决策事项、风险点、待解决问题
  4. 记录版本信息、审核人员，并在适当位置添加“非法律建议”声明
参考文件：
references/jurisdiction_formats_and_filing.md
及
references/review_escalation_and_handoff.md

Output Standards

输出标准

  • Use past tense for facts, present tense for ongoing risk where helpful; avoid sensational language
  • Every suspicion statement should cite specific transactions, dates, amounts, or documents
  • Minimize PII in drafts shared broadly; full detail in MLRO/regulator packages per policy
  • Include disclaimer: output supports compliance drafting—not legal advice on whether or when to file
  • Deliver: executive summary, full narrative, chronology table, subject/account appendix, exhibit checklist, open questions
  • 事实部分使用过去时态，持续风险部分可使用现在时态；避免使用煽动性语言
  • 每个可疑陈述需引用具体交易、日期、金额或文档
  • 在广泛共享的草稿中尽量减少个人身份信息（PII）；根据政策，在提交给MLRO/监管机构的材料中提供完整细节
  • 包含声明：本输出仅支持合规起草——不提供是否申报或何时申报的法律建议
  • 交付内容：执行摘要、完整叙事、时间线表格、主体/账户附录、附件清单、待解决问题

Reference Files

参考文件

FileUse when
references/str_report_scope.md
Boundaries, definitions, STR vs SAR vs internal notes
references/narrative_structure_and_quality.md
Who/what/when/where/why, tone, completeness
references/red_flags_and_typologies.md
Indicators, typology mapping, fact-to-suspicion links
references/subject_and_transaction_detail.md
IDs, accounts, aggregation, chronology tables
references/jurisdiction_formats_and_filing.md
FinCEN SAR, goAML, EU concepts (high level)
references/review_escalation_and_handoff.md
QA gates, MLRO pack, escalation
文件适用场景
references/str_report_scope.md
边界定义、STR/SAR与内部记录的区别
references/narrative_structure_and_quality.md
何人/何事/何时/何地/为何框架、表述语气、完整性
references/red_flags_and_typologies.md
指标、交易类型匹配、事实与可疑点关联
references/subject_and_transaction_detail.md
身份信息、账户、交易汇总、时间线表格
references/jurisdiction_formats_and_filing.md
FinCEN SAR、goAML、欧盟核心概念（宏观层面）
references/review_escalation_and_handoff.md
质量检查环节、MLRO上报包、流程上报