Rule-to-Action Map
A bridge between Regulation Map obligations and practical AML Bible controls.
Regulation Map explains why and when a requirement applies. AML Bible explains how the control should be performed and evidenced. Company policy supplies provider-specific configuration.
1. Obligation → control map
| Regulatory obligation | Control ID | AML Bible action | Evidence output |
|---|---|---|---|
| Customer identification | CDD-IDV | Identify and verify the customer before or during onboarding. | Identity data, source used, verification result and exception notes. |
| Beneficial ownership | BO-IDENTIFY / BO-VERIFY | Identify owners and controllers, then verify them using reliable evidence. | Ownership chart, UBO identifiers, registry evidence and unresolved gaps. |
| PEP screening | SCREEN-PEP | Screen relevant individuals and apply enhanced review when required. | Search record, match analysis, senior approval where applicable. |
| Targeted financial sanctions | SCREEN-SANCTIONS | Screen customers, related parties, counterparties and relevant transaction parties. | Query, parameters, result, match IDs, escalation and decision. |
| Ongoing monitoring | ONGOING-MONITORING | Monitor transactions, relationship behaviour and profile consistency. | Alert review, rationale, supporting data and disposition. |
| Periodic review | PERIODIC-REVIEW | Refresh CDD and screening based on risk or policy frequency. | Updated profile, refreshed searches, risk rating and next review date. |
| Event-driven CDD refresh | EVENT-REVIEW | Reassess the relationship when ownership, geography, activity or adverse information changes. | Trigger note, new evidence, risk reassessment and decision. |
| Recordkeeping | EVIDENCE-RETAIN | Preserve documents, search outputs, decisions and approvals for the required retention period. | Evidence pack, storage reference, retention basis and audit trail. |
| Suspicious activity/reporting | CASE-ESCALATE / STR-ASSESS / STR-FILE | Escalate concerns, assess suspicion and file when the legal threshold is met. | Case narrative, MLRO decision, filing evidence and post-filing controls. |
2. How to use the map
- Find the obligation in Regulation Map.
- Identify subject scope, sector scope, trigger, frequency, deadline and evidence source.
- Select the matching control ID.
- Open the relevant Bible workflow and evidence template.
- Apply company-specific provider, threshold and escalation settings from policy/SOP.
3. Boundary
The map does not replace legal interpretation. It normalises the operational bridge so that a legal requirement becomes a consistent analyst action and a reviewable evidence record.