PCMLTFA / FINTRAC — Anti-Money-Laundering & Terrorist-Financing

PCMLTFA / FINTRAC — Anti-Money-Laundering & Terrorist-Financing — 88% of in-scope requirements covered.

4 requirements · 4 in scope (3 enforced · 1 designed). The 88% is weighted over the in-scope base.

PCMLTFA / FINTRAC: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. kyc · enforced

    Client identification + KYC: ascertain and verify the identity of clients before conducting prescribed…

    Audit events: kye.purpose.admissibility.v1, kye.evidence.decision_map.v1 · Constitution: 12 purpose permission

  2. monitoring · enforced

    Ongoing monitoring: conduct ongoing monitoring of business relationships to detect transactions requiring…

    Audit events: kye.risk_assessment.v1, kye.purpose.admissibility.v1 · Constitution: 13 resilience loop

  3. s6-records · enforced

    Section 6 + Regulations — Record-keeping: keep prescribed records of transactions, client identification and…

    Audit events: kye.evidence.tool_call.v1, kye.replay.proof.v1 · Constitution: 30 audit worm retention

  4. s7-str · designed

    Section 7 — Suspicious transaction reporting: report to FINTRAC every financial transaction for which there…

    Audit events: kye.signal.incident.opened.v1, kye.compliance.attestation.v1 · Constitution: 13 resilience loop

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: Proceeds of Crime (Money Laundering) and Terrorist Financing Act, S.C. 2000, c. 17, and the PCMLTFA Regulations, administered by the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC). Client identification + know-your-client (PCMLTFR Part 1), ongoing monitoring + business relationships, suspicious-transaction reporting (s.7), and record-keeping (s.6 + Regulations).

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Client identification + KYC11000100%
Ongoing monitoring11000100%
Suspicious transaction reporting (s.7)1010050%
Record-keeping (s.6)11000100%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
pcmltfa.kycClient identification + KYC: ascertain and verify the identity of clients before conducting prescribed activities and determine beneficial ownershipenforcedaudit_events: kye.purpose.admissibility.v1, kye.evidence.decision_map.v1
engines: internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
pcmltfa.monitoringOngoing monitoring: conduct ongoing monitoring of business relationships to detect transactions requiring reporting and to keep client information currentenforcedaudit_events: kye.risk_assessment.v1, kye.purpose.admissibility.v1
engines: internal, internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md
pcmltfa.s7-strSection 7 — Suspicious transaction reporting: report to FINTRAC every financial transaction for which there are reasonable grounds to suspect it is related to money laundering or terrorist financingdesignedaudit_events: kye.signal.incident.opened.v1, kye.compliance.attestation.v1
engines: internal, internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md
pcmltfa.s6-recordsSection 6 + Regulations — Record-keeping: keep prescribed records of transactions, client identification and reports for the prescribed retention periodenforcedaudit_events: kye.evidence.tool_call.v1, kye.replay.proof.v1
engines: internal
constitution_refs: constitution/30-AUDIT-WORM-RETENTION.md

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.