{ "datasetId": "amlb:compliance-obligations", "datasetName": "Compliance Obligations", "schemaVersion": "1.0.0", "snapshotDate": "2026-10-10", "generatedAt": "2026-10-13T06:35:41.319Z", "recordCount": 581, "description": "Structured AML/CFT/CPF requirements, deadlines, triggers and controls.", "license": { "id": "CC-BY-NC-4.0", "name": "Creative Commons Attribution-NonCommercial 4.0 International", "commercialUse": "separate-license-required" }, "documentationUrl": "https://amlballerina.com/data/", "records": [ { "id": "SG-STR", "jurisdictionCode": "SG", "jurisdictionName": "Singapore", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A person acting in the course of trade, profession, business or employment who knows or has reasonable grounds to suspect that property may be connected to criminal activity. Sector rules add institution-specific requirements.", "trigger": "Knowledge or reasonable grounds to suspect that property may be connected to criminal activity; terrorist-financing information can also be disclosed to STRO through an STR.", "deadline": "As soon as reasonably practicable under CDSA section 45. For banks, MAS Notice 626 paragraph 14.2 requires prompt submission of suspicious-transaction reports, including attempted transactions.", "recipient": "Suspicious Transaction Reporting Office (STRO)", "submission": "Electronic filing through STRO Online Notices And Reporting (SONAR).", "applicability": "Current obligation.", "consequence": "Failure to file an STR may constitute a criminal offence. No current monetary maximum is shown without provision-specific confirmation from Singapore Statutes Online.", "enforcement": "Singapore Police Force / STRO; sector supervisors may take separate regulatory action under the applicable sector regime.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation and investigation workflows should be capable of reaching and filing an STR decision without creating delay inconsistent with the statutory/sector reporting standard.", "evidenceIds": [ "amlb:evidence:8c930867", "amlb:evidence:04bae41b", "amlb:evidence:127928a9" ], "sourceEntityIds": [ "amlb:source-entity:d98e1870", "amlb:source-entity:0c4a05b3", "amlb:source-entity:c5cdd089" ] }, { "id": "SG-BANK-CONTROLS", "jurisdictionCode": "SG", "jurisdictionName": "Singapore", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Bank AML/CFT records, controls, compliance, audit and training", "timingType": "ongoing", "sectors": [ "banking" ], "appliesTo": "Banks within the scope of MAS Notice 626.", "trigger": "Continuous while carrying on regulated banking business.", "deadline": "Ongoing. MAS Notice 626 contains continuing recordkeeping and internal policies/compliance/audit/training requirements rather than one universal filing date.", "recipient": "Monetary Authority of Singapore (supervisory oversight). Suspicious reports themselves are filed with STRO.", "submission": "No single periodic submission is asserted for this combined control obligation.", "applicability": "Current MAS banking AML/CFT control framework.", "consequence": "Non-compliance may lead to MAS supervisory or enforcement action. A single monetary penalty is not asserted because consequences depend on the breached requirement and enforcement route.", "enforcement": "Monetary Authority of Singapore (MAS)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain documented AML/CFT governance, recordkeeping, compliance, audit and training as standing controls rather than treating them as calendar-only tasks.", "evidenceIds": [ "amlb:evidence:127928a9" ], "sourceEntityIds": [ "amlb:source-entity:c5cdd089" ] }, { "id": "GB-REPCRIM", "jurisdictionCode": "GB", "jurisdictionName": "United Kingdom", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "FCA Annual Financial Crime Report (REP-CRIM)", "timingType": "scheduled", "sectors": [ "banking", "securities", "insurance" ], "appliesTo": "Firms within SUP 16.23.1R and the application table in SUP 16.23.2R, subject to the stated exclusions. This includes specified UK/non-UK banks and other listed FCA firms; it is not a return for every MLR-regulated person.", "trigger": "End of the firm’s financial year on its latest accounting reference date.", "deadline": "Annually · within 60 business days of the firm’s accounting reference date.", "recipient": "Financial Conduct Authority (FCA)", "submission": "Form specified in SUP 16 Annex 42AR using the appropriate FCA online systems.", "applicability": "SUP 16.23 current text · last updated 6 Apr 2026.", "consequence": "Failure to comply with an FCA reporting rule can lead to supervisory/enforcement consequences. No single fixed fine is shown because the sanction depends on the facts and enforcement route.", "enforcement": "Financial Conduct Authority (FCA)", "evidenceStatus": "verified", "operationalImpact": "The due date is entity-specific because it depends on the firm’s accounting reference date; the legal deadline rule is shown instead of a universal calendar date.", "evidenceIds": [ "amlb:evidence:79792eac" ], "sourceEntityIds": [ "amlb:source-entity:fb19cb4c" ] }, { "id": "GB-SAR", "jurisdictionCode": "GB", "jurisdictionName": "United Kingdom", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Individuals and organisations where a legal reporting obligation arises, including the regulated sector under POCA/TACT; detailed applicability depends on the statutory offence and role.", "trigger": "Knowledge, suspicion or belief relating to money laundering and/or terrorist financing under the applicable reporting provisions.", "deadline": "Regulated-sector reporters must submit as soon as practicable after the relevant knowledge or suspicion is formed.", "recipient": "UK Financial Intelligence Unit (UKFIU) within the National Crime Agency", "submission": "SAR Portal.", "applicability": "Current reporting route and standard verified 18 Aug 2026.", "consequence": "Where a legal duty exists, failure to report may result in criminal liability and/or regulatory action. Penalty quantum is provision-specific across POCA and TACT offences.", "enforcement": "Criminal justice authorities and the relevant sector regulator/supervisor, depending on the breach.", "evidenceStatus": "verified", "operationalImpact": "Escalation procedures should distinguish internal suspicion review from the external statutory duty and avoid internal service levels that delay filing once the reporting threshold is met.", "evidenceIds": [ "amlb:evidence:28406148", "amlb:evidence:59793d20", "amlb:evidence:218a6b93" ], "sourceEntityIds": [ "amlb:source-entity:b3437784", "amlb:source-entity:9d050209" ] }, { "id": "GB-MLR-RISK", "jurisdictionCode": "GB", "jurisdictionName": "United Kingdom", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Firm-wide ML/TF risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "A “relevant person” within the Money Laundering Regulations 2017, subject to the Regulations’ scope and exemptions.", "trigger": "Ongoing regulated activity and changes affecting the firm’s ML/TF risk exposure.", "deadline": "Ongoing · take appropriate steps to identify and assess ML/TF risks and keep an up-to-date written record of the steps taken, subject to the Regulation 18 exception.", "recipient": "Relevant AML supervisor on request / through supervision; this is primarily an internal governance obligation rather than a fixed-date filing.", "submission": "No universal scheduled submission. Evidence must be maintained and available in accordance with the applicable supervisory framework.", "applicability": "Current MLR 2017 text as amended.", "consequence": "MLR breaches can attract supervisory, civil or criminal consequences depending on the provision and facts. No single penalty is attached to the generic risk-assessment row.", "enforcement": "Relevant MLR supervisor (for example FCA, HMRC or another competent supervisor, depending on sector).", "evidenceStatus": "verified", "operationalImpact": "Treat the business-wide risk assessment as a living control with change-driven review, not a once-a-year document unless the entity’s own governance adds an annual cycle.", "evidenceIds": [ "amlb:evidence:20d2c35f" ], "sourceEntityIds": [ "amlb:source-entity:9d050209" ] }, { "id": "AE-STR", "jurisdictionCode": "AE", "jurisdictionName": "United Arab Emirates", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "STR / SAR and other suspicious reporting", "timingType": "event-driven", "sectors": [ "banking", "payments", "insurance" ], "appliesTo": "Licensed Financial Institutions and other reporting entities within the applicable UAE AML/CFT framework; CBUAE-specific operational guidance applies to LFIs.", "trigger": "Suspicion that a transaction, attempted transaction, activity or funds, regardless of amount, constitute proceeds of crime, relate to crime, or are intended for use in crime, as described by the current CBUAE framework.", "deadline": "Immediately and without delay. CBUAE guidance also sets internal alert-review / investigation expectations, but those do not replace the federal “without delay” reporting duty.", "recipient": "UAE Financial Intelligence Unit (UAEFIU)", "submission": "goAML portal; reporting entities should be connected to goAML.", "applicability": "Current 2025 federal framework; CBUAE page last updated 4 Feb 2026.", "consequence": "CBUAE guidance states that failure to report without delay, intentionally or by gross negligence, is a federal crime. Federal Decree-Law No. 10 of 2025 also establishes a general administrative-fine range of AED 10,000 to AED 5,000,000 for each violation where the administrative-sanction regime applies; the precise sanction and any criminal consequence depend on the legal classification and enforcement decision.", "enforcement": "Competent UAE authority / criminal justice authorities; CBUAE for entities within its supervisory perimeter.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Alert investigation timelines are internal control parameters. They should be designed around, and cannot dilute, the overriding requirement to report suspicion without delay.", "evidenceIds": [ "amlb:evidence:9d5c4934", "amlb:evidence:b7fb6ae0", "amlb:evidence:28caf2c1", "amlb:evidence:8651db62", "amlb:evidence:70062e21" ], "sourceEntityIds": [ "amlb:source-entity:bcf62a1f", "amlb:source-entity:743a0709", "amlb:source-entity:fc017975" ] }, { "id": "AE-DATA-RETURNS", "jurisdictionCode": "AE", "jurisdictionName": "United Arab Emirates", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CBUAE AML/CFT/CPF supervisory data returns", "timingType": "supervisor-driven", "sectors": [ "banking", "payments", "insurance" ], "appliesTo": "CBUAE-supervised LFIs/RHPs/ICRPs within the scope of the AML/CFT Supervision Department’s offsite supervision.", "trigger": "CBUAE supervisory request, data-return cycle or offsite supervision programme.", "deadline": "No public due date or filing cycle verified.", "recipient": "Central Bank of the UAE (CBUAE) · AML/CFT Supervision Department", "submission": "CBUAE supervisory process; exact return channel/form is set by the supervisor.", "applicability": "Current supervisory practice described by CBUAE in 2026.", "consequence": "CBUAE tracks compliance with supervisory deadlines and may take proportionate supervisory/enforcement action for AML/CFT breaches. No return-specific fine is asserted without the underlying notice.", "enforcement": "Central Bank of the UAE (CBUAE)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use the supervisor notice, calendar or request to set the internal filing deadline.", "evidenceIds": [ "amlb:evidence:b2324bb6", "amlb:evidence:28caf2c1" ], "sourceEntityIds": [ "amlb:source-entity:743a0709" ] }, { "id": "AF-STR", "jurisdictionCode": "AF", "jurisdictionName": "Afghanistan", "coverageStatus": "verified-with-legacy-source", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Anti-Money Laundering and Proceeds of Crime Law.", "trigger": "Suspicion or reasonable grounds to suspect a transaction or attempted transaction involves proceeds of crime, money laundering, terrorist financing or relevant predicate offences; or funds are linked to terrorists/terrorism.", "deadline": "As soon as practicable, but no later than three days after forming the suspicion.", "recipient": "Financial Transactions and Reports Analysis Center of Afghanistan (FinTRACA)", "submission": "Form and communication method prescribed by relevant regulations / FinTRACA process.", "applicability": "Current DAB-hosted statutory text.", "consequence": "Intentional failure to report under Article 18 is an offence. Article 51 provides, for a natural person, 6–12 months’ imprisonment or AFN 5,000–50,000 fine or both; for a corporate entity, AFN 25,000–125,000. Persons convicted under the paragraph may also face licence revocation as stated in Article 51(5).", "enforcement": "Competent criminal / supervisory authorities; DAB/FinTRACA within the statutory supervisory framework.", "evidenceStatus": "verified", "operationalImpact": "The three-day statutory outer limit makes the internal escalation clock operationally material; “as soon as practicable” means three days should not be treated as the default waiting period.", "evidenceIds": [ "amlb:evidence:ce47a172", "amlb:evidence:00d360ad", "amlb:evidence:2549d6fe" ], "sourceEntityIds": [ "amlb:source-entity:2330fcca" ] }, { "id": "AF-LCTR", "jurisdictionCode": "AF", "jurisdictionName": "Afghanistan", "coverageStatus": "verified-with-legacy-source", "lastReviewedDate": "2026-09-04", "title": "Large Cash Transaction Report (LCTR)", "timingType": "scheduled", "sectors": [ "banking", "payments" ], "appliesTo": "Reporting entities subject to the threshold-reporting rules. The 2018 official operational detail specifically states the banking threshold and separate non-bank thresholds.", "trigger": "Transaction above the threshold prescribed by DAB regulation in consultation with FinTRACA.", "deadline": "Current AML law Article 17 delegates the threshold and reporting period to regulation. FinTRACA’s official 2018 Annual Report documented, for banks, transactions over AFN 1,000,000 and a filing window from the first to the fifth business day of the following month. The current threshold or timetable is not verified in mapped regulations.", "recipient": "FinTRACA", "submission": "FinTRACA reporting process; current form/channel not reverified for this LCTR row.", "applicability": "Article 17 current statutory duty verified; operational threshold/timing support is dated 2018.", "consequence": "Reporting violations may attract supervisory sanctions. No current LCTR-specific fine is shown without verified operative regulation and sanction route.", "enforcement": "Da Afghanistan Bank / FinTRACA within their respective statutory functions.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not use the AFN 1,000,000 / fifth-business-day detail as a current production rule without rechecking the operative DAB regulation.", "evidenceIds": [ "amlb:evidence:ce47a172", "amlb:evidence:2446caff", "amlb:evidence:4430df27" ], "sourceEntityIds": [ "amlb:source-entity:2330fcca" ] }, { "id": "AF-RISK", "jurisdictionCode": "AF", "jurisdictionName": "Afghanistan", "coverageStatus": "verified-with-legacy-source", "lastReviewedDate": "2026-09-04", "title": "Entity AML/CFT risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under the AML-PC Law.", "trigger": "Ongoing reporting-entity activity and changes in ML/TF risk.", "deadline": "Ongoing / periodic as required by the statutory and supervisory risk framework; no single universal calendar date is stated in the cited law.", "recipient": "Relevant supervisory authority on request / through supervision.", "submission": "Maintain documented risk assessment and controls; provide information when required by the supervisory authority.", "applicability": "Current DAB-hosted statutory text.", "consequence": "Supervisory authorities may impose measures and sanctions for non-compliance; specific consequence depends on the breached obligation.", "enforcement": "Appropriate supervisory authority; DAB for the financial sector.", "evidenceStatus": "verified", "evidenceNote": "Mapped statutory sources confirm the standing control framework and supervisory powers.", "operationalImpact": "Maintain AML policies, compliance management, ongoing training and internal audit as standing obligations not only calendar filings.", "evidenceIds": [ "amlb:evidence:ce47a172" ], "sourceEntityIds": [ "amlb:source-entity:2330fcca" ] }, { "id": "FI-STR", "jurisdictionCode": "FI", "jurisdictionName": "Finland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities within the scope of the Finnish Act on Preventing Money Laundering and Terrorist Financing (444/2017).", "trigger": "A suspicious transaction or suspected terrorist financing after the obliged entity has fulfilled the statutory information-gathering obligation.", "deadline": "Without delay.", "recipient": "Financial Intelligence Unit of Finland (National Bureau of Investigation)", "submission": "Electronic reporting through the FIU Finland reporting service; the Act permits another secure connection or procedure for a special reason.", "applicability": "Current statutory obligation; official English translation used for the mapped provision.", "consequence": "Failure to report is expressly listed among sanctionable AML Act breaches. For the current ordinary administrative-fine route, Finlex states EUR 1,000–100,000 for a legal person and EUR 500–10,000 for a natural person. Serious, repeated or systematic breaches can enter the separate penalty-payment regime, with higher maxima depending on entity type.", "enforcement": "Competent AML supervisory authority; Financial Supervisory Authority for entities within its perimeter, with other supervisors/bar association according to sector.", "evidenceStatus": "verified", "operationalImpact": "Internal investigation and escalation procedures should support a filing decision without avoidable delay once the statutory suspicion threshold is met.", "evidenceIds": [ "amlb:evidence:97b3e124", "amlb:evidence:a8f7bada", "amlb:evidence:37c1487d" ], "sourceEntityIds": [ "amlb:source-entity:0f2acec2", "amlb:source-entity:768d4c0b" ] }, { "id": "FI-RISK", "jurisdictionCode": "FI", "jurisdictionName": "Finland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Obliged-entity ML/TF risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Act 444/2017.", "trigger": "Ongoing obliged-entity activity and material changes affecting ML/TF risk.", "deadline": "Prepare a risk assessment and update it on a regular basis. Supply the assessment and changes without undue delay when requested by the competent supervisor or bar association.", "recipient": "Competent AML supervisor / Finnish Bar Association, as applicable.", "submission": "Maintain internally; supply to the competent supervisor or bar association on request.", "applicability": "Current statutory framework.", "consequence": "Failure to prepare or update the risk assessment is expressly sanctionable under Chapter 8. For the current ordinary administrative-fine route, Finlex states EUR 1,000–100,000 for a legal person and EUR 500–10,000 for a natural person. Serious, repeated or systematic breaches can attract a separate penalty payment.", "enforcement": "Competent AML supervisory authority / Finnish Bar Association according to sector.", "evidenceStatus": "verified", "operationalImpact": "Treat the business-wide risk assessment as a living control; do not rely on an annual-only cycle if material changes require earlier update.", "evidenceIds": [ "amlb:evidence:97b3e124", "amlb:evidence:a8f7bada" ], "sourceEntityIds": [ "amlb:source-entity:0f2acec2" ] }, { "id": "FI-BO", "jurisdictionCode": "FI", "jurisdictionName": "Finland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Beneficial-owner notification to the Trade Register", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Companies and other entities required by Finnish Trade Register rules to file beneficial-owner details; applicability is corporate-form specific and is not identical to the AML obliged-entity perimeter.", "trigger": "No beneficial-owner filing exists yet, details change or become outdated, or a newly registered company was not formed through the YTJ online set-up route that captures the information.", "deadline": "Without delay.", "recipient": "Finnish Patent and Registration Office (PRH) · Trade Register", "submission": "Online at ytj.fi; filing and updating beneficial-owner details is free of charge.", "applicability": "Current PRH filing guidance reviewed 18 Aug 2026.", "consequence": "The filing duty is verified, but this row does not attach an AML Act monetary penalty to a Trade Register filing breach without a filing-specific sanction provision.", "enforcement": "Finnish Patent and Registration Office (PRH)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Corporate change controls should trigger an immediate check of beneficial-owner registry data rather than waiting for a periodic KYC review.", "evidenceIds": [ "amlb:evidence:e1843770", "amlb:evidence:c48c1adf" ], "sourceEntityIds": [ "amlb:source-entity:dd4ec877" ] }, { "id": "SE-AML-ANNUAL", "jurisdictionCode": "SE", "jurisdictionName": "Sweden", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Annual periodic AML reporting to Finansinspektionen", "timingType": "scheduled", "sectors": [ "banking", "payments", "securities", "insurance" ], "appliesTo": "Companies under Finansinspektionen supervision that fall within the relevant scope of the Swedish Money Laundering Act; FI states that entities covered by Chapter 1 section 2 points 1–13 report annually.", "trigger": "Annual FI AML data-collection cycle.", "deadline": "Annually. FI’s current reporting page confirms an annual duty. From 1 January 2027 the redesigned return keeps the reporting period 1 January–31 March and uses data as at 31 December of the preceding year.", "recipient": "Finansinspektionen (FI)", "submission": "Fidac reporting portal.", "applicability": "Current annual duty; redesigned reporting takes effect 1 Jan 2027.", "consequence": "Failure to comply can lead to sector-specific FI supervisory/enforcement action. No universal return-specific monetary fine is asserted because the applicable sanction powers depend on the regulated entity and breach.", "enforcement": "Finansinspektionen (FI)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain ownership of the annual FI data set and prepare for the 2027 question-set redesign; firms selected for direct AMLA supervision may have a separate reporting route under the new framework.", "evidenceIds": [ "amlb:evidence:696113dd", "amlb:evidence:4a3ae22c" ], "sourceEntityIds": [ "amlb:source-entity:2cf167e1" ] }, { "id": "SE-STR", "jurisdictionCode": "SE", "jurisdictionName": "Sweden", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report to Finanspolisen", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the Swedish Money Laundering Act.", "trigger": "Suspicion remains after the reporting entity’s closer analysis of a transaction or activity.", "deadline": "Without delay.", "recipient": "Finanspolisen (Swedish Police Authority)", "submission": "goAML.", "applicability": "Current reporting route and timing verified 18 Aug 2026.", "consequence": "Non-reporting can lead to sanctions under the applicable AML/supervisory regime; the exact monetary consequence depends on entity type and enforcement route and is not shown as one general value.", "enforcement": "Relevant AML supervisor and competent criminal/enforcement authorities; Finanspolisen receives the report.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal investigation should resolve or escalate suspicion promptly; once suspicion remains, the reporting workflow should not introduce avoidable delay.", "evidenceIds": [ "amlb:evidence:b2a87519", "amlb:evidence:ecc50f5a" ], "sourceEntityIds": [ "amlb:source-entity:d40d766d", "amlb:source-entity:82a4c781" ] }, { "id": "SE-RISK", "jurisdictionCode": "SE", "jurisdictionName": "Sweden", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "General business-wide ML/TF risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Business operators within the scope of the Swedish Money Laundering Act.", "trigger": "Ongoing activity and changes to products, services, customers, channels or geographic exposure.", "deadline": "Document the general risk assessment and keep it updated; no single universal calendar date is prescribed in the mapped provision.", "recipient": "Primarily an internal control; relevant AML supervisor through supervision/request.", "submission": "Maintain documented assessment and make it available under the applicable supervisory framework.", "applicability": "Current statutory text.", "consequence": "Supervisory consequences depend on the applicable sector and competent supervisor. No single penalty amount is asserted for the cross-sector obligation.", "enforcement": "Finansinspektionen or another competent AML supervisor depending on sector.", "evidenceStatus": "verified", "evidenceNote": "The current statute expressly requires the general risk assessment to be documented and kept updated.", "operationalImpact": "Review frequency should be change-driven and risk-based, not reduced to a purely annual document cycle.", "evidenceIds": [ "amlb:evidence:ecc50f5a" ], "sourceEntityIds": [ "amlb:source-entity:82a4c781" ] }, { "id": "DK-AMLCTF", "jurisdictionCode": "DK", "jurisdictionName": "Denmark", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "AMLCTF supervisory data return to Finanstilsynet", "timingType": "scheduled", "sectors": [ "banking", "securities" ], "appliesTo": "Entities within the Danish AML Act that fall into the Finanstilsynet AMLCTF reporting populations. Frequency differs by entity type.", "trigger": "Applicable AMLCTF reporting period under the Finanstilsynet reporting calendar.", "deadline": "2026 calendar: banks and mortgage-credit institutions report quarterly with deadlines 11 Feb, 12 May, 11 Aug and 11 Nov; investment firms and specified investment-management entities have an annual 11 Feb deadline. Entity-specific reporting population must be checked against the current calendar.", "recipient": "Finanstilsynet (Danish Financial Supervisory Authority)", "submission": "FIONA Online. Finanstilsynet states AMLCTF is a national return; the 2026 e-Reg migration applies to selected EU returns while national returns continue in FIONA.", "applicability": "Current AMLCTF page last updated 18 Feb 2026; deadline calendar August 2026.", "consequence": "Finanstilsynet may use supervisory/enforcement powers for failures within its reporting perimeter. A return-specific fixed fine is not asserted because the mapped public AMLCTF page/calendar does not state one.", "enforcement": "Finanstilsynet", "evidenceStatus": "verified-with-gap", "operationalImpact": "Banks need a quarterly reporting calendar; investment-sector firms should map whether they fall into the annual AMLCTF population rather than applying the bank cadence to non-bank firms.", "evidenceIds": [ "amlb:evidence:1bc91135", "amlb:evidence:cea50f1b", "amlb:evidence:d41e11fe" ], "sourceEntityIds": [ "amlb:source-entity:74213e86" ] }, { "id": "DK-STR", "jurisdictionCode": "DK", "jurisdictionName": "Denmark", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "Suspicious activity report to Hvidvasksekretariatet", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Businesses and persons subject to the Danish AML Act reporting obligation.", "trigger": "Suspicion of money laundering or terrorist financing that requires external notification under the AML Act.", "deadline": "Immediately / without delay under the AML reporting rule; the current FIU site requires covered reporters to file digitally.", "recipient": "Hvidvasksekretariatet (Danish FIU)", "submission": "goAML portal.", "applicability": "Current official FIU reporting channel verified 18 Aug 2026.", "consequence": "Breach of the AML Act can lead to supervisory and/or criminal consequences depending on the provision and actor. A single universal fine is not attached to this cross-sector row.", "enforcement": "Hvidvasksekretariatet receives reports; supervisory/enforcement authority depends on sector and breach.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Registration and access to goAML should be maintained before an urgent reporting event occurs.", "evidenceIds": [ "amlb:evidence:9504ae9e", "amlb:evidence:e7a473af" ], "sourceEntityIds": [ "amlb:source-entity:b1e29f44", "amlb:source-entity:c93ec0f6" ] }, { "id": "DK-RISK", "jurisdictionCode": "DK", "jurisdictionName": "Denmark", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "Business-wide ML/TF/PF risk assessment and sanctions-control framework", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Businesses and persons covered by the Danish AML Act.", "trigger": "Ongoing business activity and changes to the entity’s ML/TF/PF or relevant financial-sanctions risk exposure.", "deadline": "Ongoing. Maintain and update the section 7 business risk assessment, including specified proliferation-financing breach/evasion risks, and maintain the section 8 written policies, procedures and controls for relevant financial-sanctions and proliferation-financing obligations.", "recipient": "Primarily internal governance; competent AML supervisor through supervision.", "submission": "Maintain documented assessment and related risk-management controls; provide to the competent authority when required under the supervisory framework.", "applicability": "Act No. 764 of 8 September 2026 — principal amendments effective 15 September 2026.", "consequence": "Supervisory/enforcement consequences depend on the entity type, breach and competent authority. No generic monetary amount is asserted.", "enforcement": "Finanstilsynet or another competent AML supervisor depending on sector.", "evidenceStatus": "verified", "evidenceNote": "The Danish AML Act as amended by Act No. 764/2026 extends section 7 risk assessment and section 8 policies, procedures and controls to specified proliferation-financing and financial-sanctions risks.", "operationalImpact": "Maintain the enterprise risk assessment as the documented basis for AML controls and update it when the ML/TF/PF or relevant sanctions-risk picture changes; align written policies, procedures and controls with Act No. 764/2026.", "evidenceIds": [ "amlb:evidence:e7a473af", "amlb:evidence:10a3a70c", "amlb:evidence:c4eaf78a" ], "sourceEntityIds": [ "amlb:source-entity:c93ec0f6", "amlb:source-entity:74213e86" ] }, { "id": "NO-MF", "jurisdictionCode": "NO", "jurisdictionName": "Norway", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Report of suspicious circumstances (MF-report)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities listed in section 4 of the Norwegian Anti-Money Laundering Act.", "trigger": "After closer investigations, circumstances remain that give grounds for suspicion of money laundering or terrorist financing.", "deadline": "As soon as possible.", "recipient": "FIU / Økokrim", "submission": "Electronically through Økokrim’s reporting form; high-volume reporters may use an API. Access/role management is handled through Altinn.", "applicability": "Current Økokrim reporting route verified 18 Aug 2026.", "consequence": "AML Act sanctions depend on the breached provision and facts; this row does not generalise a single monetary amount across all reporting entities.", "enforcement": "Økokrim / competent AML supervisor according to the enforcement route.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Ensure Altinn roles and reporting access are pre-provisioned so technical access does not delay an MF-report.", "evidenceIds": [ "amlb:evidence:8d05b514", "amlb:evidence:f8eaa28a" ], "sourceEntityIds": [ "amlb:source-entity:6944b9f3", "amlb:source-entity:1fcc9ce3" ] }, { "id": "NO-RISK", "jurisdictionCode": "NO", "jurisdictionName": "Norway", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business-wide ML/TF risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Norwegian Anti-Money Laundering Act.", "trigger": "Ongoing activity and changes to the entity’s products, services, customers, channels and geographic risk.", "deadline": "Ongoing. Section 7 requires reporting entities to identify and assess their ML/TF risk; no single universal calendar due date is asserted.", "recipient": "Relevant AML supervisor through supervision.", "submission": "Maintain the documented risk assessment and associated procedures internally; provide evidence under the applicable supervisory regime.", "applicability": "Current statutory framework.", "consequence": "Supervisory and administrative consequences depend on the sector and breach. A universal penalty amount is not shown for the generic risk-assessment duty.", "enforcement": "Finanstilsynet and/or another competent AML supervisor depending on sector.", "evidenceStatus": "verified", "evidenceNote": "Section 7 is directly mapped in the current statutory text.", "operationalImpact": "Use the business-wide assessment as the basis for procedures and control intensity; update when the risk picture changes.", "evidenceIds": [ "amlb:evidence:cfc602eb" ], "sourceEntityIds": [ "amlb:source-entity:1fcc9ce3" ] }, { "id": "NO-BO", "jurisdictionCode": "NO", "jurisdictionName": "Norway", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Register beneficial owners", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "All entities that are registrable in Norway’s Register of Beneficial Owners; this corporate-registry perimeter is not identical to the AML reporting-entity perimeter.", "trigger": "The entity is registered in a public register, obtains new beneficial owners, or other reportable beneficial-owner changes occur.", "deadline": "Within 14 days.", "recipient": "Register of Beneficial Owners · Brønnøysund Register Centre", "submission": "Digital filing through Altinn / the Brønnøysund registration service.", "applicability": "Current registry guidance reviewed 18 Aug 2026.", "consequence": "The register states that daily coercive fines (tvangsmulkt) will be imposed if the registration obligation is not followed up.", "enforcement": "Brønnøysund Register Centre · Register of Beneficial Owners", "evidenceStatus": "verified-with-gap", "operationalImpact": "Company-secretarial and KYC change processes should share ownership-change events so the registry filing clock is not missed.", "evidenceIds": [ "amlb:evidence:64e8348b" ], "sourceEntityIds": [ "amlb:source-entity:4b411a27" ] }, { "id": "IS-STR", "jurisdictionCode": "IS", "jurisdictionName": "Iceland", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / funds report to the FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Notifiable / obliged entities under Iceland’s AML framework.", "trigger": "A transaction, planned transaction or funds are suspected of being connected to money laundering or terrorist financing after the required investigation.", "deadline": "In a timely manner.", "recipient": "Financial Intelligence Unit of Iceland", "submission": "Official FIU reporting process. The exact public portal/form channel was not verified in mapped public sources.", "applicability": "Current official FIU duty reviewed 18 Aug 2026.", "consequence": "Breaches can attract sanctions under the AML framework; exact sanction and amount depend on the obliged entity, supervisor and provision. No single penalty amount is shown.", "enforcement": "Financial Intelligence Unit receives reports; competent AML supervisor / enforcement authority depends on sector and breach.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep an internal escalation path that can reach the FIU promptly, and separately verify the institution’s current technical submission credentials.", "evidenceIds": [ "amlb:evidence:94dbcebc", "amlb:evidence:31abccad" ], "sourceEntityIds": [ "amlb:source-entity:4b5684f7", "amlb:source-entity:04e3d5ab" ] }, { "id": "IS-RISK", "jurisdictionCode": "IS", "jurisdictionName": "Iceland", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Business-wide ML/TF risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Act No. 140/2018; Central Bank supervisory consequences stated here apply to entities within the Bank’s AML supervisory perimeter.", "trigger": "Ongoing activity, need arising, and before new products/services, distribution channels or technologies are introduced.", "deadline": "Update at least every two years and whenever the need arises.", "recipient": "Relevant AML supervisor; Central Bank of Iceland for entities within its supervisory perimeter.", "submission": "Maintain a written analysis, documented methodology and assessment; provide through the applicable supervisory process when required.", "applicability": "Current Central Bank guidance reviewed 18 Aug 2026.", "consequence": "Within the Central Bank’s supervisory perimeter, AML breaches may lead to measures including administrative fines and, where legally applicable, management removal or licence revocation. Exact consequence depends on the provision and entity.", "enforcement": "Central Bank of Iceland for its supervised entities; other competent AML supervisors by sector.", "evidenceStatus": "verified", "evidenceNote": "The two-year minimum update cadence and change-driven/pre-launch triggers are stated on the Central Bank’s current AML measures page.", "operationalImpact": "Set a maximum two-year review cycle, with earlier event-driven refresh before material product, channel or technology changes.", "evidenceIds": [ "amlb:evidence:ff69c365", "amlb:evidence:1a6f36f5", "amlb:evidence:31abccad" ], "sourceEntityIds": [ "amlb:source-entity:7bb1c851", "amlb:source-entity:04e3d5ab" ] }, { "id": "AX-STR-LOCAL", "jurisdictionCode": "AX", "jurisdictionName": "Åland Islands", "coverageStatus": "scope-qualified", "lastReviewedDate": "2026-08-18", "title": "Suspicious transaction reporting · verified Åland local-sector scope", "timingType": "event-driven", "sectors": [ "real-estate", "gambling" ], "appliesTo": "Åland gambling operators and the real-estate / housing-rental agency sectors covered by the Åland supervisory delegation. The row is not generalised to every Åland business or financial institution.", "trigger": "A suspicious transaction or suspected terrorist financing under the Finnish Money Laundering Act.", "deadline": "Without delay.", "recipient": "Financial Intelligence Unit of Finland (National Bureau of Investigation)", "submission": "Electronic reporting through the FIU Finland online reporting system; another secure connection/procedure may be used for a special reason.", "applicability": "Åland delegation decree in force; current official AML reporting guidance verified 18 Aug 2026.", "consequence": "The Åland decree delegates Chapter 8 administrative-sanction duties for the specified gambling and real-estate/housing-rental sectors, including administrative fine, public warning and penalty payment. Under Chapter 8 section 5 of the Money Laundering Act, a penalty payment for obliged entities other than credit or financial institutions may be up to twice the gain from the breach, where determinable, or EUR 1 million, whichever is higher.", "enforcement": "Government of Åland / Ålands lotteriinspektion for the delegated supervisory functions; Government of Åland for the delegated administrative-sanction procedure described in Decree 500/2018.", "evidenceStatus": "verified-scope", "evidenceNote": "Unlike a parent-country inheritance shortcut, this row is based on an official decree that expressly allocates AML supervisory functions in Åland plus the underlying Finnish AML reporting rule.", "operationalImpact": "For the two locally delegated sectors, Åland-specific supervisor mapping matters even though the suspicious report itself goes to Finland’s national FIU.", "evidenceIds": [ "amlb:evidence:d84914cc", "amlb:evidence:a8f7bada", "amlb:evidence:37c1487d" ], "sourceEntityIds": [ "amlb:source-entity:0f2acec2", "amlb:source-entity:768d4c0b" ] }, { "id": "AX-RISK-LOCAL", "jurisdictionCode": "AX", "jurisdictionName": "Åland Islands", "coverageStatus": "scope-qualified", "lastReviewedDate": "2026-08-18", "title": "AML risk assessment · verified Åland local-sector scope", "timingType": "ongoing", "sectors": [ "real-estate", "gambling" ], "appliesTo": "Obliged entities within the locally delegated Åland supervisory sectors.", "trigger": "Ongoing activity and material changes to ML/TF risk.", "deadline": "Risk assessment must be updated on a regular basis; changes and the assessment must be supplied without undue delay to the competent supervisor at its request.", "recipient": "Government of Åland or Ålands lotteriinspektion within the delegated supervisory perimeter, as applicable.", "submission": "Maintain internally; provide to the competent supervisor on request.", "applicability": "Current official legal framework.", "consequence": "Administrative supervisory consequences may apply under the Money Laundering Act and the Åland delegation arrangements. No single penalty amount is asserted for the generic risk-assessment obligation.", "enforcement": "Government of Åland / Ålands lotteriinspektion within the delegated sectors.", "evidenceStatus": "verified-scope", "evidenceNote": "The underlying obliged-entity risk-assessment rule and Åland sector supervisory allocation are both identified. No broader Finland-to-Åland inheritance is assumed.", "operationalImpact": "Local-sector entities need a documented, regularly updated ML/TF risk assessment and should be able to provide it promptly when requested by the competent Åland supervisor.", "evidenceIds": [ "amlb:evidence:a8f7bada", "amlb:evidence:d84914cc", "amlb:evidence:a9b7ac28" ], "sourceEntityIds": [ "amlb:source-entity:0f2acec2", "amlb:source-entity:367261e6" ] }, { "id": "IE-STR", "jurisdictionCode": "IE", "jurisdictionName": "Ireland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report to FIU Ireland", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Designated persons within the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010, subject to the Act’s scope and sector-specific supervision.", "trigger": "Knowledge, suspicion or reasonable grounds to suspect that another person has been or is engaged in money laundering or terrorist financing, within the statutory reporting conditions.", "deadline": "As soon as practicable after the relevant knowledge or suspicion arises.", "recipient": "FIU Ireland (Garda National Economic Crime Bureau); Revenue Commissioners also receive the statutory report under the Irish dual-reporting framework.", "submission": "FIU Ireland operates goAML for electronic STR filing; reporting entities should follow the current FIU/Garda registration and filing instructions.", "applicability": "Current national reporting duty; reviewed 18 Aug 2026.", "consequence": "Failure to comply with the statutory reporting duty can create criminal/regulatory consequences. A single fine is not displayed because offence and sanction depend on the breached provision and person/entity involved.", "enforcement": "An Garda Síochána / FIU Ireland; relevant sector supervisor may take separate action.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation procedures should reach the MLRO/nominated reporting route quickly enough to support filing as soon as practicable.", "evidenceIds": [ "amlb:evidence:6c14dd57", "amlb:evidence:71cba8db" ], "sourceEntityIds": [ "amlb:source-entity:95db49fd", "amlb:source-entity:5444a0be" ] }, { "id": "IE-BRA", "jurisdictionCode": "IE", "jurisdictionName": "Ireland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business risk assessment and AML/CFT controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Designated persons within the 2010 Act as amended, with sector-specific expectations layered on by the relevant competent authority.", "trigger": "Establishment and continuation of an in-scope business, taking account of customer, product/service, transaction, delivery-channel and geographic risk factors.", "deadline": "Ongoing. The business risk assessment must be documented, kept up to date and available to the competent authority; no universal external filing date is asserted.", "recipient": "Relevant competent authority / sector supervisor, including the Central Bank of Ireland for supervised financial firms.", "submission": "Maintain internally and provide to the competent authority when required; no universal periodic submission is asserted.", "applicability": "Current requirement; section 30A inserted by the 2018 amendment framework.", "consequence": "Deficient risk assessment or controls may lead to supervisory, administrative or criminal consequences depending on the applicable provision and supervisor.", "enforcement": "Relevant competent authority / sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep a documented enterprise-level assessment current and use it to drive policies, CDD intensity, monitoring and governance.", "evidenceIds": [ "amlb:evidence:84b691e7", "amlb:evidence:9d7a999c" ], "sourceEntityIds": [ "amlb:source-entity:95db49fd", "amlb:source-entity:b31dce2e" ] }, { "id": "NL-UTR", "jurisdictionCode": "NL", "jurisdictionName": "Netherlands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Unusual transaction report (ongebruikelijke transactie)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Wwft reporting institutions where an objective or subjective reporting indicator is met.", "trigger": "An unusual transaction is identified under the applicable Wwft reporting indicators, including transactions giving reason to assume a connection with money laundering or terrorist financing.", "deadline": "Without unnecessary delay (onverwijld): FIU-Nederland explains this as reporting as soon as possible after the institution has made the necessary careful assessment.", "recipient": "FIU-the Netherlands (FIU-Nederland)", "submission": "Electronic reporting through FIU-Nederland’s reporting environment under the applicable reporting-group instructions.", "applicability": "Current Wwft reporting duty; reviewed 18 Aug 2026.", "consequence": "Failure to report can constitute a breach of the Wwft and may qualify as an economic offence; supervisory enforcement is also possible.", "enforcement": "FIU-Nederland receives reports; relevant Wwft supervisor and enforcement authorities handle non-compliance according to competence.", "evidenceStatus": "verified", "operationalImpact": "Transaction-monitoring and escalation workflows should support a documented assessment followed by prompt FIU reporting once the reporting indicator is met.", "evidenceIds": [ "amlb:evidence:66d98669", "amlb:evidence:4760ba46" ], "sourceEntityIds": [ "amlb:source-entity:3162cff0", "amlb:source-entity:20f2f8c0" ] }, { "id": "NL-RISK-CONTROLS", "jurisdictionCode": "NL", "jurisdictionName": "Netherlands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls and ongoing customer monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Institutions within the Wwft, with supervisory responsibility divided across DNB, AFM, BFT and other competent supervisors by sector.", "trigger": "Continuous operation of an in-scope institution and the risks presented by customers, products, services, transactions, delivery channels and geography.", "deadline": "Ongoing; intensity must be proportionate to ML/TF risk. No single external calendar filing date is asserted for this combined control duty.", "recipient": "Relevant Wwft supervisor; DNB for the financial institutions under its AML/CFT integrity supervision.", "submission": "Implemented through internal policies, CDD, transaction monitoring and risk-based measures; information is provided to supervisors as legally required.", "applicability": "Current national framework; DNB supervisory material current in 2026.", "consequence": "Inadequate Wwft controls can result in supervisory measures and administrative fines; the amount depends on the breach and enforcement decision.", "enforcement": "Relevant Wwft supervisor, including DNB for supervised institutions.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Document how risk drives CDD, monitoring and mitigating measures, and retain evidence that controls are proportionate.", "evidenceIds": [ "amlb:evidence:61be3702", "amlb:evidence:4ccc006c" ], "sourceEntityIds": [ "amlb:source-entity:814213f4" ] }, { "id": "BE-STR", "jurisdictionCode": "BE", "jurisdictionName": "Belgium", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious facts / transactions disclosure to CTIF-CFI", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities and professions listed in the Belgian Law of 18 September 2017.", "trigger": "Facts, funds or transactions where the reporting entity knows, suspects or has reasonable grounds to suspect money laundering, terrorist financing or related predicate circumstances under the law.", "deadline": "Immediately under the 2017 Law. Where the report concerns a transaction, the preventive framework expects reporting before execution where possible; statutory exceptions permit immediate post-execution reporting in defined circumstances.", "recipient": "CTIF-CFI / CFI Belgium", "submission": "Use the reporting arrangements and electronic declaration facilities prescribed by CTIF-CFI for the relevant reporting entity.", "applicability": "Current Belgian preventive framework.", "consequence": "Non-reporting or late reporting can lead to administrative/supervisory sanctions under the 2017 Law; exact amount depends on the entity, breach and sanctioning authority.", "enforcement": "CTIF-CFI receives disclosures; competent supervisory/regulatory/disciplinary authorities enforce compliance.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Reporting workflows should enable pre-execution escalation where feasible and immediate reporting once the legal suspicion test is met.", "evidenceIds": [ "amlb:evidence:b0c54560", "amlb:evidence:18d5eaf6" ], "sourceEntityIds": [ "amlb:source-entity:621c14bb", "amlb:source-entity:cb39b09e" ] }, { "id": "BE-RISK-POLICY", "jurisdictionCode": "BE", "jurisdictionName": "Belgium", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Institution-wide ML/TF risk assessment and AML policy", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under the 2017 AML Law, subject to sector-specific supervisor rules.", "trigger": "Continuous operation of the institution and changes in its business, customers, products, transactions, channels and geographic exposure.", "deadline": "Ongoing. Maintain risk assessment, policies, procedures and controls; no universal external filing date is asserted.", "recipient": "Relevant competent supervisor; NBB for supervised financial institutions within its perimeter.", "submission": "Internal governance and documentation; provide information to the supervisor when required.", "applicability": "Current Belgian AML/CFT control framework.", "consequence": "Weaknesses can trigger remediation, administrative sanctions and other supervisory measures; consequences are authority- and breach-specific.", "enforcement": "NBB / FSMA / FPS Economy / professional bodies or other competent supervisor depending on the obliged entity.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented risk-based framework that can be evidenced to the competent supervisor.", "evidenceIds": [ "amlb:evidence:783918ad", "amlb:evidence:db13b335", "amlb:evidence:18d5eaf6" ], "sourceEntityIds": [ "amlb:source-entity:cb39b09e" ] }, { "id": "LU-STR", "jurisdictionCode": "LU", "jurisdictionName": "Luxembourg", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction report to CRF", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Professionals subject to the Law of 12 November 2004, subject to sector scope and exemptions.", "trigger": "Knowledge, suspicion or reasonable grounds to suspect money laundering, associated predicate offences, terrorist financing or relevant suspicious activity under the law.", "deadline": "Without delay. CSSF guidance reiterates prompt reporting to the CRF when doubt persists.", "recipient": "Cellule de renseignement financier (CRF Luxembourg)", "submission": "goAML / CRF electronic reporting route and CRF-prescribed report forms or report types.", "applicability": "Current national AML/CFT reporting duty.", "consequence": "Failure to report or reporting deficiencies may lead to criminal, administrative or supervisory sanctions depending on the provision and professional category.", "enforcement": "CRF receives reports; CSSF and other competent supervisors enforce sector compliance.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation should allow the responsible function to complete the preliminary assessment and report without avoidable delay.", "evidenceIds": [ "amlb:evidence:d2306828", "amlb:evidence:cab4afd8", "amlb:evidence:78602492" ], "sourceEntityIds": [ "amlb:source-entity:4e6229fd", "amlb:source-entity:c5b37205" ] }, { "id": "LU-RISK-CONTROLS", "jurisdictionCode": "LU", "jurisdictionName": "Luxembourg", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Professional ML/TF risk assessment, policies and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Professionals within the 2004 Law, with sector-specific CSSF or other supervisory rules layered on where applicable.", "trigger": "Continuous business activity and changes in institutional/customer/product/geographic risk.", "deadline": "Ongoing; risk assessment and AML/CFT control framework must remain current and proportionate. No universal filing date is asserted.", "recipient": "Relevant competent supervisory authority; CSSF for entities within its perimeter.", "submission": "Maintain and evidence internally; submit/provide to supervisor where the applicable rule or supervisory request requires it.", "applicability": "Current national and CSSF framework.", "consequence": "Deficiencies may result in supervisory remediation, administrative sanctions or other measures depending on legal basis and regulated status.", "enforcement": "CSSF or other competent supervisory authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the enterprise risk assessment and control architecture aligned to actual exposure and supervisory expectations.", "evidenceIds": [ "amlb:evidence:d2306828", "amlb:evidence:78602492" ], "sourceEntityIds": [ "amlb:source-entity:4e6229fd" ] }, { "id": "DE-STR", "jurisdictionCode": "DE", "jurisdictionName": "Germany", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report (Verdachtsmeldung)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under the Geldwäschegesetz (GwG).", "trigger": "Facts indicating that an asset may originate from a criminal offence, relate to terrorist financing, or that a contracting party may not be acting for a disclosed beneficial owner, under §43 GwG.", "deadline": "Without delay (unverzüglich) once the statutory reporting facts are present.", "recipient": "Financial Intelligence Unit (FIU Germany)", "submission": "Generally electronically through the FIU goAML web portal.", "applicability": "Current GwG reporting duty.", "consequence": "Breaches can be administrative offences and may lead to fines/supervisory measures under the GwG; the applicable amount depends on the specific offence provision and case.", "enforcement": "FIU Germany receives reports; competent supervisory and administrative authorities enforce GwG compliance.", "evidenceStatus": "verified", "operationalImpact": "Escalation and filing procedures should support immediate legal assessment and electronic submission without avoidable delay.", "evidenceIds": [ "amlb:evidence:b4371163", "amlb:evidence:789c366a", "amlb:evidence:dd68a27a", "amlb:evidence:2150f454" ], "sourceEntityIds": [ "amlb:source-entity:9d4f4234", "amlb:source-entity:5e58a65f" ] }, { "id": "DE-RISK", "jurisdictionCode": "DE", "jurisdictionName": "Germany", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Institutional ML/TF risk analysis (Risikoanalyse)", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under the GwG, subject to any statutory exemptions or supervisor-approved simplifications.", "trigger": "Continuous business activity and material changes to products, customers, channels, organisation or geographic exposure.", "deadline": "Ongoing. §5 GwG requires identification and assessment of risks, documentation, regular review and updating; the current version must be supplied to the supervisory authority on request.", "recipient": "Relevant GwG supervisory authority; BaFin for supervised financial-sector entities within its perimeter.", "submission": "Maintain internally in documented form and provide the current version to the competent authority on request.", "applicability": "Current GwG institutional risk-analysis obligation.", "consequence": "Failure to maintain an adequate risk analysis can result in supervisory measures and administrative fines under the GwG.", "enforcement": "Relevant GwG supervisory authority, including BaFin where competent.", "evidenceStatus": "verified", "evidenceNote": "Current §5 duty, review/update requirement and on-request availability are directly mapped.", "operationalImpact": "Treat the risk analysis as a living governance document, not an annual checkbox; update it when the risk picture materially changes.", "evidenceIds": [ "amlb:evidence:b4371163", "amlb:evidence:0f8d339c" ], "sourceEntityIds": [ "amlb:source-entity:9d4f4234", "amlb:source-entity:f7f1027a" ] }, { "id": "FR-DS", "jurisdictionCode": "FR", "jurisdictionName": "France", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons subject to Article L.561-2 of the Code monétaire et financier, subject to professional scope and exemptions.", "trigger": "Knowledge, suspicion or good reason to suspect that funds/operations fall within Article L.561-15, including relevant ML/TF and specified tax-fraud circumstances.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; when a statutory exception permits an already-executed transaction, TRACFIN must be informed without delay.", "recipient": "TRACFIN", "submission": "Primarily electronically through the ERMES platform; official fallback procedures apply if ERMES is unavailable or in defined exceptional circumstances.", "applicability": "Current French AML/CFT reporting framework.", "consequence": "Failures may lead to disciplinary/supervisory or other legal consequences. The applicable sanction depends on profession, breach and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional supervisors enforce compliance.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal monitoring, enhanced examination and escalation should be designed so a report reaches TRACFIN without delay once suspicion is established.", "evidenceIds": [ "amlb:evidence:f246b223", "amlb:evidence:71680dd1", "amlb:evidence:b83d2f36" ], "sourceEntityIds": [ "amlb:source-entity:a0a130ef", "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "FR-RISK-CONTROLS", "jurisdictionCode": "FR", "jurisdictionName": "France", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "ML/TF risk classification, procedures and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within Article L.561-2, with detailed governance expectations varying by professional category and supervisor.", "trigger": "Continuous activity and changes in customers, products/services, transactions, delivery channels, geography and organisation.", "deadline": "Ongoing. Risk identification/classification and related procedures must be maintained and updated, including after significant internal or external changes.", "recipient": "Relevant supervisory authority; ACPR for prudentially supervised financial institutions in its perimeter.", "submission": "Internal governance and documentation; available to the competent supervisor under the applicable framework.", "applicability": "Current framework; official implementing material remains in force with later updates.", "consequence": "Deficiencies can lead to supervisory remediation and disciplinary/financial sanctions; sanction scale depends on entity and provision.", "enforcement": "ACPR or other competent supervisory/professional authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep risk classification and policies dynamically aligned to material changes and use them to calibrate vigilance and monitoring.", "evidenceIds": [ "amlb:evidence:c42d622c", "amlb:evidence:b83d2f36" ], "sourceEntityIds": [ "amlb:source-entity:a0a130ef", "amlb:source-entity:989e83c3" ] }, { "id": "FR-TRAINING", "jurisdictionCode": "FR", "jurisdictionName": "France", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Mandatory AML/CFT staff training and training-record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons subject to Article L.561-2 of the Code monétaire et financier, for personnel participating in implementation of AML/CFT obligations.", "trigger": "At hiring for relevant personnel and regularly thereafter; training content and frequency must reflect the entity’s risk classification and the personnel’s functions, activities and level of responsibility.", "deadline": "Training at hiring and regularly thereafter. Keep records of mandatory training throughout the person’s functions and for five years after those functions end.", "recipient": "Relevant competent supervisory authority under Article L.561-36.", "submission": "Maintain internal training documentation and make it available to the competent supervisory authority.", "applicability": "26 April 2026 under Decree No. 2026-310; specified beneficial-owner register request-timing provisions have a separate 10 November 2026 commencement.", "consequence": "Supervisors verify compliance with the training duty and the adequacy of training frequency and content; consequences depend on the applicable supervisory and sanctioning framework.", "enforcement": "ACPR or other competent supervisory/professional authority for the relevant Article L.561-2 category.", "evidenceStatus": "verified", "evidenceNote": "Article D.561-38-1-1 requires training at hiring and regularly thereafter, risk- and role-adjusted content/frequency, and retention of training documents for five years after the relevant functions end.", "operationalImpact": "Add training-at-hire and recurring risk-based training controls, with evidence retention extending five years beyond the employee’s relevant functions.", "evidenceIds": [ "amlb:evidence:f62f0ed5" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "ES-INDICIO", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Comunicación por indicio (suspicious transaction / fact)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 10/2010 when the structured special examination under Article 17 results in indication or certainty of ML/TF connection.", "trigger": "After the structured special examination identifies indication or certainty that a fact, transaction or attempted transaction is related to money laundering or terrorist financing.", "deadline": "Without delay (sin dilación).", "recipient": "Sepblac", "submission": "Route depends on reporter type: credit institutions and specified centralised bodies use CTL 2.3; other obliged subjects use the current Sepblac/Banco de España electronic-register process with the prescribed F19 structure, subject to current instructions.", "applicability": "Current national reporting procedure.", "consequence": "Failure to report can constitute an administrative infringement under Law 10/2010; classification and monetary range depend on the specific infringement provision and facts.", "enforcement": "Sepblac / CPBCIM and competent supervisory authorities.", "evidenceStatus": "verified", "evidenceNote": "Current Sepblac page directly confirms “sin dilación” and the reporter-specific submission routes.", "operationalImpact": "Special-examination procedures should have explicit escalation ownership and service levels to avoid reporting delay once suspicion is established.", "evidenceIds": [ "amlb:evidence:bebd347c", "amlb:evidence:b48e4f1a", "amlb:evidence:9822e0e0" ], "sourceEntityIds": [ "amlb:source-entity:fb855c43", "amlb:source-entity:0e1e896e" ] }, { "id": "ES-DMO", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Comunicación sistemática (DMO)", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged subjects and operation categories within Article 27 of Real Decreto 304/2014, subject to the explicit exemptions in Article 27.3.", "trigger": "Completion of a month containing operations subject to systematic communication; a negative semiannual declaration applies where no reportable operations occurred during the natural semester.", "deadline": "Monthly · between days 1 and 15 of each month for reportable operations from the previous month. If no reportable operations occurred during a natural semester, negative declaration between days 1 and 15 of the following month.", "recipient": "Sepblac", "submission": "Telematic submission through the DMO application. Out-of-time reporting requires the additional justification procedure described by Sepblac.", "applicability": "Current procedure; Sepblac 2026 notices continue to apply the 1–15 monthly window.", "consequence": "Late or missing systematic reporting can lead to administrative enforcement under Law 10/2010; exact classification/quantum depends on the breach.", "enforcement": "Sepblac / CPBCIM and competent supervisory authorities.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Calendar owners can compute a recurring 1–15 filing window each month for entities within the systematic-reporting perimeter.", "evidenceIds": [ "amlb:evidence:8f7b7f26", "amlb:evidence:ad0b1250", "amlb:evidence:9822e0e0" ], "sourceEntityIds": [ "amlb:source-entity:fb855c43", "amlb:source-entity:0e1e896e" ] }, { "id": "ES-CONTROLS", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Internal AML controls, risk procedures and annual training plan", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 10/2010, subject to statutory size/scope exceptions for particular internal-control measures.", "trigger": "Continuous operation and changing ML/TF risk exposure.", "deadline": "Ongoing internal-control framework. The implementing Regulation requires an annual AML/CFT training plan; no universal external filing date is asserted for the plan itself.", "recipient": "Relevant supervisory authority / Sepblac within its supervisory remit.", "submission": "Maintain internally; inspection/remediation information is supplied to supervisory authorities as required.", "applicability": "Current national internal-control framework.", "consequence": "Control failures may lead to remediation orders and administrative sanction proceedings under Law 10/2010.", "enforcement": "Sepblac / competent sector supervisor / CPBCIM.", "evidenceStatus": "verified-with-gap", "evidenceNote": "Annual plan requirement is verified, but it is an internal governance obligation rather than a universal annual filing.", "operationalImpact": "Maintain a risk-based control framework and a documented annual training plan tied to identified risks.", "evidenceIds": [ "amlb:evidence:9822e0e0", "amlb:evidence:2442d4a4", "amlb:evidence:b48e4f1a" ], "sourceEntityIds": [ "amlb:source-entity:0e1e896e", "amlb:source-entity:fb855c43" ] }, { "id": "ES-RD813-GAMING-TRANSITION", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Royal Decree 813/2026 — gaming identity and technical-system transition", "timingType": "scheduled", "sectors": [ "gaming" ], "appliesTo": "Gaming operators and players registered before the new payment-account identity-match obligation enters into force, within the scope of the amended Regulation of Law 10/2010.", "trigger": "Entry into force of Royal Decree 813/2026 on 28 October 2026.", "deadline": "28 April 2027 · six months from entry into force. Existing players must make the changes needed for the account-holder/payment-method identity check, and gaming operators have the same six-month period to adapt technical systems.", "recipient": "Internal implementation; where the six-month player verification condition is not met, the operator must terminate the contract and communicate that fact to the Directorate-General for the Regulation of Gambling.", "submission": "Implement system and customer-remediation controls; communication to the Directorate-General for the Regulation of Gambling applies in the non-compliant post-transition scenario specified by the decree.", "applicability": "Royal Decree 813/2026 enters into force on 28 October 2026; transition deadline 28 April 2027.", "consequence": "After the transition period, an operator must terminate the relevant contract if the required identity-match verification has not been achieved; other AML/CFT obligations remain applicable.", "enforcement": "SEPBLAC / competent gambling authority within their respective remits.", "evidenceStatus": "verified", "evidenceNote": "The primary regulation states a six-month transition counted from its entry into force; BOE records entry into force as 28 October 2026.", "operationalImpact": "Gaming operators should complete payment-account identity controls and technical-system changes before 28 April 2027 and establish the required post-deadline contract/notification workflow.", "evidenceIds": [ "amlb:evidence:531dc682" ], "sourceEntityIds": [ "amlb:source-entity:0e1e896e" ] }, { "id": "ES-RD813-SEPBLAC-REPRESENTATIVE", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Royal Decree 813/2026 — qualifying small obliged subjects must notify SEPBLAC representative", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged subjects in Article 2.1(i)–(u) of Law 10/2010 that, including agents, employ fewer than 10 persons and have annual turnover or annual balance sheet not exceeding EUR 2 million.", "trigger": "Entry into force of Royal Decree 813/2026 on 28 October 2026.", "deadline": "28 July 2027 · nine months from entry into force to communicate the appointment of the representative to SEPBLAC under Article 35 of the Regulation.", "recipient": "Servicio Ejecutivo de la Comisión (SEPBLAC).", "submission": "Communicate the appointment of the representative to SEPBLAC in accordance with Article 35 of the Regulation of Law 10/2010 and current SEPBLAC procedure.", "applicability": "Transition begins 28 October 2026; deadline 28 July 2027.", "consequence": "The decree creates a time-limited transition to bring qualifying entities into the representative-notification requirement; enforcement follows the applicable Law 10/2010 supervisory and sanctions framework.", "enforcement": "SEPBLAC / CPBCIM and competent supervisory authorities.", "evidenceStatus": "verified", "evidenceNote": "The primary regulation states nine months from entry into force; BOE records entry into force as 28 October 2026.", "operationalImpact": "Qualifying small obliged subjects should determine representative status early and complete the SEPBLAC notification before 28 July 2027.", "evidenceIds": [ "amlb:evidence:531dc682" ], "sourceEntityIds": [ "amlb:source-entity:0e1e896e" ] }, { "id": "ES-RD813-EID-TRANSITION", "jurisdictionCode": "ES", "jurisdictionName": "Spain", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Royal Decree 813/2026 — electronic-identification amendments become applicable", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged subjects using the electronic-identification and document-retention mechanisms affected by amended Articles 6.1(a) and 28 of the Regulation of Law 10/2010.", "trigger": "Publication of Royal Decree 813/2026 in the BOE on 8 October 2026.", "deadline": "8 April 2028 · eighteen months from publication, when the specified electronic-identification amendments become applicable.", "recipient": "Internal implementation / competent AML supervisor as applicable.", "submission": "No universal external filing is created by this transition; update identification and record-retention systems so the amended provisions can be applied from the stated date.", "applicability": "Specified amendments become applicable 8 April 2028.", "consequence": "From the applicability date, affected identity-verification and record-retention processes must operate under the amended regulatory provisions.", "enforcement": "SEPBLAC / competent sector supervisor / CPBCIM.", "evidenceStatus": "verified", "evidenceNote": "The decree states eighteen months from publication; publication was 8 October 2026.", "operationalImpact": "Plan technology, onboarding and record-retention changes sufficiently ahead of 8 April 2028.", "evidenceIds": [ "amlb:evidence:531dc682" ], "sourceEntityIds": [ "amlb:source-entity:0e1e896e" ] }, { "id": "PT-STR", "jurisdictionCode": "PT", "jurisdictionName": "Portugal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Suspicious operation communication (comunicação de operações suspeitas)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Lei n.º 83/2017, subject to the law’s professional scope.", "trigger": "Knowledge, suspicion or sufficient grounds to suspect that funds/assets derive from criminal activity or are related to terrorist financing under Article 43.", "deadline": "Immediately (de imediato) once the statutory suspicion condition is met.", "recipient": "Unidade de Informação Financeira (UIF) and DCIAP, in accordance with the Portuguese dual-recipient statutory framework.", "submission": "From 13 April 2026, submit suspicious operation communications through Portal COS / goAML. During the six-month transition through 13 October 2026, the official ASAE notice requires cumulative portal submission and sending the generated PDF to uif.comunicacoes@pj.pt.", "applicability": "Portal COS procedure operational from 13 April 2026; dual-submission transition runs through 13 October 2026.", "consequence": "Failure to communicate can result in administrative/criminal consequences under the statutory sanction framework; exact monetary range depends on breach and entity category.", "enforcement": "Relevant sector authority / enforcement bodies; UIF and DCIAP are report recipients.", "evidenceStatus": "verified", "operationalImpact": "Maintain Portal COS registration and workflow controls. Through 13 October 2026, ensure each suspicious-operation communication is submitted through the portal and the generated PDF is also sent to the UIF email address; after the transition, follow the current portal procedure.", "evidenceIds": [ "amlb:evidence:7c52ddad", "amlb:evidence:9283d81a", "amlb:evidence:d401f599" ], "sourceEntityIds": [ "amlb:source-entity:20e8de15", "amlb:source-entity:331464bf", "amlb:source-entity:2a3081a5" ] }, { "id": "PT-RPB", "jurisdictionCode": "PT", "jurisdictionName": "Portugal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Banco de Portugal annual AML/CFT Prevention Report (RPB)", "timingType": "scheduled", "sectors": [ "banking", "payments" ], "appliesTo": "Financial entities subject to Banco de Portugal supervision in AML/CFT and within Instruction No. 8/2024.", "trigger": "Completion of the annual reference period from 1 January to 31 December of the previous year.", "deadline": "Annually · by 31 March of each year, reporting the preceding calendar year.", "recipient": "Banco de Portugal", "submission": "Submit through the Banco de Portugal reporting environment in accordance with Instruction No. 8/2024 and the current technical instructions.", "applicability": "Current annual-reporting model introduced by Instruction 8/2024.", "consequence": "Late, missing or deficient reporting may lead to supervisory/remedial or sanction action under the applicable Banco de Portugal/AML legal framework; no generic fixed fine is asserted.", "enforcement": "Banco de Portugal", "evidenceStatus": "verified-with-gap", "operationalImpact": "For in-scope entities this is a genuine calendar deadline and should be tracked annually with preparation beginning before year-end data closure.", "evidenceIds": [ "amlb:evidence:e91e4960", "amlb:evidence:5e716d55" ], "sourceEntityIds": [ "amlb:source-entity:1137112d" ] }, { "id": "PT-RISK-CONTROLS", "jurisdictionCode": "PT", "jurisdictionName": "Portugal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Institutional AML/CFT risk management and internal controls", "timingType": "ongoing", "sectors": [ "banking", "payments" ], "appliesTo": "Financial entities under the Portuguese AML law and Banco de Portugal sector framework, where Banco de Portugal is the competent supervisor.", "trigger": "Continuous activity and material changes to institutional, customer, product, channel and geographic risk.", "deadline": "Ongoing. Maintain risk assessment, internal controls and compliance arrangements; separate reporting requirements such as the RPB have their own deadlines.", "recipient": "Banco de Portugal for entities within its perimeter.", "submission": "Internal governance plus reporting/provision of information under the applicable supervisory instruments.", "applicability": "Current financial-sector AML/CFT control framework.", "consequence": "Deficiencies may trigger supervisory measures and sanction proceedings depending on the breached requirement.", "enforcement": "Banco de Portugal", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep risk assessment and internal controls current and ensure RPB responses are traceable back to operational evidence.", "evidenceIds": [ "amlb:evidence:5e716d55", "amlb:evidence:7c52ddad" ], "sourceEntityIds": [ "amlb:source-entity:1137112d", "amlb:source-entity:20e8de15" ] }, { "id": "AT-STR", "jurisdictionCode": "AT", "jurisdictionName": "Austria", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Suspicious transaction report to A-FIU", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities", "insurance" ], "appliesTo": "Obliged entities within the Finanzmarkt-Geldwäschegesetz (FM-GwG) and relevant financial-market perimeter.", "trigger": "Reasonable grounds / statutory facts creating an AML/CFT reporting obligation under §16 FM-GwG.", "deadline": "Without delay (unverzüglich) under the statutory reporting framework.", "recipient": "Austrian Financial Intelligence Unit / Geldwäschemeldestelle (A-FIU)", "submission": "Suspicious reports are filed through goAML via the Austrian Unternehmensserviceportal (USP).", "applicability": "Current FM-GwG reporting framework; A-FIU goAML guidance current May 2026.", "consequence": "Reporting failures can lead to administrative/supervisory consequences under the FM-GwG; sanction depends on the specific infringement.", "enforcement": "A-FIU receives reports; FMA and other competent authorities enforce obligations within their remit.", "evidenceStatus": "verified", "evidenceNote": "Current A-FIU page confirms goAML filing; FM-GwG anchors the reporting duty.", "operationalImpact": "Ensure designated staff have active USP/goAML access and escalation processes capable of immediate filing.", "evidenceIds": [ "amlb:evidence:79455982", "amlb:evidence:12e2c785" ], "sourceEntityIds": [ "amlb:source-entity:c806951e", "amlb:source-entity:0c8fa280" ] }, { "id": "AT-RISK", "jurisdictionCode": "AT", "jurisdictionName": "Austria", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Company-level ML/TF risk assessment", "timingType": "scheduled", "sectors": [ "banking", "payments", "securities", "insurance" ], "appliesTo": "Obliged entities under the FM-GwG.", "trigger": "Ongoing exposure to business, customer, product, transaction, delivery-channel and geographic ML/TF risks.", "deadline": "Maintain and update regularly; FMA risk-assessment guidance states records should be updated at least annually.", "recipient": "Financial Market Authority (FMA) for supervised entities.", "submission": "Maintain in documented form and provide to the FMA on request in a generally available electronic format.", "applicability": "Current statutory framework; FMA guidance version Feb 2022 remains the mapped interpretive source.", "consequence": "Failure to maintain an adequate documented risk assessment can lead to FMA supervisory/enforcement action and administrative fines under the FM-GwG.", "enforcement": "Financial Market Authority (FMA)", "evidenceStatus": "verified", "evidenceNote": "§4 duty and FMA “at least annually” update expectation are mapped directly.", "operationalImpact": "Put the annual risk-assessment refresh on the compliance calendar, while also updating earlier when material risk changes occur.", "evidenceIds": [ "amlb:evidence:3d88b614", "amlb:evidence:12e2c785" ], "sourceEntityIds": [ "amlb:source-entity:cb197dbd", "amlb:source-entity:0c8fa280" ] }, { "id": "CH-MROS", "jurisdictionCode": "CH", "jurisdictionName": "Switzerland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity report to MROS", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial intermediaries and traders subject to the Swiss Anti-Money Laundering Act (AMLA), within Article 9 scope.", "trigger": "Knowledge or reasonable grounds to suspect the statutory Article 9 circumstances.", "deadline": "Immediately (unverzüglich).", "recipient": "Money Laundering Reporting Office Switzerland (MROS)", "submission": "MROS requires STRs, attachments and additional information to be transmitted through goAML.", "applicability": "Current federal AMLA reporting duty; current MROS goAML route.", "consequence": "Non-compliance may lead to criminal, regulatory or supervisory consequences depending on the breached AMLA duty and supervised status.", "enforcement": "MROS / fedpol receives reports; FINMA, SROs and other competent authorities enforce relevant compliance duties.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain goAML readiness and escalation procedures so Article 9 reports can be filed immediately.", "evidenceIds": [ "amlb:evidence:2720361a", "amlb:evidence:1743c7c9" ], "sourceEntityIds": [ "amlb:source-entity:3b5a27d5", "amlb:source-entity:24c1be47" ] }, { "id": "CH-RISK", "jurisdictionCode": "CH", "jurisdictionName": "Switzerland", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Money-laundering risk analysis and risk-based controls", "timingType": "ongoing", "sectors": [ "banking", "payments", "securities", "insurance" ], "appliesTo": "FINMA-supervised institutions subject to the Anti-Money Laundering Ordinance-FINMA and related supervisory requirements.", "trigger": "Continuous exposure to ML/TF risks and changes in business model, customers, products, markets and controls.", "deadline": "Ongoing; maintain a documented risk analysis as a central strategic risk-management instrument. No universal external filing date is asserted.", "recipient": "Swiss Financial Market Supervisory Authority (FINMA)", "submission": "Maintain internally and provide/evidence in supervision as required.", "applicability": "Current FINMA supervisory framework.", "consequence": "Deficiencies may trigger FINMA supervisory/enforcement measures; consequences depend on the facts and breached rule.", "enforcement": "FINMA", "evidenceStatus": "verified", "evidenceNote": "FINMA explicitly describes the money-laundering risk analysis as a central instrument under its ordinance framework.", "operationalImpact": "Use the risk analysis to steer customer risk classification, controls, monitoring, resources and management reporting.", "evidenceIds": [ "amlb:evidence:aef54300", "amlb:evidence:d0737c5d" ], "sourceEntityIds": [ "amlb:source-entity:3b5a27d5" ] }, { "id": "LI-STR", "jurisdictionCode": "LI", "jurisdictionName": "Liechtenstein", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction report to SFIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons subject to the Due Diligence Act (SPG).", "trigger": "Statutory suspicion under Article 17 SPG and related due-diligence reporting circumstances.", "deadline": "Where an Article 17 report relates to a transaction, the SPG requires reporting before execution; if prior filing is impossible or would hinder prosecution, reporting may occur immediately after execution under the statutory exception.", "recipient": "Financial Intelligence Unit Liechtenstein (SFIU)", "submission": "Electronic suspicious reporting through the FIU goAML environment in accordance with current FIU guidance.", "applicability": "Current SPG reporting framework.", "consequence": "Failure to comply may result in administrative/criminal or supervisory consequences depending on the SPG provision and obliged person.", "enforcement": "SFIU receives reports; FMA and other competent authorities enforce relevant obligations.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation procedures should support pre-execution reporting where the law requires it and document any statutory exception used.", "evidenceIds": [ "amlb:evidence:61179ec9", "amlb:evidence:ac9dda0d" ], "sourceEntityIds": [ "amlb:source-entity:0a66a8df", "amlb:source-entity:bbfbab03" ] }, { "id": "LI-RISK-CONTROLS", "jurisdictionCode": "LI", "jurisdictionName": "Liechtenstein", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based due-diligence organisation and AML/CFT controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons subject to the SPG/SPV and sector supervision.", "trigger": "Continuous regulated/business activity and changing customer/business risk.", "deadline": "Ongoing. Risk-based due diligence, organisation, documentation and internal controls must be maintained; no universal periodic external filing date is asserted.", "recipient": "Financial Market Authority Liechtenstein (FMA) / other competent body according to the SPG perimeter.", "submission": "Maintain internally and provide to the competent authority in supervision as required.", "applicability": "Current Liechtenstein due-diligence framework.", "consequence": "Non-compliance may result in FMA measures and statutory sanctions; exact sanction depends on the breached SPG provision.", "enforcement": "FMA Liechtenstein / competent authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the documented AML/CFT organisation and risk controls aligned to actual customer and product exposure.", "evidenceIds": [ "amlb:evidence:61179ec9", "amlb:evidence:ac9dda0d" ], "sourceEntityIds": [ "amlb:source-entity:0a66a8df", "amlb:source-entity:bbfbab03" ] }, { "id": "EE-STR", "jurisdictionCode": "EE", "jurisdictionName": "Estonia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction report to Estonian FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under the Money Laundering and Terrorist Financing Prevention Act (MLTFPA).", "trigger": "Identification of activity/facts whose characteristics refer to criminal proceeds, terrorist financing or related suspicion under the Act.", "deadline": "Immediately, but no later than within two working days after identifying the activity/facts or the suspicion.", "recipient": "Estonian Financial Intelligence Unit (Rahapesu Andmebüroo)", "submission": "Use the FIU’s current electronic reporting environment and reporting instructions.", "applicability": "Current Estonian statutory reporting duty.", "consequence": "Failure to report or other breaches can lead to supervisory/administrative or criminal consequences according to the Act and competent authority.", "enforcement": "Estonian FIU and relevant supervisory authorities.", "evidenceStatus": "verified", "evidenceNote": "Official FIU guidance directly confirms the immediate / two-working-day outer limit.", "operationalImpact": "Escalation rules should treat two working days as the statutory outer boundary, not a target service level; genuinely urgent matters should be reported immediately.", "evidenceIds": [ "amlb:evidence:94edb70d", "amlb:evidence:899ea914" ], "sourceEntityIds": [ "amlb:source-entity:770e4c07", "amlb:source-entity:2e67255d" ] }, { "id": "EE-RISK-CONTROLS", "jurisdictionCode": "EE", "jurisdictionName": "Estonia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Enterprise ML/TF risk assessment and internal rules", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under the MLTFPA.", "trigger": "Establishment/continuation of in-scope activity and changes to business/customer/product/geographic risk.", "deadline": "Ongoing. Maintain a documented risk assessment and internal procedural rules appropriate to the nature, size and risk profile of the entity.", "recipient": "Relevant supervisory authority / Estonian FIU according to statutory competence.", "submission": "Maintain internally and submit/provide in supervision where required.", "applicability": "Current MLTFPA framework.", "consequence": "Deficiencies can lead to supervisory directions and statutory sanctions; exact amount depends on breach.", "enforcement": "Estonian FIU / sector supervisor as competent.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the enterprise risk assessment linked to internal procedures, customer risk models and transaction monitoring.", "evidenceIds": [ "amlb:evidence:899ea914", "amlb:evidence:94edb70d" ], "sourceEntityIds": [ "amlb:source-entity:2e67255d", "amlb:source-entity:770e4c07" ] }, { "id": "LV-STR", "jurisdictionCode": "LV", "jurisdictionName": "Latvia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report to FIU Latvia", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Subjects of the Latvian AML/CFT/PF Law.", "trigger": "Detection of a suspicious transaction/activity or other statutory circumstances requiring reporting to the FIU.", "deadline": "Immediately under the AML/CFT/PF Law once the statutory reporting condition is met.", "recipient": "Financial Intelligence Unit of Latvia (FIU Latvia)", "submission": "Electronic filing through goAML, which FIU Latvia uses for suspicious transaction/activity reports and other prescribed declarations.", "applicability": "Current Latvian AML/CFT/PF reporting framework.", "consequence": "Reporting failures can lead to supervisory and administrative sanctions; the amount depends on the relevant provision, obliged entity and competent supervisor.", "enforcement": "FIU Latvia receives reports; competent supervisory/control authorities enforce compliance.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain goAML access and escalation procedures capable of immediate submission when suspicion is established.", "evidenceIds": [ "amlb:evidence:afcba411", "amlb:evidence:0faa3ec4", "amlb:evidence:b06d8f63" ], "sourceEntityIds": [ "amlb:source-entity:8081d239", "amlb:source-entity:fcc408a2" ] }, { "id": "LV-ICS", "jurisdictionCode": "LV", "jurisdictionName": "Latvia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "ML/TF/PF risk assessment and internal control system", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Subjects of the Latvian AML/CFT/PF Law.", "trigger": "Continuous in-scope activity and changes in institutional/customer/product/geographic risk.", "deadline": "Ongoing. Establish, document and maintain an internal control system based on the entity’s risk assessment; no universal periodic external filing date is asserted.", "recipient": "Relevant supervisory/control authority under the Latvian AML/CFT/PF Law.", "submission": "Internal governance; provide documentation/information to the competent authority as required.", "applicability": "Current national AML/CFT/PF framework.", "consequence": "Control failures may trigger supervisory remediation and administrative sanctions under the law.", "enforcement": "Relevant competent supervisory/control authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the risk assessment and internal controls current, documented and traceable to customer/transaction risk treatment.", "evidenceIds": [ "amlb:evidence:afcba411", "amlb:evidence:0faa3ec4" ], "sourceEntityIds": [ "amlb:source-entity:8081d239", "amlb:source-entity:fcc408a2" ] }, { "id": "LT-STR", "jurisdictionCode": "LT", "jurisdictionName": "Lithuania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious monetary operation / transaction report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obliged entities under the Lithuanian AML/CFT Law.", "trigger": "Suspicious monetary operation/transaction or knowledge/suspicion that assets derive from criminal activity or relate to terrorist financing.", "deadline": "If the suspicious transaction is suspended: report no later than within 3 working hours from suspension. If it cannot be suspended: within 3 working hours from detection. The general Article 16(1) knowledge/suspicion notice is immediate and no later than one working day.", "recipient": "Financial Crime Investigation Service (FCIS/FNTT)", "submission": "Submit through the Service’s external information system / data submission portal via the Electronic Government Gateway.", "applicability": "Current procedure confirmed by FCIS FAQ updated 21 Jan 2026.", "consequence": "Failure to report can lead to administrative/supervisory or other statutory consequences. Exact AML reporting fine depends on the violated provision and enforcement route.", "enforcement": "Financial Crime Investigation Service (FCIS/FNTT) and other competent supervisors as applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Case-management tooling should time-stamp suspension/detection because the statutory clock can be measured in working hours, not days.", "evidenceIds": [ "amlb:evidence:46b71064", "amlb:evidence:74353d9b" ], "sourceEntityIds": [ "amlb:source-entity:32a7dfc0" ] }, { "id": "LT-CONTROLS", "jurisdictionCode": "LT", "jurisdictionName": "Lithuania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Internal AML/CFT policies, controls and risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obliged entities under the Lithuanian AML/CFT Law.", "trigger": "Continuous activity and changes in customer, product/service, transaction, geographic and institutional risk.", "deadline": "Ongoing. Article 29 requires appropriate internal policies and control procedures covering risk assessment/management, monitoring, reporting, sanctions implementation, training and governance.", "recipient": "FCIS/FNTT and competent sector supervisor.", "submission": "Maintain internally; supply to supervisory authorities under the applicable supervision framework.", "applicability": "Current duty confirmed by FCIS guidance in 2026.", "consequence": "Deficiencies can lead to supervisory and statutory sanctions depending on the institution and breach.", "enforcement": "FCIS/FNTT / relevant sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current FCIS FAQ expressly lists Article 29 internal-control requirements.", "operationalImpact": "Map internal policy ownership to the statutory control topics and ensure reporting procedures support the short STR deadlines.", "evidenceIds": [ "amlb:evidence:46b71064", "amlb:evidence:50fddb85" ], "sourceEntityIds": [ "amlb:source-entity:32a7dfc0", "amlb:source-entity:f048a2e7" ] }, { "id": "CZ-STR", "jurisdictionCode": "CZ", "jurisdictionName": "Czechia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report (STR) to FAÚ", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Act No. 253/2008 Coll.", "trigger": "Identification of a suspicious transaction under the AML Act.", "deadline": "Without unnecessary delay after detecting the suspicious transaction; where there is danger in delay, report immediately upon detection under the Act/guidance.", "recipient": "Financial Analytical Office (FAÚ)", "submission": "Use the current FAÚ electronic reporting tools/instructions for suspicious-transaction submissions.", "applicability": "Current consolidation effective 11 Jan 2026.", "consequence": "Failure to comply can lead to administrative sanctions under the AML Act; exact amount depends on the offence and obliged entity.", "enforcement": "Financial Analytical Office (FAÚ) / competent supervisory authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation procedures should be capable of immediate reporting where delay itself creates risk.", "evidenceIds": [ "amlb:evidence:0812b356", "amlb:evidence:77974dc7" ], "sourceEntityIds": [ "amlb:source-entity:a5b822d1" ] }, { "id": "CZ-RISK-CONTROLS", "jurisdictionCode": "CZ", "jurisdictionName": "Czechia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Institutional AML risk assessment and internal system of principles", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Act No. 253/2008, subject to the Act’s differentiated requirements by category and size.", "trigger": "Continuous in-scope activity and changes in ML/TF risk exposure.", "deadline": "Ongoing. Maintain the risk assessment and system of internal principles/procedures required by the AML Act; no universal external filing date is asserted.", "recipient": "FAÚ / relevant competent supervisor.", "submission": "Maintain and document internally; provide/submit to competent authority where the AML Act or supervisory process requires.", "applicability": "Current 11 Jan 2026 consolidation.", "consequence": "Deficiencies may trigger remediation and administrative penalties under the AML Act.", "enforcement": "FAÚ / relevant supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep risk assessment, internal procedures and escalation rules aligned; document updates after material changes.", "evidenceIds": [ "amlb:evidence:77974dc7", "amlb:evidence:45958836" ], "sourceEntityIds": [ "amlb:source-entity:a5b822d1" ] }, { "id": "SK-UTR", "jurisdictionCode": "SK", "jurisdictionName": "Slovakia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Unusual business transaction report to Slovak FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged persons under Act No. 297/2008 Coll.", "trigger": "Actual or attempted unusual business transaction meeting the statutory reporting condition.", "deadline": "Without undue delay. The Act allows reporting in person, in writing, electronically, or by telephone in urgent cases; an urgent telephone report must be followed by the required written/electronic form within the statutory follow-up period.", "recipient": "Financial Intelligence Unit of the Presidium of the Police Force", "submission": "Use the method permitted by Act 297/2008 and current FIU instructions; urgent telephone reporting is only the exceptional urgent route.", "applicability": "Current Slov-Lex consolidation dated 1 Jun 2026.", "consequence": "Breaches can result in administrative penalties and other consequences under Act 297/2008; amount depends on the specific breach.", "enforcement": "Financial Intelligence Unit / competent supervisory authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain escalation contacts and a documented fallback route for urgent reports so the reporting standard is met even if the normal electronic process is unavailable.", "evidenceIds": [ "amlb:evidence:1cfc44da", "amlb:evidence:fb1a3a13" ], "sourceEntityIds": [ "amlb:source-entity:ff7132c0", "amlb:source-entity:f572c898" ] }, { "id": "SK-AML-PROGRAMME", "jurisdictionCode": "SK", "jurisdictionName": "Slovakia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Own AML activity programme, risk assessment and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged persons under Act No. 297/2008.", "trigger": "Continuous activity and changes in ML/TF risk.", "deadline": "Ongoing. Maintain the statutory programme of own activity and risk-based internal procedures; no universal external filing date is asserted.", "recipient": "Relevant supervisory authority / Slovak FIU according to competence.", "submission": "Internal governance; provide documentation to the competent authority in supervision as required.", "applicability": "Current national framework.", "consequence": "Insufficient programme/controls may lead to administrative sanctions and corrective measures under the Act.", "enforcement": "Relevant supervisory authority / FIU.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain an auditable AML programme with risk assessment, customer controls, monitoring, reporting escalation and staff responsibilities.", "evidenceIds": [ "amlb:evidence:1cfc44da", "amlb:evidence:fb1a3a13" ], "sourceEntityIds": [ "amlb:source-entity:ff7132c0", "amlb:source-entity:f572c898" ] }, { "id": "SI-STR", "jurisdictionCode": "SI", "jurisdictionName": "Slovenia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report to OMLP", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under ZPPDFT-2.", "trigger": "Identification and assessment of unusual/suspicious activity or transaction giving rise to statutory ML/TF suspicion.", "deadline": "Report when the statutory suspicion test is met under ZPPDFT-2. Current official mapped material supports prompt reporting, but No universal numeric filing deadline is verified in mapped sources.", "recipient": "Office for Money Laundering Prevention (OMLP / UPPD)", "submission": "Use the OMLP’s current reporting process and prescribed data channel.", "applicability": "Current ZPPDFT-2 framework, including amendments.", "consequence": "Failure to report can result in statutory administrative/supervisory consequences; exact amount depends on breach and obliged entity.", "enforcement": "OMLP and relevant sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain transaction-monitoring and escalation procedures that route suspicion promptly to the reporting function and OMLP.", "evidenceIds": [ "amlb:evidence:28d97a70", "amlb:evidence:e617cb06" ], "sourceEntityIds": [ "amlb:source-entity:e8d597c8", "amlb:source-entity:459a0183" ] }, { "id": "SI-CASH-15K", "jurisdictionCode": "SI", "jurisdictionName": "Slovenia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Bank cash transaction report over EUR 15,000", "timingType": "event-driven", "sectors": [ "banking" ], "appliesTo": "Banks and savings banks within the ZPPDFT-2 obligation described by Banka Slovenije.", "trigger": "Execution of a cash transaction exceeding EUR 15,000.", "deadline": "As soon as executed, or within three days of execution.", "recipient": "Office for Money Laundering Prevention (OMLP)", "submission": "Report the prescribed information to OMLP using the current reporting process.", "applicability": "Current rule confirmed by Banka Slovenije.", "consequence": "Failure to make the prescribed cash-transaction report can lead to statutory supervisory/administrative sanctions; exact amount depends on the violation.", "enforcement": "OMLP / Banka Slovenije within respective competence.", "evidenceStatus": "verified", "evidenceNote": "Threshold, EUR 15,000 amount, recipient and three-day outer limit are explicitly confirmed by Banka Slovenije.", "operationalImpact": "Bank reporting systems should automatically identify qualifying cash transactions and generate the required OMLP data within the statutory window.", "evidenceIds": [ "amlb:evidence:72b6dd5d", "amlb:evidence:28d97a70" ], "sourceEntityIds": [ "amlb:source-entity:3db918e9", "amlb:source-entity:e8d597c8" ] }, { "id": "SI-MONITORING", "jurisdictionCode": "SI", "jurisdictionName": "Slovenia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Customer monitoring, unusual-transaction identification and risk controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under ZPPDFT-2.", "trigger": "Continuous business relationship/activity and changing ML/TF risks.", "deadline": "Ongoing. Monitor customer activity and identify unusual transactions; maintain preventive measures and risk controls. No universal external filing date is asserted.", "recipient": "Relevant supervisor / OMLP according to competence.", "submission": "Internal governance and monitoring; provide evidence in supervision as required.", "applicability": "Current national framework.", "consequence": "Deficiencies may lead to supervisory remediation and statutory sanctions.", "enforcement": "OMLP / relevant sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current Banka Slovenije guidance explicitly points to ZPPDFT-2 customer monitoring and unusual-transaction identification duties.", "operationalImpact": "Keep monitoring scenarios and customer risk assessment current and link them to the STR escalation process.", "evidenceIds": [ "amlb:evidence:72b6dd5d", "amlb:evidence:28d97a70" ], "sourceEntityIds": [ "amlb:source-entity:3db918e9", "amlb:source-entity:e8d597c8" ] }, { "id": "HR-STR", "jurisdictionCode": "HR", "jurisdictionName": "Croatia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report to the Anti-Money Laundering Office", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Banks and other reporting entities under the Croatian AML/CFT Act.", "trigger": "Suspicion of money laundering or terrorist financing in a cash or non-cash transaction, regardless of amount.", "deadline": "Notify the Anti-Money Laundering Office before execution of the suspicious transaction under the current official Ministry summary. Where law permits an exception to pre-execution filing, the exact timing must be followed from the current statutory/ordinance text.", "recipient": "Croatian Anti-Money Laundering Office (AMLO)", "submission": "Use the current AMLO reporting process prescribed by Croatian law and implementing rules.", "applicability": "Current Croatian AML/CFT framework.", "consequence": "Failure to report may lead to statutory administrative/supervisory consequences; exact fine depends on the breach and reporting entity.", "enforcement": "Anti-Money Laundering Office / competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation must occur early enough to permit pre-execution reporting where required; exception use should be documented.", "evidenceIds": [ "amlb:evidence:bb892e91", "amlb:evidence:6c4f85f6" ], "sourceEntityIds": [ "amlb:source-entity:5f012c5e", "amlb:source-entity:d9e7a6e0" ] }, { "id": "HR-RISK-CONTROLS", "jurisdictionCode": "HR", "jurisdictionName": "Croatia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Institutional AML/CFT risk analysis and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Croatian AML/CFT Act, with sector-specific supervision.", "trigger": "Continuous activity and changing ML/TF risks.", "deadline": "Ongoing. Maintain risk assessment, policies, procedures, controls, staff responsibilities and monitoring required by the national framework; no universal filing date is asserted.", "recipient": "Relevant sector supervisor and Anti-Money Laundering Office according to competence.", "submission": "Internal governance; evidence supplied during supervision/inspection as required.", "applicability": "Current national framework.", "consequence": "Deficiencies may lead to remediation, administrative fines and other supervisory measures depending on the breached provision.", "enforcement": "HNB / HANFA / other competent supervisor / AMLO as applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented risk-based control framework and keep evidence supporting monitoring and reporting decisions.", "evidenceIds": [ "amlb:evidence:6c4f85f6", "amlb:evidence:bfb8bc8e" ], "sourceEntityIds": [ "amlb:source-entity:d9e7a6e0", "amlb:source-entity:7068b7b1" ] }, { "id": "MT-STR", "jurisdictionCode": "MT", "jurisdictionName": "Malta", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction / Activity Report (STR/SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Subject persons under the Prevention of Money Laundering and Funding of Terrorism Regulations (PMLFTR).", "trigger": "Knowledge or suspicion of money laundering or funding of terrorism identified and considered to subsist by the MLRO/reporting function.", "deadline": "Promptly. FIAU guidance explains this operationally as submission on the same day when knowledge or suspicion is considered to subsist by the MLRO.", "recipient": "Financial Intelligence Analysis Unit (FIAU)", "submission": "All subject persons must register on goAML to submit suspicious activity/transaction reports.", "applicability": "Current Maltese reporting framework.", "consequence": "Late or missing reporting and related AML/CFT control failures may lead to FIAU administrative measures, penalties and remediation directives under the applicable framework.", "enforcement": "Financial Intelligence Analysis Unit (FIAU)", "evidenceStatus": "verified-with-gap", "operationalImpact": "MLRO processes should document the time suspicion is considered to subsist and support same-day goAML submission.", "evidenceIds": [ "amlb:evidence:2663fe91", "amlb:evidence:b707d7eb", "amlb:evidence:292cf10f" ], "sourceEntityIds": [ "amlb:source-entity:0bfdcb69", "amlb:source-entity:cd1831bc" ] }, { "id": "MT-CRA-CONTROLS", "jurisdictionCode": "MT", "jurisdictionName": "Malta", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Customer / business risk assessment and AML/CFT control framework", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Subject persons under the PMLFTR and FIAU Implementing Procedures.", "trigger": "Establishment/continuation of business relationships and changes in customer, product/service, delivery-channel, geographic or business-wide risk.", "deadline": "Ongoing. Maintain current risk assessments, policies, controls, internal reporting and monitoring; update when risk changes. No universal external filing date is asserted for the combined control obligation.", "recipient": "FIAU and relevant sector supervisor where applicable.", "submission": "Internal governance and documentation; provide information to FIAU/supervisor when required.", "applicability": "Current FIAU procedures, including April 2026 amendments.", "consequence": "Deficiencies may lead to FIAU remediation directives and administrative penalties; quantum depends on the breach and enforcement decision.", "enforcement": "FIAU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep customer and business risk assessments live and ensure controls, internal reporting and BO/CDD processes reflect the current risk profile.", "evidenceIds": [ "amlb:evidence:b707d7eb", "amlb:evidence:8ba2c6d7", "amlb:evidence:2e4fdacf", "amlb:evidence:292cf10f" ], "sourceEntityIds": [ "amlb:source-entity:0bfdcb69", "amlb:source-entity:cd1831bc" ] }, { "id": "CY-STR", "jurisdictionCode": "CY", "jurisdictionName": "Cyprus", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction / Activity Report to MOKAS", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Law 188(I)/2007 and sector AML directives.", "trigger": "Knowledge or suspicion of money laundering or terrorist financing under the statutory reporting provisions.", "deadline": "Immediately. The law requires suspicious transactions to be reported before execution where applicable; where it is impossible to refrain or doing so may frustrate investigation, the Unit must be informed immediately afterwards.", "recipient": "MOKAS / Unit for Combating Money Laundering", "submission": "Electronic submission through the MOKAS goAML reporting portal under current procedures.", "applicability": "Current Cyprus AML/CFT reporting framework.", "consequence": "Failure to report or comply with related AML obligations can lead to supervisory/administrative or criminal consequences depending on the provision and obliged entity.", "enforcement": "MOKAS receives reports; CySEC, Central Bank of Cyprus and other competent supervisors enforce sector obligations.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation should occur before execution where required and any post-execution exception should be documented with immediate MOKAS filing.", "evidenceIds": [ "amlb:evidence:dd6bc13c", "amlb:evidence:a549016c" ], "sourceEntityIds": [ "amlb:source-entity:8aaf8c47", "amlb:source-entity:c9c73e1b" ] }, { "id": "CY-RISK-CONTROLS", "jurisdictionCode": "CY", "jurisdictionName": "Cyprus", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT policies, controls and procedures", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Law 188(I)/2007, with sector-specific directives and supervisory expectations.", "trigger": "Continuous activity and changes in customer, product/service, transaction, delivery-channel and geographic risk.", "deadline": "Ongoing. Maintain adequate policies, controls and procedures proportionate to the nature and size of the obliged entity and its ML/TF risks; no universal external filing date is asserted.", "recipient": "Relevant supervisory authority, including CySEC for entities within its perimeter.", "submission": "Internal governance; provide evidence/information in supervision as required.", "applicability": "Current Cyprus framework.", "consequence": "Deficiencies can lead to supervisory directives, administrative sanctions and other legal consequences; amount depends on the breach and supervisor.", "enforcement": "CySEC / Central Bank of Cyprus / other competent supervisory authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain policies and controls proportionate to risk and integrate them with MOKAS reporting escalation.", "evidenceIds": [ "amlb:evidence:dd6bc13c", "amlb:evidence:a549016c" ], "sourceEntityIds": [ "amlb:source-entity:8aaf8c47", "amlb:source-entity:c9c73e1b" ] }, { "id": "AL-STR", "jurisdictionCode": "AL", "jurisdictionName": "Albania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities subject to Albania’s AML/CFT reporting regime, including the categories covered by FIA Instruction No. 3/2025.", "trigger": "Knowledge or suspicion that money laundering, terrorist financing, criminal proceeds or an attempted suspicious activity/transaction is involved.", "deadline": "Immediately and no later than 72 hours. Where the entity suspects the transaction itself, it must not execute it and must immediately request FIA instructions.", "recipient": "Financial Intelligence Agency (FIA)", "submission": "Electronically using the SAR/RAD reporting standard provided by FIA; official letter only where electronic reporting is objectively impossible.", "applicability": "Current framework; Instruction No. 3 dated 24 January 2025.", "consequence": "Failure to satisfy reporting duties is subject to the administrative/enforcement framework under Law No. 9917/2008. A single monetary amount is not asserted across all entity categories.", "enforcement": "Financial Intelligence Agency and the competent sector supervisor, as applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation procedures should allow analysis and filing within the outer 72-hour limit while treating “immediately” as the operative standard, not a target to wait for.", "evidenceIds": [ "amlb:evidence:018db44a", "amlb:evidence:17186763" ], "sourceEntityIds": [ "amlb:source-entity:e71a0d6d" ] }, { "id": "AL-CASH", "jurisdictionCode": "AL", "jurisdictionName": "Albania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash Transaction Report (CTR) · ALL 1,000,000+", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities within the scope of FIA Instruction No. 3/2025 and the applicable threshold-reporting rule.", "trigger": "A physical-cash transaction of at least ALL 1,000,000, including linked transactions within 24 hours, subject to the stated exemptions.", "deadline": "Within the next working day from execution.", "recipient": "Financial Intelligence Agency (FIA)", "submission": "Electronic CTR submission using the format/access provided by FIA.", "applicability": "Current threshold/reporting instruction verified 18 Aug 2026.", "consequence": "Failure to report threshold transactions is an administrative offence under the AML/CFT framework; sanction depends on the breached provision/entity.", "enforcement": "Financial Intelligence Agency / competent supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Build transaction aggregation capable of identifying linked cash activity over 24 hours and filing by the next working day.", "evidenceIds": [ "amlb:evidence:018db44a", "amlb:evidence:17186763" ], "sourceEntityIds": [ "amlb:source-entity:e71a0d6d" ] }, { "id": "AL-RISK", "jurisdictionCode": "AL", "jurisdictionName": "Albania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Documented ML/TF business risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the AML/CFT preventive framework.", "trigger": "Operating the business and changes to customer, product, channel or geographic risk.", "deadline": "Maintain a documented assessment and risk-based controls; no single universal filing date is asserted.", "recipient": "Competent supervisor / FIA within their statutory remit.", "submission": "Internal governance document; provide to authorities when required under the applicable framework.", "applicability": "Current risk-based framework.", "consequence": "Risk-assessment failures are specifically observed and sanctioned by FIA; exact amount depends on the legal breach and entity circumstances.", "enforcement": "FIA and competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current FIA law/instruction and enforcement reporting support the obligation.", "operationalImpact": "Keep the assessment live and management-owned; calendar controls should schedule review without implying that annual review alone is sufficient.", "evidenceIds": [ "amlb:evidence:17186763", "amlb:evidence:018db44a" ], "sourceEntityIds": [ "amlb:source-entity:e71a0d6d" ] }, { "id": "BY-SPECIAL-REPORT", "jurisdictionCode": "BY", "jurisdictionName": "Belarus", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT special-form reporting to the Financial Monitoring Department", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within Law No. 165-Z and applicable sector rules.", "trigger": "An operation/activity meets the statutory or implementing-rule criteria for information to be supplied to the financial-monitoring authority.", "deadline": "Event-driven. Exact current scenario-specific filing time is not verified in mapped sources.", "recipient": "Financial Monitoring Department (FMD), State Control Committee.", "submission": "Special-form/electronic reporting under the current national rules; current technical form requirements are maintained in National Bank/FMD instruments.", "applicability": "Current legal directory includes amendments and implementing instruments through 2025.", "consequence": "Failure to comply can trigger administrative/supervisory consequences under the AML/CFT and sector framework. No single fine is asserted here.", "enforcement": "FMD and the competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route reportable operations through the current FMD reporting procedure and maintain scenario-specific deadline rules in internal procedures.", "evidenceIds": [ "amlb:evidence:aa44c310", "amlb:evidence:78f5fe7f" ], "sourceEntityIds": [ "amlb:source-entity:65e37b8b", "amlb:source-entity:fa32a96e" ] }, { "id": "BY-RISK", "jurisdictionCode": "BY", "jurisdictionName": "Belarus", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk management and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under Law No. 165-Z and sector-specific supervision.", "trigger": "Ongoing regulated activity and changes in risk exposure.", "deadline": "Ongoing; review under the current risk-management framework. No single universal filing date is asserted.", "recipient": "Competent sector supervisor; FMD receives financial-intelligence reporting.", "submission": "Maintain internally and provide within supervisory processes as required.", "applicability": "National Bank directory lists the risk-management recommendations in a January 2025 edition.", "consequence": "Deficiencies may lead to supervisory/administrative action under the applicable sector and AML/CFT rules.", "enforcement": "Competent sector supervisor / FMD as applicable.", "evidenceStatus": "verified", "evidenceNote": "Current official legislative directory confirms the risk-management framework.", "operationalImpact": "Maintain risk assessment, controls and governance as standing obligations and update them when risk context changes.", "evidenceIds": [ "amlb:evidence:aa44c310", "amlb:evidence:b711a65d" ], "sourceEntityIds": [ "amlb:source-entity:65e37b8b", "amlb:source-entity:8449ff45" ] }, { "id": "BA-STR", "jurisdictionCode": "BA", "jurisdictionName": "Bosnia & Herzegovina", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged persons under the state AML/CFT Law 13/24.", "trigger": "Knowledge, information or suspicion relevant to money laundering, terrorist financing or proliferation-financing risk as defined by the law.", "deadline": "Immediately and before execution where possible. If prior reporting is objectively impossible, without delay and no later than the next working day after execution.", "recipient": "Financial Intelligence Department (FOO/FID), SIPA.", "submission": "Report through the procedure prescribed for the Financial Intelligence Department.", "applicability": "2026-08-18", "consequence": "Non-compliance is subject to the offence/sanction provisions of the state AML/CFT Law; amount depends on the specific breach and liable person.", "enforcement": "Financial Intelligence Department / competent supervisory authorities and courts as applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation must support pre-transaction reporting where possible and next-working-day reporting only for the statutory fallback scenario.", "evidenceIds": [ "amlb:evidence:aab1ec11", "amlb:evidence:91b15c6d" ], "sourceEntityIds": [ "amlb:source-entity:8ca75427", "amlb:source-entity:c1ba56ef" ] }, { "id": "BA-CASH", "jurisdictionCode": "BA", "jurisdictionName": "Bosnia & Herzegovina", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash / linked cash and specified high-risk transaction reporting · BAM 30,000+", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged persons within the statutory threshold-reporting scope, subject to exemptions/implementing rules.", "trigger": "Cash or linked cash transaction, and other transactions specified by the law, with value at least BAM 30,000.", "deadline": "Immediately after execution and no later than 3 days, subject to the statutory scope and 2026 implementing exemptions.", "recipient": "Financial Intelligence Department (FOO/FID), SIPA.", "submission": "Prescribed reporting channel to FOO/FID.", "applicability": "2026-08-18", "consequence": "Failure to comply is sanctionable under the AML/CFT Law; exact range depends on liable entity/person and breach.", "enforcement": "Competent AML/CFT supervisory/enforcement authorities.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure threshold aggregation and exceptions using the current implementing rule rather than treating every BAM 30,000 cash item identically.", "evidenceIds": [ "amlb:evidence:aab1ec11", "amlb:evidence:538ffd35" ], "sourceEntityIds": [ "amlb:source-entity:8ca75427" ] }, { "id": "BA-TRAINING", "jurisdictionCode": "BA", "jurisdictionName": "Bosnia & Herzegovina", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Annual AML/CFT employee training plan", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged persons with employees in roles relevant to AML/CFT.", "trigger": "Beginning of each calendar year / annual training governance cycle.", "deadline": "Prepare the annual professional education/training plan no later than the end of March for the current year; training itself is continuous/annual.", "recipient": "Internal governance; available to competent supervisor during oversight.", "submission": "Maintain the written plan and training evidence internally.", "applicability": "2026-08-18", "consequence": "Failure to maintain required governance/training may lead to supervisory and offence consequences under the Law.", "enforcement": "Competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Calendar an annual Q1 governance task and retain attendance/content evidence for supervisory review.", "evidenceIds": [ "amlb:evidence:aab1ec11" ], "sourceEntityIds": [ "amlb:source-entity:8ca75427" ] }, { "id": "BA-RISK", "jurisdictionCode": "BA", "jurisdictionName": "Bosnia & Herzegovina", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Obliged-entity ML/TF/PF risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged persons under Law 13/24.", "trigger": "Ongoing business activity and changes in customer, geography, product/service, transaction or delivery-channel risk.", "deadline": "Maintain and update a documented risk assessment; no single universal external filing date is asserted.", "recipient": "Competent sector supervisor.", "submission": "Internal governance document; provide during supervision as required.", "applicability": "2026-08-18", "consequence": "Deficiencies can attract supervisory/offence consequences under the Law.", "enforcement": "Competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Risk-assessment factors and control duties are explicit in the current law.", "operationalImpact": "Use the risk assessment to drive control intensity and update it when material risk drivers change.", "evidenceIds": [ "amlb:evidence:aab1ec11" ], "sourceEntityIds": [ "amlb:source-entity:8ca75427" ] }, { "id": "BG-STR", "jurisdictionCode": "BG", "jurisdictionName": "Bulgaria", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious operation / transaction notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons obliged under the Measures Against Money Laundering Act.", "trigger": "Suspicion of money laundering or criminal proceeds in relation to an operation/transaction.", "deadline": "Notify FID-SANS immediately before carrying out the operation/transaction and delay where legally permissible; if delay is objectively impossible or would frustrate action, notify immediately after execution.", "recipient": "Financial Intelligence Directorate, State Agency for National Security (FID-SANS).", "submission": "Through the reporting procedure prescribed by FID-SANS/current implementing rules.", "applicability": "2026-08-18", "consequence": "Breaches are subject to the Act’s administrative-penalty framework, with different ranges for responsible persons and obliged entities and enhanced treatment for serious/systematic violations.", "enforcement": "FID-SANS and competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Design pre-execution escalation for suspicious activity, with immediate post-transaction reporting only where the statutory fallback applies.", "evidenceIds": [ "amlb:evidence:b2d41303" ], "sourceEntityIds": [ "amlb:source-entity:fdb59ed3" ] }, { "id": "BG-RISK", "jurisdictionCode": "BG", "jurisdictionName": "Bulgaria", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Enterprise ML/TF risk assessment and internal rules", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged persons under MAMLA.", "trigger": "Ongoing activity and changes affecting ML/TF risk.", "deadline": "Maintain/update risk assessment and internal control rules under the risk-based framework; no universal external filing date is asserted.", "recipient": "Competent supervisor / FID-SANS within their remit.", "submission": "Internal governance; supervisory production as required.", "applicability": "2026-08-18", "consequence": "Failure to maintain required controls may trigger administrative and supervisory sanctions; amount depends on breach and entity.", "enforcement": "Competent AML/CFT supervisor / FID-SANS.", "evidenceStatus": "verified", "evidenceNote": "Current consolidated MAMLA is the primary source.", "operationalImpact": "Treat risk assessment and internal rules as living controls with change-triggered review.", "evidenceIds": [ "amlb:evidence:b2d41303" ], "sourceEntityIds": [ "amlb:source-entity:fdb59ed3" ] }, { "id": "GI-SAR", "jurisdictionCode": "GI", "jurisdictionName": "Gibraltar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Relevant persons/businesses within Gibraltar’s AML/CFT reporting framework.", "trigger": "Knowledge, suspicion or reasonable grounds meeting the statutory disclosure/reporting threshold.", "deadline": "Event-driven; report promptly under the applicable statutory process. A single cross-sector numeric deadline is not asserted.", "recipient": "Gibraltar Financial Intelligence Unit (GFIU).", "submission": "Use the current GFIU reporting process; universal cross-sector technical channel is retained as a verification gap in this record.", "applicability": "2026-08-18", "consequence": "Failure to disclose/report where the statutory conditions are met may carry criminal and/or regulatory consequences. Exact offence/penalty depends on the provision and sector.", "enforcement": "GFIU / Royal Gibraltar Police and relevant AML/CFT supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and current GFIU filing instructions by sector.", "evidenceIds": [ "amlb:evidence:6b41882a", "amlb:evidence:d6ee203d" ], "sourceEntityIds": [ "amlb:source-entity:25783e92", "amlb:source-entity:c7410f70" ] }, { "id": "GI-RISK", "jurisdictionCode": "GI", "jurisdictionName": "Gibraltar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business-wide AML/CFT risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Relevant regulated/obliged businesses under POCA and sector rules.", "trigger": "Ongoing business activity and material changes in risk exposure.", "deadline": "Ongoing; maintain risk-based systems and controls. No single universal filing date is asserted.", "recipient": "Relevant AML/CFT supervisory authority.", "submission": "Internal governance; provide during supervision as required.", "applicability": "2026-08-18", "consequence": "Control failures can trigger supervisory and statutory enforcement depending on sector and breach.", "enforcement": "Relevant AML/CFT supervisor / competent authority.", "evidenceStatus": "verified", "evidenceNote": "Current consolidated POCA and government financial-crime framework support the standing obligation.", "operationalImpact": "Keep the business risk assessment aligned with customers, services, geography and delivery channels and link it to control design.", "evidenceIds": [ "amlb:evidence:6b41882a", "amlb:evidence:d6ee203d" ], "sourceEntityIds": [ "amlb:source-entity:25783e92", "amlb:source-entity:c7410f70" ] }, { "id": "GR-STR", "jurisdictionCode": "GR", "jurisdictionName": "Greece", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Law 4557/2018.", "trigger": "Knowledge, serious indication or suspicion of money laundering or terrorist financing, including attempted transactions.", "deadline": "Without delay.", "recipient": "Hellenic Financial Intelligence Unit.", "submission": "Electronic reporting through the Hellenic FIU procedure applicable to the reporting entity.", "applicability": "2026-08-18", "consequence": "Failure to report and related preventive-control breaches may lead to administrative/criminal consequences under the statute and sector rules; exact amount depends on the breach.", "enforcement": "Hellenic FIU and competent supervisory authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation should be designed around immediate FIU reporting once the statutory suspicion threshold is met.", "evidenceIds": [ "amlb:evidence:2938db3c" ], "sourceEntityIds": [ "amlb:source-entity:6d8f265e" ] }, { "id": "GR-RISK", "jurisdictionCode": "GR", "jurisdictionName": "Greece", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk assessment, policies and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Law 4557/2018.", "trigger": "Ongoing activity and material changes in risk.", "deadline": "Ongoing; maintain risk-based policies, controls and procedures. No single universal external filing date is asserted.", "recipient": "Competent sector supervisor.", "submission": "Internal governance; provide within supervisory process as required.", "applicability": "2026-08-18", "consequence": "Deficiencies can attract supervisory/administrative measures under the applicable AML/CFT and sector regime.", "enforcement": "Competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current official legal framework supports risk-based internal governance requirements.", "operationalImpact": "Tie review cadence to material risk changes rather than treating the control as a static annual document.", "evidenceIds": [ "amlb:evidence:2938db3c" ], "sourceEntityIds": [ "amlb:source-entity:6d8f265e" ] }, { "id": "GG-SAR", "jurisdictionCode": "GG", "jurisdictionName": "Guernsey", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity disclosure / report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Specified businesses and relevant employees under the Bailiwick AML/CFT/CPF framework.", "trigger": "Knowledge or suspicion requiring disclosure under the Disclosure Law / Terrorism Law and the business’s reporting procedures.", "deadline": "Event-driven; internal reports must reach the MLRO/nominated officer promptly and external disclosure follows the statutory FIU process. No universal numeric deadline is asserted.", "recipient": "Bailiwick Financial Intelligence Unit.", "submission": "Current FIU disclosure procedure; exact technical portal mechanics are not verified in mapped sources.", "applicability": "2026-08-18", "consequence": "Failure to make required disclosures can expose persons/businesses to criminal, regulatory and enforcement consequences.", "enforcement": "Bailiwick law enforcement / FIU and GFSC for regulated businesses.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Ensure staff-to-MLRO escalation and MLRO-to-FIU workflows are documented, prompt and auditable.", "evidenceIds": [ "amlb:evidence:add2e919", "amlb:evidence:6e0aa82e" ], "sourceEntityIds": [ "amlb:source-entity:c3be4fe4", "amlb:source-entity:2f992114" ] }, { "id": "GG-BRA", "jurisdictionCode": "GG", "jurisdictionName": "Guernsey", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business risk assessment and risk-based controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Specified businesses within the GFSC AML/CFT/CPF framework.", "trigger": "Ongoing operation and material changes in business/customer/product/geographic risk.", "deadline": "Maintain a current business risk assessment and proportionate policies/controls; no annual cadence is verified where the Handbook requires change-responsive maintenance.", "recipient": "Guernsey Financial Services Commission for regulated businesses / other competent authority as applicable.", "submission": "Internal governance; evidence available to supervisor during oversight.", "applicability": "2026-08-18", "consequence": "Weaknesses may lead to supervisory remediation, enforcement and, depending on breach, statutory consequences.", "enforcement": "GFSC / competent authority.", "evidenceStatus": "verified", "evidenceNote": "Current GFSC Handbook is the controlling supervisory source.", "operationalImpact": "Use business-risk assessment outputs to calibrate CDD, monitoring, governance and resource allocation.", "evidenceIds": [ "amlb:evidence:add2e919" ], "sourceEntityIds": [ "amlb:source-entity:c3be4fe4" ] }, { "id": "HU-STR", "jurisdictionCode": "HU", "jurisdictionName": "Hungary", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicion escalation and FIU reporting chain", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Service providers subject to Act LIII of 2017; record reflects the statutory internal-to-FIU reporting chain.", "trigger": "Facts, data or circumstances indicating money laundering, terrorist financing or criminal proceeds.", "deadline": "Immediate internal report to the designated person; external FIU handling follows the statutory reporting procedure. A universal portal/timestamp is not restated without current channel evidence.", "recipient": "Designated person / Hungarian FIU reporting chain (NAV).", "submission": "Internal immediate escalation; external submission under the current FIU procedure.", "applicability": "2026-08-18", "consequence": "Failure to operate/report under the AML/CFT framework can lead to supervisory and administrative measures; exact sanction depends on entity and breach.", "enforcement": "Hungarian FIU / competent sector supervisor, including MNB where applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the internal escalation path short enough that the designated person can complete the external FIU decision without avoidable delay.", "evidenceIds": [ "amlb:evidence:1f914388" ], "sourceEntityIds": [ "amlb:source-entity:4ff4c612" ] }, { "id": "HU-BRA-ANNUAL", "jurisdictionCode": "HU", "jurisdictionName": "Hungary", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Annual business-wide ML/TF risk-assessment update", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Service providers supervised by the Magyar Nemzeti Bank and within MNB Decree 30/2024.", "trigger": "Each calendar year, plus unscheduled review triggers.", "deadline": "Set a date in each calendar year when the business-wide risk assessment update is performed; conduct unscheduled review when specified changes arise.", "recipient": "Magyar Nemzeti Bank (supervisory oversight).", "submission": "Maintain internally; provide during supervision as required.", "applicability": "2026-08-18", "consequence": "Failure to maintain current risk governance can lead to MNB supervisory/enforcement measures under the AML/CFT framework.", "enforcement": "Magyar Nemzeti Bank.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Put the annual update date on the compliance calendar, but retain event-driven review triggers between annual cycles.", "evidenceIds": [ "amlb:evidence:56aed1d7", "amlb:evidence:1f914388" ], "sourceEntityIds": [ "amlb:source-entity:4ff4c612" ] }, { "id": "IM-SAR", "jurisdictionCode": "IM", "jurisdictionName": "Isle of Man", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious activity report to the Isle of Man FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Relevant persons/businesses under the Proceeds of Crime Act, Anti-Terrorism and Crime Act and AML/CFT Code.", "trigger": "Knowledge or suspicion meeting the statutory disclosure threshold.", "deadline": "Event-driven; report when the statutory suspicion threshold is met. No universal numeric deadline is asserted.", "recipient": "Isle of Man Financial Intelligence Unit (IOMFIU).", "submission": "Themis secure online reporting system.", "applicability": "2026-08-18", "consequence": "Failure to disclose where required can constitute an offence under POCA/ATCA; regulated entities may also face supervisory consequences.", "enforcement": "IOMFIU / law enforcement and Isle of Man Financial Services Authority for regulated entities.", "evidenceStatus": "verified", "evidenceNote": "Current official guidance confirms Themis and the statutory reporting framework.", "operationalImpact": "Maintain prompt employee-to-MLRO and MLRO-to-Themis escalation with auditable decision records.", "evidenceIds": [ "amlb:evidence:35004852", "amlb:evidence:7cf58c4f", "amlb:evidence:d475d66d" ], "sourceEntityIds": [ "amlb:source-entity:0c34c03c", "amlb:source-entity:074e0bae" ] }, { "id": "IM-BRA", "jurisdictionCode": "IM", "jurisdictionName": "Isle of Man", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Business risk assessment and AML/CFT controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Relevant businesses subject to the AML/CFT Code 2019.", "trigger": "Ongoing business activity and material risk changes.", "deadline": "Ongoing; maintain and update business/customer risk assessments and required controls. No single universal external filing date is asserted.", "recipient": "IOMFSA / relevant designated-body supervisor.", "submission": "Internal governance; provide to supervisor when required.", "applicability": "2026-08-18", "consequence": "Non-compliance may lead to supervisory action and, depending on the breached Code/statutory duty, criminal or administrative consequences.", "enforcement": "IOMFSA / relevant competent authority.", "evidenceStatus": "verified", "evidenceNote": "Current Code/guidance supports standing risk-based control obligations.", "operationalImpact": "Review the business risk assessment on material change and use it to calibrate CDD, monitoring, training and governance.", "evidenceIds": [ "amlb:evidence:35004852", "amlb:evidence:7cf58c4f" ], "sourceEntityIds": [ "amlb:source-entity:0c34c03c" ] }, { "id": "IM-SNPO-CFT", "jurisdictionCode": "IM", "jurisdictionName": "Isle of Man", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Specified non-profit organisation CFT controls under the 2026 Code", "timingType": "ongoing", "sectors": [ "non-profit-organisations" ], "appliesTo": "Organisations within the statutory definition of a Specified Non-Profit Organisation (SNPO) under the Isle of Man framework.", "trigger": "Ongoing while the organisation is within SNPO scope.", "deadline": "Ongoing from 1 September 2026. The Code applies risk-based CFT requirements rather than one universal periodic filing deadline.", "recipient": "Isle of Man Financial Services Authority / competent authority under the SNPO framework.", "submission": "Maintain and operate the required risk-based CFT measures and provide information through the applicable supervisory process.", "applicability": "1 September 2026.", "consequence": "Non-compliance is subject to the applicable statutory and supervisory framework; no single universal penalty amount is asserted here.", "enforcement": "Isle of Man Financial Services Authority / Department of Home Affairs as applicable.", "evidenceStatus": "verified", "evidenceNote": "The official consultation outcome confirms that the 2026 Code was made, takes effect on 1 September 2026 and replaces the 2019 Code.", "operationalImpact": "SNPOs should review their CFT risk assessment, policies and procedures against the revised 2026 Code and document implementation from its effective date.", "evidenceIds": [ "amlb:evidence:236c1a9f" ], "sourceEntityIds": [ "amlb:source-entity:0c34c03c" ] }, { "id": "IT-SOS", "jurisdictionCode": "IT", "jurisdictionName": "Italy", "coverageStatus": "verified", "lastReviewedDate": "2026-10-01", "title": "Segnalazione di operazione sospetta (SOS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Legislative Decree 231/2007.", "trigger": "Grounds to know, suspect or reasonably suspect ML/TF based on customer/activity information and indicators.", "deadline": "Without delay and, where possible, before executing the operation.", "recipient": "Unità di Informazione Finanziaria per l’Italia (UIF).", "submission": "Current UIF electronic reporting procedure for the applicable reporting category.", "applicability": "2026-08-18", "consequence": "Failure to comply may attract the administrative/sanction framework of Legislative Decree 231/2007 and sector supervisory action; exact amount depends on the breach.", "enforcement": "UIF / competent supervisory and enforcement authorities.", "evidenceStatus": "verified", "evidenceNote": "UIF’s current SOS page states the without-delay / pre-execution rule.", "operationalImpact": "Escalation and transaction-handling procedures should support filing before execution where practicable, without tipping off the customer.", "evidenceIds": [ "amlb:evidence:8882b67a" ], "sourceEntityIds": [ "amlb:source-entity:5b48614c" ] }, { "id": "IT-OGG-CASH", "jurisdictionCode": "IT", "jurisdictionName": "Italy", "coverageStatus": "verified", "lastReviewedDate": "2026-10-01", "title": "Monthly objective cash communications (comunicazioni oggettive)", "timingType": "scheduled", "sectors": [ "banking", "payments" ], "appliesTo": "Banks, Poste Italiane, payment institutions, electronic-money institutions and other entities within the UIF objective-communication scope.", "trigger": "Monthly cash activity meeting the UIF threshold/aggregation rules, including aggregate cash operations of at least EUR 10,000 with relevant component transactions.", "deadline": "Monthly; submit by the 15th day of the second month following the observation month.", "recipient": "Unità di Informazione Finanziaria per l’Italia (UIF).", "submission": "XML file transmitted electronically through Infostat-UIF.", "applicability": "Existing monthly filing rule; UIF FAQ/reporting-procedure clarifications apply to operations accounted from 1 January 2027, with the first affected submission due 15 March 2027.", "consequence": "Late/missing objective communications can lead to the applicable AML reporting/enforcement consequences; the record does not generalise a single fine without breach-specific provision mapping.", "enforcement": "UIF / competent supervisory authority.", "evidenceStatus": "verified", "evidenceNote": "UIF’s 29 September 2026 communication requires reporting-procedure changes for objective communications concerning transactions accounted from 1 January 2027; the first affected monthly submission must be transmitted by 15 March 2027.", "operationalImpact": "Before January 2027 accounting data enters the reporting pipeline, align operation-location fields, exclude “virtual cash” without actual cash movement, and add controls for classification/extraction anomalies and unusually high reported amounts; retain the standing 15th-of-second-month filing schedule.", "evidenceIds": [ "amlb:evidence:0e3df991", "amlb:evidence:b2a8d0ce" ], "sourceEntityIds": [ "amlb:source-entity:5b48614c" ] }, { "id": "IT-SARA", "jurisdictionCode": "IT", "jurisdictionName": "Italy", "coverageStatus": "verified", "lastReviewedDate": "2026-10-01", "title": "Monthly SARA aggregate AML reporting", "timingType": "scheduled", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Intermediaries/entities within the SARA reporting perimeter.", "trigger": "End of each reference month for reportable aggregate AML data.", "deadline": "Monthly; must reach UIF no later than the second day of the third month following the reference month; next working day if that day is a holiday.", "recipient": "Unità di Informazione Finanziaria per l’Italia (UIF).", "submission": "Electronic submission through Infostat-UIF.", "applicability": "2026-08-18", "consequence": "Failure or delay may attract the applicable AML reporting/supervisory consequences; exact sanction depends on the entity and breached rule.", "enforcement": "UIF / competent prudential or sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a recurring data-quality and sign-off timetable well before the statutory SARA deadline.", "evidenceIds": [ "amlb:evidence:a16ace26" ], "sourceEntityIds": [ "amlb:source-entity:5b48614c" ] }, { "id": "JE-SAR", "jurisdictionCode": "JE", "jurisdictionName": "Jersey", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity disclosure to the Jersey FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Relevant persons/businesses and MLRO/nominated officer under Jersey’s AML/CFT regime.", "trigger": "Knowledge or suspicion triggering a disclosure under the applicable proceeds-of-crime / terrorism framework.", "deadline": "As soon as practicable.", "recipient": "Jersey Financial Intelligence Unit.", "submission": "Approved form / current FIU reporting procedure.", "applicability": "2026-08-18", "consequence": "Failure to make a required disclosure may constitute an offence and regulated businesses may face supervisory enforcement.", "enforcement": "Jersey FIU / law enforcement and Jersey Financial Services Commission where applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the MLRO decision path sufficiently prompt to satisfy “as soon as practicable” and retain decision evidence.", "evidenceIds": [ "amlb:evidence:3c25200c", "amlb:evidence:c8e17b09" ], "sourceEntityIds": [ "amlb:source-entity:c613b82c" ] }, { "id": "JE-CONTROLS", "jurisdictionCode": "JE", "jurisdictionName": "Jersey", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT systems, controls, monitoring and training", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Relevant persons/businesses within the Money Laundering Order.", "trigger": "Ongoing business activity.", "deadline": "Ongoing; maintain the prescribed systems, controls, recordkeeping and staff/MLRO arrangements. No universal periodic filing date is asserted.", "recipient": "Jersey Financial Services Commission / relevant competent authority.", "submission": "Internal governance; produce during supervision as required.", "applicability": "2026-08-18", "consequence": "Deficiencies can lead to regulatory remediation/enforcement and, for statutory breaches, offence consequences.", "enforcement": "JFSC / competent authority.", "evidenceStatus": "verified", "evidenceNote": "Current Money Laundering Order is the operative primary rule.", "operationalImpact": "Operate AML/CFT controls as continuous governance with documented testing, training and monitoring not only calendar filings.", "evidenceIds": [ "amlb:evidence:3c25200c" ], "sourceEntityIds": [ "amlb:source-entity:c613b82c" ] }, { "id": "XK-FI-STR", "jurisdictionCode": "XK", "jurisdictionName": "Kosovo", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Financial-institution suspicious transaction report", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Banks and financial institutions within the Central Bank of Kosovo AML/CFT regulation.", "trigger": "An act or transaction is identified as suspicious.", "deadline": "Within 24 hours from identification as suspicious.", "recipient": "Financial Intelligence Unit of Kosovo (FIU-K).", "submission": "Current FIU reporting route prescribed by the AML/CFT framework.", "applicability": "2026-08-18", "consequence": "Failure to report can lead to AML/CFT and prudential supervisory sanctions; exact penalty depends on the breach/entity.", "enforcement": "FIU-K and Central Bank of Kosovo.", "evidenceStatus": "verified", "evidenceNote": "The current CBK regulation provides the 24-hour requirement for financial institutions.", "operationalImpact": "Configure case escalation and MLRO review so a final report can be transmitted inside the 24-hour sector deadline.", "evidenceIds": [ "amlb:evidence:6d28da1e" ], "sourceEntityIds": [ "amlb:source-entity:0553a837" ] }, { "id": "XK-FI-RISK", "jurisdictionCode": "XK", "jurisdictionName": "Kosovo", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Financial-institution AML/CFT risk assessment and control framework", "timingType": "ongoing", "sectors": [ "banking", "payments" ], "appliesTo": "CBK-supervised financial institutions.", "trigger": "Ongoing regulated activity and changes in customer/product/geographic/channel risk.", "deadline": "Ongoing; maintain and update the institution-level risk assessment and associated controls.", "recipient": "Central Bank of Kosovo.", "submission": "Internal governance; available through CBK supervisory process.", "applicability": "2026-08-18", "consequence": "Deficiencies can lead to CBK supervisory/enforcement measures under banking/financial and AML/CFT rules.", "enforcement": "Central Bank of Kosovo.", "evidenceStatus": "verified", "evidenceNote": "Current CBK AML/CFT regulation is the sector-specific supervisory source.", "operationalImpact": "Use the institutional risk assessment to calibrate CDD, monitoring, staffing, testing and escalation controls.", "evidenceIds": [ "amlb:evidence:6d28da1e" ], "sourceEntityIds": [ "amlb:source-entity:0553a837" ] }, { "id": "MD-STR", "jurisdictionCode": "MD", "jurisdictionName": "Moldova", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction special-form reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Law No. 308/2017.", "trigger": "Activity/transaction meets the suspicion criteria under the AML/CFT law and current SPCSB guidance.", "deadline": "Event-driven. Exact current scenario-specific filing time is not verified in mapped sources unless verified in current mapped sources.", "recipient": "Office for Prevention and Fight against Money Laundering (SPCSB).", "submission": "Special-form submission under the SPCSB methodology for completing and submitting reports.", "applicability": "2026-08-18", "consequence": "Non-compliance may be sanctioned under Law No. 75/2020 and the applicable AML/CFT supervision framework; exact penalty depends on the violation.", "enforcement": "SPCSB and competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep current SPCSB form specifications embedded in reporting procedures and treat the filing as event-driven.", "evidenceIds": [ "amlb:evidence:431b03bb" ], "sourceEntityIds": [ "amlb:source-entity:71d22853" ] }, { "id": "MD-RISK", "jurisdictionCode": "MD", "jurisdictionName": "Moldova", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "ML/TF risk assessment and AML/CFT controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Law No. 308/2017 and current SPCSB sector requirements.", "trigger": "Ongoing activity and changes in risk profile.", "deadline": "Ongoing; maintain risk assessment, policies and controls under the current SPCSB risk-based framework.", "recipient": "SPCSB / competent supervisor.", "submission": "Internal governance; provide in supervisory process as required.", "applicability": "2026-08-18", "consequence": "Failure may result in administrative/supervisory sanctions under Law No. 75/2020 and applicable sector law.", "enforcement": "SPCSB / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The current SPCSB legislative directory lists both the core law and 2023/2024 risk-control requirements.", "operationalImpact": "Maintain a living business risk assessment and map control changes to material shifts in risk.", "evidenceIds": [ "amlb:evidence:431b03bb" ], "sourceEntityIds": [ "amlb:source-entity:71d22853" ] }, { "id": "MC-STR", "jurisdictionCode": "MC", "jurisdictionName": "Monaco", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon via goAML", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged persons within Monaco’s AML/CFT reporting regime.", "trigger": "Suspicion meeting the statutory/AMSF reporting threshold.", "deadline": "Without delay, as soon as the suspicion arises.", "recipient": "Autorité Monégasque de Sécurité Financière (AMSF) · financial intelligence function.", "submission": "goAML.", "applicability": "2026-08-18", "consequence": "Failure to report can lead to administrative, regulatory and/or criminal consequences depending on the breached duty and entity.", "enforcement": "AMSF and competent judicial/enforcement authorities.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation should be built around immediate goAML readiness once suspicion is established.", "evidenceIds": [ "amlb:evidence:92d2268a", "amlb:evidence:a88ae7e5" ], "sourceEntityIds": [ "amlb:source-entity:ad9848d4" ] }, { "id": "MC-RISK", "jurisdictionCode": "MC", "jurisdictionName": "Monaco", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Documented ML/TF risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Monaco’s preventive AML/CFT framework.", "trigger": "Ongoing activity and material changes to risk exposure.", "deadline": "Ongoing; keep risk assessment and risk-based controls current. No universal external filing date is asserted.", "recipient": "AMSF / competent supervisory authority.", "submission": "Internal governance; supervisory production as required.", "applicability": "2026-08-18", "consequence": "Deficiencies may lead to AMSF supervisory or administrative action; precise sanction depends on entity/breach.", "enforcement": "AMSF.", "evidenceStatus": "verified", "evidenceNote": "Current AMSF guidance and supervisory framework support risk-based controls.", "operationalImpact": "Use the risk assessment to calibrate CDD, monitoring, governance and reporting escalation.", "evidenceIds": [ "amlb:evidence:a88ae7e5" ], "sourceEntityIds": [ "amlb:source-entity:ad9848d4" ] }, { "id": "PL-STR", "jurisdictionCode": "PL", "jurisdictionName": "Poland", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Suspicious circumstance / transaction notification to GIFI", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged institutions under Poland’s AML Act.", "trigger": "Suspicious circumstances or reasonable suspicion falling under the relevant AML Act reporting provisions.", "deadline": "Immediately.", "recipient": "General Inspector of Financial Information (GIFI/GIIF).", "submission": "Only through the GIFI IT System under the current official communication.", "applicability": "2026-08-18", "consequence": "Failure to report may attract administrative penalties under the AML Act and, depending on conduct, criminal consequences. Exact amount is breach-specific.", "enforcement": "General Inspector of Financial Information and competent sector supervisor / enforcement authority.", "evidenceStatus": "verified", "evidenceNote": "Current Ministry/GIFI communication states immediate notification and exclusive IT-system submission.", "operationalImpact": "Ensure MLRO escalation and system access are resilient enough for immediate electronic filing.", "evidenceIds": [ "amlb:evidence:de412369", "amlb:evidence:597dfb32" ], "sourceEntityIds": [ "amlb:source-entity:e09c9824" ] }, { "id": "PL-RISK", "jurisdictionCode": "PL", "jurisdictionName": "Poland", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Institutional ML/TF risk assessment and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged institutions under the Polish AML Act.", "trigger": "Ongoing activity and material changes in ML/TF risk.", "deadline": "Maintain/update the institutional risk assessment and risk-based controls; no single universal filing date is asserted.", "recipient": "Competent AML/CFT supervisor / GIFI within their remit.", "submission": "Internal governance; provide during supervision as required.", "applicability": "2026-08-18", "consequence": "Deficiencies may attract AML Act administrative penalties and sector supervisory measures.", "enforcement": "GIFI / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current Ministry/GIFI framework supports the standing risk-based obligation.", "operationalImpact": "Review risk assessment and internal procedure when products, customers, geography, delivery channels or external threats materially change.", "evidenceIds": [ "amlb:evidence:de412369" ], "sourceEntityIds": [ "amlb:source-entity:e09c9824" ] }, { "id": "RO-STR", "jurisdictionCode": "RO", "jurisdictionName": "Romania", "coverageStatus": "verified", "lastReviewedDate": "2026-10-06", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Law No. 129/2019.", "trigger": "Suspicion criteria under Article 6 and related AML/CFT rules.", "deadline": "Event-driven under Article 6. A single numeric cross-scenario deadline is not asserted in this record without article-level verification.", "recipient": "National Office for Prevention and Control of Money Laundering (ONPCSB).", "submission": "Electronic-only through ONPCSB channels / SETD reporting environment under the current reporting orders.", "applicability": "2026-08-18", "consequence": "Failure to submit required reports may constitute an administrative offence and can attract supervisory/enforcement action; exact fine depends on the violated provision/entity.", "enforcement": "ONPCSB and competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain separate workflow rules for suspicious and threshold reports; do not reuse the three-day objective-report deadline for STRs.", "evidenceIds": [ "amlb:evidence:8c051b2f", "amlb:evidence:9a08c615", "amlb:evidence:d3d4b1e0" ], "sourceEntityIds": [ "amlb:source-entity:6dcdb3bb" ] }, { "id": "RO-THRESHOLD", "jurisdictionCode": "RO", "jurisdictionName": "Romania", "coverageStatus": "verified", "lastReviewedDate": "2026-10-06", "title": "Article 7 threshold transaction reports", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the relevant Article 7 categories; includes cash reports and sector-specific external-transfer/remittance reports.", "trigger": "Non-suspicious reportable transactions: cash at least EUR 10,000 equivalent; external account transfers at least EUR 10,000 for credit/financial institutions; remittance at least EUR 2,000 where applicable.", "deadline": "No later than 3 working days from the transaction.", "recipient": "ONPCSB.", "submission": "Electronic-only through ONPCSB reporting channels / SETD.", "applicability": "2026-08-18", "consequence": "Late/missing Article 7 reporting is sanctionable under the AML/CFT law; exact fine depends on breach/entity.", "enforcement": "ONPCSB / competent supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure threshold aggregation and sector logic separately for cash, external transfers and remittance activity.", "evidenceIds": [ "amlb:evidence:8c051b2f", "amlb:evidence:7c68360e", "amlb:evidence:d3d4b1e0" ], "sourceEntityIds": [ "amlb:source-entity:6dcdb3bb" ] }, { "id": "RO-INDEPENDENT-AUDIT", "jurisdictionCode": "RO", "jurisdictionName": "Romania", "coverageStatus": "verified", "lastReviewedDate": "2026-10-06", "title": "Independent AML/CFT audit where Article 24(2) applies", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the statutory scope requiring an independent test of AML/CFT policies and controls.", "trigger": "Applicability threshold/scope under Article 24(2) and the entity’s control framework.", "deadline": "Periodic/ongoing governance obligation where applicable; no universal annual date is asserted for all entities.", "recipient": "Competent sector supervisor / ONPCSB as applicable.", "submission": "Independent/external review retained within governance and supervisory evidence.", "applicability": "2026-08-18", "consequence": "Failure to maintain required internal policies/control testing may attract supervisory and administrative consequences under the AML/CFT law.", "enforcement": "ONPCSB / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The statutory independent-audit duty is verified; frequency/applicability remains entity/scope-specific rather than generalised.", "operationalImpact": "Determine applicability during compliance scoping and keep audit/remediation evidence linked to the entity risk assessment.", "evidenceIds": [ "amlb:evidence:9a08c615" ], "sourceEntityIds": [ "amlb:source-entity:6dcdb3bb" ] }, { "id": "RO-TFS-FREEZE", "jurisdictionCode": "RO", "jurisdictionName": "Romania", "coverageStatus": "verified", "lastReviewedDate": "2026-10-06", "title": "International-sanctions asset freeze and immediate report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities supervised and controlled by ONPCSB for implementation of international sanctions freezing funds and economic resources.", "trigger": "A person, entity, fund or economic resource is subject to an applicable international sanctions freezing measure within the scope of Government Emergency Ordinance No. 202/2008 and Order No. 64/2026.", "deadline": "Freeze without delay and report the implementation measures immediately to ONPCSB.", "recipient": "National Office for Prevention and Control of Money Laundering (ONPCSB).", "submission": "Use the prescribed report form in Annex No. 2 to Order No. 64/2026 and submit by email to raportare.sanctiuni@onpcsb.ro.", "applicability": "2026-05-08", "consequence": "Breaches are enforceable under the international-sanctions framework; Order No. 64/2026 assigns contravention finding and sanctioning powers to authorised ONPCSB representatives.", "enforcement": "ONPCSB.", "evidenceStatus": "verified", "operationalImpact": "Maintain sanctions-list monitoring, an immediate freeze workflow, evidential records and an escalation path capable of sending the prescribed report to ONPCSB without delay.", "evidenceIds": [ "amlb:evidence:0bd1a660", "amlb:evidence:0ecf6c82" ], "sourceEntityIds": [ "amlb:source-entity:c0527132" ] }, { "id": "RU-STR", "jurisdictionCode": "RU", "jurisdictionName": "Russia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious operation information to Rosfinmonitoring", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged organisations/persons under Federal Law No. 115-FZ and implementing rules.", "trigger": "An operation is identified as suspicious under the AML/CFT control framework.", "deadline": "Within 3 working days following the day the suspicious operation is identified, under the applicable Rosfinmonitoring reporting procedure.", "recipient": "Federal Financial Monitoring Service (Rosfinmonitoring).", "submission": "Electronic reporting in the format/channel prescribed by Rosfinmonitoring for the obliged-entity category.", "applicability": "2026-08-18", "consequence": "Failure to submit required information can lead to administrative/supervisory consequences; exact penalty depends on the entity, breach and applicable Code provision.", "enforcement": "Rosfinmonitoring / Bank of Russia or other sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current official legal/regulatory materials support the three-working-day suspicious-reporting workflow.", "operationalImpact": "Start the three-working-day control clock from detection/classification, not from later case closure.", "evidenceIds": [ "amlb:evidence:887dbf14", "amlb:evidence:f453b5da", "amlb:evidence:43d9c6b3" ], "sourceEntityIds": [ "amlb:source-entity:edba70d4", "amlb:source-entity:260f04a2", "amlb:source-entity:91952f6f" ] }, { "id": "RU-MANDATORY", "jurisdictionCode": "RU", "jurisdictionName": "Russia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Mandatory-control transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under the Article 6 mandatory-control categories and implementing rules.", "trigger": "A transaction falls within a statutory mandatory-control category/threshold.", "deadline": "Within 3 working days following the day of the reportable transaction under the applicable reporting procedure.", "recipient": "Rosfinmonitoring.", "submission": "Electronic reporting using the current Rosfinmonitoring format/channel for the entity type.", "applicability": "2026-08-18", "consequence": "Failure to report mandatory-control information can result in administrative/supervisory sanctions under the AML/CFT framework.", "enforcement": "Rosfinmonitoring / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The duty is mapped separately from suspicion reporting to preserve trigger accuracy.", "operationalImpact": "Automate statutory-threshold/category detection and maintain a distinct filing queue from STR investigations.", "evidenceIds": [ "amlb:evidence:f453b5da", "amlb:evidence:887dbf14" ], "sourceEntityIds": [ "amlb:source-entity:260f04a2", "amlb:source-entity:edba70d4" ] }, { "id": "RU-CONTROLS", "jurisdictionCode": "RU", "jurisdictionName": "Russia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Internal AML/CFT control rules and risk-based monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged organisations/persons under 115-FZ and sector rules.", "trigger": "Ongoing business activity and changes in risk/regulation.", "deadline": "Ongoing; maintain internal-control rules, identification/monitoring and reporting governance.", "recipient": "Competent supervisor / Rosfinmonitoring.", "submission": "Internal governance plus required electronic reporting outputs.", "applicability": "2026-08-18", "consequence": "Control failures can lead to administrative and supervisory action; serious conduct may carry additional liability.", "enforcement": "Bank of Russia / Rosfinmonitoring / relevant sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Mapped current official sources support the standing control framework.", "operationalImpact": "Treat internal-control rules as a living operational system, not a policy document updated only when an examiner asks.", "evidenceIds": [ "amlb:evidence:887dbf14", "amlb:evidence:f453b5da" ], "sourceEntityIds": [ "amlb:source-entity:edba70d4", "amlb:source-entity:260f04a2" ] }, { "id": "SM-STR", "jurisdictionCode": "SM", "jurisdictionName": "San Marino", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Segnalazione di operazione / fatto sospetto", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Designated subjects under San Marino’s AML/CFT framework.", "trigger": "Any person/fact/operation that may be connected to money laundering or terrorist financing under the statutory suspicion standard.", "deadline": "Without delay.", "recipient": "Agenzia di Informazione Finanziaria (AIF).", "submission": "Current AIF suspicious-reporting procedure.", "applicability": "2026-08-18", "consequence": "Failure to report may lead to administrative and, depending on conduct, criminal/regulatory consequences under the AML/CFT framework.", "enforcement": "AIF and competent judicial authorities.", "evidenceStatus": "verified", "evidenceNote": "AIF instruction expressly uses the without-delay standard.", "operationalImpact": "Maintain immediate internal escalation and current AIF filing access; do not convert “without delay” into an arbitrary internal multi-day target.", "evidenceIds": [ "amlb:evidence:6dbf1a7e", "amlb:evidence:36537dd9", "amlb:evidence:06cbea9c" ], "sourceEntityIds": [ "amlb:source-entity:9ecbaf74" ] }, { "id": "SM-RISK", "jurisdictionCode": "SM", "jurisdictionName": "San Marino", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk assessment and proportionate controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Designated subjects under Law No. 92/2008 and AIF rules.", "trigger": "Ongoing activity and material changes in risk.", "deadline": "Ongoing; demonstrate that measures are commensurate with identified ML/TF risk. No universal external filing date is asserted.", "recipient": "AIF / competent supervisor.", "submission": "Internal governance and supervisory evidence.", "applicability": "2026-08-18", "consequence": "Deficiencies may lead to AIF supervisory/administrative measures under the applicable law/rules.", "enforcement": "AIF.", "evidenceStatus": "verified", "evidenceNote": "Current AIF guidance confirms the risk-proportionate control expectation.", "operationalImpact": "Document the link from risk assessment to CDD, monitoring, training and escalation decisions.", "evidenceIds": [ "amlb:evidence:06cbea9c", "amlb:evidence:a8356013" ], "sourceEntityIds": [ "amlb:source-entity:9ecbaf74" ] }, { "id": "RS-STR", "jurisdictionCode": "RS", "jurisdictionName": "Serbia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious transaction / activity report to APML", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Serbia’s current AML/CFT Law.", "trigger": "Suspicion of money laundering or terrorist financing under the statutory/reporting indicators and entity procedures.", "deadline": "Event-driven. Exact current universal deadline is not verified in mapped provision-level sources.", "recipient": "Administration for the Prevention of Money Laundering (APML).", "submission": "Current APML suspicious-activity reporting procedure.", "applicability": "2026-08-18", "consequence": "Failure to report can attract sanctions under the amended AML/CFT Law; 2025 amendments updated the sanctioning framework.", "enforcement": "APML / competent sector supervisor and enforcement authorities.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use current APML instructions and maintain an immediate escalation standard internally until provision-specific timing is mapped.", "evidenceIds": [ "amlb:evidence:e82f4575", "amlb:evidence:8fecc14e", "amlb:evidence:34bdcc62" ], "sourceEntityIds": [ "amlb:source-entity:1c65f9d6" ] }, { "id": "RS-RISK", "jurisdictionCode": "RS", "jurisdictionName": "Serbia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "ML/TF/PF risk assessment and risk-based controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under the amended AML/CFT Law.", "trigger": "Ongoing business and material changes in risk.", "deadline": "Prepare and regularly update the risk analysis; no universal external filing date is asserted.", "recipient": "Competent supervisor / APML within its remit.", "submission": "Internal governance; provide during supervision as required.", "applicability": "2026-08-18", "consequence": "Control failures may result in supervisory/administrative sanctions under the amended 2025 framework.", "enforcement": "APML / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current APML guidance and 2025 amendment confirm the risk-based framework.", "operationalImpact": "Keep the institutional risk analysis current and map changes into customer-risk methodology and monitoring controls.", "evidenceIds": [ "amlb:evidence:e82f4575", "amlb:evidence:34bdcc62" ], "sourceEntityIds": [ "amlb:source-entity:1c65f9d6" ] }, { "id": "RS-BO-DISCREPANCY", "jurisdictionCode": "RS", "jurisdictionName": "Serbia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Beneficial-owner register discrepancy workflow", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "AML/CFT obliged entities when determining the beneficial owner of a customer covered by the Central Records of Beneficial Owners Law.", "trigger": "The obliged entity finds that beneficial-owner data obtained through CDD differ from the Central Records or are absent from the Records.", "deadline": "Immediately notify the customer and enter the discrepancy note in the Central Records. The registered entity then has 30 days to reconcile its recorded data; if the discrepancy remains after that period, the statutory competent-authority escalation follows.", "recipient": "Customer / Central Records of Beneficial Owners; competent supervisory authority if the discrepancy remains unresolved.", "submission": "Enter the discrepancy note and supporting documents through the Central Records portal; follow the statutory supervisory-escalation route if unreconciled.", "applicability": "15 September 2026.", "consequence": "The Law creates a formal discrepancy and supervisory-escalation process; provision-specific sanctions are not restated here without a separately mapped penalty provision.", "enforcement": "Serbian Business Registers Agency / competent AML/CFT supervisory authority.", "evidenceStatus": "verified", "evidenceNote": "Article 16 of the official English Law text sets the comparison, immediate-note, 30-day reconciliation and subsequent escalation workflow.", "operationalImpact": "CDD systems should compare register data with customer evidence, create an auditable discrepancy record immediately and track the 30-day reconciliation period.", "evidenceIds": [ "amlb:evidence:f3a5099e" ], "sourceEntityIds": [ "amlb:source-entity:36715885" ] }, { "id": "UA-STR", "jurisdictionCode": "UA", "jurisdictionName": "Ukraine", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious financial transaction / activity reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Primary financial monitoring entities under Law No. 361-IX.", "trigger": "Suspicion or sufficient grounds for suspicion relating to a transaction/activity, regardless of amount.", "deadline": "Immediately after the suspicion or sufficient grounds arise.", "recipient": "State Financial Monitoring Service of Ukraine (SFMS).", "submission": "Electronic reporting under the current SFMS procedure applicable to the reporting entity.", "applicability": "2026-08-18", "consequence": "Failure to report can lead to supervisory/administrative consequences under the AML/CFT law and sector framework; exact amount depends on breach/entity.", "enforcement": "SFMS and competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The official English law expressly states immediate reporting for suspicious transactions/activities.", "operationalImpact": "Configure real-time escalation rather than borrowing the separate five-business-day threshold-report clock.", "evidenceIds": [ "amlb:evidence:3b052193" ], "sourceEntityIds": [ "amlb:source-entity:fa2014ca" ] }, { "id": "UA-THRESHOLD", "jurisdictionCode": "UA", "jurisdictionName": "Ukraine", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold financial transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Primary financial monitoring entities under Law No. 361-IX.", "trigger": "A transaction meets the statutory threshold/category conditions for mandatory financial monitoring.", "deadline": "For statutory categories (1)–(3), within 5 business days from conduct/attempt; categories (4)–(5) follow the law’s next-month reporting clock, no later than the fifth business day of the following month.", "recipient": "State Financial Monitoring Service of Ukraine (SFMS).", "submission": "Electronic reporting under the current SFMS reporting procedure.", "applicability": "2026-08-18", "consequence": "Late/missing statutory reports can lead to AML/CFT supervisory/administrative consequences.", "enforcement": "SFMS / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The official English law sets the distinct five-business-day reporting tracks.", "operationalImpact": "Keep threshold reports in a separate automated queue with the correct category-dependent clock.", "evidenceIds": [ "amlb:evidence:3b052193" ], "sourceEntityIds": [ "amlb:source-entity:fa2014ca" ] }, { "id": "UA-UBO-DISCREP", "jurisdictionCode": "UA", "jurisdictionName": "Ukraine", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "UBO discrepancy report to SFMS", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Primary financial monitoring entities that identify a discrepancy during customer due diligence.", "trigger": "Difference between customer UBO information obtained by the reporting entity and UBO data in the Unified State Register.", "deadline": "No later than the 10th business day of the month following the month in which the discrepancy was detected.", "recipient": "State Financial Monitoring Service of Ukraine (SFMS).", "submission": "Electronic reporting under the applicable SFMS reporting process.", "applicability": "2026-08-18", "consequence": "Failure to meet AML/CFT reporting duties can attract supervisory/administrative consequences under the applicable law.", "enforcement": "SFMS / competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Track detected discrepancies by month and schedule a controlled month-end/next-month filing process without waiting until the last permissible day.", "evidenceIds": [ "amlb:evidence:3b052193" ], "sourceEntityIds": [ "amlb:source-entity:fa2014ca" ] }, { "id": "ME-STR", "jurisdictionCode": "ME", "jurisdictionName": "Montenegro", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Montenegro’s current AML/CFT law.", "trigger": "Grounds for suspicion of money laundering, terrorist financing or related suspicious activity/transaction.", "deadline": "Without delay and before execution where possible; if prior notification is objectively impossible, without delay and no later than the next working day after execution.", "recipient": "Financial Intelligence Unit / Administration for Prevention of Money Laundering and Terrorist Financing.", "submission": "Current FIU reporting procedure.", "applicability": "2026-08-18", "consequence": "Failure to report may result in misdemeanour/administrative and supervisory consequences under the law; exact amount depends on the breach/entity.", "enforcement": "FIU / competent supervisory authority and courts as applicable.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Design pre-transaction escalation with the next-working-day rule only as the statutory fallback.", "evidenceIds": [ "amlb:evidence:45c4dee3" ], "sourceEntityIds": [ "amlb:source-entity:44674ddc" ] }, { "id": "ME-RISK", "jurisdictionCode": "ME", "jurisdictionName": "Montenegro", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business ML/TF risk analysis · initial and annual update", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged entities under the current AML/CFT law.", "trigger": "Establishment/start of activity, annual review cycle and material risk changes.", "deadline": "Develop the risk analysis within 60 days from establishment/start of activity and update it at least once a year. If the supervisor requests it, submit within 3 days.", "recipient": "Competent supervisory authority.", "submission": "Maintain internally; provide to supervisor on request.", "applicability": "2026-08-18", "consequence": "Failure to prepare/update/provide the risk analysis may lead to statutory misdemeanour and supervisory consequences.", "enforcement": "Competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Calendar both the annual refresh and a rapid-response control for supervisory production requests.", "evidenceIds": [ "amlb:evidence:45c4dee3" ], "sourceEntityIds": [ "amlb:source-entity:44674ddc" ] }, { "id": "ME-TRAINING", "jurisdictionCode": "ME", "jurisdictionName": "Montenegro", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Annual AML/CFT professional training programme", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged entities with relevant staff under the current AML/CFT law.", "trigger": "Each calendar year.", "deadline": "Prepare the professional training and development programme by the end of the first quarter.", "recipient": "Internal governance / competent supervisor during oversight.", "submission": "Maintain programme and evidence internally.", "applicability": "2026-08-18", "consequence": "Failure to comply with required training/governance duties may lead to statutory supervisory/misdemeanour consequences.", "enforcement": "Competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Put the annual training programme approval on the compliance calendar and retain completion/attendance evidence.", "evidenceIds": [ "amlb:evidence:45c4dee3" ], "sourceEntityIds": [ "amlb:source-entity:44674ddc" ] }, { "id": "MK-BO", "jurisdictionCode": "MK", "jurisdictionName": "North Macedonia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Beneficial-owner register entry / change update", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Legal entities and legal arrangements within the statutory beneficial-owner register scope.", "trigger": "Initial registration or a change in beneficial-owner data.", "deadline": "Within 15 days of entry/establishment trigger or within 15 days of the change in beneficial-owner data, as applicable.", "recipient": "Central Registry of the Republic of North Macedonia.", "submission": "Electronic entry through the registry administrator’s web portal.", "applicability": "2026-08-18", "consequence": "Failure to enter/update BO data is a misdemeanour under the AML/CFT law; exact fine depends on liable person/entity.", "enforcement": "Central Registry / Administration for Financial Intelligence and competent enforcement authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Trigger a BO update workflow from corporate/ownership changes and monitor the 15-day statutory window.", "evidenceIds": [ "amlb:evidence:37ab6cf7", "amlb:evidence:1d4a8bfa" ], "sourceEntityIds": [ "amlb:source-entity:512f7fad", "amlb:source-entity:68b2f1ec" ] }, { "id": "MK-CASH", "jurisdictionCode": "MK", "jurisdictionName": "North Macedonia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash transaction report · EUR 15,000 equivalent+", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities within Article 63 threshold-reporting scope.", "trigger": "A cash transaction of at least EUR 15,000 equivalent, whether single or obviously linked transactions.", "deadline": "No later than 3 working days from execution.", "recipient": "Financial Intelligence Office / Administration.", "submission": "Prescribed report to the Administration; sector-specific Article 64 reports are electronic where stated.", "applicability": "2026-08-18", "consequence": "Failure to submit required transaction information can trigger misdemeanour/supervisory consequences under the law.", "enforcement": "Administration for Financial Intelligence / competent supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Automate linked-transaction aggregation and file inside the three-working-day window.", "evidenceIds": [ "amlb:evidence:37ab6cf7" ], "sourceEntityIds": [ "amlb:source-entity:512f7fad" ] }, { "id": "MK-SECTOR-REPORTS", "jurisdictionCode": "MK", "jurisdictionName": "North Macedonia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Sector transaction reports under Article 64", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Banks, notaries, money-remittance providers, life insurers, casinos and other categories specifically listed in Article 64.", "trigger": "Sector-specific transactions meeting the statutory threshold/category.", "deadline": "Varies by category: several reports are due electronically within 3 working days; bank loan reports specified in Article 64 are due by the 10th day of the current month for the previous month.", "recipient": "Financial Intelligence Office / Administration.", "submission": "Electronic reports where Article 64 specifies electronic form.", "applicability": "2026-08-18", "consequence": "Failure to meet sector reporting duties is sanctionable under the AML/CFT law.", "enforcement": "Administration for Financial Intelligence / competent sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the applicable Article 64 sub-paragraph into each sector’s reporting calendar and data feeds.", "evidenceIds": [ "amlb:evidence:37ab6cf7" ], "sourceEntityIds": [ "amlb:source-entity:512f7fad" ] }, { "id": "TR-STR", "jurisdictionCode": "TR", "jurisdictionName": "Türkiye", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged parties under Law No. 5549 and the MASAK reporting regulation/Communiqué.", "trigger": "Information, suspicion or reasonable grounds that assets/transactions are linked to crime proceeds, terrorism or terrorist financing.", "deadline": "Within 10 workdays from the date suspicion occurs, or immediately where any delay may cause inconvenience.", "recipient": "Financial Crimes Investigation Board (MASAK).", "submission": "MASAK.ONLINE for obliged parties required/authorised to report electronically; current guidelines govern channel details and paper fallback where applicable.", "applicability": "2026-08-18", "consequence": "Violation of the reporting/confidentiality obligations is subject to penalties under Law No. 5549; exact monetary amount is not frozen here because statutory amounts can be amended/indexed.", "enforcement": "MASAK / Ministry of Treasury and Finance and competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "The official MASAK Communiqué gives both the 10-workday outer limit and immediate-report condition, plus MASAK.ONLINE rules.", "operationalImpact": "Treat 10 workdays as the outer statutory limit, not the internal target; urgent cases must be routed immediately.", "evidenceIds": [ "amlb:evidence:4897dd4f", "amlb:evidence:a9818296" ], "sourceEntityIds": [ "amlb:source-entity:a173c0ae" ] }, { "id": "TR-COMPLIANCE", "jurisdictionCode": "TR", "jurisdictionName": "Türkiye", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "AML/CFT compliance programme, risk management and controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged parties subject to the compliance-programme and preventive-measures framework; detailed applicability varies by entity type.", "trigger": "Ongoing regulated activity and material changes in risk.", "deadline": "Ongoing; maintain risk management, monitoring/control, compliance officer/internal reporting and training arrangements where applicable.", "recipient": "MASAK / competent sector supervisor.", "submission": "Internal governance plus MASAK reporting outputs.", "applicability": "2026-08-18", "consequence": "Control failures can lead to administrative penalties under Law No. 5549 and sector supervisory measures.", "enforcement": "MASAK / competent sector supervisor.", "evidenceStatus": "verified", "evidenceNote": "Current MASAK preventive framework and Communiqué reference the compliance-programme architecture.", "operationalImpact": "Maintain a documented compliance programme and ensure internal STR escalation routes are written, communicated and tested.", "evidenceIds": [ "amlb:evidence:a9818296", "amlb:evidence:4897dd4f" ], "sourceEntityIds": [ "amlb:source-entity:a173c0ae" ] }, { "id": "AU-SMR", "jurisdictionCode": "AU", "jurisdictionName": "Australia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Matter Report (SMR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "AUSTRAC reporting entities when the statutory suspicious-matter trigger is met in connection with a designated service.", "trigger": "Reasonable grounds for suspicion, including relevant criminal activity or terrorism-financing suspicion.", "deadline": "Within 24 hours of forming a terrorism-financing suspicion; otherwise within 3 business days after the day the suspicion was formed.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current reporting form/rules from 1 Jul 2026, subject to AUSTRAC transition arrangements.", "consequence": "Late or missing reports can attract civil penalty and enforcement action. A single monetary figure is not generalised because the applicable provision and entity facts matter.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Case-management escalation should distinguish the 24-hour terrorism-financing clock from the 3-business-day clock for other suspicions.", "evidenceIds": [ "amlb:evidence:946b2ae0", "amlb:evidence:83ddd7d5" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d" ] }, { "id": "AU-TTR", "jurisdictionCode": "AU", "jurisdictionName": "Australia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities providing a designated service involving a physical-currency threshold transaction.", "trigger": "Transfer, receipt or payment of A$10,000 or more in physical currency, including foreign currency of equivalent value.", "deadline": "Within 10 business days after the day the transaction takes place.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current AUSTRAC reporting framework verified 18 Aug 2026.", "consequence": "Failure to lodge a required TTR can lead to AUSTRAC enforcement and civil penalties; the Calendar does not substitute one generic maximum for the full statutory penalty regime.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Cash-detection logic should aggregate only as required by the applicable reporting rule and send reportable physical-currency events into a 10-business-day filing workflow.", "evidenceIds": [ "amlb:evidence:2799d585", "amlb:evidence:83ddd7d5" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d" ] }, { "id": "AU-IFTI", "jurisdictionCode": "AU", "jurisdictionName": "Australia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "International Funds Transfer Instruction (IFTI) report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities within the current IFTI reporting regime when sending or receiving an international funds transfer instruction.", "trigger": "Sending an IFTI out of Australia or receiving an IFTI into Australia under the applicable reporting category.", "deadline": "Within 10 business days.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online / applicable electronic reporting method.", "applicability": "Current transition-era IFTI regime verified 18 Aug 2026.", "consequence": "AUSTRAC states that late or missing IFTI reporting can attract penalties, including up to 100,000 penalty units for a body corporate and 20,000 for a non-body-corporate under the stated regime.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Cross-border payment systems should identify IFTIs at source and preserve the instruction date used to calculate the reporting deadline.", "evidenceIds": [ "amlb:evidence:0f857fea", "amlb:evidence:092f04f6", "amlb:evidence:83ddd7d5" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d" ] }, { "id": "AU-AMLPROGRAM", "jurisdictionCode": "AU", "jurisdictionName": "Australia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CTF program and risk controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the AML/CTF Act and Rules, with scope affected by the 2024 reform implementation and transition settings.", "trigger": "While providing regulated designated services.", "deadline": "Ongoing. Risk-based AML/CTF program obligations are continuous rather than a single fixed-date filing.", "recipient": "AUSTRAC", "submission": "Maintained internally and produced/submitted where required by AUSTRAC; no universal periodic filing asserted here.", "applicability": "Reformed obligations commenced in stages, including 1 Jul 2026 for newly regulated Tranche 2 sectors.", "consequence": "Program failures can result in supervisory remediation, infringement/civil-penalty action or other AUSTRAC enforcement depending on the breach.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "evidenceNote": "Current AUSTRAC reform and obligations pages confirm the standing program/risk-control layer.", "operationalImpact": "Maintain current risk assessment, governance, policies, monitoring, training and assurance as continuous controls rather than treating AML compliance as report-only.", "evidenceIds": [ "amlb:evidence:82d11f2f", "amlb:evidence:eb38db01", "amlb:evidence:83ddd7d5", "amlb:evidence:092f04f6" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d" ] }, { "id": "NZ-ANNUAL", "jurisdictionCode": "NZ", "jurisdictionName": "New Zealand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Annual AML/CFT Report", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities required to submit the statutory annual AML/CFT report; form content differs by entity category.", "trigger": "Annual reporting season for the preceding AML/CFT reporting period.", "deadline": "For the 2025/2026 period: submit between 1 July and 31 August 2026.", "recipient": "Department of Internal Affairs (DIA)", "submission": "AML Online.", "applicability": "Current 2025/2026 reporting window verified 18 Aug 2026.", "consequence": "Failure to submit an annual report is a compliance breach and may result in DIA supervisory/enforcement action under the AML/CFT Act.", "enforcement": "Department of Internal Affairs", "evidenceStatus": "verified", "evidenceNote": "DIA’s current Annual AML/CFT Report page states the 1 July–31 August 2026 window and AML Online route.", "operationalImpact": "Calendar owners can treat 31 August 2026 as the current external deadline while preserving entity-specific preparation and approval milestones internally.", "evidenceIds": [ "amlb:evidence:cd834963", "amlb:evidence:f8d67997" ], "sourceEntityIds": [ "amlb:source-entity:0de6975c" ] }, { "id": "NZ-SAR", "jurisdictionCode": "NZ", "jurisdictionName": "New Zealand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the AML/CFT Act when reasonable grounds for suspicion are formed.", "trigger": "Reasonable grounds for suspicion are formed in relation to suspicious activity or transaction circumstances.", "deadline": "No later than 3 working days after reasonable grounds for suspicion are formed.", "recipient": "New Zealand Police Financial Intelligence Unit (FIU)", "submission": "goAML Web.", "applicability": "Current FIU guidance verified 18 Aug 2026.", "consequence": "Failure to meet statutory reporting obligations can result in AML/CFT Act enforcement; penalty depends on the particular breach and proceedings.", "enforcement": "New Zealand Police FIU / DIA as supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal escalation should be shorter than the statutory outer limit so that review, approval and goAML filing are completed within three working days.", "evidenceIds": [ "amlb:evidence:50174664", "amlb:evidence:0aac00c5" ], "sourceEntityIds": [ "amlb:source-entity:8cab850a" ] }, { "id": "NZ-PTR", "jurisdictionCode": "NZ", "jurisdictionName": "New Zealand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Prescribed Transaction Reports (LCT / IFT)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities conducting prescribed large cash transactions or international funds transfers.", "trigger": "Large Cash Transaction: physical currency NZ$10,000 or more. International Funds Transfer: NZ$1,000 or more where the statutory cross-border conditions are met.", "deadline": "Reportable when the prescribed transaction occurs. The current public FIU page confirms thresholds and submission methods but mapped sources do not assert an exact universal filing-day clock without verifying the current regulation provision.", "recipient": "New Zealand Police Financial Intelligence Unit (FIU)", "submission": "goAML Web form, XML upload or approved B2B automated submission.", "applicability": "Current FIU PTR framework verified 18 Aug 2026.", "consequence": "Failure to report a prescribed transaction may result in AML/CFT enforcement. Exact sanction depends on the statutory breach.", "enforcement": "New Zealand Police FIU / DIA as supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Transaction systems should detect both NZ$10,000 physical-cash events and NZ$1,000 qualifying international transfers and route them to goAML processes.", "evidenceIds": [ "amlb:evidence:e99681c9", "amlb:evidence:47693f02" ], "sourceEntityIds": [ "amlb:source-entity:8cab850a" ] }, { "id": "NZ-AUDIT", "jurisdictionCode": "NZ", "jurisdictionName": "New Zealand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Independent AML/CFT audit", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the independent audit requirement.", "trigger": "Expiry of the applicable audit cycle, or earlier request by DIA.", "deadline": "Every 3 years by default, unless DIA notifies the entity that a 4-year timeframe applies; DIA may also require an audit at another time.", "recipient": "Department of Internal Affairs (supervisory oversight)", "submission": "Independent audit retained/provided as required; no universal portal filing is asserted.", "applicability": "Current audit cycle guidance verified 18 Aug 2026.", "consequence": "Failure to maintain the required audit can lead to DIA supervisory/enforcement action.", "enforcement": "Department of Internal Affairs", "evidenceStatus": "verified", "evidenceNote": "July 2026 DIA guidance explicitly states the 3-year default and possible 4-year notified timeframe.", "operationalImpact": "Track the entity-specific last-audit date and any DIA notice rather than assuming one nationwide calendar date.", "evidenceIds": [ "amlb:evidence:3aabbca1" ], "sourceEntityIds": [ "amlb:source-entity:0de6975c" ] }, { "id": "NZ-AML-LEVY", "jurisdictionCode": "NZ", "jurisdictionName": "New Zealand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "AML/CFT supervisory levy", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities that fall within a leviable class in Schedule 2 of the AML/CFT (Levy) Regulations 2026. Regulation 6 excludes reporting entities exempted from sections 10 to 71 of the Act under sections 156E or 157.", "trigger": "For each financial year in which the reporting entity falls within a leviable class, beginning with the financial year commencing 1 July 2027. The AML/CFT supervisor calculates or estimates the levy and issues an invoice.", "deadline": "Pay by the due date or dates specified in the supervisor invoice. The invoice due date must be no earlier than 30 days after the invoice issue date, subject to the challenge/judicial-review timing rules in regulation 6(4).", "recipient": "AML/CFT supervisor (Department of Internal Affairs under the current single-supervisor model)", "submission": "Payment method and due date are specified in the AML/CFT supervisor invoice.", "applicability": "Regulations commence 8 October 2026; prescribed levies apply from the financial year commencing 1 July 2027 and subsequent financial years.", "consequence": "An unpaid levy is recoverable as a debt due to the Crown under regulation 13.", "enforcement": "AML/CFT supervisor / Crown debt recovery", "evidenceStatus": "verified", "evidenceNote": "The regulations specify leviable classes, annual application, calculation and invoicing mechanics, a minimum 30-day invoice due-date window, and debt recovery.", "operationalImpact": "Reporting entities should identify whether they fall within a Schedule 2 class, budget for the annual levy from the 2027/2028 financial year, and route supervisor invoices for timely review and payment.", "evidenceIds": [ "amlb:evidence:ff40b554" ], "sourceEntityIds": [ "amlb:source-entity:e2f5a70b" ] }, { "id": "JP-STR", "jurisdictionCode": "JP", "jurisdictionName": "Japan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Specified business operators within the Act on Prevention of Transfer of Criminal Proceeds and applicable sector rules.", "trigger": "Facts giving rise to suspicion under the statutory suspicious-transaction reporting duty.", "deadline": "Report without avoidable delay in accordance with the statutory/competent-authority framework; no universal numeric day-count is asserted in mapped sources.", "recipient": "Competent administrative authority; reports are collected/analyzed within Japan’s JAFIC framework.", "submission": "Sector/authority reporting route; exact electronic channel varies and is not shown as one general value.", "applicability": "Current FSA STR reference cases updated Feb 2026.", "consequence": "Failure to comply can lead to competent-authority supervisory or statutory action; no single penalty figure is generalised.", "enforcement": "Competent administrative authority / JAFIC framework", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain escalation procedures capable of prompt competent-authority reporting and preserve sector-specific submission instructions.", "evidenceIds": [ "amlb:evidence:ce5f6758", "amlb:evidence:4dd80d18" ], "sourceEntityIds": [ "amlb:source-entity:ab53648b", "amlb:source-entity:bedd1331" ] }, { "id": "JP-AML-CONTROLS", "jurisdictionCode": "JP", "jurisdictionName": "Japan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls and monitoring", "timingType": "ongoing", "sectors": [ "banking", "securities", "insurance" ], "appliesTo": "Financial institutions supervised under the FSA AML/CFT framework.", "trigger": "Continuous while conducting regulated business.", "deadline": "Ongoing; no single external filing date.", "recipient": "Financial Services Agency (FSA)", "submission": "Internal policies, risk assessment, monitoring and governance; regulatory submission only where specifically required.", "applicability": "Current framework reviewed 18 Aug 2026.", "consequence": "Control deficiencies may lead to FSA supervisory measures and other action under the applicable financial-services laws.", "enforcement": "Financial Services Agency", "evidenceStatus": "verified", "evidenceNote": "Mapped FSA/JAFIC sources support the standing control framework.", "operationalImpact": "Treat risk assessment, CDD, monitoring, governance and training as standing controls with documented review cycles.", "evidenceIds": [ "amlb:evidence:8d35285d" ], "sourceEntityIds": [ "amlb:source-entity:ab53648b" ] }, { "id": "KR-STR", "jurisdictionCode": "KR", "jurisdictionName": "South Korea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and casinos within the Korean AML regime.", "trigger": "Reasonable grounds to suspect illegal assets, money laundering or financing for offences of public intimidation/terrorist financing.", "deadline": "Without delay.", "recipient": "Korea Financial Intelligence Unit (KoFIU)", "submission": "KoFIU standard STR reporting process/form.", "applicability": "Current KoFIU framework verified 18 Aug 2026.", "consequence": "KoFIU states that failure to report can result in sanctions including disciplinary action for employees and administrative fines for financial institutions.", "enforcement": "KoFIU", "evidenceStatus": "verified", "operationalImpact": "Internal reporting officer review must operate quickly enough to avoid introducing delay once reasonable grounds are established.", "evidenceIds": [ "amlb:evidence:97522f1e" ], "sourceEntityIds": [ "amlb:source-entity:6ad477b4" ] }, { "id": "KR-CTR", "jurisdictionCode": "KR", "jurisdictionName": "South Korea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions subject to Korea’s CTR regime.", "trigger": "An individual conducts cash deposit/withdrawal transactions above KRW 10 million in a day through a financial institution.", "deadline": "Reporting is mandatory when the threshold is met; the current public KoFIU overview checked here does not state the exact filing-day clock.", "recipient": "KoFIU", "submission": "KoFIU reporting process.", "applicability": "KRW 10 million threshold current in KoFIU guidance.", "consequence": "Failure to comply may result in KoFIU administrative/supervisory sanctions under the applicable FTRA regime.", "enforcement": "KoFIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash aggregation controls should detect same-day threshold events and preserve the data required for KoFIU reporting.", "evidenceIds": [ "amlb:evidence:86379446" ], "sourceEntityIds": [ "amlb:source-entity:6ad477b4" ] }, { "id": "KR-CDD", "jurisdictionCode": "KR", "jurisdictionName": "South Korea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Customer due diligence and AML controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other entities within the Korean AML/CFT regime.", "trigger": "Account opening, qualifying occasional transactions, or ML/TF concern; ongoing controls continue throughout the relationship.", "deadline": "Ongoing; event-based CDD triggers apply rather than one fixed calendar date.", "recipient": "KoFIU / relevant financial supervisor", "submission": "Internal control and CDD records; no universal periodic filing asserted.", "applicability": "Current KoFIU guidance verified 18 Aug 2026.", "consequence": "Deficiencies may trigger administrative/supervisory action under the Korean AML regime.", "enforcement": "KoFIU and relevant financial supervisors", "evidenceStatus": "verified", "evidenceNote": "KoFIU official guidance identifies CDD, STR and CTR as core priorities and sets event-based CDD triggers.", "operationalImpact": "Onboarding and transaction systems should link threshold/event triggers to identity, beneficial-ownership and purpose checks.", "evidenceIds": [ "amlb:evidence:86379446" ], "sourceEntityIds": [ "amlb:source-entity:6ad477b4" ] }, { "id": "HK-STR", "jurisdictionCode": "HK", "jurisdictionName": "Hong Kong SAR China", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Any person with the statutory knowledge or suspicion trigger under DTROP/OSCO/UNATMO; regulated institutions also follow sector AML/CFT controls.", "trigger": "Knowledge or suspicion that property represents proceeds, was used in connection with serious crime, or is terrorist property under the applicable ordinance.", "deadline": "As soon as it is reasonable to do so.", "recipient": "Joint Financial Intelligence Unit (JFIU)", "submission": "JFIU electronic reporting arrangements; current JFIU instructions apply to regulated entities, with email proforma available for other reporters.", "applicability": "JFIU pages last revised July 2026.", "consequence": "JFIU states that failure to make a required STR can be prosecuted and carries a maximum penalty of three months’ imprisonment.", "enforcement": "Hong Kong Police Force / Customs & Excise through JFIU; sector supervisors may act separately.", "evidenceStatus": "verified", "evidenceNote": "Current JFIU institutional page states both the statutory “as soon as reasonable” standard and FIU role.", "operationalImpact": "MLRO procedures should minimise internal delay and use the current JFIU reporting instructions for the reporter type.", "evidenceIds": [ "amlb:evidence:e60e6b57", "amlb:evidence:23f8f2d5", "amlb:evidence:069b5df4" ], "sourceEntityIds": [ "amlb:source-entity:357a5e4e" ] }, { "id": "HK-AI-CONTROLS", "jurisdictionCode": "HK", "jurisdictionName": "Hong Kong SAR China", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Authorized institution AML/CFT controls", "timingType": "ongoing", "sectors": [ "banking" ], "appliesTo": "HKMA-authorized institutions.", "trigger": "Continuous while conducting authorized banking business.", "deadline": "Ongoing; risk-based CDD, monitoring, reporting and governance controls do not have one universal annual filing date.", "recipient": "Hong Kong Monetary Authority (HKMA)", "submission": "Internal framework and records; regulatory submissions where specifically required.", "applicability": "HKMA AML-2 current guideline version issued 25 May 2023; related guidance current through 2026.", "consequence": "AMLO/control failures may lead to HKMA disciplinary and supervisory action; sanction depends on the breached provision.", "enforcement": "HKMA", "evidenceStatus": "verified", "evidenceNote": "Current HKMA regulatory repository identifies AML-2 as current and directly related 2026 guidance remains active.", "operationalImpact": "Maintain documented customer-risk assessment, transaction monitoring, STR escalation, governance and assurance under the current HKMA framework.", "evidenceIds": [ "amlb:evidence:9646b14f", "amlb:evidence:cfe21d97" ], "sourceEntityIds": [ "amlb:source-entity:43145392", "amlb:source-entity:af401335" ] }, { "id": "CN-STR", "jurisdictionCode": "CN", "jurisdictionName": "China", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obligated entities within the revised PRC AML framework, subject to sector-specific rules.", "trigger": "Suspicious transaction/activity trigger under the AML Law and implementing reporting measures.", "deadline": "Prompt reporting is required under the applicable AML/reporting framework; mapped sources do not display a numeric universal clock without verifying the current post-reform implementing provision.", "recipient": "People’s Bank of China AML system / China Anti-Money Laundering Monitoring and Analysis Center (CAMLMAC)", "submission": "Official AML reporting systems under PBOC/CAMLMAC; institution-specific technical route not generalised.", "applicability": "Revised AML Law effective 1 Jan 2025.", "consequence": "Failure to comply can result in administrative/supervisory sanctions under the revised AML framework; penalty depends on breach, entity and implementing provisions.", "enforcement": "People’s Bank of China and competent financial regulators", "evidenceStatus": "verified-with-gap", "operationalImpact": "Policies should be mapped to the revised 2025 AML Law and current PBOC implementing measures rather than relying on legacy reporting-rule summaries.", "evidenceIds": [ "amlb:evidence:50d6dde7", "amlb:evidence:9da294f4" ], "sourceEntityIds": [ "amlb:source-entity:90bae2dc", "amlb:source-entity:542c3892" ] }, { "id": "CN-BO", "jurisdictionCode": "CN", "jurisdictionName": "China", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Beneficial ownership information filing and updating", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Legal persons and arrangements/entities within the scope of the Measures for the Administration of Beneficial Ownership Information, subject to exemptions and detailed scope rules.", "trigger": "Formation/registration and changes to reportable beneficial ownership information.", "deadline": "Filing/updating is mandatory under the current BO measures. Exact entity-specific filing-day clock is not asserted here without current provision-level confirmation.", "recipient": "State Administration for Market Regulation / designated BO information system with PBOC AML use", "submission": "Registration / BO information filing mechanism prescribed by the Measures.", "applicability": "Measures effective from 1 Nov 2024; current official text mapped.", "consequence": "Non-compliance may lead to corrective/administrative measures under the BO/registration framework; a single fine is not generalised.", "enforcement": "SAMR / PBOC and competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Entity-governance workflows should treat BO changes as reportable master-data events and retain evidence of timely registry updates.", "evidenceIds": [ "amlb:evidence:42722a36" ], "sourceEntityIds": [ "amlb:source-entity:5f83ee29" ] }, { "id": "CN-AML-CONTROLS", "jurisdictionCode": "CN", "jurisdictionName": "China", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML governance and customer controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obligated entities under the revised AML Law and implementing regulations.", "trigger": "Continuous regulated activity and risk changes.", "deadline": "Ongoing; no single fixed filing date.", "recipient": "PBOC and competent sector regulators", "submission": "Internal risk management, CDD, records, monitoring and governance; regulator reporting as specifically required.", "applicability": "Current post-2025 AML framework.", "consequence": "Deficiencies may lead to supervisory remediation and administrative sanctions under the revised AML regime.", "enforcement": "PBOC / competent financial regulators", "evidenceStatus": "verified", "evidenceNote": "Current official law and supervision measures support the ongoing AML-control obligation.", "operationalImpact": "Maintain a documented post-reform control framework aligned to risk, CDD, monitoring, records and escalation requirements.", "evidenceIds": [ "amlb:evidence:50d6dde7", "amlb:evidence:9635d9d5" ], "sourceEntityIds": [ "amlb:source-entity:90bae2dc", "amlb:source-entity:5f83ee29" ] }, { "id": "IN-STR", "jurisdictionCode": "IN", "jurisdictionName": "India", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under PMLA/PML Rules when the Principal Officer is satisfied that a transaction is suspicious.", "trigger": "Principal Officer is satisfied that the transaction is suspicious.", "deadline": "Promptly and not later than 7 working days after being satisfied that the transaction is suspicious.", "recipient": "Director, Financial Intelligence Unit – India (FIU-IND)", "submission": "FIU-IND prescribed electronic reporting process/formats.", "applicability": "Current FIU-IND FAQ/rules framework verified 18 Aug 2026.", "consequence": "Non-compliance with PMLA/PML Rules reporting can lead to FIU-IND/PMLA enforcement. Exact sanction depends on the contravention and adjudication.", "enforcement": "FIU-IND / competent PMLA authority", "evidenceStatus": "verified", "evidenceNote": "FIU-IND directly states the seven-working-day outer limit.", "operationalImpact": "Internal escalation should start before the Principal Officer reaches the statutory satisfaction point and ensure external filing within seven working days thereafter.", "evidenceIds": [ "amlb:evidence:3ffc634c", "amlb:evidence:5dcbf263" ], "sourceEntityIds": [ "amlb:source-entity:40f29a4c" ] }, { "id": "IN-MONTHLY", "jurisdictionCode": "IN", "jurisdictionName": "India", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Monthly PML Rule 3 transaction reports", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities for the Rule 3 categories covering prescribed cash/connected cash, NPO receipts, counterfeit-currency cash transactions and cross-border wire transfers.", "trigger": "End of each month in which a reportable Rule 3 category occurs.", "deadline": "By the 15th day of the succeeding month.", "recipient": "FIU-IND", "submission": "FIU-IND electronic reporting process/formats.", "applicability": "Current FIU-IND reporting timetable verified 18 Aug 2026.", "consequence": "Delayed/non-filing can trigger PMLA administrative enforcement; FIU-IND rules also treat timeliness as a reporting obligation.", "enforcement": "FIU-IND", "evidenceStatus": "verified-with-gap", "operationalImpact": "Monthly reporting pipelines should close data early enough to validate and submit by the 15th of the succeeding month.", "evidenceIds": [ "amlb:evidence:3ffc634c", "amlb:evidence:5dcbf263" ], "sourceEntityIds": [ "amlb:source-entity:40f29a4c" ] }, { "id": "IN-IMMOVABLE", "jurisdictionCode": "IN", "jurisdictionName": "India", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Quarterly immovable-property transaction reporting", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Rule 3 clause F reporting for qualifying immovable-property transactions.", "trigger": "End of the relevant quarter.", "deadline": "Quarterly · by the 15th day of the month following the quarter.", "recipient": "FIU-IND", "submission": "FIU-IND prescribed reporting format/channel.", "applicability": "Current rule timetable mapped 18 Aug 2026.", "consequence": "Non-compliance can lead to PMLA/FIU-IND enforcement; no generic penalty amount is substituted for case-specific adjudication.", "enforcement": "FIU-IND", "evidenceStatus": "verified-with-gap", "operationalImpact": "Quarter-end controls should identify in-scope immovable-property transactions and complete validation before the 15th of the following month.", "evidenceIds": [ "amlb:evidence:5dcbf263" ], "sourceEntityIds": [ "amlb:source-entity:40f29a4c" ] }, { "id": "ID-STR", "jurisdictionCode": "ID", "jurisdictionName": "Indonesia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious Financial Transaction Report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting parties under Law No. 8 of 2010 and implementing PPATK rules.", "trigger": "A transaction meets the statutory suspicious-financial-transaction criteria.", "deadline": "Current PPATK framework requires prompt reporting; operational materials indicate a short working-day window, but this build leaves the exact statutory day count as a provision-verification gap rather than overstating it.", "recipient": "PPATK / INTRAC", "submission": "goAML under current PPATK reporting regulations.", "applicability": "Current PPATK/OJK framework reviewed 18 Aug 2026.", "consequence": "Failure to comply can lead to administrative/supervisory sanctions under AML and sector rules; penalty depends on reporter and breach.", "enforcement": "PPATK and relevant sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep transaction-monitoring escalation integrated with the PPATK goAML reporting workflow and preserve the trigger date used for timeliness testing.", "evidenceIds": [ "amlb:evidence:b37f2856", "amlb:evidence:1f7ed71e" ], "sourceEntityIds": [ "amlb:source-entity:3b6de22c" ] }, { "id": "ID-CASH", "jurisdictionCode": "ID", "jurisdictionName": "Indonesia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Cash financial transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting parties within the statutory cash-transaction reporting regime.", "trigger": "Cash financial transactions meeting the statutory threshold/reporting conditions.", "deadline": "Reporting is mandatory under Law No. 8 of 2010 and implementing rules; exact current threshold or deadline is not verified in mapped operative provisions.", "recipient": "PPATK / INTRAC", "submission": "PPATK reporting system / goAML where applicable.", "applicability": "Current regime reviewed 18 Aug 2026.", "consequence": "Administrative/supervisory consequences may apply for non-reporting or late reporting.", "enforcement": "PPATK / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not configure production thresholds from secondary summaries; use the operative PPATK rule for system calibration.", "evidenceIds": [ "amlb:evidence:b37f2856", "amlb:evidence:e037119f" ], "sourceEntityIds": [ "amlb:source-entity:3b6de22c", "amlb:source-entity:b7e9d768" ] }, { "id": "ID-AMLPROGRAM", "jurisdictionCode": "ID", "jurisdictionName": "Indonesia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "OJK AML/CFT/CPF program", "timingType": "ongoing", "sectors": [ "banking", "securities", "insurance" ], "appliesTo": "Financial-sector institutions within OJK Regulation No. 8 of 2023 scope.", "trigger": "Continuous regulated financial-sector activity.", "deadline": "Ongoing; no single fixed filing date.", "recipient": "Financial Services Authority (OJK)", "submission": "Internal AML/CFT/CPF program and supervisory reporting where specifically required.", "applicability": "Current OJK AML/CFT/CPF programme framework; trustee-specific PADK No. 4 of 2026 effective 7 July 2026.", "consequence": "Program deficiencies can trigger OJK supervisory/administrative action under the regulation and sector laws.", "enforcement": "OJK", "evidenceStatus": "verified", "evidenceNote": "Current OJK regulation and official release are mapped in the existing evidence base.", "operationalImpact": "Maintain risk assessment, CDD/beneficial-owner checks, monitoring, governance, TFS/CPF and assurance as continuous controls; capital-market trustees should apply the trustee-specific PADK No. 4 of 2026 guidance.", "evidenceIds": [ "amlb:evidence:6bac77bc", "amlb:evidence:640fa33e", "amlb:evidence:0a49f674" ], "sourceEntityIds": [ "amlb:source-entity:c8549cc1" ] }, { "id": "MY-STR", "jurisdictionCode": "MY", "jurisdictionName": "Malaysia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions under AMLA when the institution suspects or has reasonable grounds to suspect a transaction, attempted transaction or proposed transaction.", "trigger": "Compliance Officer establishes the suspicion.", "deadline": "Within the next working day from the date the Compliance Officer establishes the suspicion.", "recipient": "Financial Intelligence and Enforcement Department (FIED), Bank Negara Malaysia", "submission": "FINS where applicable; BNM also lists prescribed email/mail channels.", "applicability": "Current BNM guidance verified 18 Aug 2026.", "consequence": "Failure to meet AMLA reporting/control duties can lead to supervisory, administrative or criminal consequences depending on the breached provision. A single STR-failure fine is not shown as one general value.", "enforcement": "Bank Negara Malaysia / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Compliance Officer decisioning and filing should be treated as a next-working-day external SLA, with internal escalation designed accordingly.", "evidenceIds": [ "amlb:evidence:f5f32d08", "amlb:evidence:cd11e838", "amlb:evidence:553f6186" ], "sourceEntityIds": [ "amlb:source-entity:995e2d48" ] }, { "id": "MY-CTR", "jurisdictionCode": "MY", "jurisdictionName": "Malaysia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash Threshold Report (CTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Currently applicable to banking institutions, selected prescribed development financial institutions, Lembaga Tabung Haji and licensed casino, as stated by BNM.", "trigger": "Single or multiple cash transactions within the same account in a day totalling RM25,000 or above.", "deadline": "CTR submission is mandatory for in-scope institutions. The current public BNM pages checked in mapped sources verify threshold/scope but do not expose one universal filing-day clock, so no universal numeric deadline is shown.", "recipient": "Bank Negara Malaysia", "submission": "BNM/FINS reporting route as applicable.", "applicability": "Current BNM threshold/scope verified 18 Aug 2026.", "consequence": "Non-reporting can lead to AMLA/BNM enforcement; exact consequence is breach-specific.", "enforcement": "Bank Negara Malaysia", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash aggregation controls should apply the BNM same-account/day threshold and keep any deadline configuration linked to the operative reporting specification.", "evidenceIds": [ "amlb:evidence:1c00876c", "amlb:evidence:f5f32d08" ], "sourceEntityIds": [ "amlb:source-entity:995e2d48" ] }, { "id": "MY-CO-NOTIFY", "jurisdictionCode": "MY", "jurisdictionName": "Malaysia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Compliance Officer appointment/change notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions required to appoint an AML/CFT Compliance Officer.", "trigger": "Appointment of, or change to, the Compliance Officer.", "deadline": "Within 10 working days from the date of appointment or change.", "recipient": "Bank Negara Malaysia", "submission": "Written notification; BNM provides physical/online forms for DNFBP/NBFI reporters.", "applicability": "Current BNM notification rule verified 18 Aug 2026.", "consequence": "Failure to comply may result in supervisory action under the applicable AMLA/BNM framework.", "enforcement": "Bank Negara Malaysia", "evidenceStatus": "verified", "evidenceNote": "BNM’s current Compliance Officer page states the 10-working-day notification rule.", "operationalImpact": "HR/governance changes affecting the AML Compliance Officer should trigger an automatic regulatory-notification workflow.", "evidenceIds": [ "amlb:evidence:5cb7d9da" ], "sourceEntityIds": [ "amlb:source-entity:995e2d48" ] }, { "id": "MY-AMLPROGRAM", "jurisdictionCode": "MY", "jurisdictionName": "Malaysia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT/CPF compliance programme and risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting institutions within the applicable BNM policy documents.", "trigger": "Continuous while conducting regulated/reporting-institution activities.", "deadline": "Ongoing; controls and risk assessment must be maintained and regularly assessed rather than filed on one universal date.", "recipient": "Bank Negara Malaysia", "submission": "Internal programme with supervisory evidence/submissions as required.", "applicability": "Current policy framework verified 18 Aug 2026.", "consequence": "Weak controls may lead to BNM supervisory/enforcement action under AMLA and sector legislation.", "enforcement": "Bank Negara Malaysia", "evidenceStatus": "verified", "evidenceNote": "Current BNM policy documents and Compliance Officer guidance confirm ongoing control responsibilities.", "operationalImpact": "Maintain current risk assessment, policies, screening/monitoring, governance, training and assurance.", "evidenceIds": [ "amlb:evidence:553f6186", "amlb:evidence:ecb6a98a" ], "sourceEntityIds": [ "amlb:source-entity:995e2d48" ] }, { "id": "TH-REPORTING", "jurisdictionCode": "TH", "jurisdictionName": "Thailand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "AMLO transaction / suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons with reporting duties under Thailand’s Anti-Money Laundering Act and implementing rules.", "trigger": "A transaction falls into a statutory reportable category or meets the suspicious-transaction standard.", "deadline": "Report within the timeframe prescribed for the relevant transaction category. Mapped sources do not collapse category-specific Thai rules into one universal day-count.", "recipient": "Anti-Money Laundering Office (AMLO)", "submission": "AMLO prescribed reporting forms/systems for the relevant reporter category.", "applicability": "Current AMLO legal directory reviewed 18 Aug 2026.", "consequence": "Late/non-reporting can attract statutory or supervisory consequences under the AML Act and applicable regulations.", "enforcement": "AMLO", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map each business transaction type to the correct AMLO report/form and deadline rather than using one firm-wide generic STR clock.", "evidenceIds": [ "amlb:evidence:1203613d" ], "sourceEntityIds": [ "amlb:source-entity:203a17db" ] }, { "id": "TH-CDD-CONTROLS", "jurisdictionCode": "TH", "jurisdictionName": "Thailand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Customer due diligence and internal AML controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting persons within Thailand’s CDD/internal-control framework.", "trigger": "Continuous while conducting regulated/reporting business, with enhanced measures when risk triggers arise.", "deadline": "Ongoing; no single fixed-date filing.", "recipient": "AMLO / relevant sector supervisor", "submission": "Internal policies, CDD, monitoring and records; reports to AMLO when relevant triggers arise.", "applicability": "Current AMLO guidance corpus reviewed 18 Aug 2026.", "consequence": "Control failures may result in AMLO/sector-supervisor enforcement under applicable law.", "enforcement": "AMLO / sector supervisor", "evidenceStatus": "verified", "evidenceNote": "Current AMLO directory includes the CDD Regulation 2020 and reporting-person guidance.", "operationalImpact": "Maintain risk-based CDD, transaction monitoring, internal escalation and reporting procedures as continuous controls.", "evidenceIds": [ "amlb:evidence:1203613d" ], "sourceEntityIds": [ "amlb:source-entity:203a17db" ] }, { "id": "TH-DA-TRAVEL-RULE-2027", "jurisdictionCode": "TH", "jurisdictionName": "Thailand", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Digital asset Travel Rule commencement", "timingType": "scheduled", "sectors": [ "virtual-assets" ], "appliesTo": "Digital asset business operators regulated by the Securities and Exchange Commission of Thailand.", "trigger": "Commencement of SEC Travel Rule regulations for transfers and receipts of digital assets.", "deadline": "27 February 2027.", "recipient": "Securities and Exchange Commission of Thailand / supervisory records; suspicious transaction obligations remain within the applicable AMLO framework.", "submission": "Implement internal transfer-information, counterparty due-diligence, self-hosted-wallet verification and record-retention controls; this entry is an effective-date trigger rather than a periodic filing.", "applicability": "Final SEC regulations announced 2 September 2026; effective 27 February 2027.", "consequence": "Non-compliance after commencement may lead to SEC supervisory or enforcement consequences under the applicable digital-asset regulatory framework.", "enforcement": "Securities and Exchange Commission of Thailand, with AML coordination with AMLO.", "evidenceStatus": "verified", "operationalImpact": "Complete Travel Rule data capture/transmission, counterparty-VASP controls, self-hosted-wallet ownership/control verification and five-year retention implementation before 27 February 2027.", "evidenceIds": [ "amlb:evidence:7c1a395c" ], "sourceEntityIds": [ "amlb:source-entity:6f99ac75" ] }, { "id": "PH-CTR-STR", "jurisdictionCode": "PH", "jurisdictionName": "Philippines", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Covered and Suspicious Transaction Reports (CTR / STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Covered persons under the AMLA and current implementing rules.", "trigger": "A covered transaction meets the statutory threshold/category or a suspicious transaction trigger is established.", "deadline": "Submit within the prescribed AMLA/IRR reporting period. Exact day-count is not verified in mapped current rules.", "recipient": "Anti-Money Laundering Council (AMLC)", "submission": "AMLC electronic reporting/portal infrastructure.", "applicability": "Current AMLC reporting framework reviewed 18 Aug 2026.", "consequence": "Failure to submit required reports can result in AMLA administrative/criminal/regulatory consequences depending on the breach and covered person.", "enforcement": "AMLC / appropriate supervising authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Covered-person systems should separately identify CTR threshold events and STR suspicion events and route both through the current AMLC reporting format.", "evidenceIds": [ "amlb:evidence:ee6197f6", "amlb:evidence:7a0f6f6b" ], "sourceEntityIds": [ "amlb:source-entity:4f3bc233" ] }, { "id": "PH-AMLPROGRAM", "jurisdictionCode": "PH", "jurisdictionName": "Philippines", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML compliance programme and CDD controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Covered persons under the AMLA and applicable sector/AMLC rules.", "trigger": "Continuous covered-person activity.", "deadline": "Ongoing; no universal fixed filing date.", "recipient": "AMLC / appropriate supervising authority", "submission": "Internal AML programme and records; regulatory filings where specifically required.", "applicability": "Current framework reviewed 18 Aug 2026.", "consequence": "Deficiencies may result in AMLC/sector-supervisor enforcement depending on the violated duty.", "enforcement": "AMLC / sector supervisor", "evidenceStatus": "verified", "evidenceNote": "Current AMLC legal corpus supports the standing preventive-controls framework.", "operationalImpact": "Maintain risk-based CDD, BO identification, monitoring, records, training and reporting governance as ongoing controls.", "evidenceIds": [ "amlb:evidence:ee6197f6" ], "sourceEntityIds": [ "amlb:source-entity:4f3bc233" ] }, { "id": "PK-STR", "jurisdictionCode": "PK", "jurisdictionName": "Pakistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the AML Act and Suspicious Transaction / Currency Transaction Reporting Regulations 2025.", "trigger": "Suspicion is formed after internal review under the applicable reporting-entity process.", "deadline": "Promptly after suspicion is formed.", "recipient": "Financial Monitoring Unit (FMU)", "submission": "goAML / FMU reporting mechanism prescribed by the 2025 Regulations.", "applicability": "Current 2025 reporting regulations.", "consequence": "Non-compliance can lead to sanctions under the AML Act/regulatory framework; consequence depends on the entity and breach.", "enforcement": "FMU / relevant AML supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation must be designed to prevent unnecessary delay after the reporting decision is reached.", "evidenceIds": [ "amlb:evidence:43472239", "amlb:evidence:eee446b1", "amlb:evidence:3d65a639" ], "sourceEntityIds": [ "amlb:source-entity:522f523a", "amlb:source-entity:b9665198" ] }, { "id": "PK-CTR", "jurisdictionCode": "PK", "jurisdictionName": "Pakistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the currency transaction reporting regime.", "trigger": "Cash transaction at or above the threshold specified under the applicable AML reporting framework.", "deadline": "Immediately, but not later than 7 working days after the transaction.", "recipient": "Financial Monitoring Unit (FMU)", "submission": "goAML / prescribed FMU reporting mechanism.", "applicability": "Current 2025 regulations.", "consequence": "Late/non-reporting can lead to AML regulatory sanctions; threshold amount should be taken from the operative current rule/configuration applicable to the reporter.", "enforcement": "FMU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash monitoring should preserve transaction date and apply the operative threshold while enforcing the seven-working-day outer limit.", "evidenceIds": [ "amlb:evidence:43472239" ], "sourceEntityIds": [ "amlb:source-entity:522f523a" ] }, { "id": "PK-RISK", "jurisdictionCode": "PK", "jurisdictionName": "Pakistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Risk-based reporting controls and AML programme", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under the AML Act and sector regulations.", "trigger": "Continuous regulated activity.", "deadline": "Ongoing; no single filing date.", "recipient": "Relevant AML supervisor / FMU for intelligence reports", "submission": "Internal policies, controls, monitoring and governance.", "applicability": "Current framework reviewed 18 Aug 2026.", "consequence": "Control failures may lead to supervisory and AML Act sanctions.", "enforcement": "Relevant AML supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain documented risk-based transaction monitoring, escalation and reporting governance.", "evidenceIds": [ "amlb:evidence:3d65a639", "amlb:evidence:43472239" ], "sourceEntityIds": [ "amlb:source-entity:b9665198", "amlb:source-entity:522f523a" ] }, { "id": "PK-VASP-AML-CFT", "jurisdictionCode": "PK", "jurisdictionName": "Pakistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Licensed VASP AML/CFT/CPF programme", "timingType": "ongoing", "sectors": [ "virtual-assets" ], "appliesTo": "Virtual Asset Service Providers licensed by the Pakistan Virtual Assets Regulatory Authority (PVARA).", "trigger": "Continuous while carrying on licensed virtual-asset services; suspicious activity creates an immediate reporting trigger.", "deadline": "Ongoing CDD and transaction monitoring; retain customer and transaction records for at least 10 years; report suspicious transactions or activities to FMU immediately.", "recipient": "Pakistan Virtual Assets Regulatory Authority (PVARA) / Financial Monitoring Unit (FMU)", "submission": "Maintain the VASP AML/CFT/CPF control framework and records; submit suspicious-activity reports to FMU through the applicable reporting mechanism.", "applicability": "Pakistan Virtual Asset Services Regulations, 2026 notified 21 August 2026.", "consequence": "Breach can trigger supervisory or enforcement action under the Virtual Assets Act, PVARA regulations and applicable AML framework.", "enforcement": "PVARA / FMU / other competent AML authorities", "evidenceStatus": "verified", "operationalImpact": "VASP compliance programmes should combine onboarding KYC, ongoing due diligence, real-time transaction monitoring, sanctions screening, ten-year record retention and immediate suspicious-activity escalation.", "evidenceIds": [ "amlb:evidence:83130bce" ], "sourceEntityIds": [ "amlb:source-entity:28a6db80" ] }, { "id": "BD-STR", "jurisdictionCode": "BD", "jurisdictionName": "Bangladesh", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Suspicious Transaction / Activity Report (STR/SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting organisations under the Money Laundering Prevention Act and BFIU circular/guidance framework.", "trigger": "Suspicion is identified under the applicable BFIU reporting standard.", "deadline": "Report in accordance with the current BFIU STR/SAR guidance. No universal day-count is verified in mapped sources.", "recipient": "Bangladesh Financial Intelligence Unit (BFIU)", "submission": "BFIU electronic/reporting process under current guidance.", "applicability": "Current BFIU guidance repository reviewed 18 Aug 2026.", "consequence": "Failure to report can trigger AML statutory and supervisory consequences; exact penalty depends on the duty and reporter.", "enforcement": "BFIU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Institutions should map internal suspicion decisioning to the current BFIU reporting instruction rather than rely on legacy circular summaries.", "evidenceIds": [ "amlb:evidence:c28eb8b5", "amlb:evidence:6e5c9db2" ], "sourceEntityIds": [ "amlb:source-entity:672da5ec" ] }, { "id": "BD-CTR", "jurisdictionCode": "BD", "jurisdictionName": "Bangladesh", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Cash Transaction Reporting (CTR)", "timingType": "supervisor-driven", "sectors": [ "all" ], "appliesTo": "Reporting organisations within the BFIU cash-transaction reporting regime.", "trigger": "Reportable cash transactions under the operative BFIU threshold/circular.", "deadline": "No public due date or filing cycle verified.", "recipient": "BFIU", "submission": "BFIU reporting infrastructure.", "applicability": "BFIU Circular Letter No. 01 introduced a temporary weekly CTR cadence from 11 January 2026; Circular Letter No. 04 cancelled it with effect from 1 March 2026. Current reporting reverts to the Circular No. 26 framework.", "consequence": "Late/non-reporting may lead to BFIU/supervisory enforcement under the AML framework.", "enforcement": "BFIU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not continue the cancelled January–February 2026 weekly CTR cadence. Keep current CTR configuration tied to BFIU Circular No. 26 and any later operative instruction.", "evidenceIds": [ "amlb:evidence:1a85b1b6", "amlb:evidence:6e5c9db2", "amlb:evidence:c28eb8b5", "amlb:evidence:76c520ca", "amlb:evidence:a7e4151d" ], "sourceEntityIds": [ "amlb:source-entity:672da5ec" ] }, { "id": "BD-BFIU-FREEZE-RELATED-ACCOUNTS", "jurisdictionCode": "BD", "jurisdictionName": "Bangladesh", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Related-account notification after a BFIU freezing order", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting organisations receiving an account-freezing order from the Bangladesh Financial Intelligence Unit.", "trigger": "Receipt of a BFIU order freezing an account.", "deadline": "Immediately notify BFIU of the frozen account and information on other related accounts.", "recipient": "Bangladesh Financial Intelligence Unit (BFIU)", "submission": "Notification to BFIU under Circular Letter No. 5; the mapped source does not specify a separate electronic channel.", "applicability": "Circular Letter No. 5 issued 19 August 2026; no separate later commencement date is stated in the mapped source.", "consequence": "Failure to follow BFIU directions may trigger consequences under the applicable AML/CFT statutory and supervisory framework.", "enforcement": "BFIU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Freezing-order procedures should include immediate related-account identification and escalation to BFIU, rather than treating the named frozen account as the only reporting object.", "evidenceIds": [ "amlb:evidence:eda8858a" ], "sourceEntityIds": [ "amlb:source-entity:672da5ec" ] }, { "id": "LK-STR", "jurisdictionCode": "LK", "jurisdictionName": "Sri Lanka", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Institutions/persons subject to section 7 FTRA and applicable FIU-Sri Lanka sector rules.", "trigger": "Reasonable grounds to suspect a transaction or attempted transaction may relate to unlawful activity or another criminal offence.", "deadline": "As soon as practicable, but no later than 2 working days after forming the suspicion (or receiving the relevant information under the applicable guidance).", "recipient": "Financial Intelligence Unit of Sri Lanka (FIU-SL)", "submission": "Schedule V STR format; FIU guidance lists mail, telephone followed in writing within 24 hours, fax or email.", "applicability": "Current FIU-SL guidance reviewed 18 Aug 2026.", "consequence": "Failure to report can result in statutory/supervisory consequences under the FTRA and applicable sector framework.", "enforcement": "FIU-SL / relevant sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal case review and approval should be calibrated to complete external reporting within two working days.", "evidenceIds": [ "amlb:evidence:f2516709", "amlb:evidence:f0e6af84" ], "sourceEntityIds": [ "amlb:source-entity:58df87e3" ] }, { "id": "LK-AML-CONTROLS", "jurisdictionCode": "LK", "jurisdictionName": "Sri Lanka", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk management, training and preventive controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting institutions/persons under the FTRA and applicable FIU rules.", "trigger": "Continuous while carrying on covered activity.", "deadline": "Ongoing; no universal fixed filing date.", "recipient": "FIU-Sri Lanka / relevant supervisor", "submission": "Internal controls and records; reporting to FIU on event-based triggers.", "applicability": "Current framework reviewed 18 Aug 2026, including August 2026 AML/CFT amendments in the source corpus.", "consequence": "Control deficiencies may lead to FIU/supervisory enforcement depending on sector and breached provision.", "enforcement": "FIU-SL / sector supervisor", "evidenceStatus": "verified", "evidenceNote": "Current FIU legal corpus and sector guidance establish preventive controls, training and reporting governance.", "operationalImpact": "Maintain documented CDD, risk assessment, monitoring, reporting procedures and regular AML/CFT training.", "evidenceIds": [ "amlb:evidence:bdadb926", "amlb:evidence:f0e6af84" ], "sourceEntityIds": [ "amlb:source-entity:58df87e3" ] }, { "id": "NP-STR", "jurisdictionCode": "NP", "jurisdictionName": "Nepal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction / Activity Report (STR/SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Nepal’s AML framework when a suspicious transaction/activity is detected.", "trigger": "Suspicion is detected or relevant information is received under the FIU reporting standard.", "deadline": "As soon as possible, but no later than 3 working days.", "recipient": "Financial Intelligence Unit – Nepal (FIU-Nepal)", "submission": "goAML / FIU-Nepal reporting system.", "applicability": "Current FIU-Nepal guidance verified 18 Aug 2026.", "consequence": "Late/non-reporting may trigger statutory and supervisory consequences under Nepal’s AML framework.", "enforcement": "FIU-Nepal / relevant supervisor", "evidenceStatus": "verified", "evidenceNote": "Current FIU-Nepal guidance states the three-working-day outer limit.", "operationalImpact": "Escalation and approval procedures should fit within a three-working-day external filing window.", "evidenceIds": [ "amlb:evidence:1e32bdb0", "amlb:evidence:fdddda8d" ], "sourceEntityIds": [ "amlb:source-entity:490f3ff0", "amlb:source-entity:6d936b66" ] }, { "id": "NP-TTR", "jurisdictionCode": "NP", "jurisdictionName": "Nepal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities handling transactions above the FIU-prescribed threshold.", "trigger": "Transaction exceeds the prescribed threshold under the applicable FIU rule.", "deadline": "Within 15 days of the transaction date.", "recipient": "FIU-Nepal", "submission": "goAML.", "applicability": "Current FIU guidance verified 18 Aug 2026.", "consequence": "Non-reporting/late reporting can lead to AML supervisory/statutory consequences.", "enforcement": "FIU-Nepal / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Threshold monitoring should preserve the transaction date and current FIU threshold configuration to calculate the 15-day deadline.", "evidenceIds": [ "amlb:evidence:1e32bdb0", "amlb:evidence:d8406306" ], "sourceEntityIds": [ "amlb:source-entity:490f3ff0" ] }, { "id": "NP-RISK", "jurisdictionCode": "NP", "jurisdictionName": "Nepal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk assessment and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under Nepal’s AML/CFT framework.", "trigger": "Continuous covered activity and changes in risk.", "deadline": "Ongoing; no single fixed-date filing asserted.", "recipient": "Relevant supervisor / FIU-Nepal for reports", "submission": "Internal risk assessment, CDD, monitoring and governance.", "applicability": "Current framework reviewed 18 Aug 2026.", "consequence": "Deficiencies may lead to sector supervisory and AML statutory action.", "enforcement": "Relevant supervisor / FIU-Nepal", "evidenceStatus": "verified", "evidenceNote": "Existing official Nepal evidence supports standing AML controls alongside event-driven reporting.", "operationalImpact": "Maintain documented risk-based CDD, monitoring and reporting governance with periodic updates when risk changes.", "evidenceIds": [ "amlb:evidence:fdddda8d", "amlb:evidence:1e32bdb0" ], "sourceEntityIds": [ "amlb:source-entity:6d936b66", "amlb:source-entity:490f3ff0" ] }, { "id": "VN-STR", "jurisdictionCode": "VN", "jurisdictionName": "Vietnam", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the 2022 Law on Anti-Money Laundering and implementing regulations.", "trigger": "A transaction/activity meets the statutory suspicious-transaction criteria.", "deadline": "Report within the period required by the Law and implementing rules. Current implementing text does not verify one universal numeric clock.", "recipient": "State Bank of Vietnam · Anti-Money Laundering Department", "submission": "AMLD / State Bank reporting system and prescribed forms.", "applicability": "Law No. 14/2022/QH15 remains the current AML framework; amendments under Law No. 23/2026/QH16 take effect on 1 Dec 2026.", "consequence": "Failure to report may lead to administrative/supervisory consequences under Vietnamese AML and sector law.", "enforcement": "State Bank of Vietnam / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Transaction monitoring should route suspicion events to the AMLD reporting process and record the trigger date for statutory timeliness.", "evidenceIds": [ "amlb:evidence:edc43023", "amlb:evidence:f1b1682c", "amlb:evidence:56604c4c" ], "sourceEntityIds": [ "amlb:source-entity:fd62c5d1", "amlb:source-entity:e19fde85" ] }, { "id": "VN-AML-CONTROLS", "jurisdictionCode": "VN", "jurisdictionName": "Vietnam", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Risk-based AML internal rules, CDD and monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under Law No. 14/2022/QH15.", "trigger": "Continuous covered activity and risk changes.", "deadline": "Ongoing; no one universal filing date.", "recipient": "State Bank of Vietnam / competent sector authority", "submission": "Internal AML regulations, risk management, CDD, monitoring and records; external reports on prescribed triggers.", "applicability": "Law No. 14/2022/QH15 remains the current AML framework; amendments under Law No. 23/2026/QH16 take effect on 1 Dec 2026.", "consequence": "Control failures may lead to administrative and supervisory action under applicable law.", "enforcement": "State Bank of Vietnam / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain internal AML rules, customer-risk classification, CDD, monitoring, reporting and records as standing controls.", "evidenceIds": [ "amlb:evidence:edc43023", "amlb:evidence:f1b1682c", "amlb:evidence:56604c4c" ], "sourceEntityIds": [ "amlb:source-entity:fd62c5d1", "amlb:source-entity:e19fde85" ] }, { "id": "KH-STR", "jurisdictionCode": "KH", "jurisdictionName": "Cambodia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Cambodia’s AML/CFT law and applicable CAFIU regulations/guidelines.", "trigger": "Suspicious transaction/activity trigger under the AML/CFT framework.", "deadline": "Report according to the current CAFIU STR guideline; the mapped source set does not assert a numeric universal filing clock without verifying the current guideline provision.", "recipient": "Cambodia Financial Intelligence Unit (CAFIU)", "submission": "CAFIU prescribed STR submission method.", "applicability": "Current CAFIU legal directory reviewed 18 Aug 2026.", "consequence": "Failure to report can lead to statutory/supervisory consequences under Cambodia’s AML/CFT regime.", "enforcement": "CAFIU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented internal escalation path and configure the external filing SLA only from the current CAFIU guideline.", "evidenceIds": [ "amlb:evidence:dd249474", "amlb:evidence:d8df8d71" ], "sourceEntityIds": [ "amlb:source-entity:cf6f3c44" ] }, { "id": "KH-AML-CONTROLS", "jurisdictionCode": "KH", "jurisdictionName": "Cambodia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT internal controls and risk-based CDD", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Cambodia’s AML/CFT regime.", "trigger": "Continuous covered activity.", "deadline": "Ongoing; no universal fixed-date filing.", "recipient": "CAFIU / sector supervisor", "submission": "Internal risk assessment, CDD, monitoring and reporting procedures.", "applicability": "Current framework reviewed 18 Aug 2026.", "consequence": "Deficiencies may lead to supervisory/administrative sanctions under the applicable AML/CFT rules.", "enforcement": "CAFIU / sector supervisor", "evidenceStatus": "verified", "evidenceNote": "Current CAFIU legal/publication corpus supports ongoing preventive obligations.", "operationalImpact": "Maintain risk-based CDD, BO identification, monitoring, records, training and reporting governance.", "evidenceIds": [ "amlb:evidence:dd249474", "amlb:evidence:218541f6" ], "sourceEntityIds": [ "amlb:source-entity:cf6f3c44" ] }, { "id": "BN-STR", "jurisdictionCode": "BN", "jurisdictionName": "Brunei", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within Brunei Darussalam’s AML/CFT framework.", "trigger": "Suspicious transaction/activity trigger under the applicable legislation and BDCB guidance.", "deadline": "Report within the timeframe required by the current STR guideline. Exact numeric clock is not verified in mapped guideline provisions.", "recipient": "Financial Intelligence Unit, Brunei Darussalam Central Bank (BDCB)", "submission": "Integrated Financial Intelligence System (IFIS), including web-form/XML functionality.", "applicability": "Current BDCB reporting framework reviewed 18 Aug 2026.", "consequence": "Failure to report can lead to statutory/supervisory consequences under the applicable AML/CFT regime.", "enforcement": "BDCB / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Reporting entities should maintain IFIS access and internal escalation capable of meeting the operative STR guideline clock.", "evidenceIds": [ "amlb:evidence:e10cb904", "amlb:evidence:31a3f719" ], "sourceEntityIds": [ "amlb:source-entity:c197ca12", "amlb:source-entity:362d5046" ] }, { "id": "BN-CTR", "jurisdictionCode": "BN", "jurisdictionName": "Brunei", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the BDCB cash-transaction reporting regime.", "trigger": "A cash transaction meets the threshold/conditions prescribed in current BDCB guidance.", "deadline": "Submit within the applicable CTR reporting period. Exact threshold and day-count are not shown as a fixed value in the mapped source set without current guideline-level confirmation.", "recipient": "BDCB Financial Intelligence Unit", "submission": "IFIS.", "applicability": "Current BDCB reporting page reviewed 18 Aug 2026.", "consequence": "Late/non-reporting may result in statutory/supervisory action.", "enforcement": "BDCB", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash controls should remain parameterised to the current BDCB threshold and reporting specification.", "evidenceIds": [ "amlb:evidence:e10cb904" ], "sourceEntityIds": [ "amlb:source-entity:c197ca12" ] }, { "id": "MN-STR", "jurisdictionCode": "MN", "jurisdictionName": "Mongolia", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Suspicious Transaction Report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Mongolia’s Law on Combating Money Laundering and Terrorism Financing.", "trigger": "Reasonable suspicion/reportable suspicious transaction under the AML/CFT Law.", "deadline": "Within 24 hours.", "recipient": "Financial Information Unit (FIU), Bank of Mongolia", "submission": "FIU-prescribed reporting method.", "applicability": "Official law text mapped and reviewed 18 Aug 2026.", "consequence": "Failure to comply can result in sanctions under the AML/CFT Law and sector supervisory framework.", "enforcement": "FIU / Bank of Mongolia and relevant supervisor", "evidenceStatus": "verified", "evidenceNote": "Official law text states the 24-hour reporting period.", "operationalImpact": "Escalation and approval must be designed for a 24-hour external reporting clock.", "evidenceIds": [ "amlb:evidence:135b9a9c" ], "sourceEntityIds": [ "amlb:source-entity:24b83c12" ] }, { "id": "MN-THRESHOLD", "jurisdictionCode": "MN", "jurisdictionName": "Mongolia", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Large cash / foreign-settlement transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities handling transactions within the statutory threshold-reporting rule.", "trigger": "Cash and/or qualifying foreign-settlement transaction of MNT 20 million or more under the official AML/CFT Law text.", "deadline": "Within 5 working days.", "recipient": "Financial Information Unit (FIU), Bank of Mongolia", "submission": "FIU-prescribed report.", "applicability": "Official law text reviewed 18 Aug 2026.", "consequence": "Late/non-reporting may attract sanctions under the AML/CFT Law.", "enforcement": "FIU / relevant supervisor", "evidenceStatus": "verified", "evidenceNote": "Official law states both MNT 20 million threshold and five-working-day period.", "operationalImpact": "Transaction systems should detect the statutory threshold and preserve the transaction date to calculate the five-working-day deadline.", "evidenceIds": [ "amlb:evidence:135b9a9c" ], "sourceEntityIds": [ "amlb:source-entity:24b83c12" ] }, { "id": "MN-RISK", "jurisdictionCode": "MN", "jurisdictionName": "Mongolia", "coverageStatus": "verified", "lastReviewedDate": "2026-08-18", "title": "Risk-based AML/CFT controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under Mongolia’s AML/CFT Law.", "trigger": "Continuous reporting-entity activity and risk changes.", "deadline": "Ongoing; no single fixed-date filing.", "recipient": "Relevant supervisor / FIU", "submission": "Internal risk assessment, CDD, monitoring and reporting controls.", "applicability": "Current law framework reviewed 18 Aug 2026.", "consequence": "Control deficiencies may lead to AML/CFT supervisory/statutory sanctions.", "enforcement": "Relevant supervisor / FIU", "evidenceStatus": "verified", "evidenceNote": "Official law contains risk-based preventive and reporting obligations.", "operationalImpact": "Maintain risk assessment, CDD, monitoring, recordkeeping and reporting procedures as continuous controls.", "evidenceIds": [ "amlb:evidence:135b9a9c" ], "sourceEntityIds": [ "amlb:source-entity:24b83c12" ] }, { "id": "TW-CASH", "jurisdictionCode": "TW", "jurisdictionName": "Taiwan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Large cash transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions subject to the FSC cash-transaction reporting regulation.", "trigger": "Cash transaction above the amount defined by the applicable regulation.", "deadline": "Within 5 business days after completion of the transaction.", "recipient": "Investigation Bureau, Ministry of Justice", "submission": "Electronic media; hard-copy only with approval where electronic filing is unavailable for good cause.", "applicability": "Current FSC English regulation page reviewed 18 Aug 2026.", "consequence": "Non-compliance may result in administrative sanctions under the Money Laundering Control Act and financial-sector rules.", "enforcement": "Financial Supervisory Commission / Investigation Bureau", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash reporting systems should preserve completion date and use the current regulatory threshold configuration.", "evidenceIds": [ "amlb:evidence:5adab50a", "amlb:evidence:7c0f647f" ], "sourceEntityIds": [ "amlb:source-entity:55c5b281", "amlb:source-entity:9bdfa64d" ] }, { "id": "TW-STR", "jurisdictionCode": "TW", "jurisdictionName": "Taiwan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions within the FSC suspicious-transaction reporting regulation.", "trigger": "Discovery of a transaction suspected of money laundering; attempted transactions are also reportable where the regulatory criteria are met.", "deadline": "Responsible head-office section prepares the STR within 10 business days upon discovery and, after required approval, promptly files it. Obvious, significant and urgent cases should be reported promptly by fax or other feasible means.", "recipient": "Investigation Bureau, Ministry of Justice", "submission": "Prescribed STR process; urgent cases may use fax/other feasible means under Article 8.", "applicability": "Current FSC regulation reviewed 18 Aug 2026.", "consequence": "Current Money Laundering Control Act provides administrative fines for reporting/control violations; exact amount depends on entity type and breached provision.", "enforcement": "Financial Supervisory Commission / Investigation Bureau", "evidenceStatus": "verified-with-gap", "operationalImpact": "Internal review/approval should be completed within the ten-business-day rule and urgent cases must bypass normal queues for prompt reporting.", "evidenceIds": [ "amlb:evidence:5adab50a", "amlb:evidence:7c0f647f" ], "sourceEntityIds": [ "amlb:source-entity:55c5b281", "amlb:source-entity:9bdfa64d" ] }, { "id": "TW-AML-CONTROLS", "jurisdictionCode": "TW", "jurisdictionName": "Taiwan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Financial institution AML/CFT controls and records", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions under the Money Laundering Control Act and FSC AML framework.", "trigger": "Continuous regulated activity.", "deadline": "Ongoing; transaction reporting and customer-control duties operate continuously.", "recipient": "Financial Supervisory Commission / Investigation Bureau", "submission": "Internal controls/records plus prescribed external reporting.", "applicability": "Current legal framework reviewed 18 Aug 2026.", "consequence": "Violations can lead to administrative fines and sector supervisory action under current law.", "enforcement": "FSC / competent authorities", "evidenceStatus": "verified", "operationalImpact": "Maintain documented CDD, monitoring, records and reporting procedures, including annual review where specifically required by the reporting regulation.", "evidenceIds": [ "amlb:evidence:7c0f647f", "amlb:evidence:5adab50a" ], "sourceEntityIds": [ "amlb:source-entity:9bdfa64d", "amlb:source-entity:55c5b281" ] }, { "id": "US-SAR", "jurisdictionCode": "US", "jurisdictionName": "United States", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers when their sector-specific SAR rule is triggered.", "trigger": "Detection of facts meeting the applicable suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 days where no suspect is identified under the applicable rule.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework verified 19 Aug 2026.", "consequence": "Missing or late SARs can lead to FinCEN civil enforcement and, depending on the conduct, other regulatory or criminal consequences.", "enforcement": "FinCEN and the relevant functional regulator / law-enforcement authority", "evidenceStatus": "verified", "evidenceNote": "FinCEN’s current SAR material confirms the 30-day initial filing timeline; filer thresholds remain sector-specific.", "operationalImpact": "Preserve the initial-detection date and escalate investigations early enough to meet the federal SAR clock.", "evidenceIds": [ "amlb:evidence:4fde97d7", "amlb:evidence:83c2e6fd", "amlb:evidence:70676487" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:1acba317" ] }, { "id": "US-CTR", "jurisdictionCode": "US", "jurisdictionName": "United States", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation/exemptions.", "deadline": "Within 15 calendar days of the reportable transaction(s).", "recipient": "FinCEN", "submission": "BSA E-Filing System.", "applicability": "Current clock verified 19 Aug 2026.", "consequence": "Late or missing CTRs can lead to FinCEN enforcement and civil monetary penalties.", "enforcement": "FinCEN", "evidenceStatus": "verified", "operationalImpact": "Cash aggregation controls should retain the business-day context used for filing.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "US-BOI-FOREIGN", "jurisdictionCode": "US", "jurisdictionName": "United States", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Beneficial Ownership Information (BOI) report — qualifying foreign companies", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Only qualifying foreign-formed entities registered to do business in a U.S. State or Tribal jurisdiction, unless exempt. U.S.-created companies are exempt.", "trigger": "Registration to do business or a later reportable change/correction under the applicable BOI rule.", "deadline": "Qualifying foreign reporting companies registered on/after 26 Mar 2025: initial report within 30 calendar days after notice that registration is effective.", "recipient": "FinCEN", "submission": "BOI E-Filing System.", "applicability": "Final rule effective 14 Aug 2026.", "consequence": "CTA penalties remain relevant only for persons/entities still subject to the revised rule; domestic U.S. companies are not represented as filers.", "enforcement": "FinCEN / U.S. Department of the Treasury", "evidenceStatus": "verified", "evidenceNote": "FinCEN’s August 2026 material states that U.S. companies are exempt and only qualifying foreign entities remain reporting companies.", "operationalImpact": "Determine foreign-formed reporting-company status before creating a BOI task.", "evidenceIds": [ "amlb:evidence:403b1eaf", "amlb:evidence:368879d1" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a" ] }, { "id": "US-BSA-PROGRAM", "jurisdictionCode": "US", "jurisdictionName": "United States", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "BSA/AML compliance program and risk controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other covered financial businesses according to their BSA program rule.", "trigger": "While conducting business subject to applicable BSA/AML program requirements.", "deadline": "Ongoing; governance, CDD, monitoring, recordkeeping and reporting controls are continuous rather than one universal filing date.", "recipient": "FinCEN and relevant supervisors", "submission": "Maintained internally and produced to supervisors/examiners as required.", "applicability": "Current framework verified 19 Aug 2026.", "consequence": "Program deficiencies may result in supervisory findings, remediation, civil money penalties or other enforcement.", "enforcement": "FinCEN and relevant functional regulator", "evidenceStatus": "verified", "operationalImpact": "Maintain a sector-specific control inventory instead of one homogeneous U.S. AML rule set.", "evidenceIds": [ "amlb:evidence:83c2e6fd", "amlb:evidence:70676487" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:1acba317" ] }, { "id": "CA-STR", "jurisdictionCode": "CA", "jurisdictionName": "Canada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "FINTRAC reporting entities when reasonable grounds to suspect are established.", "trigger": "Completion of measures enabling reasonable grounds to suspect ML/TF linkage.", "deadline": "As soon as practicable.", "recipient": "FINTRAC", "submission": "FINTRAC Web Reporting / supported API.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure to report can lead to administrative monetary penalties or criminal enforcement depending on the violation.", "enforcement": "FINTRAC / law enforcement where applicable", "evidenceStatus": "verified", "evidenceNote": "FINTRAC expressly uses the ‘as soon as practicable’ standard.", "operationalImpact": "Give STR completion priority once the statutory suspicion threshold is reached.", "evidenceIds": [ "amlb:evidence:d0277d53", "amlb:evidence:f1338d8e" ], "sourceEntityIds": [ "amlb:source-entity:f29f070e" ] }, { "id": "CA-LCTR", "jurisdictionCode": "CA", "jurisdictionName": "Canada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Large Cash Transaction Report (LCTR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "gambling" ], "appliesTo": "FINTRAC reporting entities receiving reportable cash.", "trigger": "Receipt of C$10,000 or more in cash, including applicable 24-hour aggregation.", "deadline": "Within 15 calendar days after the day the cash is received.", "recipient": "FINTRAC", "submission": "FINTRAC Web Reporting / API.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Late or omitted prescribed reports can attract administrative monetary penalties.", "enforcement": "FINTRAC", "evidenceStatus": "verified", "operationalImpact": "Preserve receipt date and aggregation relationships for deadline calculation.", "evidenceIds": [ "amlb:evidence:a8f8d76b" ], "sourceEntityIds": [ "amlb:source-entity:f29f070e" ] }, { "id": "CA-LVCTR", "jurisdictionCode": "CA", "jurisdictionName": "Canada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Large Virtual Currency Transaction Report (LVCTR)", "timingType": "event-driven", "sectors": [ "payments" ], "appliesTo": "Reporting entities receiving virtual currency within the LVCTR rules.", "trigger": "Receipt of C$10,000 or more in virtual currency, including applicable aggregation.", "deadline": "Within 5 working days after the day the amount is received.", "recipient": "FINTRAC", "submission": "FINTRAC reporting systems / API.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure to file may attract FINTRAC administrative monetary penalties.", "enforcement": "FINTRAC", "evidenceStatus": "verified", "operationalImpact": "Calculate the working-day clock separately from cash-report timing.", "evidenceIds": [ "amlb:evidence:86303e1b" ], "sourceEntityIds": [ "amlb:source-entity:f29f070e" ] }, { "id": "CA-EFTR", "jurisdictionCode": "CA", "jurisdictionName": "Canada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "International Electronic Funds Transfer Report (EFTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Reporting entities subject to international EFT reporting.", "trigger": "Initiating or finally receiving a reportable international EFT of C$10,000 or more, including applicable aggregation.", "deadline": "Within 5 business days after the day the transfer is initiated or finally received, as applicable.", "recipient": "FINTRAC", "submission": "FINTRAC Web Reporting / API.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure to report within the prescribed timing can be an AMP violation.", "enforcement": "FINTRAC", "evidenceStatus": "verified", "operationalImpact": "Record the initiation/final-receipt event used to start the deadline.", "evidenceIds": [ "amlb:evidence:edace9e1" ], "sourceEntityIds": [ "amlb:source-entity:f29f070e" ] }, { "id": "CA-COMPLIANCE", "jurisdictionCode": "CA", "jurisdictionName": "Canada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Compliance program, risk assessment and ongoing monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "FINTRAC reporting entities, with sector-specific application.", "trigger": "While carrying on activities that make the person/entity a reporting entity.", "deadline": "Ongoing; program, risk assessment, policies/procedures, training and effectiveness review requirements apply continuously or at prescribed intervals.", "recipient": "FINTRAC", "submission": "Maintained internally; material must be available for compliance examinations.", "applicability": "Current regime verified 19 Aug 2026.", "consequence": "Deficiencies can result in findings, compliance actions and administrative monetary penalties.", "enforcement": "FINTRAC", "evidenceStatus": "verified", "evidenceNote": "Program obligations are established federally; detailed cadence varies by requirement/sector.", "operationalImpact": "Maintain periodic review tasks and evidence for monitoring, training and risk-assessment updates.", "evidenceIds": [ "amlb:evidence:8b4ba358" ], "sourceEntityIds": [ "amlb:source-entity:f29f070e" ] }, { "id": "MX-AVISO", "jurisdictionCode": "MX", "jurisdictionName": "Mexico", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "LFPIORPI notice for reportable Vulnerable Activities", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Persons carrying out ‘Actividades Vulnerables’ when the applicable notice threshold/condition is met.", "trigger": "A transaction/act exceeds the notice threshold; a no-reportable-activity information filing is also required for applicable months.", "deadline": "No later than the 17th day of the following month; if the 17th is non-business, SAT treats the next business day as the limit.", "recipient": "UIF through Servicio de Administración Tributaria (SAT)", "submission": "SAT AML Prevention Portal.", "applicability": "Current post-2025/2026 framework verified 19 Aug 2026.", "consequence": "Non-compliance can trigger LFPIORPI administrative sanctions; amount depends on the violation.", "enforcement": "SAT / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain threshold logic and a monthly close distinguishing positive notices from no-activity reports.", "evidenceIds": [ "amlb:evidence:ea546c6a", "amlb:evidence:b10523a6", "amlb:evidence:d8ad595d" ], "sourceEntityIds": [ "amlb:source-entity:4030e58e", "amlb:source-entity:74daf88b" ] }, { "id": "MX-LFPIORPI-CONTROLS", "jurisdictionCode": "MX", "jurisdictionName": "Mexico", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Vulnerable-activity identification, beneficial-owner and record controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons performing activities covered by LFPIORPI.", "trigger": "While conducting covered vulnerable activities or business relationships.", "deadline": "Ongoing; identify/verify customers, obtain beneficial-owner information where applicable, retain records and apply current risk-based controls.", "recipient": "SAT / UIF", "submission": "Internal controls and SAT registration/reporting interfaces.", "applicability": "Current reforms verified 19 Aug 2026.", "consequence": "Breaches can result in LFPIORPI administrative sanctions and other legal consequences depending on conduct.", "enforcement": "SAT / UIF / competent authorities", "evidenceStatus": "verified", "evidenceNote": "SAT confirms customer identification and beneficial-owner duties; 2025/2026 reforms are captured in the source chain.", "operationalImpact": "Align DNFBP CDD procedures to current post-reform requirements.", "evidenceIds": [ "amlb:evidence:ea546c6a", "amlb:evidence:e21ade29", "amlb:evidence:d8ad595d" ], "sourceEntityIds": [ "amlb:source-entity:4030e58e", "amlb:source-entity:74daf88b" ] }, { "id": "BR-COAF-SUSP", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Communication of suspicious operation or situation to COAF", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Institutions authorised by Banco Central do Brasil under Circular 3,978/2020.", "trigger": "Decision, after monitoring/analysis, that an operation or situation should be communicated as suspicious.", "deadline": "By the next business day after the decision to communicate.", "recipient": "COAF", "submission": "Applicable COAF/Siscoaf reporting channel.", "applicability": "Current Circular text verified 19 Aug 2026.", "consequence": "Failure or late communication can lead to BCB administrative enforcement; sanctions depend on the breach.", "enforcement": "Banco Central do Brasil / COAF within their competencies", "evidenceStatus": "verified-with-gap", "operationalImpact": "Evidence the date of the communication decision because it starts the filing clock.", "evidenceIds": [ "amlb:evidence:0f4455ca", "amlb:evidence:7543e179" ], "sourceEntityIds": [ "amlb:source-entity:73d08f8d", "amlb:source-entity:38eddb4b" ] }, { "id": "BR-CASH50", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Communication of reportable cash operations", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "BCB-authorised institutions subject to Circular 3,978.", "trigger": "Cash deposit/contribution or withdrawal equal to or above R$50,000 and other art. 49 cash events.", "deadline": "By the next business day under the Circular’s cash-communication rule.", "recipient": "COAF", "submission": "Applicable COAF electronic channel.", "applicability": "Current text verified 19 Aug 2026.", "consequence": "Missing prescribed cash communications can result in BCB enforcement.", "enforcement": "Banco Central do Brasil", "evidenceStatus": "verified", "evidenceNote": "The Circular states the R$50,000 cash trigger and communication framework.", "operationalImpact": "Identify qualifying physical-cash events separately from suspicion-based reporting.", "evidenceIds": [ "amlb:evidence:08ebb84d" ], "sourceEntityIds": [ "amlb:source-entity:73d08f8d" ] }, { "id": "BR-CNO", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Comunicação de Não Ocorrência (CNO) — selected COAF-regulated sectors", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Directly COAF-regulated factoring and jewellery/precious-stones/metals sectors where no reportable events occurred in the reference year.", "trigger": "No reportable proposals, transactions or operations during the annual period.", "deadline": "For the 2025 reference period, by 31 Jan 2026. Future annual dates must be checked against that year’s notice.", "recipient": "COAF", "submission": "Siscoaf.", "applicability": "2026 deadline verified for 2025 reference year.", "consequence": "Failure to submit can result in an administrative sanction/fine after proceedings.", "enforcement": "COAF", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not roll this date forward mechanically; ingest each annual notice.", "evidenceIds": [ "amlb:evidence:a8f935c1", "amlb:evidence:cf8f099f" ], "sourceEntityIds": [ "amlb:source-entity:38eddb4b" ] }, { "id": "BR-AIR", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Internal ML/TF risk assessment and AML controls", "timingType": "ongoing", "sectors": [ "banking", "payments" ], "appliesTo": "Institutions authorised by Banco Central do Brasil within Circular 3,978.", "trigger": "Continuous operation and changes in risk profile/products/customers/channels.", "deadline": "Ongoing; internal risk assessment, policy, monitoring, CDD, training and effectiveness controls must be maintained.", "recipient": "Banco Central do Brasil", "submission": "Internal governance and supervisory evidence.", "applicability": "Current consolidated Circular verified 19 Aug 2026.", "consequence": "Deficiencies can lead to supervisory remediation and administrative sanction proceedings.", "enforcement": "Banco Central do Brasil", "evidenceStatus": "verified", "evidenceNote": "The Circular expressly requires a risk-based AML policy and internal risk assessment.", "operationalImpact": "Maintain documented risk categories, governance approval and effectiveness testing.", "evidenceIds": [ "amlb:evidence:0f4455ca" ], "sourceEntityIds": [ "amlb:source-entity:73d08f8d" ] }, { "id": "BR-SELFHOSTED-VA10", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Communication of qualifying self-hosted virtual-asset transfers", "timingType": "event-driven", "sectors": [ "banking", "payments", "virtual-assets" ], "appliesTo": "BCB-authorised institutions subject to Circular 3,978/2020 as amended by BCB Resolution 588/2026.", "trigger": "Transfer of virtual assets to or from a self-hosted wallet with value equal to or above the equivalent of US$10,000.", "deadline": "By the next business day under the Circular’s communication-of-specific-operations rule.", "recipient": "COAF", "submission": "Applicable COAF/Siscoaf reporting channel.", "applicability": "1 Oct 2026 under BCB Resolution 588/2026.", "consequence": "Failure to make a prescribed specific-operation communication can lead to BCB administrative enforcement under the applicable AML/CFT framework.", "enforcement": "Banco Central do Brasil / COAF within their competencies", "evidenceStatus": "verified", "evidenceNote": "Resolution 588/2026 adds the self-hosted-wallet threshold to Article 49 and sets 1 October 2026 commencement; the existing Circular reporting framework supplies the communication route and timing.", "operationalImpact": "Add the US$10,000-equivalent self-hosted-wallet threshold to specific-operation monitoring and reporting logic before 1 October 2026.", "evidenceIds": [ "amlb:evidence:786c73d6", "amlb:evidence:0f4455ca" ], "sourceEntityIds": [ "amlb:source-entity:73d08f8d" ] }, { "id": "BR-SUSEP-RES99-TRANSITION", "jurisdictionCode": "BR", "jurisdictionName": "Brazil", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "SUSEP Resolution No. 99/2026 AML/CFT/CPF framework transition", "timingType": "scheduled", "sectors": [ "insurance" ], "appliesTo": "SUSEP-supervised insurers, capitalisation companies, open pension entities, reinsurers, reinsurance brokers, insurance brokers and the additional supervised categories expressly brought into scope by Resolution No. 99/2026.", "trigger": "Publication of Resolution No. 99/2026 replacing Circular No. 612/2020.", "deadline": "Implement the updated framework by 1 January 2027, when Resolution No. 99/2026 enters into force and Circular No. 612/2020 is revoked.", "recipient": "Superintendência de Seguros Privados (SUSEP)", "submission": "No discrete filing identified in the official summary; implementation is through internal AML/CFT/CPF policies, risk assessment, CDD and control procedures subject to SUSEP supervision.", "applicability": "1 January 2027.", "consequence": "Non-compliance may be addressed through SUSEP supervisory and administrative enforcement under the applicable sector framework.", "enforcement": "Superintendência de Seguros Privados (SUSEP)", "evidenceStatus": "verified", "evidenceNote": "SUSEP’s official Resolution 99/2026 page confirms the replacement of Circular 612/2020 and the 1 January 2027 commencement.", "operationalImpact": "Complete gap analysis and update AML/CFT/CPF governance, internal risk assessment, CDD tiers, PEP/beneficial-owner procedures and higher-risk controls before commencement.", "evidenceIds": [ "amlb:evidence:e396d6a9" ], "sourceEntityIds": [ "amlb:source-entity:f8fcff89" ] }, { "id": "AR-ROS", "jurisdictionCode": "AR", "jurisdictionName": "Argentina", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "ROS-LA / RFT / RFP suspicious reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under article 20 of Law 25,246, subject to sector rules.", "trigger": "For ML: conclusion that the analysed operation is suspicious. For TF/PF: the relevant performed/attempted operation.", "deadline": "24 hours. ROS-LA: from conclusion that it is suspicious and not later than 90 calendar days from the performed/attempted operation. TF/PF: 24 hours from the performed/attempted operation.", "recipient": "Unidad de Información Financiera (UIF)", "submission": "UIF electronic reporting systems.", "applicability": "Current timing verified 19 Aug 2026.", "consequence": "Failure to report can lead to UIF administrative sanctions and other consequences under Law 25,246.", "enforcement": "UIF Argentina", "evidenceStatus": "verified", "operationalImpact": "Distinguish the internal analysis period from the post-classification filing clock.", "evidenceIds": [ "amlb:evidence:e57f9fe7", "amlb:evidence:a8c2cee2", "amlb:evidence:f8a1edab" ], "sourceEntityIds": [ "amlb:source-entity:be9aff77", "amlb:source-entity:d79d1b2b" ] }, { "id": "AR-RSM", "jurisdictionCode": "AR", "jurisdictionName": "Argentina", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Reporte Sistemático Mensual (RSM) — applicable sectors", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Obliged subjects covered by UIF resolutions requiring monthly systematic reporting.", "trigger": "End of a month with reportable operations; applicable no-movements filing where none occurred.", "deadline": "By the 15th day of each month for the immediately preceding calendar month.", "recipient": "UIF Argentina", "submission": "UIF RSM / SRO+ tools.", "applicability": "Current FAQ verified 19 Aug 2026.", "consequence": "Late/non-filing may result in UIF administrative sanctions.", "enforcement": "UIF Argentina", "evidenceStatus": "verified", "operationalImpact": "Schedule a monthly close before the 15th and retain sector-specific report schemas.", "evidenceIds": [ "amlb:evidence:e57f9fe7", "amlb:evidence:a8c2cee2", "amlb:evidence:f980eccf", "amlb:evidence:485e77fa" ], "sourceEntityIds": [ "amlb:source-entity:be9aff77", "amlb:source-entity:d79d1b2b" ] }, { "id": "AR-RISK", "jurisdictionCode": "AR", "jurisdictionName": "Argentina", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "AML/CFT/CPF risk-based controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 25,246 and sector UIF resolutions.", "trigger": "While carrying on covered activities/business relationships.", "deadline": "Ongoing; risk self-assessment, CDD, monitoring, policies, governance and recordkeeping apply under sector rules.", "recipient": "UIF Argentina / sector supervisor", "submission": "Internal control environment and sector-required filings.", "applicability": "Current framework verified 19 Aug 2026.", "consequence": "Control failures may lead to UIF administrative proceedings and sector-supervisory action.", "enforcement": "UIF Argentina / competent supervisor", "evidenceStatus": "verified", "evidenceNote": "The 2024 reform and current sector rules establish a risk-based framework; review dates remain sector-specific.", "operationalImpact": "Map sector-specific self-assessment/review cycles instead of one universal annual date.", "evidenceIds": [ "amlb:evidence:75230379", "amlb:evidence:a8c2cee2", "amlb:evidence:0b96149e", "amlb:evidence:485e77fa" ], "sourceEntityIds": [ "amlb:source-entity:d79d1b2b", "amlb:source-entity:be9aff77" ] }, { "id": "AR-CNV-CLIENT-FUNDS", "jurisdictionCode": "AR", "jurisdictionName": "Argentina", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "CNV traceable client-fund receipt and payment controls", "timingType": "ongoing", "sectors": [ "securities" ], "appliesTo": "Obliged subjects registered with the Comisión Nacional de Valores (CNV), including applicable market intermediaries under Title XI of the CNV Rules.", "trigger": "Each receipt of client funds or payment/delivery of funds to clients in covered CNV activity.", "deadline": "Per transaction / ongoing from 15 September 2026. Use the permitted bank-account or CVU transfer routes and preserve identification and traceability; cheque payment is no longer a permitted modality under amended Article 3.", "recipient": "Comisión Nacional de Valores (CNV) supervisory oversight; this is a transaction-control obligation rather than a separate periodic filing.", "submission": "Execute client-fund movements through the prescribed traceable account/CVU routes and retain the transaction/control evidence required by the CNV framework.", "applicability": "15 September 2026.", "consequence": "Non-compliance can form part of CNV supervisory or enforcement action under the capital-markets and AML/CFT/PF control framework; no single penalty amount is asserted here.", "enforcement": "Comisión Nacional de Valores (CNV)", "evidenceStatus": "verified", "evidenceNote": "General Resolution 1166/2026 replaces Article 3 of Section II, Title XI and enters into force on publication.", "operationalImpact": "Remove cheque-based client-fund payment workflows from the covered CNV process and enforce account ownership/CVU identification and transfer traceability at transaction execution.", "evidenceIds": [ "amlb:evidence:49bbe427" ], "sourceEntityIds": [ "amlb:source-entity:8e09d71c" ] }, { "id": "AR-RPI-RES93-TRANSITION", "jurisdictionCode": "AR", "jurisdictionName": "Argentina", "coverageStatus": "verified", "lastReviewedDate": "2026-10-04", "title": "Real Property Registries — UIF Resolution 93/2026 implementation", "timingType": "scheduled", "sectors": [ "real-estate" ], "appliesTo": "Real Property Registries (Registros de la Propiedad Inmueble) that are obliged subjects under article 20(19) of Law 25,246.", "trigger": "Publication of UIF Resolution 93/2026 on 10 August 2026 and the transition provisions in article 23.", "deadline": "New monthly systematic-report form/content applies from November 2026. The core Resolution 93/2026 regime applies from 8 November 2026. Manual, Code of Conduct and technology adaptation deadline: 7 April 2027.", "recipient": "Unidad de Información Financiera (UIF)", "submission": "UIF digital reporting mechanisms for systematic reports; internal implementation for the prevention manual, Code of Conduct and technology controls.", "applicability": "Resolution published 10 August 2026; core regime effective 8 November 2026; transition deadline 7 April 2027.", "consequence": "Breaches of duties under Resolution 93/2026 are sanctionable under Chapter IV of Law 25,246.", "enforcement": "UIF Argentina", "evidenceStatus": "verified", "operationalImpact": "Real Property Registries should update risk-based controls, monthly reporting configuration, governance documents and supporting technology against the staged Resolution 93/2026 implementation dates.", "evidenceIds": [ "amlb:evidence:ec6bed59" ], "sourceEntityIds": [ "amlb:source-entity:be9aff77" ] }, { "id": "CL-ROS", "jurisdictionCode": "CL", "jurisdictionName": "Chile", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Private-sector reporting entities listed in article 3 of Law 19,913 and other covered entities.", "trigger": "Detection of an operation considered suspicious under law/UAF instructions.", "deadline": "Report opportunely / in the shortest possible time after detection; no universal numeric clock is asserted.", "recipient": "Unidad de Análisis Financiero (UAF)", "submission": "UAF Portal de Entidades Reportantes.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure to comply can lead to UAF administrative sanctions within its supervisory competence.", "enforcement": "UAF Chile", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat ROS as priority event-driven reporting and avoid periodic batching.", "evidenceIds": [ "amlb:evidence:7557de9a", "amlb:evidence:d20cd243", "amlb:evidence:11b4f24c" ], "sourceEntityIds": [ "amlb:source-entity:095bbee9" ] }, { "id": "CL-ROE", "jurisdictionCode": "CL", "jurisdictionName": "Chile", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operaciones en Efectivo (ROE)", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Reporting entities/activities to which UAF cash-reporting requirements apply.", "trigger": "Reportable cash operations during the sector period, or required negative ROE where none occurred.", "deadline": "Monthly, quarterly or semiannual depending on sector, on dates set in the current UAF calendar.", "recipient": "UAF Chile", "submission": "Portal de Entidades Reportantes · ROE upload.", "applicability": "Current frequency framework verified 19 Aug 2026.", "consequence": "Missing the applicable ROE deadline can initiate an administrative sanction process.", "enforcement": "UAF Chile", "evidenceStatus": "verified-with-gap", "evidenceNote": "UAF confirms mandatory filing and three possible frequencies; there is no single national due date.", "operationalImpact": "Bind the obligation to sector before calculating a due date.", "evidenceIds": [ "amlb:evidence:7557de9a", "amlb:evidence:d20cd243" ], "sourceEntityIds": [ "amlb:source-entity:095bbee9" ] }, { "id": "CL-CONTROLS", "jurisdictionCode": "CL", "jurisdictionName": "Chile", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT/CPF preventive system and compliance officer controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the UAF preventive regime.", "trigger": "While conducting an activity covered by Law 19,913/current instructions.", "deadline": "Ongoing; registration, compliance-officer designation, policies, CDD, monitoring and reporting controls.", "recipient": "UAF Chile", "submission": "Internal controls plus UAF portal registration/reporting.", "applicability": "Current framework verified 19 Aug 2026.", "consequence": "UAF may supervise, inspect and sanction entities within statutory scope.", "enforcement": "UAF Chile", "evidenceStatus": "verified", "evidenceNote": "UAF describes registration, compliance-officer and preventive-policy duties.", "operationalImpact": "Maintain an auditable control framework and current UAF portal access.", "evidenceIds": [ "amlb:evidence:7557de9a", "amlb:evidence:d20cd243" ], "sourceEntityIds": [ "amlb:source-entity:095bbee9" ] }, { "id": "CO-ROS", "jurisdictionCode": "CO", "jurisdictionName": "Colombia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities subject to UIAF reporting under applicable SARLAFT/SAGRILAFT/sector rules.", "trigger": "An operation is classified as suspicious.", "deadline": "Immediately.", "recipient": "Unidad de Información y Análisis Financiero (UIAF)", "submission": "SIREL · ROS module.", "applicability": "2026 UIAF calendar verified 19 Aug 2026.", "consequence": "Failure to report can trigger supervisory/administrative consequences under the applicable regime.", "enforcement": "Relevant supervisor / competent authority; UIAF receives the report", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route positive suspicion decisions directly to SIREL without waiting for periodic windows.", "evidenceIds": [ "amlb:evidence:cd9d80db" ], "sourceEntityIds": [ "amlb:source-entity:61a76ee2" ] }, { "id": "CO-PERIODIC", "jurisdictionCode": "CO", "jurisdictionName": "Colombia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "UIAF periodic sector reports and absence-of-ROS reports", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Entities for which UIAF/supervisor calendars prescribe product, transaction, card, threshold or absence reports.", "trigger": "End of the applicable reporting period for the relevant sector/report code.", "deadline": "According to the current UIAF calendar; 2026 windows differ by report and sector.", "recipient": "UIAF", "submission": "SIREL.", "applicability": "Current calendar family verified 19 Aug 2026.", "consequence": "Late/missing reports can trigger sector-supervisory enforcement.", "enforcement": "Applicable sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Store supervisor/report code before generating deadline reminders.", "evidenceIds": [ "amlb:evidence:cd9d80db" ], "sourceEntityIds": [ "amlb:source-entity:61a76ee2" ] }, { "id": "CO-AML-SYSTEM", "jurisdictionCode": "CO", "jurisdictionName": "Colombia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "SARLAFT / SAGRILAFT risk-management controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities subject to SARLAFT, SAGRILAFT or another sector AML/CFT system.", "trigger": "Continuous operation of the covered entity.", "deadline": "Ongoing; risk identification, governance, CDD, monitoring, reporting, documentation and training under the relevant system.", "recipient": "Applicable supervisor and UIAF for reports", "submission": "Internal controls plus required reporting.", "applicability": "Current frameworks verified 19 Aug 2026.", "consequence": "Supervisors can impose administrative sanctions/remediation for system deficiencies.", "enforcement": "Applicable sector supervisor", "evidenceStatus": "verified", "evidenceNote": "Both SARLAFT and SAGRILAFT remain active; scope is entity-specific.", "operationalImpact": "Determine the applicable supervisor/system before assigning controls.", "evidenceIds": [ "amlb:evidence:76fdae54", "amlb:evidence:5d958b49" ], "sourceEntityIds": [ "amlb:source-entity:846568f7", "amlb:source-entity:f780a797" ] }, { "id": "PE-ROS", "jurisdictionCode": "PE", "jurisdictionName": "Peru", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operaciones Sospechosas (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Subjects obliged to report to UIF-Perú under their applicable AML/CFT regulation.", "trigger": "An operation is analysed and classified as suspicious under the applicable sector rule.", "deadline": "Event-driven; exact deadline must be taken from the subject’s applicable rule. No universal national hour/day value is asserted.", "recipient": "UIF-Perú (SBS)", "submission": "ROSEL / Portal PLAFT.", "applicability": "Current architecture verified 19 Aug 2026.", "consequence": "Failure to report can constitute an AML regulatory infringement and lead to sanctions.", "enforcement": "SBS / UIF-Perú or relevant sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Determine supervisory rule before calculating the deadline; maintain ROSEL access.", "evidenceIds": [ "amlb:evidence:11ee83b3", "amlb:evidence:f8128ab2" ], "sourceEntityIds": [ "amlb:source-entity:7cbbcc97" ] }, { "id": "PE-SPLAFT", "jurisdictionCode": "PE", "jurisdictionName": "Peru", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "SPLAFT preventive system and compliance-officer controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects under relevant SBS/UIF or sector AML/CFT rules.", "trigger": "While conducting covered activities.", "deadline": "Ongoing; prevention manual, code of conduct, compliance officer, transaction records, CDD, monitoring and risk controls. Some entities also have an IAOC.", "recipient": "SBS / UIF-Perú or relevant supervisor", "submission": "Internal framework; IAOC/other filings where prescribed.", "applicability": "Current framework verified 19 Aug 2026.", "consequence": "Deficiencies may be classified as administrative infringements with sector-specific sanctions.", "enforcement": "SBS / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain sector-level obligation mapping so IAOC is not assumed universally.", "evidenceIds": [ "amlb:evidence:255fe54a" ], "sourceEntityIds": [ "amlb:source-entity:7cbbcc97" ] }, { "id": "UY-ROS", "jurisdictionCode": "UY", "jurisdictionName": "Uruguay", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial and non-financial obliged subjects under Law 19,574 and applicable rules.", "trigger": "Detection/analysis meeting the suspicious-operation standard.", "deadline": "Promptly / without undue delay under the applicable regime; no single national numeric clock asserted.", "recipient": "UIAF, Banco Central del Uruguay", "submission": "Applicable UIAF reporting channel.", "applicability": "Framework checked after Law 20,469 of 19 Mar 2026.", "consequence": "Failure to report can lead to regulatory/administrative sanctions and other consequences.", "enforcement": "BCU / SENACLAFT / competent authorities according to sector", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat ROS as prompt reporting and verify the sector detail before setting SLA.", "evidenceIds": [ "amlb:evidence:9de3739a", "amlb:evidence:18d9ce43", "amlb:evidence:9e669ce3" ], "sourceEntityIds": [ "amlb:source-entity:6a31dbb1", "amlb:source-entity:403b8764", "amlb:source-entity:97e22738" ] }, { "id": "UY-CONTROLS", "jurisdictionCode": "UY", "jurisdictionName": "Uruguay", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk-based preventive controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects under the applicable financial or non-financial regime.", "trigger": "Continuous conduct of covered activities.", "deadline": "Ongoing; CDD, beneficial-owner identification, risk assessment, monitoring, recordkeeping, training and governance.", "recipient": "BCU or SENACLAFT / relevant supervisor", "submission": "Internal framework and supervisory evidence.", "applicability": "Current framework checked 19 Aug 2026.", "consequence": "Control deficiencies may lead to sector-supervisory sanctions/remediation.", "enforcement": "BCU / SENACLAFT / competent supervisor", "evidenceStatus": "verified", "evidenceNote": "2026 reform and official normative directories confirm the ongoing framework.", "operationalImpact": "Keep financial and non-financial supervisor obligations separated.", "evidenceIds": [ "amlb:evidence:89922ded", "amlb:evidence:18d9ce43" ], "sourceEntityIds": [ "amlb:source-entity:97e22738", "amlb:source-entity:403b8764" ] }, { "id": "PY-ROS", "jurisdictionCode": "PY", "jurisdictionName": "Paraguay", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 1015/97 and the applicable SEPRELAD sector rule.", "trigger": "An operation is classified as suspicious under the relevant sector rule.", "deadline": "Event-driven. Multiple sector rules use short clocks (including 24 hours), but exact deadline must be verified against the entity’s current sector regulation.", "recipient": "SEPRELAD", "submission": "SIRO · ROS module.", "applicability": "Current SIRO/sector framework verified 19 Aug 2026.", "consequence": "Failure to report may result in SEPRELAD administrative sanctions.", "enforcement": "SEPRELAD", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure the reporting entity’s SEPRELAD sector before generating the filing SLA.", "evidenceIds": [ "amlb:evidence:5e1b673f", "amlb:evidence:673f81a2" ], "sourceEntityIds": [ "amlb:source-entity:650ba010" ] }, { "id": "PY-ANNUAL", "jurisdictionCode": "PY", "jurisdictionName": "Paraguay", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Formulario Anual — applicable SEPRELAD sectors", "timingType": "supervisor-driven", "sectors": [ "all" ], "appliesTo": "SEPRELAD-regulated sectors whose applicable regulation requires the annual form.", "trigger": "End of the applicable annual reporting period.", "deadline": "Timing is sector-specific and must follow the current supervisor timetable or form instructions.", "recipient": "SEPRELAD", "submission": "SIRO.", "applicability": "Use through SIRO confirmed in 2026 official training material.", "consequence": "Late/non-filing can lead to administrative enforcement.", "enforcement": "SEPRELAD", "evidenceStatus": "verified-with-gap", "operationalImpact": "Bind the form to sector and annual filing notice.", "evidenceIds": [ "amlb:evidence:dd19f623" ], "sourceEntityIds": [ "amlb:source-entity:650ba010" ] }, { "id": "BO-ROS", "jurisdictionCode": "BO", "jurisdictionName": "Bolivia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under the Bolivian AML/CFT framework and sector instructions.", "trigger": "Operation/activity is classified as suspicious under the applicable rule.", "deadline": "Event-driven; exact current filing clock is an evidence gap and must be checked against the entity’s sector instruction.", "recipient": "UIF Bolivia", "submission": "UIF reporting system / sector channel.", "applicability": "Current UIF site checked 19 Aug 2026.", "consequence": "Failure may result in supervisory/administrative consequences under the applicable sector framework.", "enforcement": "UIF Bolivia / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep a gap flag until the entity’s sector rule is verified from the operative provision.", "evidenceIds": [ "amlb:evidence:5d71c8e5", "amlb:evidence:1029c339" ], "sourceEntityIds": [ "amlb:source-entity:4d3fcad4" ] }, { "id": "BO-CONTROLS", "jurisdictionCode": "BO", "jurisdictionName": "Bolivia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive controls and UIF reporting readiness", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects within applicable Bolivian sector regimes.", "trigger": "While carrying on a covered activity.", "deadline": "Ongoing; CDD, monitoring, records, compliance governance and sector-prescribed reporting controls.", "recipient": "UIF Bolivia / relevant supervisor", "submission": "Internal controls and applicable UIF systems.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Consequences depend on sector/breach; no single national penalty is generalised.", "enforcement": "Relevant supervisor / UIF Bolivia", "evidenceStatus": "verified", "evidenceNote": "Current UIF framework establishes the preventive architecture; periodic filings remain sector-dependent.", "operationalImpact": "Use sector-specific inventory before assigning periodic tasks.", "evidenceIds": [ "amlb:evidence:c582461d" ], "sourceEntityIds": [ "amlb:source-entity:4d3fcad4" ] }, { "id": "EC-THRESHOLD", "jurisdictionCode": "EC", "jurisdictionName": "Ecuador", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Report of transactions equal to or above the legal threshold", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "UAFE obliged subjects subject to threshold reporting.", "trigger": "Transactions meeting the legal threshold during the month, including applicable aggregation.", "deadline": "Within 15 days after the end of each month.", "recipient": "UAFE", "submission": "UAFE reporting systems.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Late/non-reporting may lead to administrative sanctions.", "enforcement": "UAFE / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Close monthly aggregation early enough to validate and submit within the window.", "evidenceIds": [ "amlb:evidence:ea4f38e8", "amlb:evidence:6f040355" ], "sourceEntityIds": [ "amlb:source-entity:e7884d51" ] }, { "id": "EC-ROS", "jurisdictionCode": "EC", "jurisdictionName": "Ecuador", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operaciones Inusuales, Injustificadas o Sospechosas (ROII/ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "UAFE obliged subjects.", "trigger": "Compliance committee/officer becomes aware of a qualifying operation.", "deadline": "Within 4 days from the date the Compliance Committee or Compliance Officer becomes aware.", "recipient": "UAFE", "submission": "UAFE reporting systems.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure/late filing may trigger administrative sanctions.", "enforcement": "UAFE", "evidenceStatus": "verified-with-gap", "operationalImpact": "Record the knowledge date because it starts the deadline.", "evidenceIds": [ "amlb:evidence:ea4f38e8" ], "sourceEntityIds": [ "amlb:source-entity:e7884d51" ] }, { "id": "EC-RIA", "jurisdictionCode": "EC", "jurisdictionName": "Ecuador", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Información Adicional (RIA)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects receiving an additional-information request from UAFE.", "trigger": "Receipt of a UAFE request.", "deadline": "Within 5 days from request; UAFE states the period may be extended by up to 3 days.", "recipient": "UAFE", "submission": "UAFE-prescribed response channel.", "applicability": "Current guidance verified 19 Aug 2026.", "consequence": "Failure to answer FIU requests can lead to enforcement under the applicable framework.", "enforcement": "UAFE", "evidenceStatus": "verified", "evidenceNote": "UAFE directly states the 5-day period and possible 3-day extension.", "operationalImpact": "Route requests into a dedicated regulatory-response workflow.", "evidenceIds": [ "amlb:evidence:ea4f38e8" ], "sourceEntityIds": [ "amlb:source-entity:e7884d51" ] }, { "id": "PA-ROS", "jurisdictionCode": "PA", "jurisdictionName": "Panama", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial and non-financial obliged subjects under Law 23/2015 and applicable rules.", "trigger": "Detection/classification of an operation as suspicious.", "deadline": "Report immediately/promptly under the applicable regime; exact numeric clock must be checked against the current sector rule.", "recipient": "UAF Panamá", "submission": "UAF En Línea / current UAF reporting platform.", "applicability": "Current platform/framework checked 19 Aug 2026.", "consequence": "Failure can result in administrative sanctions by the relevant supervisor and other consequences under Law 23.", "enforcement": "Relevant supervisor / competent authority; UAF receives ROS", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain UAF access and a sector-specific reporting SLA.", "evidenceIds": [ "amlb:evidence:1c9f9717", "amlb:evidence:a208fbbc" ], "sourceEntityIds": [ "amlb:source-entity:06a4ee35" ] }, { "id": "PA-CONTROLS", "jurisdictionCode": "PA", "jurisdictionName": "Panama", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT preventive measures", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 23/2015, subject to sector supervision.", "trigger": "While conducting covered business/activity.", "deadline": "Ongoing; CDD, beneficial-owner identification, risk controls, monitoring, recordkeeping, governance and reporting readiness.", "recipient": "Relevant sector supervisor / UAF for reports", "submission": "Internal compliance framework.", "applicability": "Current framework checked 19 Aug 2026.", "consequence": "Supervisors can impose administrative sanctions for control breaches.", "enforcement": "Relevant Panamanian supervisor", "evidenceStatus": "verified", "evidenceNote": "Law 23 establishes the preventive regime; implementation varies by sector.", "operationalImpact": "Map the entity to its supervisor before applying filing/penalty rules.", "evidenceIds": [ "amlb:evidence:a208fbbc" ], "sourceEntityIds": [ "amlb:source-entity:06a4ee35" ] }, { "id": "CR-ROS", "jurisdictionCode": "CR", "jurisdictionName": "Costa Rica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities/subjects required to report under Law 8204 and related rules.", "trigger": "Identification/analysis of an operation meeting the suspicious standard.", "deadline": "Immediate/timely reporting is required; exact universal numeric deadline remains an evidence gap.", "recipient": "UIF, Instituto Costarricense sobre Drogas", "submission": "UIF reporting service / UIF Directo as applicable.", "applicability": "Current services checked 19 Aug 2026.", "consequence": "Failure to report can lead to sanctions under the applicable legal/supervisory regime.", "enforcement": "Relevant supervisor / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat ROS as priority event-driven reporting and confirm the sector rule for a hard SLA.", "evidenceIds": [ "amlb:evidence:b1b4c06d", "amlb:evidence:7d46f452" ], "sourceEntityIds": [ "amlb:source-entity:e62e91e5", "amlb:source-entity:bb1f2b15" ] }, { "id": "CR-CONTROLS", "jurisdictionCode": "CR", "jurisdictionName": "Costa Rica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive programme and monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/obliged entities under Law 8204 and sector rules.", "trigger": "While carrying on regulated activity.", "deadline": "Ongoing; CDD, monitoring, records, internal policies, compliance function and training.", "recipient": "Relevant supervisor / UIF", "submission": "Internal controls and supervisory evidence.", "applicability": "Current framework checked 19 Aug 2026.", "consequence": "Control failures may trigger supervisory/administrative sanctions.", "enforcement": "Relevant Costa Rican supervisor", "evidenceStatus": "verified", "evidenceNote": "Current framework supports ongoing preventive controls; periodic detail is sector-specific.", "operationalImpact": "Keep sector-specific procedures and evidence of monitoring/training available.", "evidenceIds": [ "amlb:evidence:fc42257b", "amlb:evidence:7d46f452" ], "sourceEntityIds": [ "amlb:source-entity:e62e91e5", "amlb:source-entity:bb1f2b15" ] }, { "id": "GT-RTS", "jurisdictionCode": "GT", "jurisdictionName": "Guatemala", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Reporte de Transacción Sospechosa (RTS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons obliged under Decreto 15-2026 and applicable implementing rules/instructions.", "trigger": "A transaction is examined and determined to be suspicious.", "deadline": "Event-driven; exact current filing clock must be checked in the applicable IVE/sector instruction.", "recipient": "Intendencia de Verificación Especial (IVE)", "submission": "IVE-prescribed reporting channel.", "applicability": "Decreto 15-2026 effective 17 September 2026; implementing regulation/instructions remain in progress.", "consequence": "Failure can lead to administrative and other sanctions under AML law/rules.", "enforcement": "Superintendencia de Bancos / IVE / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Bind the entity to its current IVE instruction before setting an SLA.", "evidenceIds": [ "amlb:evidence:c44881b0", "amlb:evidence:c2befe86", "amlb:evidence:c711d47d" ], "sourceEntityIds": [ "amlb:source-entity:01eb5f8e", "amlb:source-entity:182f73ed" ] }, { "id": "GT-CONTROLS", "jurisdictionCode": "GT", "jurisdictionName": "Guatemala", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "AML preventive controls and transaction monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons obliged under Decreto 15-2026, including the expanded sectors and activities brought within the integrated AML/CFT/CPF framework.", "trigger": "Continuous operation as an obliged person.", "deadline": "Ongoing; apply risk-based prevention, identification, monitoring, analysis, governance and reporting controls, subject to the implementing regulation/instructions.", "recipient": "IVE / relevant supervisor", "submission": "Internal framework and prescribed IVE channels.", "applicability": "Decreto 15-2026 effective 17 September 2026.", "consequence": "Non-compliance can result in administrative sanctions and other consequences.", "enforcement": "Superintendencia de Bancos / IVE", "evidenceStatus": "verified", "operationalImpact": "Document how unusual transactions are identified, analysed and escalated.", "evidenceIds": [ "amlb:evidence:c44881b0", "amlb:evidence:c2befe86" ], "sourceEntityIds": [ "amlb:source-entity:01eb5f8e" ] }, { "id": "SV-ROS", "jurisdictionCode": "SV", "jurisdictionName": "El Salvador", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under the Special AML/TF/PF Law.", "trigger": "Detection of an unusual operation followed by analysis concluding it is suspicious.", "deadline": "Up to 15 business days from detection to analyse; once analysis concludes a ROS is warranted, submit within a maximum of 24 hours.", "recipient": "Unidad de Investigación Financiera (UIF)", "submission": "goAML / UIF reporting portal.", "applicability": "Current FAQ verified 19 Aug 2026.", "consequence": "Late/non-reporting may trigger sanctions under the Special Law and supervisory regime.", "enforcement": "UIF / Fiscalía / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Measure the unusual-activity analysis and post-classification filing stages separately.", "evidenceIds": [ "amlb:evidence:ea50f0c3", "amlb:evidence:58ba1f69" ], "sourceEntityIds": [ "amlb:source-entity:d834b9ed" ] }, { "id": "SV-REGULATED", "jurisdictionCode": "SV", "jurisdictionName": "El Salvador", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Report of regulated cash/other/electronic-transfer operations above prescribed thresholds", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects when transactions meet the statutory reporting trigger.", "trigger": "Execution of a regulated transaction meeting applicable monetary/reporting conditions.", "deadline": "Within 5 business days after the operation.", "recipient": "UIF El Salvador", "submission": "UIF reporting platform / applicable electronic module.", "applicability": "Current FAQ verified 19 Aug 2026.", "consequence": "Failure to file required transaction reports can lead to sanctions.", "enforcement": "UIF / relevant supervisor", "evidenceStatus": "verified", "evidenceNote": "Current UIF FAQ states a five-business-day window for the regulated operations described there.", "operationalImpact": "Route threshold reports into a distinct five-business-day queue rather than the ROS workflow.", "evidenceIds": [ "amlb:evidence:ea50f0c3" ], "sourceEntityIds": [ "amlb:source-entity:d834b9ed" ] }, { "id": "HN-ROS", "jurisdictionCode": "HN", "jurisdictionName": "Honduras", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS / eROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Decree 144-2014 and applicable CNBS/UIF rules.", "trigger": "Identification, analysis and determination of an operation as suspicious.", "deadline": "Event-driven; exact current filing clock should be verified against the applicable sector regulation.", "recipient": "UIF, CNBS", "submission": "eROS portal.", "applicability": "Current eROS channel/framework checked 19 Aug 2026.", "consequence": "Failure can result in sanctions under the Special AML Law/sector rules.", "enforcement": "CNBS / UIF / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain eROS access and a sector-specific ROS SLA.", "evidenceIds": [ "amlb:evidence:4a16e28b", "amlb:evidence:7106cb08" ], "sourceEntityIds": [ "amlb:source-entity:b67485bf" ] }, { "id": "HN-TRANSACTIONS", "jurisdictionCode": "HN", "jurisdictionName": "Honduras", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Registration of threshold cash, multiple-cash and financial transactions", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged subjects covered by transaction-registration rules.", "trigger": "Transactions reach/exceed amounts established by Banco Central de Honduras for the relevant category.", "deadline": "Ongoing transaction capture; reporting/confirmation timing is governed by current UIF instructions for the institution/period.", "recipient": "UIF Honduras", "submission": "UIF Capturador de Transacciones.", "applicability": "Circular 6-2025 framework verified 19 Aug 2026.", "consequence": "Failure to register/report prescribed transactions may lead to administrative enforcement.", "enforcement": "CNBS / UIF", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain complete transaction capture even where confirmation dates sit in a separate calendar.", "evidenceIds": [ "amlb:evidence:f2a66170" ], "sourceEntityIds": [ "amlb:source-entity:b67485bf" ] }, { "id": "DO-ROS", "jurisdictionCode": "DO", "jurisdictionName": "Dominican Republic", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects under Law 155-17 and applicable sector rules.", "trigger": "An operation is analysed and determined to be suspicious.", "deadline": "Prompt event-driven reporting. UAF material references a 24-hour period, but exact universal trigger wording remains a verification gap.", "recipient": "Unidad de Análisis Financiero (UAF)", "submission": "UAF reporting platform / prescribed channel.", "applicability": "Current framework checked 19 Aug 2026.", "consequence": "Failure can result in administrative and/or other sanctions under Law 155-17 and sector rules.", "enforcement": "Relevant supervisor / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat ROS as priority event-driven and verify the sector rule before a hard timer.", "evidenceIds": [ "amlb:evidence:fe766640", "amlb:evidence:ade78b81", "amlb:evidence:6176d0b1" ], "sourceEntityIds": [ "amlb:source-entity:a7e088fe", "amlb:source-entity:f3e5a4c9", "amlb:source-entity:55c8713d" ] }, { "id": "DO-RTE", "jurisdictionCode": "DO", "jurisdictionName": "Dominican Republic", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Reporte de Transacciones en Efectivo (RTE) — applicable obliged subjects", "timingType": "supervisor-driven", "sectors": [ "all" ], "appliesTo": "Obliged subjects required by Law 155-17/sector rules to file cash-transaction reports.", "trigger": "Cash transactions meeting the applicable reporting threshold/conditions.", "deadline": "Timing is sector-specific and must follow the current supervisor timetable or form instructions.", "recipient": "UAF", "submission": "UAF reporting platform.", "applicability": "Current duty checked 19 Aug 2026.", "consequence": "Late/non-filing may trigger administrative sanctions.", "enforcement": "Relevant supervisor / UAF-related enforcement framework", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the relevant RTE sector rule before deadline calculation.", "evidenceIds": [ "amlb:evidence:289c25e5", "amlb:evidence:ade78b81" ], "sourceEntityIds": [ "amlb:source-entity:a7e088fe", "amlb:source-entity:f3e5a4c9" ] }, { "id": "BS-AML-SURVEY", "jurisdictionCode": "BS", "jurisdictionName": "Bahamas", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Annual AML/CFT/CPF supervisory survey", "timingType": "supervisor-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Central Bank supervised financial institutions within the sector-specific 2026 survey programme.", "trigger": "Central Bank AML/CFT/CPF survey cycle or supervisory request.", "deadline": "No public due date or filing cycle verified.", "recipient": "Central Bank of The Bahamas", "submission": "Current Central Bank survey submission process.", "applicability": "2026 guidance published 20 Mar 2026.", "consequence": "Late/non-submission may result in supervisory follow-up/enforcement.", "enforcement": "Central Bank of The Bahamas", "evidenceStatus": "verified-with-gap", "operationalImpact": "Track the current Central Bank survey instruction/calendar; do not reuse legacy AML Data Return timing.", "evidenceIds": [ "amlb:evidence:75bf7717", "amlb:evidence:dd9d58ae", "amlb:evidence:3d117d8a" ], "sourceEntityIds": [ "amlb:source-entity:35dd419a" ] }, { "id": "BS-STR", "jurisdictionCode": "BS", "jurisdictionName": "Bahamas", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other persons subject to Bahamian reporting rules.", "trigger": "Knowledge/suspicion meeting the reporting standard under the FTRA and related guidance.", "deadline": "Event-driven; exact universal public filing clock remains an evidence gap.", "recipient": "Financial Intelligence Unit (The Bahamas)", "submission": "FIU-prescribed reporting channel.", "applicability": "Current framework checked 19 Aug 2026.", "consequence": "Failure to make a required disclosure may lead to criminal/regulatory consequences.", "enforcement": "FIU / relevant supervisor / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain STR escalation/FIU channel readiness; do not use the annual survey as a filing-timing source.", "evidenceIds": [ "amlb:evidence:45172253", "amlb:evidence:3d117d8a" ], "sourceEntityIds": [ "amlb:source-entity:35dd419a" ] }, { "id": "JM-STR", "jurisdictionCode": "JM", "jurisdictionName": "Jamaica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons in the regulated sector under POCA and persons subject to relevant TPA reporting.", "trigger": "Information/suspicion meeting the relevant disclosure standard.", "deadline": "As soon as reasonably practicable / promptly, and in any event within 15 days under the applicable POCA/TPA rule.", "recipient": "Financial Investigations Division (FID) / Designated Authority", "submission": "FID/goAML or prescribed reporting method.", "applicability": "Current FID FAQ checked 19 Aug 2026.", "consequence": "FID states that failure to report can constitute an offence and expose persons/entities to fines and, for individuals, possible imprisonment depending on offence/court.", "enforcement": "FID / Designated Authority / courts", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not treat 15 days as a target; file as soon as reasonably practicable.", "evidenceIds": [ "amlb:evidence:3a9ac5ad", "amlb:evidence:2cd94e3b", "amlb:evidence:7322b705" ], "sourceEntityIds": [ "amlb:source-entity:a4fe9103", "amlb:source-entity:4fc90df1" ] }, { "id": "JM-TTR", "jurisdictionCode": "JM", "jurisdictionName": "Jamaica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "scheduled", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions subject to POCA threshold reporting.", "trigger": "Cash transactions meeting the prescribed threshold during the quarter.", "deadline": "Quarterly, within one month after quarter-end: Apr 30, Jul 31, Oct 31 and Jan 31.", "recipient": "FID / Designated Authority", "submission": "FID prescribed channel / goAML where applicable.", "applicability": "Current FID FAQ checked 19 Aug 2026.", "consequence": "Failure to file required reports can result in offences/penalties under POCA.", "enforcement": "FID / competent courts", "evidenceStatus": "verified", "evidenceNote": "FID publishes the quarterly periods and exact due dates.", "operationalImpact": "Schedule quarter-end verification/validation so filing is not ad hoc.", "evidenceIds": [ "amlb:evidence:3a9ac5ad", "amlb:evidence:f9e4d4fa" ], "sourceEntityIds": [ "amlb:source-entity:a4fe9103" ] }, { "id": "JM-LISTED", "jurisdictionCode": "JM", "jurisdictionName": "Jamaica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Listed Entity Report under the Terrorism Prevention Act", "timingType": "scheduled", "sectors": [ "all" ], "appliesTo": "Entities required to submit listed-entity reports under the TPA regime.", "trigger": "End of each four-month reporting period.", "deadline": "Within one month after each period: Jan–Apr due May 31; May–Aug due Sep 30; Sep–Dec due Jan 31.", "recipient": "FID / Designated Authority", "submission": "FID reporting channel / goAML.", "applicability": "Current FID FAQ checked 19 Aug 2026.", "consequence": "Non-compliance can lead to offences/penalties under the TPA framework.", "enforcement": "FID / Designated Authority / courts", "evidenceStatus": "verified", "evidenceNote": "FID publishes the four-month cycle and exact due dates.", "operationalImpact": "Include the three annual listed-entity dates separately from STR events.", "evidenceIds": [ "amlb:evidence:3a9ac5ad", "amlb:evidence:7f9ec421" ], "sourceEntityIds": [ "amlb:source-entity:a4fe9103" ] }, { "id": "SA-STR", "jurisdictionCode": "SA", "jurisdictionName": "Saudi Arabia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to the Saudi Anti-Money Laundering Law.", "trigger": "Knowledge or reasonable grounds to suspect that funds or a transaction are linked to money laundering, a predicate offence or proceeds of crime.", "deadline": "Report the suspicious transaction to the General Directorate of Financial Intelligence when the statutory suspicion threshold is met. The official provisions reviewed here do not support a single numeric day-count.", "recipient": "General Directorate of Financial Intelligence (SAFIU)", "submission": "Prescribed suspicious-transaction reporting process / forms of the Directorate.", "applicability": "Current in-force SAMA rulebook provisions reviewed 19 Aug 2026.", "consequence": "Failure to report can attract sanctions under the AML Law; exact consequences depend on the breach and responsible person.", "enforcement": "General Directorate of Financial Intelligence / competent supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicion immediately and preserve the decision timestamp so internal procedures do not delay the statutory report.", "evidenceIds": [ "amlb:evidence:350ca95e", "amlb:evidence:f7899921" ], "sourceEntityIds": [ "amlb:source-entity:6ee123cc" ] }, { "id": "SA-AML-CONTROLS", "jurisdictionCode": "SA", "jurisdictionName": "Saudi Arabia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Saudi Central Bank (SAMA) / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Saudi Central Bank (SAMA) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:a9765a25", "amlb:evidence:58fb0daf" ], "sourceEntityIds": [ "amlb:source-entity:6ee123cc" ] }, { "id": "SA-BO", "jurisdictionCode": "SA", "jurisdictionName": "Saudi Arabia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Beneficial ownership register / disclosure maintenance", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Companies and other entities within the scope of the Saudi Ministry of Commerce beneficial-ownership rules, subject to applicable exemptions.", "trigger": "Formation/registration and later changes to reportable beneficial-ownership information.", "deadline": "Maintain and update beneficial-ownership information in accordance with the applicable Ministry of Commerce rules. The public source mapped in mapped sources do not justify a universal numeric update clock across all entity scenarios.", "recipient": "Saudi Ministry of Commerce", "submission": "Ministry of Commerce corporate / beneficial-ownership process.", "applicability": "Current rules/source reviewed 19 Aug 2026.", "consequence": "Non-compliance may attract corporate-registry or other sanctions under the applicable rules.", "enforcement": "Saudi Ministry of Commerce", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain and update BO information under the Ministry of Commerce framework; for Awqaf relationships, SAMA-supervised institutions can use the General Authority for Awqaf channels identified in Circular No. 482008022 to support verification.", "evidenceIds": [ "amlb:evidence:c45a3d00", "amlb:evidence:8c67f390" ], "sourceEntityIds": [ "amlb:source-entity:a97f4622", "amlb:source-entity:6ee123cc" ] }, { "id": "QA-STR", "jurisdictionCode": "QA", "jurisdictionName": "Qatar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-09", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs that are reporting entities under Qatar Law No. 20 of 2019 and implementing regulations.", "trigger": "Suspicion of money laundering, associated predicate offences or terrorism financing.", "deadline": "Submit in accordance with Law No. 20 of 2019, its Implementing Regulations and QFIU instructions; mapped sources do not impose a universal numeric day-count not directly verified from the operative instruction.", "recipient": "Qatar Financial Information Unit (QFIU)", "submission": "QFIU electronic system (ESTR) for linked reporting entities. For entities supervised by the Ministry of Justice, the QFIU–MoJ mechanism signed 7 September 2026 governs registration and account-management procedures on Ekhtar, the platform dedicated to electronic STR submission; other QFIU-prescribed channels apply where relevant.", "applicability": "Current QFIU framework; Ekhtar registration mechanism for Ministry of Justice-supervised entities published 7 Sep 2026. No separate legal effective date is stated in the notice.", "consequence": "Failure to report or tipping-off can attract sanctions under Qatar’s AML/CFT framework.", "enforcement": "QFIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain access to the applicable QFIU reporting channel. Ministry of Justice-supervised entities should keep Ekhtar registration, account verification, reporting-officer details and contact-point information current under the new mechanism.", "evidenceIds": [ "amlb:evidence:d9024320", "amlb:evidence:3bde7dfe", "amlb:evidence:8e170a7e" ], "sourceEntityIds": [ "amlb:source-entity:f8508e98" ] }, { "id": "QA-AML-CONTROLS", "jurisdictionCode": "QA", "jurisdictionName": "Qatar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-09", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "QFIU / competent sector supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "QFIU / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:3ddc428d", "amlb:evidence:0786ae07" ], "sourceEntityIds": [ "amlb:source-entity:f8508e98" ] }, { "id": "BH-STR", "jurisdictionCode": "BH", "jurisdictionName": "Bahrain", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "CBB licensees and other persons subject to Bahrain AML/CFT reporting requirements.", "trigger": "Suspicious transaction or activity identified through the institution’s AML/CFT controls.", "deadline": "Report through the applicable Bahrain suspicious-transaction reporting process. Sector-specific CBB modules apply; no single numeric filing clock is asserted across all licensee categories in mapped sources.", "recipient": "Bahrain financial intelligence / competent authority", "submission": "CBB-prescribed / national suspicious transaction reporting channel for the relevant reporting entity.", "applicability": "Current CBB material reviewed 19 Aug 2026.", "consequence": "Reporting/control breaches can result in CBB supervisory action and sanctions under Bahrain law.", "enforcement": "Central Bank of Bahrain / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the correct CBB volume and reporting path to each licensed business line.", "evidenceIds": [ "amlb:evidence:93c11114", "amlb:evidence:42eef8bf" ], "sourceEntityIds": [ "amlb:source-entity:669767b4", "amlb:source-entity:8ce69365" ] }, { "id": "BH-AML-CONTROLS", "jurisdictionCode": "BH", "jurisdictionName": "Bahrain", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Central Bank of Bahrain / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Central Bank of Bahrain / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:93c11114", "amlb:evidence:4fab46e2" ], "sourceEntityIds": [ "amlb:source-entity:669767b4" ] }, { "id": "BH-BO", "jurisdictionCode": "BH", "jurisdictionName": "Bahrain", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Beneficial ownership information maintenance", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Commercial entities within the scope of Bahrain beneficial-ownership requirements.", "trigger": "Registration and subsequent changes to reportable beneficial-owner information.", "deadline": "Maintain and update BO information under the Ministry of Industry and Commerce framework; exact scenario-specific update clock remains a gap in mapped sources.", "recipient": "Ministry of Industry and Commerce", "submission": "Applicable commercial-registry / beneficial-owner filing process.", "applicability": "Current official source reviewed 19 Aug 2026.", "consequence": "Registry and other sanctions may apply for non-compliance.", "enforcement": "Ministry of Industry and Commerce", "evidenceStatus": "verified-with-gap", "operationalImpact": "Connect ownership/control changes to a legal-entity BO update workflow.", "evidenceIds": [ "amlb:evidence:cf76101f" ], "sourceEntityIds": [ "amlb:source-entity:cbab5abf" ] }, { "id": "KW-STR", "jurisdictionCode": "KW", "jurisdictionName": "Kuwait", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to Law No. 106 of 2013.", "trigger": "Knowledge or suspicion meeting the statutory suspicious-transaction threshold.", "deadline": "Submit an STR to KWFIU as required by Article 12 and the applicable reporting guidance. Mapped sources do not state a universal numeric day-count without provision-level verification.", "recipient": "Kuwait Financial Intelligence Unit (KWFIU)", "submission": "KWFIU prescribed STR format / reporting process.", "applicability": "Current KWFIU sources reviewed 19 Aug 2026.", "consequence": "Failure to comply can attract sanctions under Law No. 106/2013 and implementing rules.", "enforcement": "KWFIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the STR workflow tied to the statutory suspicion decision and current KWFIU form requirements.", "evidenceIds": [ "amlb:evidence:da07ce70", "amlb:evidence:cdc5d928" ], "sourceEntityIds": [ "amlb:source-entity:e724561c" ] }, { "id": "KW-AML-CONTROLS", "jurisdictionCode": "KW", "jurisdictionName": "Kuwait", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "KWFIU / competent sector supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "KWFIU / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:cdc5d928", "amlb:evidence:5580edef" ], "sourceEntityIds": [ "amlb:source-entity:e724561c" ] }, { "id": "OM-STR", "jurisdictionCode": "OM", "jurisdictionName": "Oman", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities subject to Oman’s AML/CFT Law.", "trigger": "Identification of suspicious transactions or activity under the national AML/CFT framework.", "deadline": "Report under Royal Decree 30/2016 and the applicable CBO / national STR guidance. No single numeric clock is asserted in mapped sources.", "recipient": "National Centre for Financial Information / competent FIU", "submission": "Prescribed national/CBO reporting process.", "applicability": "Current CBO framework reviewed 19 Aug 2026.", "consequence": "Non-reporting can attract sanctions under the AML/CFT Law and supervisory framework.", "enforcement": "Central Bank of Oman / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Ensure alert escalation and FIU reporting paths are documented separately from internal investigation SLAs.", "evidenceIds": [ "amlb:evidence:69a77541", "amlb:evidence:fdb95b3c" ], "sourceEntityIds": [ "amlb:source-entity:211d2e82" ] }, { "id": "OM-AML-CONTROLS", "jurisdictionCode": "OM", "jurisdictionName": "Oman", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Central Bank of Oman / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Central Bank of Oman / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:fdb95b3c", "amlb:evidence:d3265e01" ], "sourceEntityIds": [ "amlb:source-entity:211d2e82" ] }, { "id": "IL-UNUSUAL", "jurisdictionCode": "IL", "jurisdictionName": "Israel", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Unusual activity reporting to IMPA", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities covered by the Prohibition on Money Laundering Law and applicable sector reporting orders.", "trigger": "Activity meeting the unusual-activity reporting standard in the applicable order.", "deadline": "File under the applicable sector order. Deadlines differ by reporting regime; no single universal day-count is asserted.", "recipient": "Israel Money Laundering and Terror Financing Prohibition Authority (IMPA)", "submission": "Applicable IMPA / regulator reporting form or electronic process.", "applicability": "Current government framework reviewed 19 Aug 2026.", "consequence": "Late/missing reports can attract regulatory or statutory consequences under the applicable order/law.", "enforcement": "IMPA / relevant sector regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map each regulated activity to its exact reporting order instead of using a generic Israeli STR rule.", "evidenceIds": [ "amlb:evidence:dd86a71e", "amlb:evidence:3bb8c41d", "amlb:evidence:9d624e61" ], "sourceEntityIds": [ "amlb:source-entity:0dfc8572", "amlb:source-entity:d28eafeb" ] }, { "id": "IL-AML-CONTROLS", "jurisdictionCode": "IL", "jurisdictionName": "Israel", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "IMPA / relevant sector regulator", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "IMPA / relevant sector regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:9d624e61", "amlb:evidence:dd86a71e" ], "sourceEntityIds": [ "amlb:source-entity:d28eafeb", "amlb:source-entity:0dfc8572" ] }, { "id": "IL-BOI-MLTF-INVESTIGATION-REPORTING", "jurisdictionCode": "IL", "jurisdictionName": "Israel", "coverageStatus": "verified", "lastReviewedDate": "2026-10-05", "title": "Report qualifying ML/TF investigations to Bank of Israel Banking Supervision", "timingType": "event-driven", "sectors": [ "banking" ], "appliesTo": "Banking corporations subject to Proper Conduct of Banking Business Directive 411.", "trigger": "The banking corporation becomes aware of a qualifying investigation concerning suspicion of money laundering or terrorist-financing offences involving the banking corporation or a controlled entity, including the officers and employees covered by the amended Directive 411 reporting scope.", "deadline": "Immediately, under the Directive 411 supervisory-reporting requirement.", "recipient": "Bank of Israel — Banking Supervision Department", "submission": "Supervisory reporting channel required by the Bank of Israel / Banking Supervision Department.", "applicability": "30 April 2026 for the final Directive 411 amendment; Annex B2 amendments have a separate transition of up to six months.", "consequence": "Failure to meet supervisory reporting requirements may expose a banking corporation to supervisory action under the applicable banking and AML/CFT framework.", "enforcement": "Bank of Israel — Banking Supervision Department", "evidenceStatus": "verified", "operationalImpact": "Banks should route qualifying ML/TF investigation notices to Banking Supervision immediately and ensure escalation procedures cover the expanded officer/employee scope.", "evidenceIds": [ "amlb:evidence:ff4becc8" ], "sourceEntityIds": [ "amlb:source-entity:84140265" ] }, { "id": "JO-SAR", "jurisdictionCode": "JO", "jurisdictionName": "Jordan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Jordan Anti-Money Laundering and Counter Terrorist Financing Law No. 20 of 2021.", "trigger": "Suspicion meeting the statutory reporting threshold.", "deadline": "Submit through the applicable AMLU reporting process. Exact universal numeric SAR clock is not asserted in mapped sources.", "recipient": "Anti-Money Laundering and Counter Terrorist Financing Unit (AMLU)", "submission": "goAML electronic reporting system.", "applicability": "Current AMLU framework reviewed 19 Aug 2026.", "consequence": "Failure to report can attract sanctions under the AML/CFT Law.", "enforcement": "AMLU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain goAML access and document the internal point at which suspicion becomes reportable.", "evidenceIds": [ "amlb:evidence:53433669", "amlb:evidence:8a795128", "amlb:evidence:c3091e80" ], "sourceEntityIds": [ "amlb:source-entity:db6d4a15" ] }, { "id": "JO-AML-CONTROLS", "jurisdictionCode": "JO", "jurisdictionName": "Jordan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "AMLU / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "AMLU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:c3091e80", "amlb:evidence:8a795128" ], "sourceEntityIds": [ "amlb:source-entity:db6d4a15" ] }, { "id": "JO-TFS", "jurisdictionCode": "JO", "jurisdictionName": "Jordan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze implementation", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "All persons and entities in Jordan, including reporting entities and competent authorities, within the scope of applicable targeted financial sanctions.", "trigger": "Designation or amendment of the applicable National / UN sanctions list.", "deadline": "Apply freezing measures without delay; AMLU guidance defines this as immediately and within 24 hours of issuance of the listing/amendment decision.", "recipient": "Relevant competent authority / technical committee; reporting/escalation per applicable instructions.", "submission": "Internal sanctions screening and freeze controls; notifications/reports via the channel prescribed by Jordanian TFS instructions.", "applicability": "Current AMLU FAQ reviewed 19 Aug 2026.", "consequence": "Failure to freeze or making funds available may trigger sanctions under applicable Jordanian law.", "enforcement": "Jordan competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Sanctions screening needs same-day list-change ingestion and freeze escalation capable of meeting the 24-hour outer benchmark.", "evidenceIds": [ "amlb:evidence:53433669" ], "sourceEntityIds": [ "amlb:source-entity:db6d4a15" ] }, { "id": "LB-STR", "jurisdictionCode": "LB", "jurisdictionName": "Lebanon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Banks, financial institutions and other reporting entities within Law No. 44 of 2015 and relevant implementing circulars.", "trigger": "Reasonable grounds to suspect a transaction, attempted transaction or funds are linked to money laundering or terrorist financing.", "deadline": "File an STR with the SIC when the reporting threshold is met. No universal numeric day-count is asserted from the reviewed official sources.", "recipient": "Special Investigation Commission (SIC)", "submission": "SIC prescribed reporting process / forms.", "applicability": "Current SIC framework reviewed 19 Aug 2026.", "consequence": "Failure to report or other AML/CFT breaches can attract sanctions under Law No. 44 and sector rules.", "enforcement": "Special Investigation Commission / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicion directly to the MLRO/SIC workflow and avoid internal SLAs that could delay filing.", "evidenceIds": [ "amlb:evidence:45d5400b", "amlb:evidence:8ab35204" ], "sourceEntityIds": [ "amlb:source-entity:87456eef" ] }, { "id": "LB-AML-CONTROLS", "jurisdictionCode": "LB", "jurisdictionName": "Lebanon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Special Investigation Commission / Banque du Liban / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Special Investigation Commission / Banque du Liban / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:8ab35204", "amlb:evidence:b9f7204d" ], "sourceEntityIds": [ "amlb:source-entity:87456eef" ] }, { "id": "IQ-STR", "jurisdictionCode": "IQ", "jurisdictionName": "Iraq", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to Iraq Anti-Money Laundering and Terrorism Financing Law No. 39 of 2015.", "trigger": "Suspicion of money laundering, predicate crime or terrorist financing under the national law.", "deadline": "Report to the Anti-Money Laundering and Terrorism Financing Office in accordance with Law No. 39/2015 and implementing instructions; no numeric universal clock is asserted here.", "recipient": "Anti-Money Laundering and Terrorism Financing Office", "submission": "Official AML Office reporting process / prescribed system.", "applicability": "Current official portal reviewed 19 Aug 2026.", "consequence": "Non-reporting can attract statutory and supervisory consequences.", "enforcement": "AML/CFT Office / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented escalation route to the Iraqi AML/CFT Office and record the suspicion decision time.", "evidenceIds": [ "amlb:evidence:e28a2bf4", "amlb:evidence:1e22f5b2" ], "sourceEntityIds": [ "amlb:source-entity:f3842cad" ] }, { "id": "IQ-AML-CONTROLS", "jurisdictionCode": "IQ", "jurisdictionName": "Iraq", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "AML/CFT Office / competent sector supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "AML/CFT Office / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:1e22f5b2", "amlb:evidence:e28a2bf4" ], "sourceEntityIds": [ "amlb:source-entity:f3842cad" ] }, { "id": "IR-STR", "jurisdictionCode": "IR", "jurisdictionName": "Iran", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons and institutions subject to Iran’s AML legislation and executive rules.", "trigger": "Knowledge or suspicion meeting the reporting standard under the AML Act / executive by-law.", "deadline": "Report to the Financial Intelligence Center under the applicable law and by-law. The exact universal filing clock is not asserted in mapped sources.", "recipient": "Financial Intelligence Center (FIC), Ministry of Economic Affairs and Finance", "submission": "FIC-prescribed reporting process.", "applicability": "Current FIC legal corpus reviewed 19 Aug 2026.", "consequence": "Violations may attract administrative or criminal consequences under Iranian AML/CFT law.", "enforcement": "Financial Intelligence Center / competent supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep internal case escalation tied to current FIC requirements and preserve the evidence used to reach suspicion.", "evidenceIds": [ "amlb:evidence:5fce39df", "amlb:evidence:f6ada5b0" ], "sourceEntityIds": [ "amlb:source-entity:21e5714b" ] }, { "id": "IR-AML-CONTROLS", "jurisdictionCode": "IR", "jurisdictionName": "Iran", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Financial Intelligence Center / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Center / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:5fce39df", "amlb:evidence:18ccbd8d" ], "sourceEntityIds": [ "amlb:source-entity:21e5714b" ] }, { "id": "EG-STR", "jurisdictionCode": "EG", "jurisdictionName": "Egypt", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other entities subject to Egypt’s AML Law No. 80 of 2002 and implementing controls.", "trigger": "Suspicious transaction or activity meeting the statutory reporting threshold.", "deadline": "Report through the Egyptian FIU process as required by Law No. 80/2002 and applicable sector rules. No single numeric deadline is asserted across all sectors.", "recipient": "Egyptian Money Laundering and Terrorist Financing Combating Unit (EMLCU / Egyptian FIU)", "submission": "FIU / supervisor-prescribed reporting system.", "applicability": "Current official framework reviewed 19 Aug 2026.", "consequence": "Failure to report/control breaches may attract sanctions under the AML Law and sector regulation.", "enforcement": "Egyptian FIU / Central Bank of Egypt / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map FIU reporting to the institution’s regulator-specific AML procedures and document the suspicion trigger.", "evidenceIds": [ "amlb:evidence:8951af9d", "amlb:evidence:9622bd20", "amlb:evidence:aaf785ff" ], "sourceEntityIds": [ "amlb:source-entity:90e0c241", "amlb:source-entity:5970e875" ] }, { "id": "EG-AML-CONTROLS", "jurisdictionCode": "EG", "jurisdictionName": "Egypt", "coverageStatus": "verified", "lastReviewedDate": "2026-09-28", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Egyptian FIU / relevant sector supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 28 Sep 2026; FRA Circular No. 5/2026 dated 27 Sep 2026 requires supervised institutions to align CDD and internal AML/CFT controls with the updated September 2026 procedures.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Egyptian FIU / relevant sector supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "Law No. 80/2002 anchors the national framework; FRA Circular No. 5/2026 supplies current sector-specific CDD procedure evidence for FRA-supervised financial institutions. No separate future effective date is stated in the circular.", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:aaf785ff", "amlb:evidence:8951af9d", "amlb:evidence:2d5d3d78" ], "sourceEntityIds": [ "amlb:source-entity:5970e875", "amlb:source-entity:90e0c241" ] }, { "id": "MA-STR", "jurisdictionCode": "MA", "jurisdictionName": "Morocco", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Credit institutions and other reporting persons subject to Moroccan Law No. 43-05 and sector rules.", "trigger": "Suspicion meeting the reporting standard under the AML/CFT framework.", "deadline": "Submit a suspicious report to ANRF under the applicable law and sector requirements. No universal numeric deadline is asserted here.", "recipient": "Autorité Nationale du Renseignement Financier (ANRF)", "submission": "ANRF / competent-supervisor prescribed reporting process.", "applicability": "Current Bank Al-Maghrib material reviewed 19 Aug 2026.", "consequence": "Failure to report or preventive-control breaches may attract sanctions under Moroccan law and supervisory rules.", "enforcement": "ANRF / Bank Al-Maghrib / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route reportable suspicion to ANRF through the current sector channel and retain the decision record.", "evidenceIds": [ "amlb:evidence:69136e76", "amlb:evidence:c9172dbb", "amlb:evidence:c31aae29" ], "sourceEntityIds": [ "amlb:source-entity:97652542" ] }, { "id": "MA-AML-CONTROLS", "jurisdictionCode": "MA", "jurisdictionName": "Morocco", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Bank Al-Maghrib / ANRF / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Bank Al-Maghrib / ANRF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:c31aae29", "amlb:evidence:1aefaff6" ], "sourceEntityIds": [ "amlb:source-entity:97652542" ] }, { "id": "DZ-STR", "jurisdictionCode": "DZ", "jurisdictionName": "Algeria", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "Suspicious transaction declaration", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other covered persons under Algeria Law No. 05-01 as amended.", "trigger": "Suspicion meeting the statutory declaration threshold.", "deadline": "Submit the suspicious transaction declaration to CTRF under Law No. 05-01 and implementing rules; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Cellule de Traitement du Renseignement Financier (CTRF)", "submission": "CTRF prescribed declaration/reporting process.", "applicability": "Current CTRF legal directory reviewed 19 Aug 2026.", "consequence": "Failure to declare or maintain preventive controls may attract statutory/supervisory sanctions.", "enforcement": "CTRF / Bank of Algeria / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Preserve internal suspicion timestamps and ensure staff know the current CTRF reporting channel.", "evidenceIds": [ "amlb:evidence:12d97332" ], "sourceEntityIds": [ "amlb:source-entity:8e64e422" ] }, { "id": "DZ-AML-CONTROLS", "jurisdictionCode": "DZ", "jurisdictionName": "Algeria", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Bank of Algeria / CTRF / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Bank of Algeria / CTRF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:1d2d765d", "amlb:evidence:12d97332" ], "sourceEntityIds": [ "amlb:source-entity:0220169b", "amlb:source-entity:8e64e422" ] }, { "id": "DZ-KYC-REVIEW", "jurisdictionCode": "DZ", "jurisdictionName": "Algeria", "coverageStatus": "verified", "lastReviewedDate": "2026-10-10", "title": "Risk-based KYC, periodic customer review and enhanced due diligence", "timingType": "ongoing", "sectors": [ "banking", "payments" ], "appliesTo": "Banks, financial institutions and financial services of Algeria Post subject to Bank of Algeria Instruction No. 04-2026.", "trigger": "Before entering a business relationship, throughout the relationship and for occasional transactions; enhanced measures apply to higher-risk customers and relationships.", "deadline": "Identify and verify the customer before onboarding and maintain KYC throughout the relationship. Review customer information at least annually for high-risk customers, at most every 3 years for medium-risk customers and at most every 5 years for low-risk customers, with earlier review on significant changes, unusual activity, PEP-status changes, sanctions alerts or suspicion.", "recipient": "Primarily internal compliance and authorised management; Bank of Algeria through supervision and CTRF where a suspicious-reporting trigger arises.", "submission": "Maintain documented KYC files, customer risk classification, beneficial-owner verification, sanctions/PEP screening, transaction-monitoring evidence and high-risk approval records; make them available under the applicable supervisory framework and report suspicions to CTRF where required.", "applicability": "Instruction No. 04-2026 signed 30 April 2026; Article 7 states that it takes effect from the date of signature.", "consequence": "Failure to apply the prescribed KYC and vigilance controls may attract supervisory or statutory measures under the applicable Algerian AML/CFT framework; the instruction itself does not state one universal monetary penalty for this control set.", "enforcement": "Bank of Algeria / CTRF under the applicable supervisory and AML/CFT framework.", "evidenceStatus": "verified", "evidenceNote": "The primary instruction directly states the covered institutions, pre-onboarding and ongoing identification/verification duties, risk-based approach, enhanced measures, review frequencies and effective date.", "operationalImpact": "Implement risk-tiered KYC refresh scheduling, event-driven refresh triggers, beneficial-owner verification, sanctions/PEP screening, high-risk senior-management approval and auditable ongoing monitoring for the covered institutions.", "evidenceIds": [ "amlb:evidence:366a8568" ], "sourceEntityIds": [ "amlb:source-entity:0220169b" ] }, { "id": "TN-STR", "jurisdictionCode": "TN", "jurisdictionName": "Tunisia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction declaration", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to Tunisia’s AML/CFT framework.", "trigger": "Suspicion of money laundering or terrorist financing meeting the statutory declaration threshold.", "deadline": "Declare the suspicious operation to CTAF in accordance with Organic Law No. 2015-26 as amended and implementing rules; no universal numeric day-count is asserted here.", "recipient": "Tunisian Financial Analysis Commission (CTAF)", "submission": "CTAF prescribed reporting/declaration channel.", "applicability": "Current CTAF framework reviewed 19 Aug 2026.", "consequence": "Non-reporting/control failures may attract sanctions under Tunisian law.", "enforcement": "CTAF / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented CTAF escalation route and keep evidence supporting the suspicion decision.", "evidenceIds": [ "amlb:evidence:ba972cc6" ], "sourceEntityIds": [ "amlb:source-entity:b552f0c8" ] }, { "id": "TN-AML-CONTROLS", "jurisdictionCode": "TN", "jurisdictionName": "Tunisia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "CTAF / competent sector supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CTAF / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:ba972cc6" ], "sourceEntityIds": [ "amlb:source-entity:b552f0c8" ] }, { "id": "ZA-STR", "jurisdictionCode": "ZA", "jurisdictionName": "South Africa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious and unusual transaction/activity report (section 29)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Any person/institution with a section 29 reporting duty under the FIC Act when knowledge or suspicion arises.", "trigger": "Awareness of facts creating the reportable knowledge or suspicion concerning a transaction or activity.", "deadline": "As soon as possible, but no later than 15 days excluding Saturdays, Sundays and public holidays after the relevant person becomes aware of the reportable fact.", "recipient": "Financial Intelligence Centre (FIC)", "submission": "Electronic reporting via the FIC reporting platform; exceptional non-electronic route only where permitted.", "applicability": "Current FIC FAQ reviewed 19 Aug 2026.", "consequence": "Failure to submit an STR can lead to severe criminal/administrative consequences; FIC FAQ notes imprisonment up to 15 years or a fine up to R100 million for failure to submit an STR.", "enforcement": "Financial Intelligence Centre / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Start the statutory clock from awareness of the reportable fact, not from completion of an internal committee cycle.", "evidenceIds": [ "amlb:evidence:8f8d9dac", "amlb:evidence:8f309849" ], "sourceEntityIds": [ "amlb:source-entity:3d3ba5a5" ] }, { "id": "ZA-CTR", "jurisdictionCode": "ZA", "jurisdictionName": "South Africa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash Threshold Report (CTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable institutions listed in Schedule 1 to the FIC Act.", "trigger": "Receipt or payment of physical cash at/above the prescribed threshold; current FIC guidance describes reportable cash as R50,000 or more (more than R49,999.99).", "deadline": "As soon as possible, but no later than 3 business days from awareness of the cash transaction.", "recipient": "Financial Intelligence Centre (FIC)", "submission": "FIC electronic reporting platform.", "applicability": "Current FIC threshold/guidance reviewed 19 Aug 2026.", "consequence": "Failure to submit a CTR may result in criminal or administrative sanctions; FIC FAQ describes imprisonment up to 15 years or a fine up to R100 million.", "enforcement": "Financial Intelligence Centre / competent supervisor", "evidenceStatus": "verified", "evidenceNote": "FIC directly states the threshold and three-business-day reporting period.", "operationalImpact": "Cash monitoring should aggregate/report using the current FIC definition and preserve the date staff became aware of the transaction.", "evidenceIds": [ "amlb:evidence:cd515eb7", "amlb:evidence:8f309849" ], "sourceEntityIds": [ "amlb:source-entity:3d3ba5a5" ] }, { "id": "ZA-AML-CONTROLS", "jurisdictionCode": "ZA", "jurisdictionName": "South Africa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Financial Intelligence Centre / relevant supervisory body", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre / relevant supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:0c1cd5cd", "amlb:evidence:33557838" ], "sourceEntityIds": [ "amlb:source-entity:3d3ba5a5" ] }, { "id": "KE-STR", "jurisdictionCode": "KE", "jurisdictionName": "Kenya", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction or activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions under the Proceeds of Crime and Anti-Money Laundering Act (POCAMLA).", "trigger": "A suspicious or unusual transaction/activity gives rise to suspicion under the Act.", "deadline": "Report to the Financial Reporting Centre within 2 days after the suspicion arose.", "recipient": "Financial Reporting Centre (FRC)", "submission": "FRC prescribed reporting manner/system.", "applicability": "Current Kenya Law text reviewed 19 Aug 2026.", "consequence": "Failure to report can attract offences, penalties and supervisory consequences under POCAMLA.", "enforcement": "Financial Reporting Centre / relevant supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Timestamp the point of suspicion and run internal escalation fast enough to preserve the two-day statutory window.", "evidenceIds": [ "amlb:evidence:06d2de70", "amlb:evidence:c57ed7c5" ], "sourceEntityIds": [ "amlb:source-entity:1beedb7d" ] }, { "id": "KE-AML-CONTROLS", "jurisdictionCode": "KE", "jurisdictionName": "Kenya", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Financial Reporting Centre / competent supervisory body", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Reporting Centre / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:06d2de70", "amlb:evidence:c57ed7c5" ], "sourceEntityIds": [ "amlb:source-entity:1beedb7d" ] }, { "id": "NG-STR", "jurisdictionCode": "NG", "jurisdictionName": "Nigeria", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions subject to the Money Laundering (Prevention and Prohibition) Act 2022 and related rules.", "trigger": "A transaction is determined to be suspicious under the statutory / NFIU reporting standard.", "deadline": "Render the STR to NFIU within 24 hours in accordance with section 7 and current NFIU guidance.", "recipient": "Nigeria Financial Intelligence Unit (NFIU)", "submission": "NFIU prescribed electronic reporting process.", "applicability": "Current NFIU guidance reviewed 19 Aug 2026.", "consequence": "Failure to report can attract offences and administrative penalties under the 2022 Act and related legislation.", "enforcement": "NFIU / relevant supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat 24 hours as an external statutory deadline, not an internal investigation target; escalation must happen earlier.", "evidenceIds": [ "amlb:evidence:7ce2cd9a", "amlb:evidence:b6a406b6" ], "sourceEntityIds": [ "amlb:source-entity:d36b11c1" ] }, { "id": "NG-AML-CONTROLS", "jurisdictionCode": "NG", "jurisdictionName": "Nigeria", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "NFIU / relevant supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "NFIU / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:b6a406b6", "amlb:evidence:737ab2cf" ], "sourceEntityIds": [ "amlb:source-entity:d36b11c1" ] }, { "id": "GH-STR", "jurisdictionCode": "GH", "jurisdictionName": "Ghana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable institutions / persons subject to the Anti-Money Laundering Act, 2020 (Act 1044).", "trigger": "Knowledge or grounds for suspicion of the transaction under Act 1044.", "deadline": "Submit an STR to the Financial Intelligence Centre within 24 hours after the knowledge or the ground for suspicion.", "recipient": "Financial Intelligence Centre (Ghana)", "submission": "FIC prescribed reporting process.", "applicability": "Current primary Act reviewed 19 Aug 2026.", "consequence": "Failure to report may attract offences, administrative sanctions or supervisory consequences under Act 1044.", "enforcement": "Financial Intelligence Centre / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture both the knowledge/suspicion timestamp and filing timestamp for defensible deadline evidence.", "evidenceIds": [ "amlb:evidence:8d1a4c8c" ], "sourceEntityIds": [ "amlb:source-entity:44956d99" ] }, { "id": "GH-AML-CONTROLS", "jurisdictionCode": "GH", "jurisdictionName": "Ghana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Financial Intelligence Centre / competent supervisory body", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:8d1a4c8c" ], "sourceEntityIds": [ "amlb:source-entity:44956d99" ] }, { "id": "MU-STR", "jurisdictionCode": "MU", "jurisdictionName": "Mauritius", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons and auditors subject to FIAMLA.", "trigger": "Awareness of a suspicious transaction.", "deadline": "Report promptly to the FIU, but no later than 5 working days after the suspicion arose.", "recipient": "Financial Intelligence Unit (Mauritius)", "submission": "FIU prescribed suspicious-transaction reporting process.", "applicability": "Current consolidated Laws of Mauritius text reviewed 19 Aug 2026.", "consequence": "Failure to report within the statutory period is an offence and may attract the penalties provided by FIAMLA.", "enforcement": "Financial Intelligence Unit / relevant supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use five working days only as the legal outer bound; workflow should file promptly once suspicion is established.", "evidenceIds": [ "amlb:evidence:4a439bdf" ], "sourceEntityIds": [ "amlb:source-entity:713a71b1" ] }, { "id": "MU-AML-CONTROLS", "jurisdictionCode": "MU", "jurisdictionName": "Mauritius", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Financial Intelligence Unit / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:4a439bdf", "amlb:evidence:f18dbbc1" ], "sourceEntityIds": [ "amlb:source-entity:713a71b1" ] }, { "id": "SC-STR", "jurisdictionCode": "SC", "jurisdictionName": "Seychelles", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Seychelles Anti-Money Laundering and Countering the Financing of Terrorism Act 2020.", "trigger": "Suspicion meeting the statutory reporting threshold.", "deadline": "Report to the Seychelles FIU under the 2020 Act and applicable regulations/guidance. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Unit (Seychelles)", "submission": "FIU prescribed reporting process.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Failure to report can attract sanctions under the AML/CFT Act and applicable rules.", "enforcement": "Seychelles FIU / competent supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain an FIU escalation procedure that records when suspicion arose and the submission evidence.", "evidenceIds": [ "amlb:evidence:9f0d7ea5" ], "sourceEntityIds": [ "amlb:source-entity:fd3e3a85" ] }, { "id": "SC-AML-CONTROLS", "jurisdictionCode": "SC", "jurisdictionName": "Seychelles", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial businesses/professions within the applicable national AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, monitoring, governance and records for the period required by the applicable law / sector rule; No single universal retention period is shown where rules differ by record type or sector.", "recipient": "Seychelles FIU / competent supervisor", "submission": "Internal AML programme, customer/beneficial-owner records, transaction monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Control or recordkeeping failures can attract supervisory, administrative or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Seychelles FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the firm’s control library mapped to the exact sector rule and keep evidence of CDD, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:9f0d7ea5" ], "sourceEntityIds": [ "amlb:source-entity:fd3e3a85" ] }, { "id": "TZ-STR", "jurisdictionCode": "TZ", "jurisdictionName": "Tanzania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons under Tanzania’s AML/CFT framework.", "trigger": "Identification of a transaction or activity meeting the suspicious-reporting threshold.", "deadline": "Report promptly to the FIU under the AML Act and applicable regulations/guidance. FIU DNFBP guidance states within 24 hours from identification as suspicious; mapped sources do not assert that clock universally across every reporting sector.", "recipient": "Financial Intelligence Unit (Tanzania)", "submission": "FIU prescribed reporting channel / goAML-compatible reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the AML framework.", "enforcement": "Financial Intelligence Unit (Tanzania)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Timestamp suspicion formation, route the case immediately to the MLRO and retain submission evidence.", "evidenceIds": [ "amlb:evidence:19398130", "amlb:evidence:9fe55698" ], "sourceEntityIds": [ "amlb:source-entity:f85463af" ] }, { "id": "TZ-AML-CONTROLS", "jurisdictionCode": "TZ", "jurisdictionName": "Tanzania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons under Tanzania’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Unit (Tanzania) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit (Tanzania) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:19398130", "amlb:evidence:9fe55698" ], "sourceEntityIds": [ "amlb:source-entity:f85463af" ] }, { "id": "UG-STR", "jurisdictionCode": "UG", "jurisdictionName": "Uganda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable persons under Uganda’s Anti-Money Laundering Act.", "trigger": "Knowledge or suspicion meeting the statutory STR threshold.", "deadline": "Submit an STR to FIA through the prescribed reporting process. No current universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Authority (Uganda)", "submission": "goAML / FIA prescribed channel.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply with suspicious-reporting duties can attract sanctions under the AML Act.", "enforcement": "Financial Intelligence Authority (Uganda)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately when suspicion arises and retain the goAML acknowledgement and decision trail.", "evidenceIds": [ "amlb:evidence:463cfd72", "amlb:evidence:277ee107", "amlb:evidence:6fccb3e0" ], "sourceEntityIds": [ "amlb:source-entity:3f75a1c0" ] }, { "id": "UG-AML-CONTROLS", "jurisdictionCode": "UG", "jurisdictionName": "Uganda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Accountable persons under Uganda’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Authority (Uganda) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Authority (Uganda) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:463cfd72", "amlb:evidence:277ee107", "amlb:evidence:6fccb3e0" ], "sourceEntityIds": [ "amlb:source-entity:3f75a1c0" ] }, { "id": "RW-STR", "jurisdictionCode": "RW", "jurisdictionName": "Rwanda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction or activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Rwanda’s AML/CFT reporting perimeter.", "trigger": "A transaction or activity is identified as suspicious or unusual under the applicable AML/CFT threshold.", "deadline": "Promptly submit the report to FIC within 24 hours.", "recipient": "Financial Intelligence Centre (Rwanda)", "submission": "Electronically or another channel determined by FIC.", "applicability": "Current FIC guidance reviewed 2026-08-19.", "consequence": "Late or missing reports can attract sanctions under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre (Rwanda)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Run an always-on escalation clock from identification and preserve the electronic submission receipt.", "evidenceIds": [ "amlb:evidence:d638708c", "amlb:evidence:63f633c2" ], "sourceEntityIds": [ "amlb:source-entity:b8b27fec" ] }, { "id": "RW-RECORDS", "jurisdictionCode": "RW", "jurisdictionName": "Rwanda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Rwanda’s AML/CFT perimeter.", "trigger": "Creation of customer, transaction, due-diligence or AML/CFT evidence that must be retained.", "deadline": "Keep relevant AML/CFT records for 10 years, subject to any longer requirement or lawful preservation request.", "recipient": "Financial Intelligence Centre (Rwanda) / competent supervisor", "submission": "Internal records and retrievable evidence for inspection or investigation.", "applicability": "Current FIC guidance reviewed 2026-08-19.", "consequence": "Inadequate retention can impede regulatory or investigative access and attract sanctions.", "enforcement": "Financial Intelligence Centre (Rwanda) / competent supervisor", "evidenceStatus": "verified-scope", "evidenceNote": "FIC training/guidance states that customer, transaction and due-diligence documentation should be kept for 10 years.", "operationalImpact": "Set a 10-year minimum retention rule for covered AML evidence and preserve legal-hold overrides.", "evidenceIds": [ "amlb:evidence:d638708c", "amlb:evidence:63f633c2" ], "sourceEntityIds": [ "amlb:source-entity:b8b27fec" ] }, { "id": "RW-AML-CONTROLS", "jurisdictionCode": "RW", "jurisdictionName": "Rwanda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Rwanda’s AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Centre (Rwanda) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre (Rwanda) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:d638708c", "amlb:evidence:63f633c2" ], "sourceEntityIds": [ "amlb:source-entity:b8b27fec" ] }, { "id": "ZM-STR", "jurisdictionCode": "ZM", "jurisdictionName": "Zambia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Zambia’s Financial Intelligence Centre Act.", "trigger": "A reporting entity forms reasonable suspicion that property or a transaction relates to proceeds of crime, ML, TF or PF.", "deadline": "Submit to FIC as soon as possible, but not later than 3 working days after forming the suspicion.", "recipient": "Financial Intelligence Centre (Zambia)", "submission": "FIC prescribed electronic or designated submission channel.", "applicability": "Current FIC materials reviewed 2026-08-19.", "consequence": "Failure to submit an STR is an offence and may attract the sanctions stated in the FIC Act.", "enforcement": "Financial Intelligence Centre (Zambia)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Start the clock at documented suspicion formation, not committee approval, and retain submission proof.", "evidenceIds": [ "amlb:evidence:cb08948f", "amlb:evidence:deda3ab2", "amlb:evidence:5b103304" ], "sourceEntityIds": [ "amlb:source-entity:c4caff97" ] }, { "id": "ZM-CTR", "jurisdictionCode": "ZM", "jurisdictionName": "Zambia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Prescribed currency transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Zambia’s currency-transaction reporting requirement.", "trigger": "A cash/currency transaction reaches the prescribed reporting threshold, including linked transactions where the rule applies.", "deadline": "Submit the CTR promptly and not later than 3 working days of the reportable transaction.", "recipient": "Financial Intelligence Centre (Zambia)", "submission": "FIC prescribed CTR process.", "applicability": "Current FIC materials reviewed 2026-08-19.", "consequence": "Failure to report threshold transactions can attract sanctions under the FIC framework.", "enforcement": "Financial Intelligence Centre (Zambia)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure threshold detection separately from the filing clock and retain linkage logic for aggregated transactions.", "evidenceIds": [ "amlb:evidence:cb08948f", "amlb:evidence:deda3ab2", "amlb:evidence:5b103304" ], "sourceEntityIds": [ "amlb:source-entity:c4caff97" ] }, { "id": "ZM-AML-CONTROLS", "jurisdictionCode": "ZM", "jurisdictionName": "Zambia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under Zambia’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Centre (Zambia) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre (Zambia) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:cb08948f", "amlb:evidence:deda3ab2", "amlb:evidence:5b103304" ], "sourceEntityIds": [ "amlb:source-entity:c4caff97" ] }, { "id": "ZW-STR", "jurisdictionCode": "ZW", "jurisdictionName": "Zimbabwe", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Designated institutions and persons subject to Zimbabwe’s AML/CFT reporting framework.", "trigger": "Suspicion meeting the reporting threshold under the Money Laundering and Proceeds of Crime Act.", "deadline": "Submit the STR to the FIU as required by section 30 and applicable reporting rules. A numeric universal clock is not asserted in mapped sources.", "recipient": "Financial Intelligence Unit of Zimbabwe", "submission": "FIU prescribed reporting channel.", "applicability": "Current RBZ framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the Act.", "enforcement": "Financial Intelligence Unit of Zimbabwe / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately on suspicion and retain the FIU filing acknowledgement and supporting analysis.", "evidenceIds": [ "amlb:evidence:b13e2f74" ], "sourceEntityIds": [ "amlb:source-entity:9032b3e2" ] }, { "id": "ZW-AML-CONTROLS", "jurisdictionCode": "ZW", "jurisdictionName": "Zimbabwe", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Designated institutions and persons subject to Zimbabwe’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Unit of Zimbabwe / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit of Zimbabwe / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:b13e2f74" ], "sourceEntityIds": [ "amlb:source-entity:9032b3e2" ] }, { "id": "ZW-RBZ-NRA-QUARTERLY", "jurisdictionCode": "ZW", "jurisdictionName": "Zimbabwe", "coverageStatus": "verified", "lastReviewedDate": "2026-10-08", "title": "Quarterly RBZ update on implementation of national risk-assessment results", "timingType": "scheduled", "sectors": [ "banking", "deposit-taking-microfinance" ], "appliesTo": "Banking institutions and deposit-taking microfinance institutions supervised by the Reserve Bank of Zimbabwe.", "trigger": "End of each calendar quarter.", "deadline": "Within 14 days after the end of each quarter. The first submission under the 2026 Monetary Policy Statement was due no later than 14 April 2026.", "recipient": "Reserve Bank of Zimbabwe", "submission": "Submit an update on activities and initiatives undertaken to incorporate the 2024 National Risk Assessment results, including supporting evidence.", "applicability": "Requirement stated in the Reserve Bank of Zimbabwe Monetary Policy Statement dated 27 February 2026.", "consequence": "The mapped primary statement establishes the supervisory reporting requirement but does not state a standalone fixed monetary penalty for late or missing quarterly updates.", "enforcement": "Reserve Bank of Zimbabwe", "evidenceStatus": "verified", "evidenceNote": "Paragraph 272 expressly requires quarterly updates 14 days after each quarter and states the first submission deadline of 14 April 2026; paragraph 273 separately requires incorporation of specified national and sector risk-assessment results into AML/CFT/CPF frameworks and activities.", "operationalImpact": "Maintain a quarter-end evidence pack and submit the RBZ update within 14 days after each quarter; align AML/CFT/CPF frameworks with the referenced risk assessments.", "evidenceIds": [ "amlb:evidence:e0f3f053" ], "sourceEntityIds": [ "amlb:source-entity:9032b3e2" ] }, { "id": "BW-STR", "jurisdictionCode": "BW", "jurisdictionName": "Botswana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Specified parties / accountable institutions under Botswana’s Financial Intelligence framework.", "trigger": "Suspicion meeting the statutory reporting threshold.", "deadline": "Submit a suspicious transaction report to the Financial Intelligence Agency under the applicable Act and FIA guidance. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Agency (Botswana)", "submission": "FIA prescribed reporting channel.", "applicability": "Current government framework reviewed 2026-08-19.", "consequence": "Failure to comply with reporting duties can attract sanctions under the Financial Intelligence framework.", "enforcement": "Financial Intelligence Agency (Botswana)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Document the moment of suspicion and route immediately to the MLRO/FIA filing workflow.", "evidenceIds": [ "amlb:evidence:056cc839", "amlb:evidence:5d8d86a1" ], "sourceEntityIds": [ "amlb:source-entity:fe89464e" ] }, { "id": "BW-AML-CONTROLS", "jurisdictionCode": "BW", "jurisdictionName": "Botswana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Specified parties / accountable institutions under Botswana’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Agency (Botswana) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Agency (Botswana) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:056cc839", "amlb:evidence:5d8d86a1" ], "sourceEntityIds": [ "amlb:source-entity:fe89464e" ] }, { "id": "NA-STR", "jurisdictionCode": "NA", "jurisdictionName": "Namibia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction or activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable and reporting institutions under Namibia’s Financial Intelligence Act.", "trigger": "A transaction or activity meets the suspicion/reporting threshold under section 33 and applicable regulations.", "deadline": "Submit the STR/SAR to the FIC under section 33 and regulations 20–22. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Centre (Namibia)", "submission": "FIC prescribed external/goAML reporting process.", "applicability": "Current FIC materials reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the Financial Intelligence Act.", "enforcement": "Financial Intelligence Centre (Namibia)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately upon suspicion and preserve the report, supporting records and submission evidence.", "evidenceIds": [ "amlb:evidence:60c9c4f1", "amlb:evidence:d7616aff", "amlb:evidence:06717dbe" ], "sourceEntityIds": [ "amlb:source-entity:c790feb8" ] }, { "id": "NA-STR-RECORDS", "jurisdictionCode": "NA", "jurisdictionName": "Namibia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Retention of suspicious-reporting records", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons subject to Namibia’s suspicious-reporting recordkeeping requirements.", "trigger": "An STR/SAR and its supporting records are created or submitted.", "deadline": "Retain the suspicious-reporting record and supporting documentation for at least 5 years from the report date, subject to any longer lawful preservation requirement.", "recipient": "Financial Intelligence Centre (Namibia) / competent authority", "submission": "Internal retrievable records for FIU, supervisory or law-enforcement access.", "applicability": "Current consolidated framework reviewed 2026-08-19.", "consequence": "Failure to retain required records can attract sanctions under the Act.", "enforcement": "Financial Intelligence Centre (Namibia) / competent supervisor", "evidenceStatus": "verified-scope", "operationalImpact": "Apply a five-year minimum to the STR case file and preserve legal-hold overrides.", "evidenceIds": [ "amlb:evidence:60c9c4f1", "amlb:evidence:d7616aff", "amlb:evidence:06717dbe" ], "sourceEntityIds": [ "amlb:source-entity:c790feb8" ] }, { "id": "NA-AML-CONTROLS", "jurisdictionCode": "NA", "jurisdictionName": "Namibia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Accountable and reporting institutions under Namibia’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Centre (Namibia) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Centre (Namibia) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:60c9c4f1", "amlb:evidence:d7616aff", "amlb:evidence:06717dbe" ], "sourceEntityIds": [ "amlb:source-entity:c790feb8" ] }, { "id": "MW-STR", "jurisdictionCode": "MW", "jurisdictionName": "Malawi", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting institutions under Malawi’s Financial Crimes Act.", "trigger": "Suspicion meeting the statutory STR threshold.", "deadline": "Report the suspicious transaction to the Financial Intelligence Authority under the Financial Crimes Act and applicable regulations. Mapped sources preserve the numeric filing-clock gap.", "recipient": "Financial Intelligence Authority (Malawi)", "submission": "FIA prescribed STR channel/form.", "applicability": "Current FIA framework reviewed 2026-08-19.", "consequence": "Failure to report can attract penalties under the Financial Crimes Act.", "enforcement": "Financial Intelligence Authority (Malawi)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use immediate internal escalation and retain the filed STR and supporting evidence.", "evidenceIds": [ "amlb:evidence:e0dfce2b", "amlb:evidence:64cfd278" ], "sourceEntityIds": [ "amlb:source-entity:27a1c729" ] }, { "id": "MW-AML-CONTROLS", "jurisdictionCode": "MW", "jurisdictionName": "Malawi", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting institutions under Malawi’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Intelligence Authority (Malawi) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Authority (Malawi) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:e0dfce2b", "amlb:evidence:64cfd278" ], "sourceEntityIds": [ "amlb:source-entity:27a1c729" ] }, { "id": "AO-STR", "jurisdictionCode": "AO", "jurisdictionName": "Angola", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious operation report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Subject entities under Angola’s AML/CFT/PF framework.", "trigger": "An operation or attempted operation meets the statutory suspicion/reporting threshold.", "deadline": "Communicate the suspicious operation to UIF under Law 5/20 as amended. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Unidade de Informação Financeira (Angola)", "submission": "UIF prescribed suspicious-operation reporting process.", "applicability": "Current UIF legal index reviewed 2026-08-19.", "consequence": "Failure to comply with reporting duties can attract sanctions under the AML/CFT/PF framework.", "enforcement": "Unidade de Informação Financeira (Angola)", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicious operations immediately and preserve the UIF submission trail.", "evidenceIds": [ "amlb:evidence:5f58726c", "amlb:evidence:0349d904", "amlb:evidence:566b2430" ], "sourceEntityIds": [ "amlb:source-entity:7712f3a5" ] }, { "id": "AO-UIF-REGISTRATION", "jurisdictionCode": "AO", "jurisdictionName": "Angola", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "UIF registration and profile maintenance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Subject entities and competent authorities required by Angola’s AML/CFT/PF framework to register with UIF.", "trigger": "Entering the regulated perimeter and whenever registered information changes.", "deadline": "Register with UIF and keep the registration information updated as required by the applicable law and UIF guidance.", "recipient": "Unidade de Informação Financeira (Angola)", "submission": "UIF registration / prescribed update process.", "applicability": "Current UIF guidance reviewed 2026-08-19.", "consequence": "Failure to register or maintain required information can attract sanctions under the applicable framework.", "enforcement": "Unidade de Informação Financeira (Angola)", "evidenceStatus": "verified", "evidenceNote": "UIF’s official guidance expressly describes registration as a legal requirement for subject entities and competent authorities.", "operationalImpact": "Maintain an ownership/control for UIF-registration data and trigger updates when legal name, licensing, ownership or responsible-officer data changes.", "evidenceIds": [ "amlb:evidence:5f58726c", "amlb:evidence:0349d904", "amlb:evidence:566b2430" ], "sourceEntityIds": [ "amlb:source-entity:7712f3a5" ] }, { "id": "AO-AML-CONTROLS", "jurisdictionCode": "AO", "jurisdictionName": "Angola", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Subject entities under Angola’s AML/CFT/PF framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Unidade de Informação Financeira (Angola) / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Unidade de Informação Financeira (Angola) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:5f58726c", "amlb:evidence:0349d904", "amlb:evidence:566b2430" ], "sourceEntityIds": [ "amlb:source-entity:7712f3a5" ] }, { "id": "MZ-STR", "jurisdictionCode": "MZ", "jurisdictionName": "Mozambique", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious operation report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged entities under Mozambique’s AML/CFT/PF framework.", "trigger": "An operation or attempted operation meets the statutory suspicion/reporting threshold.", "deadline": "Communicate the suspicious operation to GIFiM under Law 14/2023 and Decree 53/2023. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Gabinete de Informação Financeira de Moçambique (GIFiM)", "submission": "GIFiM prescribed / goAML reporting process.", "applicability": "Current GIFiM framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the AML/CFT/PF framework.", "enforcement": "GIFiM / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate on suspicion immediately and keep the goAML filing receipt and supporting case evidence.", "evidenceIds": [ "amlb:evidence:b7ff00f0", "amlb:evidence:c7adb2c7" ], "sourceEntityIds": [ "amlb:source-entity:71b0741d" ] }, { "id": "MZ-AML-CONTROLS", "jurisdictionCode": "MZ", "jurisdictionName": "Mozambique", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged entities under Mozambique’s AML/CFT/PF framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "GIFiM / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "GIFiM / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:b7ff00f0", "amlb:evidence:c7adb2c7" ], "sourceEntityIds": [ "amlb:source-entity:71b0741d" ] }, { "id": "MG-STR", "jurisdictionCode": "MG", "jurisdictionName": "Madagascar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration d’opération suspecte", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and designated non-financial professions subject to Madagascar’s AML/CFT/PF framework.", "trigger": "A transaction, attempted transaction or funds meet the statutory suspicion threshold, including suspected criminal proceeds or terrorist-financing links.", "deadline": "Declare the suspicious operation to SAMIFIN without delay. No numeric outer limit is added where the official current material uses a non-numeric standard.", "recipient": "SAMIFIN (Madagascar)", "submission": "SAMIFIN prescribed suspicious-operation reporting process.", "applicability": "Current SAMIFIN framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the AML/CFT/PF framework.", "enforcement": "SAMIFIN / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat the trigger as immediate escalation, record the suspicion timestamp and retain filing evidence.", "evidenceIds": [ "amlb:evidence:b7ad391b", "amlb:evidence:a9141612" ], "sourceEntityIds": [ "amlb:source-entity:ab4e6266" ] }, { "id": "MG-AML-CONTROLS", "jurisdictionCode": "MG", "jurisdictionName": "Madagascar", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons subject to Madagascar’s AML/CFT/PF framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "SAMIFIN / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "SAMIFIN / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:b7ad391b", "amlb:evidence:a9141612" ], "sourceEntityIds": [ "amlb:source-entity:ab4e6266" ] }, { "id": "SZ-STR", "jurisdictionCode": "SZ", "jurisdictionName": "Eswatini", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable institutions under Eswatini’s AML/CFT framework.", "trigger": "Suspicion meeting the reporting threshold under the AML/CFT Act.", "deadline": "Submit the STR to EFIU under the Act and applicable rules. Mapped sources do not assert a numeric universal STR clock outside the separately verified sanctions-hit scenario.", "recipient": "Eswatini Financial Intelligence Unit (EFIU)", "submission": "EFIU prescribed reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the AML/CFT Act.", "enforcement": "Eswatini Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately on suspicion and retain the EFIU report and decision trail.", "evidenceIds": [ "amlb:evidence:2219e847", "amlb:evidence:a921192a" ], "sourceEntityIds": [ "amlb:source-entity:75536f13", "amlb:source-entity:ce7a8912" ] }, { "id": "SZ-TFS-REPORT", "jurisdictionCode": "SZ", "jurisdictionName": "Eswatini", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Sanctions-list freeze and FIU reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Eswatini targeted-financial-sanctions obligations.", "trigger": "Detection of funds or other assets linked to a designated/listed person or entity requiring an immediate freeze.", "deadline": "Freeze without delay and file the required report/STR with EFIU within 24 hours of detecting/freezing the funds or assets.", "recipient": "Eswatini Financial Intelligence Unit (EFIU)", "submission": "Immediate freeze controls plus EFIU prescribed reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to freeze or report can attract sanctions under the applicable TFS/AML framework.", "enforcement": "Eswatini Financial Intelligence Unit / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Run sanctions screening with an immediate blocking path and a 24-hour external-report SLA.", "evidenceIds": [ "amlb:evidence:2219e847", "amlb:evidence:a921192a" ], "sourceEntityIds": [ "amlb:source-entity:75536f13", "amlb:source-entity:ce7a8912" ] }, { "id": "SZ-AML-CONTROLS", "jurisdictionCode": "SZ", "jurisdictionName": "Eswatini", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Accountable institutions under Eswatini’s AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "Eswatini Financial Intelligence Unit / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Eswatini Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:2219e847", "amlb:evidence:a921192a" ], "sourceEntityIds": [ "amlb:source-entity:75536f13", "amlb:source-entity:ce7a8912" ] }, { "id": "SN-STR", "jurisdictionCode": "SN", "jurisdictionName": "Senegal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Senegal’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Sénégal", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Sénégal / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:6a9e7585", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:58a860b2", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "SN-AML-CONTROLS", "jurisdictionCode": "SN", "jurisdictionName": "Senegal", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Senegal’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Sénégal / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Sénégal / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:6a9e7585", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:58a860b2", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "CI-STR", "jurisdictionCode": "CI", "jurisdictionName": "Côte d’Ivoire", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Côte d’Ivoire’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Côte d’Ivoire", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Côte d’Ivoire / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:4e2e3c07", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:ac63ad1b", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "CI-AML-CONTROLS", "jurisdictionCode": "CI", "jurisdictionName": "Côte d’Ivoire", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Côte d’Ivoire’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Côte d’Ivoire / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Côte d’Ivoire / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:4e2e3c07", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:ac63ad1b", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "BJ-STR", "jurisdictionCode": "BJ", "jurisdictionName": "Benin", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Benin’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Bénin", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Bénin / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:ea536b50", "amlb:evidence:1e07efbd", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:028d254a", "amlb:source-entity:afdc8020", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "BJ-AML-CONTROLS", "jurisdictionCode": "BJ", "jurisdictionName": "Benin", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Benin’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Bénin / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Bénin / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:ea536b50", "amlb:evidence:1e07efbd", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:028d254a", "amlb:source-entity:afdc8020", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "BF-STR", "jurisdictionCode": "BF", "jurisdictionName": "Burkina Faso", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Burkina Faso’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Burkina Faso", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Burkina Faso / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:28460906", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:fb9f81b8", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "BF-AML-CONTROLS", "jurisdictionCode": "BF", "jurisdictionName": "Burkina Faso", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Burkina Faso’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Burkina Faso / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Burkina Faso / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:28460906", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:fb9f81b8", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "ML-STR", "jurisdictionCode": "ML", "jurisdictionName": "Mali", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Mali’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Mali", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Mali / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:6b8dc047", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:de9bd399", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "ML-AML-CONTROLS", "jurisdictionCode": "ML", "jurisdictionName": "Mali", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Mali’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Mali / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Mali / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:6b8dc047", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:de9bd399", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "NE-STR", "jurisdictionCode": "NE", "jurisdictionName": "Niger", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Niger’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Niger", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Niger / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:65fc9e5b", "amlb:evidence:607dbe87", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:f1b258e4", "amlb:source-entity:f499c9ec", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "NE-AML-CONTROLS", "jurisdictionCode": "NE", "jurisdictionName": "Niger", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Niger’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Niger / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Niger / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:65fc9e5b", "amlb:evidence:607dbe87", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:f1b258e4", "amlb:source-entity:f499c9ec", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "TG-STR", "jurisdictionCode": "TG", "jurisdictionName": "Togo", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Togo’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Togo", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Togo / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:afcf9771", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:5826d6e0", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "TG-AML-CONTROLS", "jurisdictionCode": "TG", "jurisdictionName": "Togo", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Togo’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Togo / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Togo / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:afcf9771", "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:5826d6e0", "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "GW-STR", "jurisdictionCode": "GW", "jurisdictionName": "Guinea-Bissau", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting persons within Guinea-Bissau’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "A transaction, attempted transaction or activity meets the applicable suspicion threshold.", "deadline": "Declare the suspicious transaction/activity to the national CENTIF without delay / promptly under the applicable national transposition and UMOA framework. No numeric outer filing deadline is verified in mapped national text.", "recipient": "CENTIF Guiné-Bissau", "submission": "National CENTIF prescribed reporting channel.", "applicability": "Current regional/national framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the applicable national AML/CFT/PF law.", "enforcement": "CENTIF Guiné-Bissau / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation event and preserve the national CENTIF filing acknowledgement and supporting evidence.", "evidenceIds": [ "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "GW-AML-CONTROLS", "jurisdictionCode": "GW", "jurisdictionName": "Guinea-Bissau", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within Guinea-Bissau’s AML/CFT/PF perimeter and the applicable UMOA framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, governance and records for the periods required by the applicable law and sector rules.", "recipient": "CENTIF Guiné-Bissau / competent supervisor", "submission": "Internal AML programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "CENTIF Guiné-Bissau / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and keep evidence of CDD, beneficial ownership, monitoring, escalation and record retention.", "evidenceIds": [ "amlb:evidence:f0761c0f", "amlb:evidence:f0fe4280", "amlb:evidence:76f74fee" ], "sourceEntityIds": [ "amlb:source-entity:36e197ff", "amlb:source-entity:9dda818f" ] }, { "id": "BZ-STR", "jurisdictionCode": "BZ", "jurisdictionName": "Belize", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Belize AML/CFT obligations.", "trigger": "Knowledge, suspicion or reasonable grounds for suspicion concerning money laundering, terrorist financing or related criminal activity arise.", "deadline": "Report as soon as possible, but no later than 3 days after the suspicion/grounds arise.", "recipient": "Financial Intelligence Unit of Belize (FIU Belize)", "submission": "FIU-prescribed STR reporting process/channel.", "applicability": "Current official FIU guidance reviewed 2026-08-19.", "consequence": "Failure to report may trigger sanctions under Belize AML/CFT law.", "enforcement": "FIU Belize / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately, start a three-day maximum filing clock, preserve the STR acknowledgement and prohibit tipping-off.", "evidenceIds": [ "amlb:evidence:3f018fde", "amlb:evidence:71828f47" ], "sourceEntityIds": [ "amlb:source-entity:75376029" ] }, { "id": "BZ-RECORDS", "jurisdictionCode": "BZ", "jurisdictionName": "Belize", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT recordkeeping and CDD evidence", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Belize AML/CFT obligations.", "trigger": "Continuous while conducting covered business and after transactions/relationships end.", "deadline": "Maintain required business, transaction and customer-identification records for at least 5 years, subject to any longer period required by law or direction.", "recipient": "FIU Belize / competent supervisor", "submission": "Internal retention controls; produce records to competent authorities when lawfully required.", "applicability": "Current official FIU guidance reviewed 2026-08-19.", "consequence": "Recordkeeping failures may attract supervisory or statutory sanctions.", "enforcement": "FIU Belize / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Set a five-year minimum AML retention rule with legal-hold override and retrievable CDD/transaction evidence.", "evidenceIds": [ "amlb:evidence:a85991fe", "amlb:evidence:71828f47" ], "sourceEntityIds": [ "amlb:source-entity:75376029" ] }, { "id": "NI-STR", "jurisdictionCode": "NI", "jurisdictionName": "Nicaragua", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Sujetos obligados within the scope of Nicaragua’s AML/CFT/PF framework.", "trigger": "An operation or attempted operation is determined to be suspicious under the applicable law, regulation and UAF methodology.", "deadline": "File with UAF promptly within the deadline applicable to the reporter and current reporting regulation. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Unidad de Análisis Financiero (UAF)", "submission": "UAF-prescribed ROS reporting channel/form.", "applicability": "Current UAF legal framework reviewed 2026-08-19.", "consequence": "Non-reporting or late reporting may attract sanctions under the applicable AML/CFT/PF framework.", "enforcement": "UAF / sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route a suspicious determination directly to the UAF filing workflow and map the reporter’s sector-specific current clock before production use.", "evidenceIds": [ "amlb:evidence:2b0e963d", "amlb:evidence:567744b9", "amlb:evidence:b0b1ee28" ], "sourceEntityIds": [ "amlb:source-entity:921f3652", "amlb:source-entity:05d702db" ] }, { "id": "NI-AML-CONTROLS", "jurisdictionCode": "NI", "jurisdictionName": "Nicaragua", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT/PF controls and due diligence", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Sujetos obligados within the applicable Nicaraguan AML/CFT/PF perimeter.", "trigger": "Continuous while conducting covered business; enhanced measures apply as risk requires.", "deadline": "Maintain the CDD, beneficial-owner, monitoring, escalation and records required by current law and sector/UAF regulation.", "recipient": "UAF / competent sector supervisor", "submission": "Internal compliance programme and regulatory submissions where separately prescribed.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control failures may attract administrative, supervisory and/or statutory sanctions.", "enforcement": "UAF / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a sector-mapped control library and preserve customer, beneficial-owner, monitoring and escalation evidence.", "evidenceIds": [ "amlb:evidence:2b0e963d", "amlb:evidence:567744b9", "amlb:evidence:b0b1ee28" ], "sourceEntityIds": [ "amlb:source-entity:921f3652", "amlb:source-entity:05d702db" ] }, { "id": "VE-RAS", "jurisdictionCode": "VE", "jurisdictionName": "Venezuela", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Actividad Sospechosa (RAS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Sujetos obligados under Venezuela’s applicable AML/CFT framework.", "trigger": "After analysis, an activity/operation is considered suspicious under the applicable legal and sector framework.", "deadline": "Submit the RAS with the immediacy/promptness required by current UNIF and sector rules; no universal numeric outer limit is asserted here.", "recipient": "Unidad Nacional de Inteligencia Financiera (UNIF)", "submission": "UNIF-prescribed reporting mechanism.", "applicability": "Current UNIF materials reviewed 2026-08-19.", "consequence": "Failure to report may expose the obligated person to sanctions under the applicable framework.", "enforcement": "UNIF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a suspicious determination as an immediate escalation and filing event; map the specific sector rule before setting a hard SLA.", "evidenceIds": [ "amlb:evidence:ce47e123", "amlb:evidence:0e9551a9", "amlb:evidence:1404de95" ], "sourceEntityIds": [ "amlb:source-entity:df9f4d90" ] }, { "id": "VE-AML-CONTROLS", "jurisdictionCode": "VE", "jurisdictionName": "Venezuela", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT risk controls, monitoring and internal escalation", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Sujetos obligados under the applicable Venezuelan sector regime.", "trigger": "Continuous while carrying on covered business and whenever risk indicators require enhanced scrutiny.", "deadline": "Maintain preventive controls, monitoring, analysis and escalation under the applicable sector rule and UNIF framework.", "recipient": "UNIF / competent supervisor", "submission": "Internal AML controls and evidence; regulatory submission where separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Deficiencies may attract sector supervisory or statutory consequences.", "enforcement": "UNIF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep documented risk assessment, CDD/beneficial-owner evidence, monitoring rationale and escalation records linked to the relevant sector rule.", "evidenceIds": [ "amlb:evidence:ce47e123", "amlb:evidence:0e9551a9", "amlb:evidence:1404de95" ], "sourceEntityIds": [ "amlb:source-entity:df9f4d90" ] }, { "id": "CU-ROS", "jurisdictionCode": "CU", "jurisdictionName": "Cuba", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Reporte de Operación Sospechosa (ROS)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities subject to Cuba’s AML/CFT reporting framework.", "trigger": "An operation/activity meets the applicable suspicion threshold after internal analysis.", "deadline": "Submit without unnecessary delay under the applicable rule; a universal numeric outer limit is not asserted from the public material reviewed.", "recipient": "Dirección General de Investigación de Operaciones Financieras (DGIOF), Banco Central de Cuba", "submission": "CAROS secure web reporting platform; supplementary information via ARCANO where applicable.", "applicability": "Current BCC operational description published 2025 and reviewed 2026-08-19.", "consequence": "Failure to report may trigger consequences under applicable Cuban AML/CFT rules.", "enforcement": "DGIOF / Banco Central de Cuba / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Wire the internal suspicion decision to CAROS submission and retain the filing receipt plus any ARCANO supplement trail.", "evidenceIds": [ "amlb:evidence:1d2dd0f1" ], "sourceEntityIds": [ "amlb:source-entity:7f41492f" ] }, { "id": "CU-AML-CONTROLS", "jurisdictionCode": "CU", "jurisdictionName": "Cuba", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive controls and customer monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities within Cuba’s applicable AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business and when risk indicators arise.", "deadline": "Maintain due diligence, monitoring, internal analysis and records in accordance with the applicable Cuban regulatory framework.", "recipient": "DGIOF / Banco Central de Cuba / competent supervisor", "submission": "Internal control programme and regulator/FIU submissions where required.", "applicability": "Current official architecture reviewed 2026-08-19.", "consequence": "Deficiencies may attract supervisory or statutory consequences.", "enforcement": "Banco Central de Cuba / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain auditable CDD, monitoring and escalation evidence mapped to the entity’s applicable BCC/sector rule.", "evidenceIds": [ "amlb:evidence:1d2dd0f1" ], "sourceEntityIds": [ "amlb:source-entity:7f41492f" ] }, { "id": "HT-DS", "jurisdictionCode": "HT", "jurisdictionName": "Haiti", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Haiti’s AML/CFT reporting obligations.", "trigger": "Facts or transactions meet the legal threshold for a declaration of suspicion.", "deadline": "Submit to UCREF within the timing required by the applicable law/guideline. A universal numeric outer limit is not asserted here.", "recipient": "Unité Centrale de Renseignements Financiers (UCREF)", "submission": "AMLUCREF online reporting environment / UCREF prescribed process.", "applicability": "Current UCREF pages reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under Haitian AML/CFT law.", "enforcement": "UCREF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicious matters immediately into the UCREF/AMLUCREF workflow and preserve the submission acknowledgement.", "evidenceIds": [ "amlb:evidence:7c61dab8", "amlb:evidence:5d65fedd", "amlb:evidence:0b7f9a99" ], "sourceEntityIds": [ "amlb:source-entity:9cf6fc2d" ] }, { "id": "HT-AML-CONTROLS", "jurisdictionCode": "HT", "jurisdictionName": "Haiti", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT due diligence, monitoring and record controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities within Haiti’s applicable AML/CFT perimeter.", "trigger": "Continuous while conducting covered business.", "deadline": "Maintain customer due diligence, monitoring, internal escalation and records under the applicable law and UCREF/sector guidance.", "recipient": "UCREF / competent supervisor", "submission": "Internal AML programme and evidence; regulatory submissions when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control failures may attract applicable supervisory or statutory sanctions.", "enforcement": "UCREF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a sector-specific retention/control matrix and link CDD, monitoring and escalation evidence to the governing rule.", "evidenceIds": [ "amlb:evidence:7c61dab8", "amlb:evidence:5d65fedd", "amlb:evidence:0b7f9a99" ], "sourceEntityIds": [ "amlb:source-entity:9cf6fc2d" ] }, { "id": "BB-STR", "jurisdictionCode": "BB", "jurisdictionName": "Barbados", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious or unusual transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under Barbados AML/CFT law; Central Bank operational detail applies to regulated financial institutions within its scope.", "trigger": "A transaction/activity is known or suspected to involve criminal proceeds, money laundering or terrorist financing under the applicable threshold.", "deadline": "Report promptly/forthwith under the applicable law and sector guidance. A single numeric outer limit is not asserted nationally.", "recipient": "Financial Intelligence Unit (Barbados)", "submission": "FIU-prescribed reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under the applicable AML/CFT law.", "enforcement": "Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use an immediate internal escalation SLA and map any sector-specific filing clock before deployment.", "evidenceIds": [ "amlb:evidence:9c5966e4", "amlb:evidence:b9dd9985" ], "sourceEntityIds": [ "amlb:source-entity:3ba32763", "amlb:source-entity:defa2033" ] }, { "id": "BB-RECORDS", "jurisdictionCode": "BB", "jurisdictionName": "Barbados", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT recordkeeping and preventive controls", "timingType": "ongoing", "sectors": [ "financial-institutions" ], "appliesTo": "Financial institutions subject to Central Bank of Barbados AML/CFT guidance; other sectors follow their competent authority rules.", "trigger": "Continuous while conducting covered business and after the relevant transaction/relationship.", "deadline": "For Central Bank-regulated financial institutions, retain relevant business transaction/AML records for at least 5 years, alongside required CDD, monitoring and control evidence.", "recipient": "Central Bank of Barbados / FIU / competent supervisor", "submission": "Internal retention and AML control programme; produce records when lawfully required.", "applicability": "Guidance scope reviewed 2026-08-19.", "consequence": "Record/control failures may attract supervisory or statutory sanctions.", "enforcement": "Central Bank of Barbados / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Apply a five-year minimum where the Central Bank guideline governs, with legal-hold override and sector mapping elsewhere.", "evidenceIds": [ "amlb:evidence:9c5966e4", "amlb:evidence:b9dd9985" ], "sourceEntityIds": [ "amlb:source-entity:3ba32763", "amlb:source-entity:defa2033" ] }, { "id": "TT-STR", "jurisdictionCode": "TT", "jurisdictionName": "Trinidad & Tobago", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious transaction / activity report (STR/SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Listed businesses and financial institutions subject to Trinidad and Tobago AML/CFT reporting obligations.", "trigger": "Knowledge, suspicion or reasonable grounds for suspicion arise under the applicable reporting threshold.", "deadline": "Report as soon as possible and, in any event, within 5 days from the relevant knowledge/suspicion/reasonable grounds.", "recipient": "Financial Intelligence Unit of Trinidad and Tobago (FIUTT)", "submission": "FIUTT-prescribed STR/SAR filing mechanism.", "applicability": "5-day outer clock effective following proclamation on 15 August 2025; reviewed 2026-08-19.", "consequence": "Late or non-reporting may attract sanctions under the applicable AML/CFT framework.", "enforcement": "FIUTT / competent supervisor", "evidenceStatus": "verified", "evidenceNote": "FIUTT expressly states the change from the earlier 14-day limit to five days.", "operationalImpact": "Replace any legacy 14-day workflow immediately; trigger escalation on suspicion and enforce a five-day maximum filing SLA.", "evidenceIds": [ "amlb:evidence:47abe832", "amlb:evidence:8d77374b", "amlb:evidence:a93566f5" ], "sourceEntityIds": [ "amlb:source-entity:7b82d998" ] }, { "id": "TT-AML-CONTROLS", "jurisdictionCode": "TT", "jurisdictionName": "Trinidad & Tobago", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "AML/CFT preventive programme and reporting governance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Listed businesses and financial institutions subject to Trinidad and Tobago AML/CFT obligations.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain CDD, monitoring, internal escalation, reporting governance and records as required by the applicable law and sector rules.", "recipient": "FIUTT / competent supervisor", "submission": "Internal compliance programme; regulatory/FIU filings where prescribed.", "applicability": "Current framework and FIUTT reporting materials reviewed 2026-08-19.", "consequence": "Deficiencies may attract regulatory, administrative or statutory sanctions.", "enforcement": "FIUTT / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Document ownership, monitoring, MLRO escalation and evidence retention, with the new five-day STR clock embedded in procedures.", "evidenceIds": [ "amlb:evidence:47abe832", "amlb:evidence:8d77374b", "amlb:evidence:a93566f5", "amlb:evidence:d3524204" ], "sourceEntityIds": [ "amlb:source-entity:7b82d998" ] }, { "id": "TT-TRUST-INFO", "jurisdictionCode": "TT", "jurisdictionName": "Trinidad & Tobago", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Express trust / legal-arrangement service-provider information maintenance", "timingType": "event-driven", "sectors": [ "tcsp", "legal-accounting-services" ], "appliesTo": "Trustees of express trusts and administrators of other forms of legal arrangement within the amended Trustee Ordinance framework.", "trigger": "A change in the required basic information on regulated agents and service providers connected with the trust or other legal arrangement.", "deadline": "Update the required information within at least 5 days of a change; retain it for at least 6 years after the trustee/administrator involvement ends; provide it to FIUTT or another competent authority upon written request within the timeframe specified in that request.", "recipient": "Financial Intelligence Unit of Trinidad and Tobago (FIUTT) / competent authority", "submission": "Maintain the required information at the designated place in Trinidad and Tobago and provide it when lawfully requested.", "applicability": "Miscellaneous Provisions (FATF Compliance) Act, 2026 — 5 March 2026.", "consequence": "Failure to maintain or provide required information can trigger statutory enforcement measures and offences under the amended framework.", "enforcement": "Registrar General / FIUTT / competent authority", "evidenceStatus": "verified", "operationalImpact": "Trust and legal-arrangement administrators need a five-day change-control process, six-year post-involvement retention and a mechanism to respond within authority-specified request deadlines.", "evidenceIds": [ "amlb:evidence:910af510" ], "sourceEntityIds": [ "amlb:source-entity:c89e93b3" ] }, { "id": "GD-STR", "jurisdictionCode": "GD", "jurisdictionName": "Grenada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other persons within section 48 / applicable AML reporting scope.", "trigger": "A transaction is deemed suspicious under the Proceeds of Crime Act framework.", "deadline": "Report as soon as reasonably practicable and in any event within 14 days from the date the transaction is deemed suspicious.", "recipient": "Financial Intelligence Unit of Grenada", "submission": "FIU-prescribed suspicious transaction reporting process.", "applicability": "Current consolidated parliamentary text reviewed 2026-08-19.", "consequence": "Failure to comply may attract consequences under the Proceeds of Crime Act and related AML framework.", "enforcement": "Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use immediate internal escalation and a hard 14-day statutory maximum from the suspicious determination date.", "evidenceIds": [ "amlb:evidence:54efccfa", "amlb:evidence:611b0dc8" ], "sourceEntityIds": [ "amlb:source-entity:cfa0dd34" ] }, { "id": "GD-AML-PROGRAMME", "jurisdictionCode": "GD", "jurisdictionName": "Grenada", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Written AML compliance programme", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities within the applicable section 48 compliance-programme scope.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain a written programme covering internal controls, independent testing, employee training and designated responsible personnel, as applicable.", "recipient": "Competent supervisor / FIU", "submission": "Internal compliance programme and retained evidence.", "applicability": "Current consolidated parliamentary text reviewed 2026-08-19.", "consequence": "Programme deficiencies may attract supervisory or statutory consequences.", "enforcement": "Competent supervisor / Financial Intelligence Unit", "evidenceStatus": "verified", "evidenceNote": "Section 48 expressly describes core elements of the written compliance programme.", "operationalImpact": "Maintain evidence of control ownership, independent testing, training completion and responsible-person designation.", "evidenceIds": [ "amlb:evidence:54efccfa", "amlb:evidence:611b0dc8" ], "sourceEntityIds": [ "amlb:source-entity:cfa0dd34" ] }, { "id": "DM-SAR", "jurisdictionCode": "DM", "jurisdictionName": "Dominica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Dominica AML/CFT reporting obligations.", "trigger": "Knowledge, suspicion or reasonable grounds arise under the applicable AML/CFT threshold.", "deadline": "Report promptly in accordance with the applicable Act, Code and sector guidance. No universal numeric outer limit is asserted here.", "recipient": "Financial Intelligence Unit of Dominica", "submission": "FIU-prescribed SAR/STR reporting process.", "applicability": "Current government/FIU framework reviewed 2026-08-19.", "consequence": "Failure to report may attract consequences under applicable AML/CFT law.", "enforcement": "Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as an immediate escalation and map the exact reporter/sector rule before setting a hard filing timer.", "evidenceIds": [ "amlb:evidence:b8b635ef", "amlb:evidence:4c4a203e", "amlb:evidence:6b24a096" ], "sourceEntityIds": [ "amlb:source-entity:0b0b7da3", "amlb:source-entity:f5404e67" ] }, { "id": "DM-AML-CONTROLS", "jurisdictionCode": "DM", "jurisdictionName": "Dominica", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls and due diligence", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities within Dominica’s applicable AML/CFT perimeter.", "trigger": "Continuous while conducting covered business and when higher-risk facts arise.", "deadline": "Maintain CDD, beneficial-owner checks, monitoring, internal reporting, training and records under the applicable law/Code.", "recipient": "Competent supervisor / FIU", "submission": "Internal AML programme and evidence; regulatory submissions where required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control failures may attract supervisory/statutory sanctions.", "enforcement": "Competent supervisor / Financial Intelligence Unit", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep a sector-mapped control library with auditable CDD, monitoring, training and escalation evidence.", "evidenceIds": [ "amlb:evidence:b8b635ef", "amlb:evidence:4c4a203e", "amlb:evidence:6b24a096" ], "sourceEntityIds": [ "amlb:source-entity:0b0b7da3", "amlb:source-entity:f5404e67" ] }, { "id": "AG-STR", "jurisdictionCode": "AG", "jurisdictionName": "Antigua & Barbuda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious financial activity / transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting persons subject to Antigua and Barbuda AML/CFT law.", "trigger": "Reasonable suspicion arises concerning covered financial activity or a transaction.", "deadline": "Report promptly to the Supervisory Authority; no numeric outer limit is asserted unless the reporter’s applicable rule supplies one.", "recipient": "ONDCP / Supervisory Authority (FIU function)", "submission": "ONDCP-prescribed suspicious transaction/activity reporting process.", "applicability": "Current ONDCP official material reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under applicable AML/CFT law.", "enforcement": "ONDCP / Supervisory Authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicion immediately and treat “promptly” as a no-delay operational standard, preserving the filing evidence.", "evidenceIds": [ "amlb:evidence:c383d95c", "amlb:evidence:80fb023a" ], "sourceEntityIds": [ "amlb:source-entity:9400c2d3" ] }, { "id": "AG-AML-CONTROLS", "jurisdictionCode": "AG", "jurisdictionName": "Antigua & Barbuda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive controls, due diligence and records", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting persons within the Antigua and Barbuda AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain preventive controls, CDD, monitoring, internal escalation and records under the applicable AML/CFT law and supervisory rules.", "recipient": "ONDCP / competent supervisor", "submission": "Internal AML programme and evidence; required supervisory/FIU submissions.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Deficiencies may attract supervisory/statutory sanctions.", "enforcement": "ONDCP / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map obligations by regulated sector and preserve CDD, monitoring, escalation and training evidence.", "evidenceIds": [ "amlb:evidence:c383d95c", "amlb:evidence:80fb023a" ], "sourceEntityIds": [ "amlb:source-entity:9400c2d3" ] }, { "id": "LC-SAR", "jurisdictionCode": "LC", "jurisdictionName": "St. Lucia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Saint Lucia AML/CFT reporting obligations.", "trigger": "Knowledge, suspicion or reasonable grounds meet the applicable reporting threshold.", "deadline": "File promptly in accordance with the applicable AML/CFT law and FIA guidance; no universal numeric outer limit is asserted in mapped sources.", "recipient": "Financial Intelligence Authority of Saint Lucia", "submission": "FIA-prescribed suspicious activity reporting mechanism.", "applicability": "Current FIA/government materials reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under applicable law.", "enforcement": "Financial Intelligence Authority / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Trigger immediate MLRO escalation and preserve FIA submission evidence; map any sector-specific clock separately.", "evidenceIds": [ "amlb:evidence:9a69f163", "amlb:evidence:12acaabd", "amlb:evidence:8f7ac504" ], "sourceEntityIds": [ "amlb:source-entity:532f8297" ] }, { "id": "LC-AML-CONTROLS", "jurisdictionCode": "LC", "jurisdictionName": "St. Lucia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT programme and monitoring", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities within Saint Lucia’s applicable AML/CFT perimeter.", "trigger": "Continuous while conducting covered business.", "deadline": "Maintain CDD, beneficial-owner identification, monitoring, escalation, training and records under applicable legislation and supervisory guidance.", "recipient": "Financial Intelligence Authority / competent supervisor", "submission": "Internal AML programme and retained evidence.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control failures may attract regulatory/statutory sanctions.", "enforcement": "Competent supervisor / Financial Intelligence Authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a reporter-specific obligation matrix and auditable CDD/monitoring/escalation evidence.", "evidenceIds": [ "amlb:evidence:9a69f163", "amlb:evidence:12acaabd", "amlb:evidence:8f7ac504" ], "sourceEntityIds": [ "amlb:source-entity:532f8297" ] }, { "id": "VC-SAR", "jurisdictionCode": "VC", "jurisdictionName": "St. Vincent & Grenadines", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Saint Vincent and the Grenadines AML/CFT reporting obligations.", "trigger": "Activity/transaction meets the applicable suspicion threshold.", "deadline": "Report to the FIU within the timing required by current law/FIU guidance. A universal numeric outer limit is not asserted here.", "recipient": "Financial Intelligence Unit, Saint Vincent and the Grenadines", "submission": "FIU-prescribed SAR reporting process.", "applicability": "Current FIU materials reviewed 2026-08-19.", "consequence": "Failure to report may attract consequences under applicable AML/CFT law.", "enforcement": "SVG FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate promptly, preserve the suspicion decision trail, and map the entity’s exact filing SLA to its current rule.", "evidenceIds": [ "amlb:evidence:4ed7bc44", "amlb:evidence:dde364a3", "amlb:evidence:6badd7e0" ], "sourceEntityIds": [ "amlb:source-entity:c704eb45", "amlb:source-entity:a6d2e376" ] }, { "id": "VC-MLRO-CONTROLS", "jurisdictionCode": "VC", "jurisdictionName": "St. Vincent & Grenadines", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT governance, MLCO/MLRO and preventive controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/reporting entities within the SVG AML/CFT framework.", "trigger": "Continuous while conducting covered business.", "deadline": "Maintain appropriate AML/CFT governance, ML compliance/reporting officer arrangements, CDD, monitoring and records under the applicable law and supervisory guidance.", "recipient": "Financial Services Authority / FIU / competent supervisor", "submission": "Internal governance and control evidence; regulatory submissions when required.", "applicability": "Current FSA/FIU framework reviewed 2026-08-19.", "consequence": "Governance/control failures may attract supervisory or statutory consequences.", "enforcement": "FSA / FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Document MLCO/MLRO appointment, authority, escalation routes, monitoring and training evidence.", "evidenceIds": [ "amlb:evidence:4ed7bc44", "amlb:evidence:dde364a3", "amlb:evidence:6badd7e0" ], "sourceEntityIds": [ "amlb:source-entity:c704eb45", "amlb:source-entity:a6d2e376" ] }, { "id": "KN-STR", "jurisdictionCode": "KN", "jurisdictionName": "St. Kitts & Nevis", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Saint Kitts and Nevis AML/CFT reporting obligations.", "trigger": "A transaction/activity meets the applicable suspicion threshold.", "deadline": "Report to the FIU promptly within the deadline applicable to the reporter’s law/regulation; no universal numeric outer limit is asserted here.", "recipient": "Financial Intelligence Unit of Saint Kitts and Nevis", "submission": "FIU-prescribed STR/SAR reporting process.", "applicability": "Current government/FSRC materials reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under applicable law.", "enforcement": "Financial Intelligence Unit / FSRC / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use immediate escalation and attach the exact sector clock to the entity profile before operational deployment.", "evidenceIds": [ "amlb:evidence:3a28ee9d", "amlb:evidence:3470bfdc" ], "sourceEntityIds": [ "amlb:source-entity:3dd272b8", "amlb:source-entity:69600538" ] }, { "id": "KN-AML-CONTROLS", "jurisdictionCode": "KN", "jurisdictionName": "St. Kitts & Nevis", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls and supervisory compliance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/reporting entities in Saint Kitts and Nevis.", "trigger": "Continuous while conducting covered business.", "deadline": "Maintain risk assessment, CDD/beneficial-owner controls, monitoring, escalation, governance and records under the applicable rule.", "recipient": "FSRC / FIU / competent supervisor", "submission": "Internal compliance programme and evidence; supervisory submissions where required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Deficiencies may attract supervisory/statutory consequences.", "enforcement": "FSRC / FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep regulated-activity-specific controls and evidence of CDD, monitoring, reporting governance and training.", "evidenceIds": [ "amlb:evidence:3a28ee9d", "amlb:evidence:3470bfdc" ], "sourceEntityIds": [ "amlb:source-entity:3dd272b8", "amlb:source-entity:69600538" ] }, { "id": "GY-STR", "jurisdictionCode": "GY", "jurisdictionName": "Guyana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Guyana’s AML/CFT obligations.", "trigger": "Suspicion is formed that a transaction/activity meets the applicable AML/CFT reporting threshold.", "deadline": "Report as soon as possible, but no later than 3 days after the suspicion is formed.", "recipient": "Financial Intelligence Unit, Guyana", "submission": "FIU-prescribed STR reporting process.", "applicability": "Current FIU guidance reviewed 2026-08-19.", "consequence": "Late/non-reporting may attract sanctions under the applicable AML/CFT framework.", "enforcement": "Guyana FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Start the statutory clock when suspicion is formed, file as soon as possible, and retain the FIU acknowledgement.", "evidenceIds": [ "amlb:evidence:27d7ad5f", "amlb:evidence:ffbdfeb2", "amlb:evidence:3581bb0b" ], "sourceEntityIds": [ "amlb:source-entity:25c83fa8" ] }, { "id": "GY-OTHER-REPORTS", "jurisdictionCode": "GY", "jurisdictionName": "Guyana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold and terrorist-property reporting streams", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities to which Guyana threshold transaction and terrorist-property reporting requirements apply.", "trigger": "A transaction/property event meets the applicable statutory threshold or terrorist-property reporting trigger.", "deadline": "File within the deadline prescribed for the applicable report type. Mapped sources do not substitute the STR three-day clock for different report categories.", "recipient": "Financial Intelligence Unit, Guyana", "submission": "FIU-prescribed threshold transaction / terrorist-property reporting process.", "applicability": "Current FIU reporting architecture reviewed 2026-08-19.", "consequence": "Failure to file a required report may attract applicable sanctions.", "enforcement": "Guyana FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain separate trigger logic and SLAs for STR, threshold transaction and terrorist-property reporting.", "evidenceIds": [ "amlb:evidence:27d7ad5f", "amlb:evidence:ffbdfeb2", "amlb:evidence:3581bb0b" ], "sourceEntityIds": [ "amlb:source-entity:25c83fa8" ] }, { "id": "KY-SAR", "jurisdictionCode": "KY", "jurisdictionName": "Cayman Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Cayman Islands AML/CFT suspicious-reporting obligations.", "trigger": "Knowledge, suspicion or reasonable grounds arise under the applicable Proceeds of Crime / AML reporting threshold.", "deadline": "File as soon as required by the applicable law and sector rule. A universal numeric outer limit is not asserted here.", "recipient": "Financial Reporting Authority (FRA), Cayman Islands", "submission": "AMLive electronic reporting portal / FRA prescribed process.", "applicability": "Current FRA/CIMA materials reviewed 2026-08-19.", "consequence": "Failure to report may attract criminal, regulatory or supervisory consequences under applicable law.", "enforcement": "FRA / CIMA / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route suspicious matters to the MLRO/FRA workflow immediately and preserve AMLive filing receipts and supporting analysis.", "evidenceIds": [ "amlb:evidence:1170e0da", "amlb:evidence:5609f87e", "amlb:evidence:7caeeb6d" ], "sourceEntityIds": [ "amlb:source-entity:942f3410", "amlb:source-entity:9e610c14" ] }, { "id": "KY-AML-PROGRAMME", "jurisdictionCode": "KY", "jurisdictionName": "Cayman Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Effective AML compliance programme and governance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "CIMA-regulated Financial Services Providers conducting Relevant Financial Business, including in-scope branches, subsidiaries, affiliates and CIMA-regulated financial-group members, subject to the Rule and AMLRs.", "trigger": "Continuous while conducting covered business.", "deadline": "Ongoing from 18 September 2026. Maintain documented risk-based governance and controls; training is ongoing and at least annual under CIMA’s implementation FAQs; independent-audit frequency remains risk-based.", "recipient": "CIMA / competent supervisor / FRA as applicable", "submission": "Internal programme and retained evidence; supervisory/FIU submissions where prescribed.", "applicability": "CIMA Effective Compliance Programme Rule effective 18 September 2026.", "consequence": "Programme deficiencies may attract supervisory/regulatory sanctions.", "enforcement": "CIMA / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Map governance, AMLCO accountability, documented risk assessment, policies/controls, outsourcing oversight, training and independent audit evidence to the new Rule.", "evidenceIds": [ "amlb:evidence:096c48db", "amlb:evidence:6a1e4b9e", "amlb:evidence:475c7086" ], "sourceEntityIds": [ "amlb:source-entity:9e610c14", "amlb:source-entity:fffd898b" ] }, { "id": "KY-SANCTIONS-TFS", "jurisdictionCode": "KY", "jurisdictionName": "Cayman Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Financial sanctions and targeted financial sanctions compliance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "All Regulated Persons supervised by CIMA under the Regulatory Acts, whether or not they conduct Relevant Financial Business.", "trigger": "Continuous while operating as a CIMA Regulated Person and whenever sanctions / TFS exposure is identified.", "deadline": "Ongoing from 18 September 2026; apply sanctions/TFS controls and follow FRA reporting requirements when a reporting trigger arises.", "recipient": "CIMA / Financial Reporting Authority (FRA), as applicable", "submission": "Internal sanctions/TFS control framework and FRA-prescribed reporting process where required.", "applicability": "CIMA Financial Sanctions and Targeted Financial Sanctions Rule effective 18 September 2026.", "consequence": "Non-compliance may lead to supervisory or other legal consequences under the applicable Cayman Islands sanctions/TFS framework.", "enforcement": "CIMA / Financial Reporting Authority / competent authorities", "evidenceStatus": "verified", "evidenceNote": "CIMA states that the Rule applies to all Regulated Persons it supervises and reinforces compliance with FRA reporting guidelines and the Cayman TFS legislative framework.", "operationalImpact": "Maintain documented sanctions/TFS governance, screening, escalation, decision and reporting controls across all CIMA-regulated business.", "evidenceIds": [ "amlb:evidence:9dbfc613", "amlb:evidence:6a1e4b9e", "amlb:evidence:f0586435" ], "sourceEntityIds": [ "amlb:source-entity:9e610c14", "amlb:source-entity:fffd898b" ] }, { "id": "BM-SAR", "jurisdictionCode": "BM", "jurisdictionName": "Bermuda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Bermuda AML/ATF reporting obligations.", "trigger": "Knowledge, suspicion or reasonable grounds meet the applicable reporting threshold.", "deadline": "Submit promptly in accordance with the applicable Proceeds of Crime / AML/ATF rule; no universal numeric outer limit is asserted here.", "recipient": "Bermuda Financial Intelligence Agency (FIA)", "submission": "goAML reporting platform / FIA prescribed process.", "applicability": "Current FIA/BMA materials reviewed 2026-08-19.", "consequence": "Failure to report may attract criminal, regulatory or supervisory consequences.", "enforcement": "FIA / BMA / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately to the reporting officer, file through goAML as required, and retain the submission/analysis trail.", "evidenceIds": [ "amlb:evidence:037990cb", "amlb:evidence:67f73085", "amlb:evidence:73803fea" ], "sourceEntityIds": [ "amlb:source-entity:0c266c31", "amlb:source-entity:4d6c564a" ] }, { "id": "BM-AML-CONTROLS", "jurisdictionCode": "BM", "jurisdictionName": "Bermuda", "coverageStatus": "verified", "lastReviewedDate": "2026-09-18", "title": "AML/ATF risk controls and supervisory compliance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "BMA-regulated and other reporting entities within Bermuda’s AML/ATF perimeter.", "trigger": "Continuous while conducting covered business and as risk changes.", "deadline": "Maintain risk assessment, CDD/beneficial-owner controls, monitoring, reporting governance, training and records under applicable rules.", "recipient": "Bermuda Monetary Authority / competent supervisor", "submission": "Internal compliance programme and retained evidence.", "applicability": "Current framework; legal/accounting Version 2 guidance published 12 June 2026.", "consequence": "Deficiencies may attract BMA or other statutory sanctions.", "enforcement": "BMA / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a sector control matrix. Legal and accounting firms supervised by the Barristers and Accountants AML/ATF Board should align risk assessment, CDD/EDD, monitoring, SAR/sanctions, CPF, outsourcing, training, records and internal-audit controls with Version 2 guidance.", "evidenceIds": [ "amlb:evidence:037990cb", "amlb:evidence:67f73085", "amlb:evidence:73803fea", "amlb:evidence:7a515a67" ], "sourceEntityIds": [ "amlb:source-entity:0c266c31", "amlb:source-entity:4d6c564a", "amlb:source-entity:a96eceb0" ] }, { "id": "VG-SAR", "jurisdictionCode": "VG", "jurisdictionName": "British Virgin Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities within BVI AML/CFT suspicious-reporting scope.", "trigger": "Suspicion arises in the course of business, trade, employment or profession under the applicable legal threshold.", "deadline": "File as required by the applicable law/FIA guidance without avoidable delay. No universal numeric outer limit is asserted here.", "recipient": "BVI Financial Investigation Agency (FIA)", "submission": "FIA-prescribed SAR reporting process.", "applicability": "Current FIA/FSC materials reviewed 2026-08-19.", "consequence": "Failure to file a required SAR can lead to criminal prosecution and/or regulatory consequences.", "enforcement": "BVI FIA / FSC / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate suspicion immediately, ensure reporting-officer ownership, and preserve the FIA filing and supporting analysis trail.", "evidenceIds": [ "amlb:evidence:6dcbf5a6", "amlb:evidence:a904efc5", "amlb:evidence:91b35e44" ], "sourceEntityIds": [ "amlb:source-entity:e8c2936c", "amlb:source-entity:eb6b8032" ] }, { "id": "VG-AML-CONTROLS", "jurisdictionCode": "VG", "jurisdictionName": "British Virgin Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT systems, controls and reporting governance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/reporting entities in the British Virgin Islands.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain AML/CFT systems and controls, CDD, monitoring, reporting governance, training and records under applicable FSC/FIA rules.", "recipient": "BVI FSC / FIA / competent supervisor", "submission": "Internal AML programme and retained evidence; regulatory submissions as required.", "applicability": "Current official framework reviewed 2026-08-19.", "consequence": "Deficiencies may attract regulatory/statutory sanctions.", "enforcement": "BVI FSC / FIA / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain sector-specific policies, MLRO escalation, training and auditable CDD/monitoring evidence.", "evidenceIds": [ "amlb:evidence:6dcbf5a6", "amlb:evidence:a904efc5", "amlb:evidence:91b35e44" ], "sourceEntityIds": [ "amlb:source-entity:e8c2936c", "amlb:source-entity:eb6b8032" ] }, { "id": "TC-SAR", "jurisdictionCode": "TC", "jurisdictionName": "Turks & Caicos Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to Turks and Caicos Islands AML/CTF reporting requirements.", "trigger": "An activity/transaction meets the applicable legal suspicion threshold.", "deadline": "File with the FIA in accordance with the applicable law and reporting guidance; no universal numeric outer limit is asserted here.", "recipient": "Turks and Caicos Islands Financial Intelligence Agency (FIA)", "submission": "FIA-prescribed SAR reporting process.", "applicability": "Current FIA/FSC framework reviewed 2026-08-19.", "consequence": "Failure to report may attract criminal, regulatory or supervisory consequences.", "enforcement": "TCI FIA / FSC / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as immediate escalation and map the entity’s exact filing requirement to its applicable regulation/guidance.", "evidenceIds": [ "amlb:evidence:dac48f13", "amlb:evidence:531261fa", "amlb:evidence:56f81c71" ], "sourceEntityIds": [ "amlb:source-entity:4a418031", "amlb:source-entity:70d351c2", "amlb:source-entity:5b7f1c9e" ] }, { "id": "TC-AML-CONTROLS", "jurisdictionCode": "TC", "jurisdictionName": "Turks & Caicos Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CTF systems, controls and due diligence", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/reporting entities in the Turks and Caicos Islands.", "trigger": "Continuous while conducting covered business.", "deadline": "Maintain risk-based CDD, beneficial-owner controls, monitoring, reporting governance, training and records under the applicable framework.", "recipient": "TCI FSC / competent supervisor / FIA", "submission": "Internal compliance programme and retained evidence.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control failures may attract supervisory/statutory consequences.", "enforcement": "TCI FSC / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a regulated-activity control matrix with auditable CDD, monitoring, training and escalation evidence.", "evidenceIds": [ "amlb:evidence:dac48f13", "amlb:evidence:531261fa", "amlb:evidence:56f81c71" ], "sourceEntityIds": [ "amlb:source-entity:4a418031", "amlb:source-entity:70d351c2", "amlb:source-entity:5b7f1c9e" ] }, { "id": "CW-UTR", "jurisdictionCode": "CW", "jurisdictionName": "Curaçao", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Unusual transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Service providers/reporting entities within Curaçao’s NORUT reporting perimeter.", "trigger": "An executed or intended transaction meets an applicable objective or subjective unusual-transaction indicator.", "deadline": "Report to FIU Curaçao within the timing required by NORUT and the applicable indicator/regulation. No universal numeric outer limit is asserted here.", "recipient": "FIU Curaçao", "submission": "FIU Curaçao reporting tool / prescribed reporting process.", "applicability": "Current FIU framework reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under Curaçao’s AML reporting framework.", "enforcement": "FIU Curaçao / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Implement indicator-driven detection and route qualifying executed/intended transactions into the FIU reporting workflow.", "evidenceIds": [ "amlb:evidence:9a8120f7", "amlb:evidence:3dc67c43", "amlb:evidence:c3445cd0" ], "sourceEntityIds": [ "amlb:source-entity:c36db3b1" ] }, { "id": "CW-AML-CONTROLS", "jurisdictionCode": "CW", "jurisdictionName": "Curaçao", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT due diligence, monitoring and reporting controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Service providers/reporting entities within Curaçao’s AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain customer due diligence, beneficial-owner checks, monitoring, internal escalation and records under the applicable AML/CFT ordinances and supervisory rules.", "recipient": "Competent supervisor / FIU Curaçao", "submission": "Internal AML programme and evidence; FIU/supervisory submissions as required.", "applicability": "Current official framework reviewed 2026-08-19.", "consequence": "Deficiencies may attract supervisory/statutory sanctions.", "enforcement": "Competent supervisor / FIU Curaçao", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the entity’s regulated activity to the exact CDD/retention rule and preserve monitoring/escalation evidence.", "evidenceIds": [ "amlb:evidence:9a8120f7", "amlb:evidence:3dc67c43", "amlb:evidence:c3445cd0" ], "sourceEntityIds": [ "amlb:source-entity:c36db3b1" ] }, { "id": "AW-UTR", "jurisdictionCode": "AW", "jurisdictionName": "Aruba", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Unusual transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Service providers/reporting entities subject to Aruba’s unusual-transaction reporting regime.", "trigger": "A transaction is designated unusual under the applicable objective or subjective indicator.", "deadline": "Report promptly and within 5 business days after the transaction is designated unusual.", "recipient": "FIU Aruba", "submission": "FIU Aruba prescribed reporting mechanism.", "applicability": "Current FIU indicators reviewed 2026-08-19.", "consequence": "Late/non-reporting may attract sanctions under the applicable reporting framework.", "enforcement": "FIU Aruba / competent supervisor", "evidenceStatus": "verified", "evidenceNote": "FIU Aruba expressly states the five-business-day outer limit.", "operationalImpact": "Start the filing clock when the transaction is designated unusual and enforce a five-business-day maximum with evidence of submission.", "evidenceIds": [ "amlb:evidence:85847b9b", "amlb:evidence:66001d12", "amlb:evidence:9430bd4e" ], "sourceEntityIds": [ "amlb:source-entity:c2c6997a", "amlb:source-entity:e70ca35c" ] }, { "id": "AW-AML-CONTROLS", "jurisdictionCode": "AW", "jurisdictionName": "Aruba", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD, unusual-transaction monitoring and record retention controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated/reporting service providers within Aruba’s AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain CDD, monitoring/reporting processes and record retention as required by the applicable CBA/FIU legislation and supervisory rules.", "recipient": "Central Bank of Aruba / FIU Aruba / competent supervisor", "submission": "Internal AML control programme and retained evidence.", "applicability": "Current FIU/CBA framework reviewed 2026-08-19.", "consequence": "Control failures may attract supervisory or statutory sanctions.", "enforcement": "Central Bank of Aruba / FIU Aruba", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain auditable CDD, indicator testing, reporting decisions and records mapped to the applicable supervisory rule.", "evidenceIds": [ "amlb:evidence:85847b9b", "amlb:evidence:66001d12", "amlb:evidence:9430bd4e" ], "sourceEntityIds": [ "amlb:source-entity:c2c6997a", "amlb:source-entity:e70ca35c" ] }, { "id": "PG-SMR", "jurisdictionCode": "PG", "jurisdictionName": "Papua New Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious matter report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions/reporting entities subject to Papua New Guinea AML/CTF reporting duties.", "trigger": "Reasonable grounds arise to suspect information is relevant to money laundering, terrorist financing, sanctions offences, a foreign indictable offence or criminal property.", "deadline": "Report as soon as practicable and within a maximum of 5 working days.", "recipient": "Financial Analysis and Supervision Unit (FASU), Bank of Papua New Guinea", "submission": "FASU prescribed Suspicious Matter Report process/form.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Intentional or reckless failure to comply, or false/misleading reporting, is an offence under the AML/CTF reporting framework.", "enforcement": "FASU / Bank of Papua New Guinea", "evidenceStatus": "verified", "evidenceNote": "The current Bank of PNG reporting page expressly states the five-working-day maximum.", "operationalImpact": "Start the filing clock when reasonable grounds arise, escalate immediately and retain the FASU submission evidence.", "evidenceIds": [ "amlb:evidence:cce25838", "amlb:evidence:8b979a42" ], "sourceEntityIds": [ "amlb:source-entity:375c6f0f", "amlb:source-entity:85193379" ] }, { "id": "PG-TTR", "jurisdictionCode": "PG", "jurisdictionName": "Papua New Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions/reporting entities subject to PNG threshold-transaction reporting.", "trigger": "Cash or bearer negotiable instrument transaction of K20,000 or more, including linked transactions that collectively meet the threshold.", "deadline": "Report as soon as practicable and within a maximum of 10 working days from the transaction, or the last linked transaction.", "recipient": "FASU, Bank of Papua New Guinea", "submission": "FASU prescribed Threshold Transaction Report form/process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply with the reporting requirement can constitute an offence.", "enforcement": "FASU / Bank of Papua New Guinea", "evidenceStatus": "verified-with-gap", "operationalImpact": "Aggregate linked transactions, trigger at K20,000 and enforce a ten-working-day maximum.", "evidenceIds": [ "amlb:evidence:cce25838", "amlb:evidence:8b979a42" ], "sourceEntityIds": [ "amlb:source-entity:375c6f0f", "amlb:source-entity:85193379" ] }, { "id": "PG-IEFT", "jurisdictionCode": "PG", "jurisdictionName": "Papua New Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "International electronic funds transfer report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions/reporting entities subject to PNG IEFT reporting.", "trigger": "International electronic funds transfer of K20,000 or more, including linked transfers that collectively meet the threshold.", "deadline": "Report as soon as practicable and within a maximum of 10 working days from the transfer, or the last linked transfer.", "recipient": "FASU, Bank of Papua New Guinea", "submission": "FASU prescribed IEFT report form/process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply with the reporting requirement can constitute an offence.", "enforcement": "FASU / Bank of Papua New Guinea", "evidenceStatus": "verified-with-gap", "operationalImpact": "Aggregate linked IEFTs and preserve a filing workflow with a ten-working-day hard stop.", "evidenceIds": [ "amlb:evidence:cce25838", "amlb:evidence:8b979a42" ], "sourceEntityIds": [ "amlb:source-entity:375c6f0f", "amlb:source-entity:85193379" ] }, { "id": "PG-AML-CONTROLS", "jurisdictionCode": "PG", "jurisdictionName": "Papua New Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Papua New Guinea’s AML/CTF perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "FASU / Bank of Papua New Guinea", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "FASU / Bank of Papua New Guinea", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:cce25838", "amlb:evidence:8b979a42" ], "sourceEntityIds": [ "amlb:source-entity:375c6f0f", "amlb:source-entity:85193379" ] }, { "id": "FJ-STR", "jurisdictionCode": "FJ", "jurisdictionName": "Fiji", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and covered DNFBPs under Fiji’s Financial Transactions Reporting framework.", "trigger": "A transaction or attempted transaction meets the statutory suspicion threshold.", "deadline": "Report to the Fiji FIU within the period prescribed by the FTR Act, Regulations and current FIU notices. No universal numeric filing deadline across all covered sectors is verified in mapped sources.", "recipient": "Fiji Financial Intelligence Unit, Reserve Bank of Fiji", "submission": "FIU prescribed STR form/channel.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to report may attract penalties under the FTR framework.", "enforcement": "Fiji FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalate immediately and map the filing SLA to the current sector-specific FTR rule or FIU notice.", "evidenceIds": [ "amlb:evidence:dcb35901", "amlb:evidence:9fea6bae", "amlb:evidence:5459a2a8" ], "sourceEntityIds": [ "amlb:source-entity:b97a3a92" ] }, { "id": "FJ-AML-CONTROLS", "jurisdictionCode": "FJ", "jurisdictionName": "Fiji", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and covered DNFBPs under the FTR Act.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Fiji FIU / Reserve Bank of Fiji", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Fiji FIU / Reserve Bank of Fiji", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:dcb35901", "amlb:evidence:9fea6bae", "amlb:evidence:5459a2a8" ], "sourceEntityIds": [ "amlb:source-entity:b97a3a92" ] }, { "id": "VU-STR", "jurisdictionCode": "VU", "jurisdictionName": "Vanuatu", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious activity / transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within Vanuatu’s AML/CTF Act perimeter.", "trigger": "Suspicion or reasonable grounds meeting the reporting threshold under Part 6 of the AML/CTF Act.", "deadline": "Report to the Vanuatu FIU in accordance with Part 6 and applicable current rules; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Vanuatu Financial Intelligence Unit", "submission": "FIU prescribed reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply can attract sanctions under the AML/CTF framework.", "enforcement": "Vanuatu FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and record the exact statutory clock applicable to the reporting entity before filing.", "evidenceIds": [ "amlb:evidence:907e7615", "amlb:evidence:bc5277e5" ], "sourceEntityIds": [ "amlb:source-entity:5e899f98" ] }, { "id": "VU-AML-CONTROLS", "jurisdictionCode": "VU", "jurisdictionName": "Vanuatu", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Vanuatu’s AML/CTF perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Vanuatu FIU / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Vanuatu FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:907e7615", "amlb:evidence:bc5277e5" ], "sourceEntityIds": [ "amlb:source-entity:5e899f98" ] }, { "id": "WS-STR", "jurisdictionCode": "WS", "jurisdictionName": "Samoa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions subject to Samoa’s Money Laundering Prevention Act.", "trigger": "A reporting institution forms suspicion requiring reporting under the MLPA.", "deadline": "Report as soon as possible after forming suspicion, but no later than 2 working days.", "recipient": "Samoa Financial Intelligence Unit, Central Bank of Samoa", "submission": "FIU prescribed STR process/form.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to meet statutory AML obligations can attract enforcement under the MLPA framework.", "enforcement": "Money Laundering Prevention Authority / Samoa FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Start the clock when suspicion is formed and keep evidence of submission within two working days.", "evidenceIds": [ "amlb:evidence:3fb4b1ee" ], "sourceEntityIds": [ "amlb:source-entity:a3831b22" ] }, { "id": "WS-RECORDS", "jurisdictionCode": "WS", "jurisdictionName": "Samoa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Business transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions subject to Samoa’s MLPA.", "trigger": "Creation of relevant business-transaction and AML/CFT records.", "deadline": "Keep relevant business transaction records for a minimum of 5 years.", "recipient": "Money Laundering Prevention Authority / Samoa FIU", "submission": "Internal records kept retrievable for supervision or lawful request.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Inadequate records can result in non-compliance with the MLPA preventive framework.", "enforcement": "Money Laundering Prevention Authority / Samoa FIU", "evidenceStatus": "verified", "operationalImpact": "Apply a five-year minimum retention rule with legal-hold and longer-sector-rule overrides.", "evidenceIds": [ "amlb:evidence:3fb4b1ee" ], "sourceEntityIds": [ "amlb:source-entity:a3831b22" ] }, { "id": "WS-AML-CONTROLS", "jurisdictionCode": "WS", "jurisdictionName": "Samoa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions within Samoa’s MLPA perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Money Laundering Prevention Authority / Samoa FIU", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Money Laundering Prevention Authority / Samoa FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:3fb4b1ee" ], "sourceEntityIds": [ "amlb:source-entity:a3831b22" ] }, { "id": "TO-STR", "jurisdictionCode": "TO", "jurisdictionName": "Tonga", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions subject to Tonga’s MLPC reporting framework.", "trigger": "A transaction is identified as suspicious under the MLPC framework.", "deadline": "Report to the Transactions Reporting Authority as required by the MLPC Act and TRA guidance; the current public page does not state one numeric filing clock.", "recipient": "Transactions Reporting Authority (TRA), National Reserve Bank of Tonga", "submission": "TRA Suspicious Transaction Report form/process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Penalties exist for failure to report or to supply full and correct information.", "enforcement": "Transactions Reporting Authority / NRBT", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate escalation and use the current TRA form; verify the operative sector clock before submission.", "evidenceIds": [ "amlb:evidence:1d0c9bae" ], "sourceEntityIds": [ "amlb:source-entity:b67a0a5b" ] }, { "id": "TO-CTR", "jurisdictionCode": "TO", "jurisdictionName": "Tonga", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions/personnel subject to Tonga’s currency-transaction reporting rule.", "trigger": "A currency transaction meets the reportable criteria under Regulation 23(5) and current TRA rules.", "deadline": "Submit the prescribed Currency Transaction Report under the applicable regulation; the current TRA page does not publish one numeric filing clock/threshold for this report.", "recipient": "Transactions Reporting Authority, NRBT", "submission": "TRA Currency Transaction Report form.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Penalties exist for failure to report or provide complete/correct information.", "enforcement": "Transactions Reporting Authority / NRBT", "evidenceStatus": "verified-with-gap", "operationalImpact": "Parameterise the current threshold and clock from the operative regulation/TRA instruction before automating CTR generation.", "evidenceIds": [ "amlb:evidence:1d0c9bae" ], "sourceEntityIds": [ "amlb:source-entity:b67a0a5b" ] }, { "id": "TO-AML-CONTROLS", "jurisdictionCode": "TO", "jurisdictionName": "Tonga", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and cash dealers subject to Tonga’s MLPC framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Transactions Reporting Authority / NRBT", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Transactions Reporting Authority / NRBT", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:1d0c9bae" ], "sourceEntityIds": [ "amlb:source-entity:b67a0a5b" ] }, { "id": "SB-STR", "jurisdictionCode": "SB", "jurisdictionName": "Solomon Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Solomon Islands AML/CFT reporting perimeter.", "trigger": "A transaction/activity meets the statutory suspicion threshold.", "deadline": "Report to the Solomon Islands Financial Intelligence Unit under the applicable AML/CFT law and guidance; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Solomon Islands Financial Intelligence Unit (SIFIU), Central Bank of Solomon Islands", "submission": "SIFIU prescribed reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Non-reporting can attract consequences under the applicable AML/CFT framework.", "enforcement": "SIFIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain prompt internal escalation and map the statutory clock before operational filing.", "evidenceIds": [ "amlb:evidence:3b16b2ef", "amlb:evidence:a8008e8f" ], "sourceEntityIds": [ "amlb:source-entity:58e1ffa6" ] }, { "id": "SB-AML-CONTROLS", "jurisdictionCode": "SB", "jurisdictionName": "Solomon Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Solomon Islands AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "SIFIU / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "SIFIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:3b16b2ef", "amlb:evidence:a8008e8f" ], "sourceEntityIds": [ "amlb:source-entity:58e1ffa6" ] }, { "id": "TL-STR", "jurisdictionCode": "TL", "jurisdictionName": "Timor-Leste", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial and non-financial reporting entities covered by Law No. 17/2011.", "trigger": "Reasonable grounds exist to suspect an unusual transaction or money-laundering/terrorist-financing activity.", "deadline": "Immediately report / communicate the suspicious transaction to the FIU.", "recipient": "Financial Information Unit (UIF/FIU), Banco Central de Timor-Leste", "submission": "FIU prescribed STR reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to submit an STR can constitute an administrative breach and attract fines; BCTL’s FIU page publishes separate ranges for natural and legal persons.", "enforcement": "Financial Information Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat suspicion as a zero-delay escalation event and preserve the timestamped filing evidence.", "evidenceIds": [ "amlb:evidence:bd27e62b" ], "sourceEntityIds": [ "amlb:source-entity:727f9f37" ] }, { "id": "TL-AML-CONTROLS", "jurisdictionCode": "TL", "jurisdictionName": "Timor-Leste", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial and non-financial reporting entities covered by Law No. 17/2011.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Information Unit / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Information Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:bd27e62b" ], "sourceEntityIds": [ "amlb:source-entity:727f9f37" ] }, { "id": "BT-STR", "jurisdictionCode": "BT", "jurisdictionName": "Bhutan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Bhutan’s AML/CFT Act and FID reporting requirements.", "trigger": "Suspicion is formed or information is received that triggers the suspicious-transaction reporting duty.", "deadline": "Report to FID no later than 2 working days after forming the suspicion or receiving the information being reported.", "recipient": "Financial Intelligence Department (FID), Royal Monetary Authority of Bhutan", "submission": "FID prescribed STR / Financial Intelligence Analysis System reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Delayed or deficient reporting can attract regulatory sanctions; RMA has publicly enforced AML/CFT-system and STR-filing failures.", "enforcement": "FID / Royal Monetary Authority of Bhutan", "evidenceStatus": "verified-with-gap", "operationalImpact": "Start the filing SLA at suspicion/information receipt and retain system acknowledgement before the two-working-day deadline.", "evidenceIds": [ "amlb:evidence:bcb92359", "amlb:evidence:f5ef9868", "amlb:evidence:17f05c47" ], "sourceEntityIds": [ "amlb:source-entity:1d6385d9" ] }, { "id": "BT-AML-CONTROLS", "jurisdictionCode": "BT", "jurisdictionName": "Bhutan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Bhutan’s AML/CFT Act perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "FID / Royal Monetary Authority of Bhutan", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "FID / Royal Monetary Authority of Bhutan", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:bcb92359", "amlb:evidence:f5ef9868", "amlb:evidence:17f05c47" ], "sourceEntityIds": [ "amlb:source-entity:1d6385d9" ] }, { "id": "MM-STR", "jurisdictionCode": "MM", "jurisdictionName": "Myanmar (Burma)", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting organizations subject to Myanmar AML reporting obligations.", "trigger": "A transaction/activity meets the suspicious-reporting threshold under applicable Myanmar AML law and MFIU rules.", "deadline": "Submit the STR to MFIU in accordance with the current AML law and reporting method. No universal numeric filing deadline is verified in mapped sources.", "recipient": "Myanmar Financial Intelligence Unit (MFIU)", "submission": "MFIU reporting forms/methods, including the web-based online reporting system as implemented for reporting entities.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may attract consequences under the applicable AML framework.", "enforcement": "Myanmar Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use the current MFIU electronic channel and keep the internal escalation SLA shorter than any applicable statutory maximum.", "evidenceIds": [ "amlb:evidence:8c86bb19", "amlb:evidence:863e4a41" ], "sourceEntityIds": [ "amlb:source-entity:b63c50cc" ] }, { "id": "MM-AML-CONTROLS", "jurisdictionCode": "MM", "jurisdictionName": "Myanmar (Burma)", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting organizations subject to Myanmar AML/CFT requirements.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "MFIU / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "MFIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:8c86bb19", "amlb:evidence:863e4a41" ], "sourceEntityIds": [ "amlb:source-entity:b63c50cc" ] }, { "id": "LA-STR", "jurisdictionCode": "LA", "jurisdictionName": "Laos", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs that are reporting entities under Lao PDR AML/CFT law.", "trigger": "Information or activity is suspicious of money laundering or terrorist financing.", "deadline": "Report to AMLIO under the applicable AML/CFT law and instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Anti-Money Laundering Intelligence Office (AMLIO), Bank of Lao PDR", "submission": "AMLIO online reporting system or prescribed STR form/process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may attract sanctions under the applicable AML/CFT framework.", "enforcement": "AMLIO / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route STRs through AMLIO’s current reporting mechanism and map the operative filing deadline to the entity’s sector rule.", "evidenceIds": [ "amlb:evidence:828f58a4", "amlb:evidence:c9cc59fa" ], "sourceEntityIds": [ "amlb:source-entity:fcc27584" ] }, { "id": "LA-CTR", "jurisdictionCode": "LA", "jurisdictionName": "Laos", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Lao PDR cash-transaction reporting.", "trigger": "A cash transaction meets the criteria prescribed by AMLIO / applicable AML/CFT law.", "deadline": "Submit the CTR under the current AMLIO rule; mapped sources do not assert a universal threshold or numeric deadline.", "recipient": "AMLIO, Bank of Lao PDR", "submission": "AMLIO online reporting system or prescribed CTR form.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may attract sanctions under the applicable framework.", "enforcement": "AMLIO / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Parameterise the current threshold and deadline before automating cash-report detection and submission.", "evidenceIds": [ "amlb:evidence:828f58a4", "amlb:evidence:c9cc59fa" ], "sourceEntityIds": [ "amlb:source-entity:fcc27584" ] }, { "id": "LA-AML-CONTROLS", "jurisdictionCode": "LA", "jurisdictionName": "Laos", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs that are reporting entities under Lao PDR AML/CFT law.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "AMLIO / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "AMLIO / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:828f58a4", "amlb:evidence:c9cc59fa" ], "sourceEntityIds": [ "amlb:source-entity:fcc27584" ] }, { "id": "KZ-STR", "jurisdictionCode": "KZ", "jurisdictionName": "Kazakhstan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction financial-monitoring report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Subjects of financial monitoring under Kazakhstan AML/CFT law.", "trigger": "A transaction is recognized as suspicious under the statutory criteria, regardless of the manner or amount.", "deadline": "Submit financial-monitoring information under the applicable Law and current implementing rules; mapped sources do not compress the rule set into one universal numeric clock.", "recipient": "Authorized financial monitoring body of the Republic of Kazakhstan", "submission": "Electronic financial-monitoring reporting process prescribed by current rules.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure or late submission can attract administrative or other sanctions under Kazakhstan law.", "enforcement": "Authorized financial monitoring body / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map each report event to the current electronic-reporting rule and preserve the recognition/submission timestamps.", "evidenceIds": [ "amlb:evidence:f3e65079", "amlb:evidence:ead346d4" ], "sourceEntityIds": [ "amlb:source-entity:e60eb06f" ] }, { "id": "KZ-AML-CONTROLS", "jurisdictionCode": "KZ", "jurisdictionName": "Kazakhstan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Subjects of financial monitoring under Kazakhstan AML/CFT law.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Authorized financial monitoring body / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Authorized financial monitoring body / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:f3e65079", "amlb:evidence:ead346d4" ], "sourceEntityIds": [ "amlb:source-entity:e60eb06f" ] }, { "id": "KG-STR", "jurisdictionCode": "KG", "jurisdictionName": "Kyrgyzstan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious operation / transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities subject to Kyrgyz Republic financial-monitoring reporting obligations.", "trigger": "An operation/transaction is recognized as suspicious under the applicable financial-monitoring criteria.", "deadline": "Submit the suspicious transaction report to the FIU within 5 hours from recognition.", "recipient": "State Financial Intelligence Service under the Ministry of Finance of the Kyrgyz Republic", "submission": "FIU prescribed financial-monitoring reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Late or deficient reporting can attract consequences under the applicable financial-monitoring framework.", "enforcement": "State Financial Intelligence Service / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat recognition as the timestamp that starts a five-hour hard filing SLA and retain the FIU submission receipt.", "evidenceIds": [ "amlb:evidence:13ede1ae", "amlb:evidence:6dfeefce" ], "sourceEntityIds": [ "amlb:source-entity:c1c3fc23" ] }, { "id": "KG-AML-CONTROLS", "jurisdictionCode": "KG", "jurisdictionName": "Kyrgyzstan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities subject to Kyrgyz Republic financial-monitoring obligations.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "State Financial Intelligence Service / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "State Financial Intelligence Service / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:13ede1ae", "amlb:evidence:6dfeefce" ], "sourceEntityIds": [ "amlb:source-entity:c1c3fc23" ] }, { "id": "UZ-STR", "jurisdictionCode": "UZ", "jurisdictionName": "Uzbekistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting / escalation", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Organizations subject to Uzbekistan AML/CFT/CPF internal-control and reporting requirements.", "trigger": "A prepared, ongoing or completed transaction is classified as suspicious for ML/TF purposes under applicable internal-control rules.", "deadline": "Report/escalate to the specially authorized state body within the period prescribed by the applicable sector internal-control rules; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Department for Combating Tax, Currency Crimes and Money Laundering under the General Prosecutor’s Office of Uzbekistan", "submission": "Reporting mechanism prescribed by the applicable sector internal-control rules.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Non-compliance can attract sanctions under applicable AML/CFT/CPF law and supervisory rules.", "enforcement": "Specially authorized state body / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the institution’s sector internal-control rule to the FIU/reporting workflow and preserve suspicion-classification timestamps.", "evidenceIds": [ "amlb:evidence:b1d4965b", "amlb:evidence:9d572e1a" ], "sourceEntityIds": [ "amlb:source-entity:263ab636" ] }, { "id": "UZ-AML-CONTROLS", "jurisdictionCode": "UZ", "jurisdictionName": "Uzbekistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Organizations subject to Uzbekistan AML/CFT/CPF internal-control requirements.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Specially authorized state body / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Specially authorized state body / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:b1d4965b", "amlb:evidence:9d572e1a" ], "sourceEntityIds": [ "amlb:source-entity:263ab636" ] }, { "id": "TJ-STR", "jurisdictionCode": "TJ", "jurisdictionName": "Tajikistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities subject to Tajikistan AML/CFT/PF rules.", "trigger": "A transaction is detected as suspicious under the applicable AML/CFT/PF criteria.", "deadline": "Report to the Financial Monitoring Department in accordance with current law and reporting rules; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Monitoring Department, National Bank of Tajikistan", "submission": "Prescribed financial-monitoring reporting process.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to meet reporting duties can attract consequences under the applicable legal and supervisory framework.", "enforcement": "Financial Monitoring Department / National Bank of Tajikistan", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain prompt internal escalation and map the statutory clock from the current sector reporting rule.", "evidenceIds": [ "amlb:evidence:3d571d0c", "amlb:evidence:bed0f2d8" ], "sourceEntityIds": [ "amlb:source-entity:4a102539" ] }, { "id": "TJ-AML-CONTROLS", "jurisdictionCode": "TJ", "jurisdictionName": "Tajikistan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities subject to Tajikistan AML/CFT/PF rules.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Monitoring Department / National Bank of Tajikistan", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Monitoring Department / National Bank of Tajikistan", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:3d571d0c", "amlb:evidence:bed0f2d8" ], "sourceEntityIds": [ "amlb:source-entity:4a102539" ] }, { "id": "PW-STR", "jurisdictionCode": "PW", "jurisdictionName": "Palau", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report and execution hold", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions within the Republic of Palau Financial Institutions Act.", "trigger": "A transaction appears to have an unlawful purpose or is suspected to relate to serious criminal activity.", "deadline": "Do not carry out the transaction until a confidential written report is submitted to FIC and FIU. If delay is impossible or likely to frustrate pursuit of beneficiaries, inform FIC and FIU in writing immediately afterwards.", "recipient": "Palau Financial Institutions Commission (FIC) and Financial Intelligence Unit (FIU)", "submission": "Confidential written report containing the information required by 26 PNCA §1062.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "The framework permits FIU instructions not to execute the transaction and subjects AML/CFT procedures/reporting to FIC examination.", "enforcement": "Palau FIC / FIU", "evidenceStatus": "verified", "evidenceNote": "Section 1062 expressly sets the pre-execution report requirement and immediate-after exception.", "operationalImpact": "Insert a transaction hold into the escalation workflow and allow the post-execution exception only where the statutory impossibility/frustration condition is documented.", "evidenceIds": [ "amlb:evidence:fdb99f3b", "amlb:evidence:13b086a1" ], "sourceEntityIds": [ "amlb:source-entity:966909c1" ] }, { "id": "PW-AML-CONTROLS", "jurisdictionCode": "PW", "jurisdictionName": "Palau", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions within Palau’s AML/CFT supervisory perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Palau FIC / FIU", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Palau FIC / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:fdb99f3b", "amlb:evidence:13b086a1" ], "sourceEntityIds": [ "amlb:source-entity:966909c1" ] }, { "id": "MO-STR", "jurisdictionCode": "MO", "jurisdictionName": "Macao SAR China", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Entities/professionals subject to Macao SAR suspicious-transaction reporting requirements.", "trigger": "A transaction/activity is detected as suspicious under the applicable AML/CFT law or sector guideline.", "deadline": "Report to GIF under the applicable law and sector rule; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Office of Unitary Police Service (GIF), Macao SAR", "submission": "GIF online STR reporting system, prescribed sector form or other accepted GIF channel.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may attract sanctions under the applicable reporting/supervisory framework.", "enforcement": "GIF / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use the correct GIF sector form/channel and store the sector-specific filing SLA with the rule citation.", "evidenceIds": [ "amlb:evidence:81d939b7", "amlb:evidence:9b2b622a", "amlb:evidence:12b1ea54" ], "sourceEntityIds": [ "amlb:source-entity:43e6ee0d" ] }, { "id": "MO-AML-CONTROLS", "jurisdictionCode": "MO", "jurisdictionName": "Macao SAR China", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities/professionals within Macao SAR’s AML/CFT reporting perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "GIF / competent sector supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "GIF / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:81d939b7", "amlb:evidence:9b2b622a", "amlb:evidence:12b1ea54" ], "sourceEntityIds": [ "amlb:source-entity:43e6ee0d" ] }, { "id": "GE-STR", "jurisdictionCode": "GE", "jurisdictionName": "Georgia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Accountable persons under Georgia’s AML/CFT Law.", "trigger": "Reasonable doubt is raised in relation to a transaction under Article 25.", "deadline": "Submit the report to the Service on the day the reasonable doubt is raised.", "recipient": "Financial Monitoring Service of Georgia", "submission": "Electronic or written form under the procedure established by the head of the Service.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may trigger supervisory or statutory measures under the AML/CFT framework.", "enforcement": "Financial Monitoring Service / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat the suspicion timestamp as a same-day filing deadline and retain proof of electronic/written submission.", "evidenceIds": [ "amlb:evidence:bd7fe0a1" ], "sourceEntityIds": [ "amlb:source-entity:0d82646b" ] }, { "id": "GE-RECORDS", "jurisdictionCode": "GE", "jurisdictionName": "Georgia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT information and record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Accountable persons under Georgia’s AML/CFT Law.", "trigger": "Termination of a business relationship, completion of a single transaction, transaction/report creation or other retained AML/CFT evidence.", "deadline": "Retain required information/documents and reports for 5 years; the period may be extended by up to 5 additional years on request of the Service or supervisory body.", "recipient": "Financial Monitoring Service / competent supervisory body", "submission": "Internal retrievable records; provide to competent authorities within the required time when requested.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Inadequate retention or retrievability can constitute non-compliance.", "enforcement": "Financial Monitoring Service / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure five-year minimum retention plus an extendable legal-hold mechanism for regulator/FMS requests.", "evidenceIds": [ "amlb:evidence:bd7fe0a1" ], "sourceEntityIds": [ "amlb:source-entity:0d82646b" ] }, { "id": "GE-AML-CONTROLS", "jurisdictionCode": "GE", "jurisdictionName": "Georgia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Accountable persons under Georgia’s AML/CFT Law.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Monitoring Service / competent supervisory body", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Monitoring Service / competent supervisory body", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:bd7fe0a1" ], "sourceEntityIds": [ "amlb:source-entity:0d82646b" ] }, { "id": "AM-STR", "jurisdictionCode": "AM", "jurisdictionName": "Armenia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / business relationship report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within Armenia’s AML/CFT framework.", "trigger": "A transaction or business relationship meets the statutory suspicion threshold.", "deadline": "Report to the Financial Monitoring Center within the period prescribed by the applicable AML/CFT law and reporting procedure; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Monitoring Center, Central Bank of Armenia", "submission": "FMC prescribed reporting process/forms.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to report can attract sanctions under the AML/CFT framework.", "enforcement": "Financial Monitoring Center / Central Bank of Armenia / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate escalation and map the current FMC filing period to the entity’s applicable reporting procedure.", "evidenceIds": [ "amlb:evidence:8ccbcae9", "amlb:evidence:7766acac" ], "sourceEntityIds": [ "amlb:source-entity:5d107462" ] }, { "id": "AM-AML-CONTROLS", "jurisdictionCode": "AM", "jurisdictionName": "Armenia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Armenia’s AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Monitoring Center / competent supervisor", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Monitoring Center / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:8ccbcae9", "amlb:evidence:7766acac" ], "sourceEntityIds": [ "amlb:source-entity:5d107462" ] }, { "id": "AZ-STR", "jurisdictionCode": "AZ", "jurisdictionName": "Azerbaijan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report and suspension rule", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obliged persons subject to Azerbaijan AML/CFT law.", "trigger": "A transaction meets the suspicion conditions in Article 11.2 and, for financial institutions, falls within the suspension mechanics of Articles 11.5–11.6.", "deadline": "For Article 11.5 transactions, suspend and submit information/documents immediately without conducting the transaction; where the statutory exception in Article 11.6 applies, inform the financial monitoring organ immediately after conducting it.", "recipient": "Financial Monitoring Service / financial monitoring organ of Azerbaijan", "submission": "Prescribed information/document submission to the financial monitoring organ.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Violations can lead to supervisory measures, administrative consequences and possible licence/certificate consequences under the framework.", "enforcement": "Financial Monitoring Service / competent supervision authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Build a transaction-hold decision into the STR workflow and document whether the pre-execution or immediate-after branch applies.", "evidenceIds": [ "amlb:evidence:067807b3" ], "sourceEntityIds": [ "amlb:source-entity:5503f270" ] }, { "id": "AZ-MONITORING-REPORTS", "jurisdictionCode": "AZ", "jurisdictionName": "Azerbaijan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Article 11 transaction monitoring reports", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged persons required to submit information/documents on the categories listed in Article 11.", "trigger": "A transaction falls within Article 11.1 / specified Article 11.3 categories, or within the immediate-report categories referenced in Article 11.4.", "deadline": "For Article 11.1, 11.3.1 and 11.3.3 categories: within 3 working days after the transaction. For Article 4.14, 4.15 and 11.3.2 cases: immediately after the reporting grounds are identified, no later than the end of that business day.", "recipient": "Financial Monitoring Service / financial monitoring organ of Azerbaijan", "submission": "Prescribed information/document submission format.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure or late submission can trigger supervisory/administrative measures under the AML/CFT framework.", "enforcement": "Financial Monitoring Service / competent supervision authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain separate rule-engine queues for the three-working-day categories and the immediate/end-of-day categories.", "evidenceIds": [ "amlb:evidence:067807b3" ], "sourceEntityIds": [ "amlb:source-entity:5503f270" ] }, { "id": "AZ-AML-CONTROLS", "jurisdictionCode": "AZ", "jurisdictionName": "Azerbaijan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Obliged persons within Azerbaijan’s AML/CFT perimeter.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "Financial Monitoring Service / competent supervision authority", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "Financial Monitoring Service / competent supervision authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:067807b3" ], "sourceEntityIds": [ "amlb:source-entity:5503f270" ] }, { "id": "PS-STR", "jurisdictionCode": "PS", "jurisdictionName": "Palestinian Territories", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to the Palestinian AML/CFT framework.", "trigger": "A transaction/activity meets the suspicion threshold under Decree Law No. 39 of 2022 and applicable sector instructions.", "deadline": "Report to the Financial Follow-up Unit under the current Decree Law and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Follow-up Unit (FFU), Palestine", "submission": "FFU prescribed reporting process/channel under the applicable sector instruction.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Failure to comply may attract supervisory or statutory measures under the AML/CFT framework.", "enforcement": "FFU / competent supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and attach the specific FFU/supervisory instruction that governs the reporting entity’s filing SLA.", "evidenceIds": [ "amlb:evidence:087b7e03", "amlb:evidence:8c8bc58c" ], "sourceEntityIds": [ "amlb:source-entity:addc227d" ] }, { "id": "PS-AML-CONTROLS", "jurisdictionCode": "PS", "jurisdictionName": "Palestinian Territories", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based AML/CFT controls, CDD and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs subject to the Palestinian AML/CFT framework.", "trigger": "Continuous while carrying on covered business; enhanced measures apply when higher-risk customers, products, transactions or relationships are identified.", "deadline": "Maintain risk assessment, CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the applicable law and sector rules.", "recipient": "FFU / competent supervisory authority", "submission": "Internal AML/CFT programme, CDD/beneficial-owner files, monitoring, escalation and retained evidence; supervisory submissions apply when separately required.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control, CDD or recordkeeping failures can attract supervisory, administrative and/or criminal consequences under the applicable AML/CFT framework.", "enforcement": "FFU / competent supervisory authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the exact sector rule and preserve auditable evidence of CDD, beneficial ownership, monitoring, escalation, training and record retention.", "evidenceIds": [ "amlb:evidence:087b7e03", "amlb:evidence:8c8bc58c" ], "sourceEntityIds": [ "amlb:source-entity:addc227d" ] }, { "id": "CM-STR", "jurisdictionCode": "CM", "jurisdictionName": "Cameroon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Cameroon subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CM-TFS-FREEZE", "jurisdictionCode": "CM", "jurisdictionName": "Cameroon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Cameroon holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CF-STR", "jurisdictionCode": "CF", "jurisdictionName": "Central African Republic", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Central African Republic subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CF-TFS-FREEZE", "jurisdictionCode": "CF", "jurisdictionName": "Central African Republic", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Central African Republic holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "TD-STR", "jurisdictionCode": "TD", "jurisdictionName": "Chad", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Chad subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "TD-TFS-FREEZE", "jurisdictionCode": "TD", "jurisdictionName": "Chad", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Chad holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CG-STR", "jurisdictionCode": "CG", "jurisdictionName": "Congo - Brazzaville", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Republic of the Congo subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CG-TFS-FREEZE", "jurisdictionCode": "CG", "jurisdictionName": "Congo - Brazzaville", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Republic of the Congo holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "GA-STR", "jurisdictionCode": "GA", "jurisdictionName": "Gabon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Gabon subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "GA-TFS-FREEZE", "jurisdictionCode": "GA", "jurisdictionName": "Gabon", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Gabon holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "GQ-STR", "jurisdictionCode": "GQ", "jurisdictionName": "Equatorial Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under current CEMAC AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Equatorial Guinea subject to the current CEMAC AML/CFT/CPF preventive framework.", "trigger": "Knowledge, suspicion or reasonable grounds regarding funds, transactions or activity potentially linked to money laundering, predicate crime, terrorist financing or proliferation financing under the applicable framework.", "deadline": "Report promptly/immediately when the suspicion threshold is met under Regulation No. 02/24; mapped sources do not assert a separate country-specific numeric outer limit unless one is independently verified.", "recipient": "National financial intelligence unit / ANIF", "submission": "Use the national FIU/ANIF reporting channel and format applicable to the reporting entity; the exact current country portal/workflow remains an explicit operational gap in mapped sources.", "applicability": "Current CEMAC framework in force; reviewed 2026-08-19.", "consequence": "Failure to report or related AML/CFT control failures can attract sanctions under the regional framework and national enforcement provisions.", "enforcement": "National FIU / competent supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Configure immediate internal escalation at the suspicion threshold and map the entity to the exact national ANIF filing channel before relying on a numeric SLA.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "GQ-TFS-FREEZE", "jurisdictionCode": "GQ", "jurisdictionName": "Equatorial Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Targeted financial sanctions freeze and frozen-asset notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Natural and legal persons in Equatorial Guinea holding or controlling funds or other assets of designated persons/entities under the current CEMAC targeted-financial-sanctions framework.", "trigger": "A sanctions designation or match engages the regional freeze obligation for funds or other assets within the scope of Regulation No. 04/24.", "deadline": "Freeze covered funds/assets without delay and without prior notice. Communicate information on frozen assets/measures, including attempted operations covered by the rule, to the competent authority/state body no later than 24 hours under Article 35.", "recipient": "Competent national TFS authority and designated state body administering frozen assets", "submission": "Immediate freeze/control action plus the prescribed national notification to the competent authority; exact country submission address/portal is retained as a gap.", "applicability": "Current CEMAC TFS framework reviewed 2026-08-19.", "consequence": "Failure to freeze or notify can expose the person/entity to applicable sanctions and enforcement measures.", "enforcement": "Competent national TFS authority / supervisor / enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat a confirmed designation match as a zero-delay control event, preserve the freeze decision trail, and route the 24-hour notification through the verified national authority channel.", "evidenceIds": [ "amlb:evidence:1e9b71de", "amlb:evidence:f2c5392e" ], "sourceEntityIds": [ "amlb:source-entity:c3089442" ] }, { "id": "CD-STR", "jurisdictionCode": "CD", "jurisdictionName": "Congo - Kinshasa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report to CENAREF", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to the DRC AML/CFT framework.", "trigger": "A transaction or activity meets the statutory suspicion threshold.", "deadline": "Submit the suspicious transaction report to CENAREF when the reporting duty is triggered; mapped sources do not assert a universal numeric outer limit from the current public operational material.", "recipient": "CENAREF", "submission": "Use CENAREF’s prescribed reporting process; TRANSACTUS is identified by CENAREF as a secure digital STR reporting tool for financial institutions.", "applicability": "Current CENAREF operational material reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under the applicable AML/CFT framework.", "enforcement": "CENAREF / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation, map the entity to the applicable CENAREF reporting workflow and retain proof of submission.", "evidenceIds": [ "amlb:evidence:432b0578", "amlb:evidence:ed3ecb8b" ], "sourceEntityIds": [ "amlb:source-entity:e7c79b68" ] }, { "id": "CD-RECORDS", "jurisdictionCode": "CD", "jurisdictionName": "Congo - Kinshasa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Customer and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities subject to the DRC AML/CFT recordkeeping requirements.", "trigger": "Creation of customer-identification, account/business-relationship or transaction records.", "deadline": "Retain the relevant transaction and customer documentation for 10 years under the current CENAREF summary of Articles 27–30.", "recipient": "CENAREF / competent supervisor on request or inspection", "submission": "Maintain retrievable customer, transaction and supporting records in the entity’s recordkeeping system.", "applicability": "Current requirement reviewed 2026-08-19.", "consequence": "Deficient retention can attract AML/CFT supervisory or statutory measures.", "enforcement": "CENAREF / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Set the retention engine to a ten-year minimum for covered records and preserve retrieval/audit capability throughout the period.", "evidenceIds": [ "amlb:evidence:432b0578", "amlb:evidence:ed3ecb8b" ], "sourceEntityIds": [ "amlb:source-entity:e7c79b68" ] }, { "id": "DJ-STR", "jurisdictionCode": "DJ", "jurisdictionName": "Djibouti", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Immediate suspicious transaction report to ANRF", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons subject to Law No. 178/AN/25/9ème L.", "trigger": "The reporting entity knows, suspects or has reasonable grounds to suspect funds/transactions within the statutory AML/CFT/CPF reporting threshold.", "deadline": "Report immediately to the ANRF. Where possible report before execution; if the transaction cannot be delayed, report immediately after execution. Supplementary relevant information is supplied without delay.", "recipient": "Agence Nationale du Renseignement Financier (ANRF)", "submission": "Written report and, where possible, electronic transmission in the form/process required by the ANRF.", "applicability": "Published 2026; reviewed 2026-08-19.", "consequence": "Failure to comply can attract the sanctions and measures provided by the AML/CFT/CPF law.", "enforcement": "ANRF / competent supervisory and enforcement authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Trigger real-time escalation on suspicion, block/delay execution where legally appropriate and feasible, and keep evidence of immediate ANRF submission.", "evidenceIds": [ "amlb:evidence:1f8805d3" ], "sourceEntityIds": [ "amlb:source-entity:29d94022" ] }, { "id": "DJ-RECORDS", "jurisdictionCode": "DJ", "jurisdictionName": "Djibouti", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons subject to the recordkeeping provisions of Law No. 178/AN/25/9ème L.", "trigger": "Creation of CDD, account/business correspondence or transaction records.", "deadline": "Retain the required CDD/account/business-relationship records for five years after the relevant relationship/transaction endpoint and transaction records for five years under Article 2-2-19.", "recipient": "ANRF / competent supervisor on request or inspection", "submission": "Maintain records in a retrievable form sufficient to reconstruct transactions and evidence CDD.", "applicability": "Published 2026; reviewed 2026-08-19.", "consequence": "Recordkeeping failures can attract statutory or supervisory measures.", "enforcement": "ANRF / competent supervisor", "evidenceStatus": "verified", "operationalImpact": "Configure a five-year minimum retention control tied to relationship termination/transaction completion and maintain rapid retrieval for authorities.", "evidenceIds": [ "amlb:evidence:1f8805d3" ], "sourceEntityIds": [ "amlb:source-entity:29d94022" ] }, { "id": "ET-STR", "jurisdictionCode": "ET", "jurisdictionName": "Ethiopia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under the amended AML/CFT framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Ethiopia’s AML/CFT framework.", "trigger": "A transaction/activity reaches the statutory suspicion threshold.", "deadline": "Report to the competent Ethiopian financial-intelligence authority under Proclamation No. 780/2013 as amended; mapped sources do not assert one universal current numeric outer limit without a provision-level consolidated source.", "recipient": "Financial Intelligence Service / competent financial-intelligence authority", "submission": "Use the reporting channel prescribed by the competent authority and applicable sector rules.", "applicability": "Current amended framework reviewed 2026-08-19.", "consequence": "Failure to report may attract measures under the applicable AML/CFT legislation.", "enforcement": "Financial Intelligence Service / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep a no-delay internal escalation control and attach the exact current sector/FIS filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:ea25697a", "amlb:evidence:1e474fe7", "amlb:evidence:e3c10cc5" ], "sourceEntityIds": [ "amlb:source-entity:aa7a093f" ] }, { "id": "ET-AML-CONTROLS", "jurisdictionCode": "ET", "jurisdictionName": "Ethiopia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, beneficial-ownership controls and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities and covered legal-person/control functions under Ethiopia’s current AML/CFT framework.", "trigger": "Continuous operation of covered business and onboarding/monitoring of customers, legal persons and beneficial owners.", "deadline": "Maintain risk-based CDD, beneficial-ownership identification, monitoring, internal controls and records for the periods prescribed by the amended framework and applicable directives; no universal retention period is generalized in mapped sources.", "recipient": "Financial Intelligence Service / competent supervisory or registration authority", "submission": "Maintain internal controls, CDD/BO files, monitoring evidence and records; submit/register BO information where the applicable 2026 regulation requires.", "applicability": "Current framework reviewed 2026-08-19.", "consequence": "Control or BO-compliance failures may attract administrative, supervisory or statutory consequences.", "enforcement": "Competent AML/CFT supervisor / registration authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map customer/BO lifecycle controls to the applicable directive and preserve auditable evidence of verification, monitoring and updates.", "evidenceIds": [ "amlb:evidence:ea25697a", "amlb:evidence:1e474fe7", "amlb:evidence:e3c10cc5" ], "sourceEntityIds": [ "amlb:source-entity:aa7a093f" ] }, { "id": "BI-STR", "jurisdictionCode": "BI", "jurisdictionName": "Burundi", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report under the current Burundi framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Burundi’s current AML/CFT legislation.", "trigger": "A transaction/activity meets the applicable statutory suspicion threshold.", "deadline": "Submit the report to the competent financial-intelligence unit under the current 2025/2026 framework; No universal numeric filing deadline is verified in mapped sources.", "recipient": "National financial intelligence unit / CNRF", "submission": "Use the current CNRF/prescribed reporting process applicable to the entity; exact portal/form detail is retained as an operational gap here.", "applicability": "Current reform package reviewed 2026-08-19.", "consequence": "Failure to report may attract sanctions under the applicable AML/CFT framework.", "enforcement": "CNRF / Banque de la République du Burundi / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and map the reporting entity to the exact CNRF filing instruction before fixing the external SLA.", "evidenceIds": [ "amlb:evidence:0f308adc", "amlb:evidence:3298d487", "amlb:evidence:bcd2c532" ], "sourceEntityIds": [ "amlb:source-entity:ec567062" ] }, { "id": "BI-AML-CONTROLS", "jurisdictionCode": "BI", "jurisdictionName": "Burundi", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "KYC, monitoring and internal AML/CFT controls", "timingType": "ongoing", "sectors": [ "financial-institutions" ], "appliesTo": "BRB-supervised financial institutions subject to the 2026 AML/CFT regulation and related circulars.", "trigger": "Continuous while carrying on regulated financial business; heightened measures apply where risk or suspicious indicators warrant.", "deadline": "Maintain KYC/CDD, transaction monitoring, internal AML/CFT controls and compliance processes on an ongoing basis under the current BRB framework; exact sector retention periods should be taken from the applicable rule/circular.", "recipient": "Banque de la République du Burundi / competent AML/CFT authority", "submission": "Internal programme, KYC/CDD files, monitoring evidence, controls, escalation and regulatory submissions where prescribed.", "applicability": "Current BRB framework reviewed 2026-08-19.", "consequence": "Control failures may attract BRB supervisory or statutory measures.", "enforcement": "Banque de la République du Burundi", "evidenceStatus": "verified-with-gap", "operationalImpact": "Refresh the financial-institution control framework against Regulation No. 02/2026 and the applicable KYC/typology/control circulars.", "evidenceIds": [ "amlb:evidence:0f308adc", "amlb:evidence:3298d487", "amlb:evidence:bcd2c532" ], "sourceEntityIds": [ "amlb:source-entity:ec567062" ] }, { "id": "ER-STR", "jurisdictionCode": "ER", "jurisdictionName": "Eritrea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Prompt suspicious transaction report", "timingType": "event-driven", "sectors": [ "financial-institutions" ], "appliesTo": "Financial institutions subject to Eritrea’s AML/CFT framework as assessed by ESAAMLG.", "trigger": "Reasonable grounds to suspect that funds or a transaction, including an attempted transaction, involve criminal proceeds or terrorist financing within the applicable framework.", "deadline": "Report promptly. The 2025 MER notes that a more specific timing/form/manner was not prescribed in the assessed framework, so no numeric outer limit is shown.", "recipient": "Financial Intelligence Unit / competent authority", "submission": "Use the reporting method prescribed by the competent authority; operational channel readiness/current mechanics require local verification.", "applicability": "Framework assessed in ESAAMLG MER adopted July 2025.", "consequence": "Failure to comply may attract applicable AML/CFT sanctions.", "enforcement": "Competent AML/CFT authority / supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use immediate internal escalation, then verify the current competent filing channel before treating the obligation as operationally closed.", "evidenceIds": [ "amlb:evidence:2c573124", "amlb:evidence:1ab6cb90" ], "sourceEntityIds": [ "amlb:source-entity:87782728" ] }, { "id": "ER-RECORDS", "jurisdictionCode": "ER", "jurisdictionName": "Eritrea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Financial-institution transaction and CDD record retention", "timingType": "ongoing", "sectors": [ "financial-institutions" ], "appliesTo": "Financial institutions subject to Eritrea’s AML/CFT recordkeeping rules.", "trigger": "Creation of transaction records, CDD files, account files or business correspondence.", "deadline": "Maintain transaction records for at least 10 years after completion and CDD/account/business correspondence for at least 10 years after termination of the relationship or relevant occasional transaction, as assessed in the 2025 MER.", "recipient": "Competent supervisor / enforcement authority on request", "submission": "Maintain retrievable records capable of reconstructing transactions and evidencing CDD.", "applicability": "Current framework assessed in ESAAMLG MER adopted July 2025.", "consequence": "Recordkeeping failures may attract supervisory or statutory measures.", "enforcement": "Competent AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Apply a ten-year minimum retention rule to in-scope FI records and preserve rapid retrieval for competent authorities.", "evidenceIds": [ "amlb:evidence:2c573124", "amlb:evidence:1ab6cb90" ], "sourceEntityIds": [ "amlb:source-entity:87782728" ] }, { "id": "LS-STR", "jurisdictionCode": "LS", "jurisdictionName": "Lesotho", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Lesotho subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Unit / competent authority", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit / competent authority / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:69b97b02", "amlb:evidence:0fc239d1" ], "sourceEntityIds": [ "amlb:source-entity:7ba98610" ] }, { "id": "LS-AML-CONTROLS", "jurisdictionCode": "LS", "jurisdictionName": "Lesotho", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Lesotho subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "Financial Intelligence Unit / competent authority / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:69b97b02", "amlb:evidence:0fc239d1" ], "sourceEntityIds": [ "amlb:source-entity:7ba98610" ] }, { "id": "KM-STR", "jurisdictionCode": "KM", "jurisdictionName": "Comoros", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Union of the Comoros subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "National financial intelligence unit / competent authority", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "National financial intelligence unit / competent authority / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:26fa3e4f", "amlb:evidence:e1022bc3" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "KM-AML-CONTROLS", "jurisdictionCode": "KM", "jurisdictionName": "Comoros", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Union of the Comoros subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "National financial intelligence unit / competent authority / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:26fa3e4f", "amlb:evidence:e1022bc3" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "CV-STR", "jurisdictionCode": "CV", "jurisdictionName": "Cape Verde", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Cabo Verde subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Unidade de Informação Financeira (UIF)", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "Unidade de Informação Financeira (UIF) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:d0b48578", "amlb:evidence:fa16098c", "amlb:evidence:11d7944f" ], "sourceEntityIds": [ "amlb:source-entity:5d70bc7f", "amlb:source-entity:be82df5e" ] }, { "id": "CV-AML-CONTROLS", "jurisdictionCode": "CV", "jurisdictionName": "Cape Verde", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Cabo Verde subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "Unidade de Informação Financeira (UIF) / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:d0b48578", "amlb:evidence:fa16098c", "amlb:evidence:11d7944f" ], "sourceEntityIds": [ "amlb:source-entity:5d70bc7f", "amlb:source-entity:be82df5e" ] }, { "id": "GM-STR", "jurisdictionCode": "GM", "jurisdictionName": "Gambia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in The Gambia subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Unit of The Gambia", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit of The Gambia / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:1e47e342" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "GM-AML-CONTROLS", "jurisdictionCode": "GM", "jurisdictionName": "Gambia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in The Gambia subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "Financial Intelligence Unit of The Gambia / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:1e47e342" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "GN-STR", "jurisdictionCode": "GN", "jurisdictionName": "Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Guinea subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "CENTIF / national financial intelligence unit", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "CENTIF / national financial intelligence unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:4ac04d5a" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "GN-AML-CONTROLS", "jurisdictionCode": "GN", "jurisdictionName": "Guinea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Guinea subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "CENTIF / national financial intelligence unit / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:4ac04d5a" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "LR-STR", "jurisdictionCode": "LR", "jurisdictionName": "Liberia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Liberia subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Agency (FIA)", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Agency (FIA) / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:400cf36e", "amlb:evidence:58b5c6b3", "amlb:evidence:c4898c51" ], "sourceEntityIds": [ "amlb:source-entity:13f896f1" ] }, { "id": "LR-AML-CONTROLS", "jurisdictionCode": "LR", "jurisdictionName": "Liberia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Liberia subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "Financial Intelligence Agency (FIA) / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:400cf36e", "amlb:evidence:58b5c6b3", "amlb:evidence:c4898c51" ], "sourceEntityIds": [ "amlb:source-entity:13f896f1" ] }, { "id": "SL-STR", "jurisdictionCode": "SL", "jurisdictionName": "Sierra Leone", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Sierra Leone subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "Financial Intelligence Unit Sierra Leone", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "Financial Intelligence Unit Sierra Leone / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:9af9640b", "amlb:evidence:112a38e5" ], "sourceEntityIds": [ "amlb:source-entity:e0e64a3e", "amlb:source-entity:be82df5e" ] }, { "id": "SL-AML-CONTROLS", "jurisdictionCode": "SL", "jurisdictionName": "Sierra Leone", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Sierra Leone subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "Financial Intelligence Unit Sierra Leone / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:9af9640b", "amlb:evidence:112a38e5" ], "sourceEntityIds": [ "amlb:source-entity:e0e64a3e", "amlb:source-entity:be82df5e" ] }, { "id": "ST-STR", "jurisdictionCode": "ST", "jurisdictionName": "São Tomé & Príncipe", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in São Tomé and Príncipe subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "National financial intelligence unit", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "National financial intelligence unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:0b5b0de1" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "ST-AML-CONTROLS", "jurisdictionCode": "ST", "jurisdictionName": "São Tomé & Príncipe", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in São Tomé and Príncipe subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "National financial intelligence unit / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:0b5b0de1" ], "sourceEntityIds": [ "amlb:source-entity:be82df5e" ] }, { "id": "MR-STR", "jurisdictionCode": "MR", "jurisdictionName": "Mauritania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities in Mauritania subject to the current AML/CFT framework.", "trigger": "A transaction/activity meets the applicable suspicion threshold under the national AML/CFT framework.", "deadline": "Report to the competent financial intelligence unit in accordance with the current national framework and applicable sector instructions; No universal numeric filing deadline is verified in mapped sources.", "recipient": "National financial intelligence unit", "submission": "Use the FIU/prescribed sector reporting channel and form; exact current portal, form or sector-specific clock remains an explicit mapping item where not independently verified.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Failure to report may attract statutory, administrative or supervisory measures under the applicable AML/CFT framework.", "enforcement": "National financial intelligence unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain immediate internal escalation and bind the entity to the verified current FIU filing instruction before setting a hard external SLA.", "evidenceIds": [ "amlb:evidence:dd3cdff0", "amlb:evidence:ceff542e" ], "sourceEntityIds": [ "amlb:source-entity:25600d98" ] }, { "id": "MR-AML-CONTROLS", "jurisdictionCode": "MR", "jurisdictionName": "Mauritania", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Risk-based CDD, monitoring, records and internal controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities in Mauritania subject to preventive AML/CFT obligations.", "trigger": "Continuous operation of covered business; customer onboarding, ongoing monitoring and elevated risk indicators trigger the applicable preventive measures.", "deadline": "Maintain risk-based CDD/beneficial-owner identification, ongoing monitoring, internal controls and records for the periods required by the current law and sector rules; mapped sources do not generalize an unsupported universal retention period.", "recipient": "National financial intelligence unit / competent supervisor", "submission": "Maintain internal AML/CFT programme documentation, CDD/BO files, monitoring/escalation evidence and retrievable records; make regulatory submissions when the applicable rule requires.", "applicability": "Current framework/evaluation material reviewed 2026-08-19.", "consequence": "Preventive-control failures may attract supervisory, administrative or statutory measures.", "enforcement": "Competent AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the control library to the precise current sector rule and preserve auditable evidence of CDD, monitoring, escalation, training and retention.", "evidenceIds": [ "amlb:evidence:dd3cdff0", "amlb:evidence:ceff542e" ], "sourceEntityIds": [ "amlb:source-entity:25600d98" ] }, { "id": "PR-SAR", "jurisdictionCode": "PR", "jurisdictionName": "Puerto Rico", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers operating in the territory when their applicable sector-specific SAR rule is triggered.", "trigger": "Initial detection of facts meeting the applicable BSA suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 calendar days where the applicable rule permits an extension because no suspect is identified.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Missing or late SARs may lead to FinCEN and functional-regulator enforcement, with consequences depending on the filer, rule and conduct.", "enforcement": "FinCEN and applicable federal / territorial functional regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the initial-detection date and map the entity to its exact BSA SAR provision before applying thresholds or exemptions.", "evidenceIds": [ "amlb:evidence:5c9359d1", "amlb:evidence:4fde97d7", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd" ], "sourceEntityIds": [ "amlb:source-entity:54430121", "amlb:source-entity:ede8195a" ] }, { "id": "PR-CTR", "jurisdictionCode": "PR", "jurisdictionName": "Puerto Rico", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions in the territory subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation rules and applicable exemptions.", "deadline": "Within 15 calendar days after the reportable transaction(s).", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Late or missing CTRs may lead to civil monetary penalties and other BSA enforcement depending on the circumstances.", "enforcement": "FinCEN and applicable functional regulator", "evidenceStatus": "verified", "operationalImpact": "Aggregate same-business-day cash activity correctly and retain evidence of the transaction date, aggregation logic and filing receipt.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:1a81de77", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "AS-SAR", "jurisdictionCode": "AS", "jurisdictionName": "American Samoa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers operating in the territory when their applicable sector-specific SAR rule is triggered.", "trigger": "Initial detection of facts meeting the applicable BSA suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 calendar days where the applicable rule permits an extension because no suspect is identified.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Missing or late SARs may lead to FinCEN and functional-regulator enforcement, with consequences depending on the filer, rule and conduct.", "enforcement": "FinCEN and applicable federal / territorial functional regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the initial-detection date and map the entity to its exact BSA SAR provision before applying thresholds or exemptions.", "evidenceIds": [ "amlb:evidence:5c9359d1", "amlb:evidence:4fde97d7", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd" ], "sourceEntityIds": [ "amlb:source-entity:54430121", "amlb:source-entity:ede8195a" ] }, { "id": "AS-CTR", "jurisdictionCode": "AS", "jurisdictionName": "American Samoa", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions in the territory subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation rules and applicable exemptions.", "deadline": "Within 15 calendar days after the reportable transaction(s).", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Late or missing CTRs may lead to civil monetary penalties and other BSA enforcement depending on the circumstances.", "enforcement": "FinCEN and applicable functional regulator", "evidenceStatus": "verified", "operationalImpact": "Aggregate same-business-day cash activity correctly and retain evidence of the transaction date, aggregation logic and filing receipt.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:1a81de77", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "GU-SAR", "jurisdictionCode": "GU", "jurisdictionName": "Guam", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers operating in the territory when their applicable sector-specific SAR rule is triggered.", "trigger": "Initial detection of facts meeting the applicable BSA suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 calendar days where the applicable rule permits an extension because no suspect is identified.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Missing or late SARs may lead to FinCEN and functional-regulator enforcement, with consequences depending on the filer, rule and conduct.", "enforcement": "FinCEN and applicable federal / territorial functional regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the initial-detection date and map the entity to its exact BSA SAR provision before applying thresholds or exemptions.", "evidenceIds": [ "amlb:evidence:5c9359d1", "amlb:evidence:4fde97d7", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd" ], "sourceEntityIds": [ "amlb:source-entity:54430121", "amlb:source-entity:ede8195a" ] }, { "id": "GU-CTR", "jurisdictionCode": "GU", "jurisdictionName": "Guam", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions in the territory subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation rules and applicable exemptions.", "deadline": "Within 15 calendar days after the reportable transaction(s).", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Late or missing CTRs may lead to civil monetary penalties and other BSA enforcement depending on the circumstances.", "enforcement": "FinCEN and applicable functional regulator", "evidenceStatus": "verified", "operationalImpact": "Aggregate same-business-day cash activity correctly and retain evidence of the transaction date, aggregation logic and filing receipt.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:1a81de77", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "MP-SAR", "jurisdictionCode": "MP", "jurisdictionName": "Northern Mariana Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers operating in the territory when their applicable sector-specific SAR rule is triggered.", "trigger": "Initial detection of facts meeting the applicable BSA suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 calendar days where the applicable rule permits an extension because no suspect is identified.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Missing or late SARs may lead to FinCEN and functional-regulator enforcement, with consequences depending on the filer, rule and conduct.", "enforcement": "FinCEN and applicable federal / territorial functional regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the initial-detection date and map the entity to its exact BSA SAR provision before applying thresholds or exemptions.", "evidenceIds": [ "amlb:evidence:5c9359d1", "amlb:evidence:4fde97d7", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd" ], "sourceEntityIds": [ "amlb:source-entity:54430121", "amlb:source-entity:ede8195a" ] }, { "id": "MP-CTR", "jurisdictionCode": "MP", "jurisdictionName": "Northern Mariana Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions in the territory subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation rules and applicable exemptions.", "deadline": "Within 15 calendar days after the reportable transaction(s).", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Late or missing CTRs may lead to civil monetary penalties and other BSA enforcement depending on the circumstances.", "enforcement": "FinCEN and applicable functional regulator", "evidenceStatus": "verified", "operationalImpact": "Aggregate same-business-day cash activity correctly and retain evidence of the transaction date, aggregation logic and filing receipt.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:1a81de77", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "VI-SAR", "jurisdictionCode": "VI", "jurisdictionName": "U.S. Virgin Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "Financial institutions and other BSA-covered filers operating in the territory when their applicable sector-specific SAR rule is triggered.", "trigger": "Initial detection of facts meeting the applicable BSA suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 calendar days where the applicable rule permits an extension because no suspect is identified.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Missing or late SARs may lead to FinCEN and functional-regulator enforcement, with consequences depending on the filer, rule and conduct.", "enforcement": "FinCEN and applicable federal / territorial functional regulator", "evidenceStatus": "verified-with-gap", "operationalImpact": "Capture the initial-detection date and map the entity to its exact BSA SAR provision before applying thresholds or exemptions.", "evidenceIds": [ "amlb:evidence:5c9359d1", "amlb:evidence:4fde97d7", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd" ], "sourceEntityIds": [ "amlb:source-entity:54430121", "amlb:source-entity:ede8195a" ] }, { "id": "VI-CTR", "jurisdictionCode": "VI", "jurisdictionName": "U.S. Virgin Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions in the territory subject to the federal CTR requirement.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation rules and applicable exemptions.", "deadline": "Within 15 calendar days after the reportable transaction(s).", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal framework reviewed 19 Aug 2026.", "consequence": "Late or missing CTRs may lead to civil monetary penalties and other BSA enforcement depending on the circumstances.", "enforcement": "FinCEN and applicable functional regulator", "evidenceStatus": "verified", "operationalImpact": "Aggregate same-business-day cash activity correctly and retain evidence of the transaction date, aggregation logic and filing receipt.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:1a81de77", "amlb:evidence:1176acd7", "amlb:evidence:83c2e6fd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "GF-DS", "jurisdictionCode": "GF", "jurisdictionName": "French Guiana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "GF-RECORDS", "jurisdictionCode": "GF", "jurisdictionName": "French Guiana", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "GP-DS", "jurisdictionCode": "GP", "jurisdictionName": "Guadeloupe", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "GP-RECORDS", "jurisdictionCode": "GP", "jurisdictionName": "Guadeloupe", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "MQ-DS", "jurisdictionCode": "MQ", "jurisdictionName": "Martinique", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "MQ-RECORDS", "jurisdictionCode": "MQ", "jurisdictionName": "Martinique", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "RE-DS", "jurisdictionCode": "RE", "jurisdictionName": "Réunion", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "RE-RECORDS", "jurisdictionCode": "RE", "jurisdictionName": "Réunion", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "YT-DS", "jurisdictionCode": "YT", "jurisdictionName": "Mayotte", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "YT-RECORDS", "jurisdictionCode": "YT", "jurisdictionName": "Mayotte", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "BL-DS", "jurisdictionCode": "BL", "jurisdictionName": "St. Barthélemy", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "BL-RECORDS", "jurisdictionCode": "BL", "jurisdictionName": "St. Barthélemy", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "MF-DS", "jurisdictionCode": "MF", "jurisdictionName": "St. Martin", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "MF-RECORDS", "jurisdictionCode": "MF", "jurisdictionName": "St. Martin", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "PM-DS", "jurisdictionCode": "PM", "jurisdictionName": "St. Pierre & Miquelon", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "PM-RECORDS", "jurisdictionCode": "PM", "jurisdictionName": "St. Pierre & Miquelon", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:01565963" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "NC-DS", "jurisdictionCode": "NC", "jurisdictionName": "New Caledonia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "NC-RECORDS", "jurisdictionCode": "NC", "jurisdictionName": "New Caledonia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "PF-DS", "jurisdictionCode": "PF", "jurisdictionName": "French Polynesia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "PF-RECORDS", "jurisdictionCode": "PF", "jurisdictionName": "French Polynesia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "WF-DS", "jurisdictionCode": "WF", "jurisdictionName": "Wallis & Futuna", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Déclaration de soupçon (TRACFIN)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons within the applicable French AML/CFT reporting perimeter under Article L.561-2, subject to profession-specific scope and any territorial adaptations.", "trigger": "Knowledge, suspicion or good reason to suspect that funds or operations fall within the suspicious-transaction reporting grounds under Article L.561-15 and related provisions.", "deadline": "Without delay (sans délai). Where possible the declaration should precede execution; where a statutory exception permits execution first, TRACFIN must be informed without delay afterward.", "recipient": "TRACFIN", "submission": "Primarily through the ERMES electronic reporting platform; official fallback procedures apply in defined exceptional circumstances.", "applicability": "Current French/TRACFIN framework reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to disciplinary, supervisory or other legal consequences according to the profession and competent authority.", "enforcement": "TRACFIN receives declarations; ACPR and other competent professional / territorial supervisors enforce the preventive framework.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Escalation workflows should enable reporting without delay once suspicion is established and should preserve the decision and submission timestamps.", "evidenceIds": [ "amlb:evidence:2a3d360b", "amlb:evidence:af78251d", "amlb:evidence:28baaa0a", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3" ] }, { "id": "WF-RECORDS", "jurisdictionCode": "WF", "jurisdictionName": "Wallis & Futuna", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons within the applicable Article L.561-2 preventive AML/CFT perimeter, subject to profession-specific scope and territorial adaptations.", "trigger": "Customer relationship termination/closure for CDD records and execution of an occasional or reportable transaction for transaction records.", "deadline": "French AML baseline: retain relevant CDD/customer-relationship documents for 5 years after closure/termination and transaction documents for 5 years after execution, subject to more stringent provisions and applicable territorial adaptations.", "recipient": "Relevant AML/CFT supervisor / competent authority on request", "submission": "Retained internally in retrievable form; produced to competent authorities where lawfully required.", "applicability": "Current Code monétaire et financier baseline reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may support supervisory or disciplinary enforcement under the applicable professional regime.", "enforcement": "Applicable French / territorial AML/CFT supervisor", "evidenceStatus": "verified-with-gap", "evidenceNote": "The five-year Code baseline is verified; for this special overseas jurisdiction the precise entity/professional perimeter and any local adaptation must be checked before implementation.", "operationalImpact": "Retention schedules should distinguish relationship-end and transaction-execution trigger dates and preserve any longer sector-specific requirement.", "evidenceIds": [ "amlb:evidence:2532e035", "amlb:evidence:c06294ed", "amlb:evidence:e1ceadb9" ], "sourceEntityIds": [ "amlb:source-entity:989e83c3" ] }, { "id": "BQ-UTR", "jurisdictionCode": "BQ", "jurisdictionName": "Caribbean Netherlands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Unusual Transaction Report (Wwft BES)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Service providers/reporting entities within the Wwft BES perimeter for Bonaire, Sint Eustatius and Saba.", "trigger": "A completed or intended transaction meets an applicable objective indicator or is assessed as unusual under the subjective indicator.", "deadline": "Without delay after the unusual character of the transaction becomes known.", "recipient": "FIU-the Netherlands (Caribbean Netherlands / BES reporting)", "submission": "FIU-the Netherlands reporting portal; form or XML route according to the reporting group.", "applicability": "Current FIU/DNB BES framework reviewed 19 Aug 2026.", "consequence": "Failure to report can constitute a breach/economic offence and may lead to supervisory or enforcement action.", "enforcement": "FIU-the Netherlands / DNB / AFM / other competent BES supervisor according to sector", "evidenceStatus": "verified", "evidenceNote": "Official BES material confirms reporting of both completed and intended unusual transactions and the Article 3.5 without-delay standard.", "operationalImpact": "Apply the relevant BES indicator set, capture when unusual character became known, and file through the portal without unnecessary internal delay.", "evidenceIds": [ "amlb:evidence:821fc1c9", "amlb:evidence:b6eb8546", "amlb:evidence:07a06f30" ], "sourceEntityIds": [ "amlb:source-entity:3162cff0", "amlb:source-entity:814213f4", "amlb:source-entity:06f6005e" ] }, { "id": "BQ-RECORDS", "jurisdictionCode": "BQ", "jurisdictionName": "Caribbean Netherlands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "CDD and unusual-transaction data retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Wwft BES reporting entities/service providers.", "trigger": "Completion of a transaction or termination of the relevant business relationship.", "deadline": "Retain Wwft-related customer due-diligence and unusual-transaction data for 5 years after the transaction or termination of the business relationship, as applicable.", "recipient": "Competent BES supervisor / FIU-the Netherlands where lawfully required", "submission": "Retained internally and produced to competent authorities as required.", "applicability": "Current FIU BES guidance reviewed 19 Aug 2026.", "consequence": "Failure to maintain required data can result in supervisory/enforcement consequences under the Wwft BES.", "enforcement": "DNB / AFM / other competent BES supervisor", "evidenceStatus": "verified", "operationalImpact": "Configure retention triggers separately for transaction completion and relationship termination and keep report data retrievable for the full period.", "evidenceIds": [ "amlb:evidence:992fb952", "amlb:evidence:b6eb8546" ], "sourceEntityIds": [ "amlb:source-entity:3162cff0", "amlb:source-entity:814213f4" ] }, { "id": "SX-UTR", "jurisdictionCode": "SX", "jurisdictionName": "Sint Maarten", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Unusual Transaction Report (MOT / FIU Sint Maarten)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs within the Sint Maarten reporting perimeter.", "trigger": "A transaction meets an applicable objective or subjective unusual-transaction indicator / reporting ground.", "deadline": "Report under the applicable Sint Maarten AML/CFT rule once the transaction is reportable; no single current cross-sector numeric outer limit is asserted in mapped sources.", "recipient": "Financial Intelligence Unit Sint Maarten (MOT)", "submission": "FIU Sint Maarten electronic reporting / SERT environment according to the current reporting procedure.", "applicability": "Current FIU/Government material reviewed 19 Aug 2026.", "consequence": "Non-reporting or control failures may result in enforcement measures under the applicable national AML/CFT framework.", "enforcement": "FIU Sint Maarten / MOT and competent financial-sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain indicator-based escalation and submit through the FIU system as soon as the transaction becomes reportable; map any sector-specific timing separately.", "evidenceIds": [ "amlb:evidence:077f0d76", "amlb:evidence:c13719ed", "amlb:evidence:c04490f3" ], "sourceEntityIds": [ "amlb:source-entity:4cec64c0" ] }, { "id": "SX-AML-CONTROLS", "jurisdictionCode": "SX", "jurisdictionName": "Sint Maarten", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD, monitoring, reporting and internal AML controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Institutions and professions within the national AML/CFT preventive perimeter.", "trigger": "Continuous while carrying on covered business.", "deadline": "Maintain CDD, transaction monitoring, unusual-transaction reporting and internal controls continuously; mapped sources do not assert one cross-sector numeric retention period.", "recipient": "FIU Sint Maarten / MOT and applicable financial-sector supervisor", "submission": "Internal AML framework and retained evidence; supervisory production/reporting where required.", "applicability": "Current official framework reviewed 19 Aug 2026.", "consequence": "Deficiencies can lead to supervisory findings and enforcement measures under the applicable national rules.", "enforcement": "FIU Sint Maarten / MOT and competent financial-sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the control inventory tied to the reporting-entity category and keep evidence of CDD, monitoring and reporting decisions.", "evidenceIds": [ "amlb:evidence:1b383541", "amlb:evidence:c04490f3" ], "sourceEntityIds": [ "amlb:source-entity:4cec64c0" ] }, { "id": "CK-SAR", "jurisdictionCode": "CK", "jurisdictionName": "Cook Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions within the Financial Transactions Reporting Act 2017 perimeter.", "trigger": "Reasonable grounds to suspect that activity is connected with financial misconduct or a serious offence under the FTRA reporting test.", "deadline": "As soon as possible, and no later than 2 working days after forming the suspicion.", "recipient": "Cook Islands Financial Intelligence Unit (CIFIU)", "submission": "Report to CIFIU in the form/manner required by the FTRA and FIU guidance.", "applicability": "Current FSC framework reviewed 19 Aug 2026.", "consequence": "Failure to report is an offence and may attract statutory penalties under the FTRA.", "enforcement": "Cook Islands Financial Intelligence Unit / Financial Supervisory Commission", "evidenceStatus": "verified-with-gap", "operationalImpact": "Start the clock when reasonable suspicion is formed and ensure internal escalation cannot consume the two-working-day filing window.", "evidenceIds": [ "amlb:evidence:8f6baf1c", "amlb:evidence:9f31b05b", "amlb:evidence:1f905746" ], "sourceEntityIds": [ "amlb:source-entity:699b3a2c" ] }, { "id": "CK-THRESHOLD", "jurisdictionCode": "CK", "jurisdictionName": "Cook Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cash and electronic funds threshold reports", "timingType": "event-driven", "sectors": [ "banking", "payments", "all" ], "appliesTo": "Reporting institutions subject to FTRA threshold transaction reporting.", "trigger": "Cash transaction or relevant electronic funds transfer over the NZ$10,000 statutory threshold, subject to the applicable FTRA/Regulations scope and exclusions.", "deadline": "File according to the FTRA 2017 / Regulations reporting timetable; mapped sources verifies the NZ$10,000 threshold but does not assign a numeric filing clock without current article-level confirmation.", "recipient": "Cook Islands Financial Intelligence Unit (CIFIU)", "submission": "CIFIU prescribed threshold-reporting process.", "applicability": "Current FSC framework reviewed 19 Aug 2026.", "consequence": "Failure to submit required threshold reports may attract statutory enforcement under the FTRA.", "enforcement": "CIFIU / Financial Supervisory Commission", "evidenceStatus": "verified-with-gap", "operationalImpact": "Detect threshold transactions at source and route them to CIFIU while separately validating the filing timetable applicable to the report type.", "evidenceIds": [ "amlb:evidence:8f6baf1c", "amlb:evidence:9f31b05b" ], "sourceEntityIds": [ "amlb:source-entity:699b3a2c" ] }, { "id": "FO-STR", "jurisdictionCode": "FO", "jurisdictionName": "Faroe Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction/activity report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons and undertakings within the Faroese AML Act perimeter.", "trigger": "Knowledge, suspicion or reasonable grounds to suspect money laundering or terrorist financing that cannot be dispelled, including attempted transactions.", "deadline": "Immediately (omgående). Where a transaction cannot be stopped or delaying it would frustrate investigation, report immediately after execution.", "recipient": "Hvidvasksekretariatet at National enhed for Særlig Kriminalitet (NSK)", "submission": "Through the reporting route prescribed by Hvidvasksekretariatet / NSK.", "applicability": "Current consolidated/amended framework reviewed 19 Aug 2026.", "consequence": "Failure to comply can lead to enforcement under the applicable Faroese AML framework.", "enforcement": "Relevant Faroese/Danish supervisory authority and NSK", "evidenceStatus": "verified", "evidenceNote": "The current Faroese legal text uses an immediate reporting standard and expressly covers attempted transactions and the post-execution exception.", "operationalImpact": "Escalate unresolved suspicion directly into an immediate filing workflow and record any reason a transaction could not be stopped before submission.", "evidenceIds": [ "amlb:evidence:40301ae4", "amlb:evidence:c63ac055" ], "sourceEntityIds": [ "amlb:source-entity:46e3df28", "amlb:source-entity:74213e86" ] }, { "id": "FO-RECORDS", "jurisdictionCode": "FO", "jurisdictionName": "Faroe Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML customer and transaction record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons and undertakings within the Faroese AML Act perimeter.", "trigger": "End of the business relationship or completion of the relevant occasional transaction, according to the record type.", "deadline": "Retain required AML records and documents for at least 5 years after the business relationship ends or the occasional transaction is completed, subject to applicable longer-law exceptions.", "recipient": "Applicable AML/CFT supervisor / competent authority on lawful request", "submission": "Retained internally in retrievable form and produced as required.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may lead to supervisory or statutory enforcement under the applicable AML framework.", "enforcement": "Relevant Faroese/Danish supervisory authority", "evidenceStatus": "verified", "operationalImpact": "Tie deletion/retention controls to the correct relationship or transaction trigger and prevent early disposal of AML evidence.", "evidenceIds": [ "amlb:evidence:40301ae4" ], "sourceEntityIds": [ "amlb:source-entity:46e3df28" ] }, { "id": "AD-STR", "jurisdictionCode": "AD", "jurisdictionName": "Andorra", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report to UIFAND", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and DNFBPs within the Law 14/2017 reporting perimeter.", "trigger": "Knowledge, suspicion or reasonable grounds concerning money laundering or terrorist financing requiring an Article 20 suspicious transaction report.", "deadline": "File without avoidable delay under the applicable Article 20 workflow; a single universal numeric outer limit was not established from the current public UIFAND material reviewed.", "recipient": "UIFAND", "submission": "Through the UIFAND reporting route and designated representative/control framework applicable to the reporting entity.", "applicability": "Current UIFAND national-legislation and reporting-entity pages reviewed 19 Aug 2026.", "consequence": "Failure to report or maintain required AML/CFT controls can lead to administrative or other enforcement under Law 14/2017.", "enforcement": "UIFAND / competent sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented escalation path to the UIFAND representative and treat the filing decision as time-critical even where a sector-specific numeric clock must be confirmed.", "evidenceIds": [ "amlb:evidence:ef6c46cf", "amlb:evidence:01c99d0b" ], "sourceEntityIds": [ "amlb:source-entity:54e81749" ] }, { "id": "AD-RECORDS", "jurisdictionCode": "AD", "jurisdictionName": "Andorra", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "AML/CFT record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to Law 14/2017.", "trigger": "Termination of a business relationship or completion of the relevant occasional transaction / creation of AML documentation.", "deadline": "Retain AML/CFT-related documentation for at least 5 years; UIFAND guidance notes that the period may be extended for up to a further 5 years where legally required.", "recipient": "UIFAND / competent supervisor on lawful request", "submission": "Retained internally in retrievable form and produced to competent authorities when required.", "applicability": "Current UIFAND guidance reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may trigger supervisory or administrative sanctions.", "enforcement": "UIFAND / competent sector supervisor", "evidenceStatus": "verified", "operationalImpact": "Tie deletion schedules to relationship/transaction trigger dates and preserve extension holds where UIFAND or law requires longer retention.", "evidenceIds": [ "amlb:evidence:ef6c46cf", "amlb:evidence:01c99d0b" ], "sourceEntityIds": [ "amlb:source-entity:54e81749" ] }, { "id": "AI-SAR", "jurisdictionCode": "AI", "jurisdictionName": "Anguilla", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting agencies within Anguilla’s AML/CFT perimeter.", "trigger": "Suspicious activity or transaction meeting the applicable Proceeds of Crime / AML reporting test.", "deadline": "Submit in accordance with the applicable statutory and sector rules; exact current universal numeric outer limit requires entity/sector confirmation.", "recipient": "Anguilla Financial Intelligence Unit / Money Laundering Reporting Authority route", "submission": "Government FIU SAR form; electronically to the FIU using the prescribed secure/password-protected route or by hand in a sealed envelope, as stated on the current SAR page.", "applicability": "Current FIU website and SAR form reviewed 19 Aug 2026.", "consequence": "Failure to make a required disclosure may lead to criminal, regulatory or supervisory consequences under the applicable framework.", "enforcement": "Anguilla FIU / MLRA / relevant sector supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use the current FIU SAR route and maintain sector-specific controls for the actual statutory reporting clock.", "evidenceIds": [ "amlb:evidence:ba6b2f23", "amlb:evidence:a9d53115", "amlb:evidence:589d2cb8" ], "sourceEntityIds": [ "amlb:source-entity:73e9f0d1" ] }, { "id": "AI-CONTROLS", "jurisdictionCode": "AI", "jurisdictionName": "Anguilla", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive controls and reporting governance", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Anguilla AML/CFT regime.", "trigger": "Ongoing operation as a regulated/reporting entity.", "deadline": "Ongoing; apply the current entity- and sector-specific AML/CFT rules, including internal reporting and escalation arrangements. A single universal retention period was not safely established in mapped sources.", "recipient": "Relevant Anguilla supervisor / FIU where reporting or information production is required", "submission": "Internal policies, controls, records and prescribed regulatory/FIU reporting routes.", "applicability": "Current FIU legal-framework library reviewed 19 Aug 2026.", "consequence": "Control failures may lead to supervisory, administrative or criminal consequences according to the applicable enactment.", "enforcement": "Relevant Anguilla AML/CFT supervisor / FIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the entity to its precise statute/code before configuring retention and periodic control testing.", "evidenceIds": [ "amlb:evidence:a9d53115", "amlb:evidence:722e9c04" ], "sourceEntityIds": [ "amlb:source-entity:73e9f0d1" ] }, { "id": "FM-STR", "jurisdictionCode": "FM", "jurisdictionName": "Micronesia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and cash dealers subject to Chapter 9 reporting duties.", "trigger": "The institution has reasonable grounds to suspect a transaction or attempted transaction involves proceeds of crime, money laundering or terrorist financing under the statutory test.", "deadline": "As soon as possible and, wherever possible, before execution; in all cases no later than 3 working days after forming the suspicion.", "recipient": "Department of Justice / designated national AML authority under the FSM Code", "submission": "Written report in the form and manner required under Chapter 9 and implementing directions.", "applicability": "Current FSM Code page reviewed 19 Aug 2026.", "consequence": "Failure to report can expose the institution and responsible persons to statutory enforcement and penalties.", "enforcement": "FSM Department of Justice / competent supervisory authorities", "evidenceStatus": "verified", "evidenceNote": "Section 915 states an outer limit of three working days after forming suspicion and says filing should occur before the transaction wherever possible.", "operationalImpact": "Timestamp formation of suspicion and route cases to external reporting early enough to preserve the pre-execution expectation where feasible.", "evidenceIds": [ "amlb:evidence:3e95d898" ], "sourceEntityIds": [ "amlb:source-entity:a575dc1f" ] }, { "id": "FM-RECORDS", "jurisdictionCode": "FM", "jurisdictionName": "Micronesia", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Transaction and identification record retention", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and cash dealers subject to Chapter 9 recordkeeping.", "trigger": "Completion of the transaction / end of the relevant relationship or creation of records required by the statute.", "deadline": "Retain required records for at least 5 years under the statutory recordkeeping rule.", "recipient": "Department of Justice / competent authority on lawful request", "submission": "Retained internally and made available in accordance with the law.", "applicability": "Current FSM Code page reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may attract statutory penalties and impair reconstruction of transactions.", "enforcement": "FSM Department of Justice / competent supervisory authorities", "evidenceStatus": "verified", "operationalImpact": "Configure a five-year minimum hold and preserve records in a form capable of reconstructing transactions and customer activity.", "evidenceIds": [ "amlb:evidence:3e95d898" ], "sourceEntityIds": [ "amlb:source-entity:a575dc1f" ] }, { "id": "GL-STR", "jurisdictionCode": "GL", "jurisdictionName": "Greenland", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Money-laundering / terrorist-financing notification", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons and undertakings within the AML Act perimeter as in force for Greenland.", "trigger": "Knowledge, suspicion or reasonable grounds concerning a transaction, funds or activity linked to money laundering or terrorist financing, including attempted activity, subject to Greenland territorial application.", "deadline": "Danish AML baseline is immediate notification (omgående); confirm the latest Greenland territorial consolidation and entity scope before implementation.", "recipient": "Hvidvasksekretariatet at National enhed for Særlig Kriminalitet (NSK), where the Greenland-in-force framework directs reporting", "submission": "Prescribed Hvidvasksekretariatet/NSK notification route under the applicable Greenland-in-force rules.", "applicability": "Latest identified Greenland amendment order dated 2026; reviewed 19 Aug 2026.", "consequence": "Non-compliance may result in enforcement under the Greenland-in-force AML framework.", "enforcement": "Finanstilsynet / other competent Greenland or Danish authority by sector", "evidenceStatus": "verified-with-gap", "evidenceNote": "Current Danish guidance states immediate reporting, and the AML Act is in force in Greenland through territorial orders. The precise current consolidated section/perimeter is flagged for local legal confirmation.", "operationalImpact": "Do not configure a Greenland deadline by copying a Denmark rule blindly; verify the entity is within the latest territorial order and then apply the corresponding immediate escalation control.", "evidenceIds": [ "amlb:evidence:dfd49634", "amlb:evidence:8fe3ddc5", "amlb:evidence:c63ac055" ], "sourceEntityIds": [ "amlb:source-entity:74213e86", "amlb:source-entity:c93ec0f6" ] }, { "id": "GL-RECORDS", "jurisdictionCode": "GL", "jurisdictionName": "Greenland", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML recordkeeping under Greenland-in-force framework", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons and undertakings within the Greenland-in-force AML Act perimeter.", "trigger": "Creation of CDD, transaction, investigation and other AML/CFT records under the applicable territorial provisions.", "deadline": "Retain records for the period required by the current Greenland-in-force AML provisions; exact consolidated trigger/quantum is left as a territorial-consolidation gap in mapped sources.", "recipient": "Competent Greenland/Danish AML supervisor or authority on lawful request", "submission": "Retained internally in retrievable form under the applicable territorial AML rules.", "applicability": "Current territorial law collection and 2026 amendment reviewed 19 Aug 2026.", "consequence": "Failure to preserve required records may lead to supervisory or statutory enforcement.", "enforcement": "Competent Greenland/Danish AML supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use a jurisdiction-specific legal mapping before changing retention schedules; preserve records until the current territorial period is confirmed.", "evidenceIds": [ "amlb:evidence:dfd49634", "amlb:evidence:8fe3ddc5" ], "sourceEntityIds": [ "amlb:source-entity:74213e86", "amlb:source-entity:c93ec0f6" ] }, { "id": "KI-STR", "jurisdictionCode": "KI", "jurisdictionName": "Kiribati", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report to Kiribati FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities within the Kiribati AML/CFT reporting system.", "trigger": "Activity or transaction meets the applicable statutory suspicion test for money laundering or terrorist financing.", "deadline": "Report under the applicable Kiribati AML/CFT rules; exact current universal numeric outer limit was not established from current public evidence in mapped sources.", "recipient": "Kiribati Financial Intelligence Unit", "submission": "Use the FIU/reporting mechanism prescribed by the current Kiribati framework.", "applicability": "Current institutional architecture confirmed by 2023 UNODC engagement and APG material; reviewed 19 Aug 2026.", "consequence": "Failure to comply with statutory reporting duties may lead to enforcement under applicable Kiribati law.", "enforcement": "Kiribati FIU / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep a local-law verification step for the filing clock and current submission method while maintaining immediate internal escalation.", "evidenceIds": [ "amlb:evidence:02ec76bd", "amlb:evidence:9f497637" ], "sourceEntityIds": [ "amlb:source-entity:a5ffefa6", "amlb:source-entity:f4024631" ] }, { "id": "KI-CONTROLS", "jurisdictionCode": "KI", "jurisdictionName": "Kiribati", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT preventive controls and records", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Kiribati AML/CFT framework.", "trigger": "Ongoing customer relationships and reportable financial activity.", "deadline": "Ongoing; apply current Kiribati CDD, monitoring, recordkeeping and reporting controls. Exact current cross-sector retention quantum is an evidence gap.", "recipient": "Kiribati FIU / relevant supervisory or law-enforcement authority", "submission": "Internal AML/CFT programme, records and FIU reporting as required.", "applicability": "Current institutional architecture reviewed 19 Aug 2026.", "consequence": "Weak or absent controls may result in enforcement under the applicable legal framework.", "enforcement": "Kiribati FIU / competent authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not delete AML records based on an assumed regional norm; verify the applicable Kiribati rule for the entity and record type.", "evidenceIds": [ "amlb:evidence:f894065f", "amlb:evidence:9f497637" ], "sourceEntityIds": [ "amlb:source-entity:a5ffefa6", "amlb:source-entity:f4024631" ] }, { "id": "LY-STR", "jurisdictionCode": "LY", "jurisdictionName": "Libya", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report through goAML", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities within the Libyan AML/CFT perimeter.", "trigger": "A transaction or activity meets the applicable suspicion threshold under Libyan AML/CFT law.", "deadline": "Submit in accordance with the applicable Libyan reporting rule; exact universal numeric outer limit requires sector/legal confirmation.", "recipient": "Libyan Financial Information Unit", "submission": "goAML electronic reporting platform; commercial-bank reporting officers are registered and using the system according to the Central Bank.", "applicability": "goAML officially launched 4 May 2025; CBL page current through Aug 2026.", "consequence": "Failure to report or comply with AML/CFT obligations may lead to enforcement under applicable Libyan law.", "enforcement": "Libyan FIU / Central Bank of Libya / competent sector authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Register the reporting officer, maintain goAML access, and map the entity-specific filing clock before relying on automation.", "evidenceIds": [ "amlb:evidence:ed452ddf" ], "sourceEntityIds": [ "amlb:source-entity:2f42a0d4" ] }, { "id": "LY-CONTROLS", "jurisdictionCode": "LY", "jurisdictionName": "Libya", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT internal compliance and FIU reporting readiness", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities subject to the Libyan AML/CFT framework.", "trigger": "Ongoing operation and monitoring of customers/transactions.", "deadline": "Ongoing; maintain controls capable of identifying suspicious activity and submitting reports through the current national system. Current universal retention/cadence details require entity-specific confirmation.", "recipient": "Libyan FIU / competent supervisor", "submission": "Internal monitoring and documented escalation with goAML-ready reporting where applicable.", "applicability": "Current CBL operational reporting architecture reviewed 19 Aug 2026.", "consequence": "Control deficiencies may lead to supervisory or legal enforcement.", "enforcement": "Central Bank of Libya / Libyan FIU / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat goAML readiness as an operational control and separately confirm sector-specific CDD, retention and reporting timelines.", "evidenceIds": [ "amlb:evidence:ed452ddf" ], "sourceEntityIds": [ "amlb:source-entity:2f42a0d4" ] }, { "id": "MH-STR", "jurisdictionCode": "MH", "jurisdictionName": "Marshall Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Banks, financial services providers and cash dealers within the Banking Act reporting provision; other sectors require separate scope mapping.", "trigger": "A transaction is suspicious under the applicable Banking Act / AML criteria.", "deadline": "Published Banking Act amendment text states within 3 days of the transaction for the covered institutions; confirm latest consolidated section and sector scope before implementation.", "recipient": "Banking Commissioner / Domestic Financial Intelligence Unit", "submission": "Report in the manner required by the Commissioner / DFIU.", "applicability": "Current technical framework confirmed by the 2024 APG assessment; statutory clock text reviewed with consolidation caveat.", "consequence": "Failure to report can lead to statutory and supervisory penalties.", "enforcement": "Banking Commissioner / DFIU", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use the three-day rule only for entities clearly within the cited Banking Act scope and verify no later amendment alters the clock.", "evidenceIds": [ "amlb:evidence:6ca835be", "amlb:evidence:5f221422" ], "sourceEntityIds": [ "amlb:source-entity:8de58e75", "amlb:source-entity:c4320f87" ] }, { "id": "MH-RECORDS", "jurisdictionCode": "MH", "jurisdictionName": "Marshall Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT record keeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within the applicable Marshall Islands AML/CFT perimeter.", "trigger": "Creation of customer, transaction and AML/CFT records required by applicable law.", "deadline": "Maintain required records for the period prescribed by the applicable current law; a single universal current retention quantum was not established from the public current assessment page.", "recipient": "DFIU / Banking Commissioner / competent supervisor on lawful request", "submission": "Retained internally and produced to competent authorities as required.", "applicability": "Current 2024 assessment reviewed 19 Aug 2026.", "consequence": "Recordkeeping breaches may result in supervisory or statutory enforcement.", "enforcement": "DFIU / Banking Commissioner / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Verify the entity-specific statutory retention period before configuring deletion controls.", "evidenceIds": [ "amlb:evidence:5f221422", "amlb:evidence:91c55261" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87", "amlb:source-entity:8de58e75" ] }, { "id": "MS-SAR", "jurisdictionCode": "MS", "jurisdictionName": "Montserrat", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction / activity disclosure", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons and businesses required to make disclosures under the Proceeds of Crime Act and related AML/CFT/CPF enactments.", "trigger": "Knowledge, suspicion or applicable statutory grounds concerning criminal property, money laundering, terrorist financing or proliferation financing.", "deadline": "Submit within the current statutory/sector-specific period; one universal cross-sector numeric clock was not safely established from current public FIU material in mapped sources.", "recipient": "Montserrat Financial Intelligence Unit", "submission": "Disclosure/SAR through the route prescribed by the FIU and relevant sector guidance.", "applicability": "Current FIU powers page and 2025 FSC guidance framework reviewed 19 Aug 2026.", "consequence": "Failure to disclose or comply with AML/CFT obligations may lead to criminal or supervisory consequences.", "enforcement": "Montserrat FIU / Financial Services Commission / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Route suspicion to the MLRO/FIU process immediately and verify the sector-specific statutory clock before final submission.", "evidenceIds": [ "amlb:evidence:af29b097", "amlb:evidence:ecba80e1" ], "sourceEntityIds": [ "amlb:source-entity:28ce7aac", "amlb:source-entity:4345f02e" ] }, { "id": "MS-CONTROLS", "jurisdictionCode": "MS", "jurisdictionName": "Montserrat", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT/CPF internal controls and recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Regulated and other relevant businesses subject to Montserrat AML/CFT/CPF rules.", "trigger": "Ongoing customer relationships, transactions and internal reporting activity.", "deadline": "Ongoing; maintain the policies, MLRO/reporting governance and records required by the applicable sector framework. Exact cross-sector retention quantum requires sector mapping.", "recipient": "Montserrat FSC / FIU / other competent supervisor", "submission": "Internal records and controls; produce/report as prescribed by the applicable enactment or guidance.", "applicability": "Current framework reviewed 19 Aug 2026.", "consequence": "Deficiencies can result in supervisory, administrative or criminal enforcement.", "enforcement": "Montserrat FSC / FIU / competent authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map the precise sector guidance before setting retention and periodic review rules.", "evidenceIds": [ "amlb:evidence:ecba80e1", "amlb:evidence:af29b097" ], "sourceEntityIds": [ "amlb:source-entity:4345f02e", "amlb:source-entity:28ce7aac" ] }, { "id": "MV-BANK-STR", "jurisdictionCode": "MV", "jurisdictionName": "Maldives", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Bank suspicious transaction report", "timingType": "event-driven", "sectors": [ "banking" ], "appliesTo": "Banks licensed under the Maldives Banking Act.", "trigger": "The bank suspects or has grounds to suspect funds or property are proceeds of crime or related to money laundering or terrorist financing, including designated-party related suspicion.", "deadline": "As soon as practicable and no later than 3 working days after forming the suspicion or grounds for suspicion.", "recipient": "Maldives Financial Intelligence Unit", "submission": "Submit to the FIU in the form/manner required by the applicable MMA/FIU framework.", "applicability": "Bank regulation clock reviewed against current 2025 FATF-endorsed assessment; reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to action under the AML/CFT Act, banking regulation and supervisory powers.", "enforcement": "Maldives Monetary Authority / Financial Intelligence Unit", "evidenceStatus": "verified-with-gap", "operationalImpact": "Bank workflows should timestamp formation of suspicion and ensure FIU filing within three working days at the latest.", "evidenceIds": [ "amlb:evidence:6ee58619", "amlb:evidence:0cb83a20" ], "sourceEntityIds": [ "amlb:source-entity:dd311873", "amlb:source-entity:c4320f87" ] }, { "id": "MV-BANK-RECORDS", "jurisdictionCode": "MV", "jurisdictionName": "Maldives", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Bank AML/CFT record retention", "timingType": "ongoing", "sectors": [ "banking" ], "appliesTo": "Banks licensed under the Maldives Banking Act.", "trigger": "Completion of a single transaction, termination of a business relationship, or submission of an STR, according to record type.", "deadline": "Retain specified records for 5 years after the relevant trigger: transaction completion, relationship termination, or STR submission unless the FIU instructs otherwise.", "recipient": "Maldives Monetary Authority / Financial Intelligence Unit on lawful request", "submission": "Retained internally and produced as required.", "applicability": "Bank regulation reviewed with 2025 FATF assessment context.", "consequence": "Recordkeeping failures may lead to supervisory or statutory consequences.", "enforcement": "Maldives Monetary Authority / Financial Intelligence Unit", "evidenceStatus": "verified-scope", "operationalImpact": "Configure distinct retention triggers for single transactions, relationships and STR files, and preserve FIU-directed extensions.", "evidenceIds": [ "amlb:evidence:6ee58619", "amlb:evidence:556db1b6" ], "sourceEntityIds": [ "amlb:source-entity:dd311873", "amlb:source-entity:c4320f87" ] }, { "id": "NR-SAR", "jurisdictionCode": "NR", "jurisdictionName": "Nauru", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Anti-Money Laundering and Targeted Financial Sanctions Act.", "trigger": "Any circumstance in section 59 occurs, including suspected or attempted transactions/activity linked to financial crime or criminal conduct.", "deadline": "No later than 2 working days after the occurrence of the suspicious circumstance.", "recipient": "Nauru Financial Intelligence Unit", "submission": "Submit in the prescribed form/manner and with regard to FIU guidance.", "applicability": "Base Act reviewed together with current FIU page listing 2024 amendments; reviewed 19 Aug 2026.", "consequence": "Contravention is subject to the offence/enforcement provisions of the Act.", "enforcement": "Nauru Financial Intelligence Unit / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Timestamp the occurrence of the reportable circumstance and file within two working days while maintaining a legal-change check for amendments.", "evidenceIds": [ "amlb:evidence:1efa1670", "amlb:evidence:fe5c3bcb" ], "sourceEntityIds": [ "amlb:source-entity:9443db18", "amlb:source-entity:3d146e1d" ] }, { "id": "NR-FIU-FOLLOWUP", "jurisdictionCode": "NR", "jurisdictionName": "Nauru", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "FIU follow-up information after SAR", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A reporting entity that has filed a suspicious activity report and receives an FIU request for further information.", "trigger": "The FIU requests additional information in relation to a report submitted under section 59.", "deadline": "Provide requested further information within 14 working days. Separately, results of further analysis under section 61 are due within 14 days after the SAR unless the FIU allows longer in writing.", "recipient": "Nauru Financial Intelligence Unit", "submission": "Provide the information/results to the FIU in the manner directed.", "applicability": "Base Act reviewed with current FIU amendment listing; reviewed 19 Aug 2026.", "consequence": "Failure to comply may trigger enforcement under the Act.", "enforcement": "Nauru Financial Intelligence Unit", "evidenceStatus": "verified-with-gap", "evidenceNote": "The Act gives a 14-working-day response period for FIU-requested further information and a 14-day period for further-analysis results, subject to written extension for the latter.", "operationalImpact": "Track FIU requests separately from the original SAR and calculate the correct working-day versus calendar-day clock.", "evidenceIds": [ "amlb:evidence:1efa1670", "amlb:evidence:fe5c3bcb" ], "sourceEntityIds": [ "amlb:source-entity:9443db18", "amlb:source-entity:3d146e1d" ] }, { "id": "NU-STR", "jurisdictionCode": "NU", "jurisdictionName": "Niue", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities within Niue’s AML/CFT reporting perimeter.", "trigger": "The applicable legal suspicion threshold is met for money laundering, terrorist financing or related criminal activity.", "deadline": "Report within the period required by current Niue law; exact current universal numeric filing clock was not established in mapped sources.", "recipient": "Niue Financial Intelligence Unit / competent reporting authority", "submission": "Use the current prescribed reporting route.", "applicability": "FATF-endorsed mutual evaluation published 23 Dec 2025; reviewed 19 Aug 2026.", "consequence": "Non-compliance may lead to enforcement under the applicable AML/CFT framework.", "enforcement": "Niue FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain rapid internal escalation and confirm the current sector-specific filing deadline and form before submission.", "evidenceIds": [ "amlb:evidence:69eac9ac" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87" ] }, { "id": "NU-RECORDS", "jurisdictionCode": "NU", "jurisdictionName": "Niue", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT record keeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities within Niue’s AML/CFT perimeter.", "trigger": "Creation of CDD, customer and transaction records required by the AML/CFT framework.", "deadline": "Retain for the period required by current Niue law; exact universal retention quantum was not established from the public current assessment page.", "recipient": "Niue FIU / competent supervisor on lawful request", "submission": "Retained internally and produced when required.", "applicability": "Current 2025 assessment reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures may lead to statutory or supervisory consequences.", "enforcement": "Niue FIU / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Confirm the statutory trigger and retention period for the entity before setting automatic deletion dates.", "evidenceIds": [ "amlb:evidence:69eac9ac" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87" ] }, { "id": "SD-FI-STR", "jurisdictionCode": "SD", "jurisdictionName": "Sudan", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-28", "title": "Supervised-institution suspicious transaction report", "timingType": "event-driven", "sectors": [ "banking", "financial-institutions" ], "appliesTo": "Institutions under the supervision of the Central Bank of Sudan within Circular No. 8/2026.", "trigger": "The institution suspects or has reasonable grounds to suspect funds constitute proceeds or that transactions/attempted transactions are linked to money laundering or terrorist financing.", "deadline": "Immediately.", "recipient": "Sudan Financial Intelligence Unit", "submission": "Compliance officer files using the reporting template designed by the FIU.", "applicability": "Circular No. 8/2026 effective from 30 April 2026.", "consequence": "Failure to report may lead to supervisory and statutory enforcement.", "enforcement": "Central Bank of Sudan / Sudan FIU", "evidenceStatus": "verified", "operationalImpact": "Configure immediate internal escalation and FIU reporting for suspicious transactions or attempted transactions under Circular No. 8/2026.", "evidenceIds": [ "amlb:evidence:e3f4ea9c" ], "sourceEntityIds": [ "amlb:source-entity:2e2325ce" ] }, { "id": "SD-FI-RECORDS", "jurisdictionCode": "SD", "jurisdictionName": "Sudan", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-28", "title": "Supervised-institution AML/CFT record retention", "timingType": "ongoing", "sectors": [ "banking", "financial-institutions" ], "appliesTo": "Institutions under the supervision of the Central Bank of Sudan within Circular No. 8/2026.", "trigger": "Transactions/attempted transactions, STR submission, risk assessment or training activity, depending on record type.", "deadline": "At least 5 years for covered transaction records; STR-related records for at least 5 years after notifying the FIU; risk-assessment and AML/CFT training records also have five-year baselines in the circular.", "recipient": "Central Bank of Sudan / Sudan FIU on lawful request", "submission": "Retained internally in sufficient detail for transaction reconstruction and supervisory/FIU access.", "applicability": "Circular No. 8/2026 effective from 30 April 2026.", "consequence": "Recordkeeping deficiencies may trigger supervisory and statutory enforcement.", "enforcement": "Central Bank of Sudan / Sudan FIU", "evidenceStatus": "verified", "operationalImpact": "Apply the Circular No. 8/2026 five-year recordkeeping baselines to CDD records, transactions/attempts, FIU reports, unusual-transaction files, risk assessments and AML/CFT/CPF training records.", "evidenceIds": [ "amlb:evidence:e3f4ea9c" ], "sourceEntityIds": [ "amlb:source-entity:2e2325ce" ] }, { "id": "SD-CUSTOMER-DATA-2026", "jurisdictionCode": "SD", "jurisdictionName": "Sudan", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-28", "title": "Bank customer-data update exercise", "timingType": "scheduled", "sectors": [ "banking" ], "appliesTo": "Banks and their customers within the CBOS customer-data update exercise announced as having begun under directions issued from February 2026.", "trigger": "Complete outstanding customer-data updates and account classification required by CBOS supervisory and AML/CFT requirements.", "deadline": "By 31 December 2026 (CBOS extended the update period through the end of 2026).", "recipient": "Central Bank of Sudan supervisory framework; completion occurs through the customer’s bank under the required procedures.", "submission": "Provide/validate approved customer documentation and complete the bank’s customer-data and account-classification update process.", "applicability": "Deadline extension announced 16 August 2026.", "consequence": "The CBOS notice stresses completion within the specified period; no standalone monetary penalty is asserted from the notice itself.", "enforcement": "Central Bank of Sudan", "evidenceStatus": "verified", "operationalImpact": "Banks should track outstanding KYC/customer-data remediation to completion by year-end 2026 and preserve evidence of the updated customer profile/account classification.", "evidenceIds": [ "amlb:evidence:8da2e7ed" ], "sourceEntityIds": [ "amlb:source-entity:2e2325ce" ] }, { "id": "SH-SAR", "jurisdictionCode": "SH", "jurisdictionName": "St. Helena", "coverageStatus": "verified", "lastReviewedDate": "2026-08-19", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Relevant businesses and MLROs within the Saint Helena AML/CFT/CPF Directive perimeter.", "trigger": "The MLRO concludes there is knowledge, suspicion or reasonable grounds for knowledge/suspicion that a person is engaged in money laundering or terrorist financing.", "deadline": "As soon as reasonably practicable and in any event within 7 days.", "recipient": "Royal St Helena Police Service and Money Laundering Regulatory Authority", "submission": "SAR by email to the Royal St Helena Police Service and copied/submitted to the MLRA as specified by the Directive.", "applicability": "Current 2025 Directive reviewed 19 Aug 2026.", "consequence": "Failure to comply can lead to regulatory or legal consequences under the Saint Helena AML/CFT regime.", "enforcement": "Money Laundering Regulatory Authority / Royal St Helena Police", "evidenceStatus": "verified", "evidenceNote": "Section 8.18 expressly requires filing as soon as reasonably practicable and in any event within seven days.", "operationalImpact": "Run the external SAR clock from the MLRO determination/attention point and keep evidence of both recipients and submission time.", "evidenceIds": [ "amlb:evidence:be49f074" ], "sourceEntityIds": [ "amlb:source-entity:c6680436" ] }, { "id": "SH-CONSENT", "jurisdictionCode": "SH", "jurisdictionName": "St. Helena", "coverageStatus": "verified", "lastReviewedDate": "2026-08-19", "title": "Consent stop before suspicious transaction proceeds", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Relevant businesses handling a suspicious transaction within the Directive perimeter.", "trigger": "A transaction is suspicious and would otherwise proceed after escalation/reporting.", "deadline": "Do not proceed unless consent is given by the MLRA or Royal St Helena Police, or 20 working days elapse without a response.", "recipient": "Money Laundering Regulatory Authority / Royal St Helena Police Service", "submission": "Hold the transaction and document consent/no-response status through the 20-working-day window.", "applicability": "Current 2025 Directive reviewed 19 Aug 2026.", "consequence": "Proceeding contrary to applicable consent/AML controls may create regulatory or legal exposure.", "enforcement": "MLRA / Royal St Helena Police", "evidenceStatus": "verified", "evidenceNote": "Section 8.20 sets the explicit consent-or-20-working-days rule.", "operationalImpact": "Implement a transaction hold with a working-day timer and auditable release basis: express consent or expiry with no response.", "evidenceIds": [ "amlb:evidence:be49f074" ], "sourceEntityIds": [ "amlb:source-entity:c6680436" ] }, { "id": "SO-STR", "jurisdictionCode": "SO", "jurisdictionName": "Somalia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report (STR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions listed under the AML/CFT Act, including banks, insurance, money-service businesses, mobile money, microfinance and DNFBPs.", "trigger": "A transaction/activity meets the suspicious-transaction threshold under the AML/CFT Act.", "deadline": "Report under the current Somali AML/CFT reporting rule; exact numeric outer limit was not established from the current official public page.", "recipient": "Financial Reporting Center (FRC)", "submission": "Use the FRC reporting route prescribed for reporting institutions.", "applicability": "Current NAMLC reporting-obligations page reviewed 19 Aug 2026.", "consequence": "Failure to report may lead to action under the AML/CFT Act and supervisory framework.", "enforcement": "Financial Reporting Center / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain prompt internal escalation and confirm the current FRC form/channel and deadline applicable to the entity.", "evidenceIds": [ "amlb:evidence:63e1f225", "amlb:evidence:3c54d609" ], "sourceEntityIds": [ "amlb:source-entity:9ad73b68", "amlb:source-entity:87283476" ] }, { "id": "SO-LCTR", "jurisdictionCode": "SO", "jurisdictionName": "Somalia", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Large Cash Transaction Report (LCTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting institutions within Article 14 of the AML/CFT Act.", "trigger": "A cash transaction reaches the official large-cash reporting threshold.", "deadline": "Report large cash transactions of US$10,000 and more; exact current filing clock was not stated on the official public summary reviewed.", "recipient": "Financial Reporting Center (FRC)", "submission": "Use the FRC-prescribed LCTR/reporting channel.", "applicability": "Current NAMLC reporting-obligations page reviewed 19 Aug 2026.", "consequence": "Failure to submit required threshold reports may lead to statutory/supervisory enforcement.", "enforcement": "Financial Reporting Center / relevant supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Detect threshold cash activity and route it to the FRC process while separately confirming the current submission deadline.", "evidenceIds": [ "amlb:evidence:63e1f225", "amlb:evidence:3c54d609" ], "sourceEntityIds": [ "amlb:source-entity:9ad73b68", "amlb:source-entity:87283476" ] }, { "id": "SR-UTR", "jurisdictionCode": "SR", "jurisdictionName": "Suriname", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Unusual Transaction Report (MOT)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial and non-financial service providers within the Wet MOT reporting perimeter.", "trigger": "A performed or intended transaction meets an objective or subjective unusual-transaction indicator / possible ML/TF information threshold.", "deadline": "Statutory text is described in the CFATF evaluation as immediate reporting; prior FIU guidance timing created an identified inconsistency, so operational deployment should confirm the current instruction.", "recipient": "Financial Intelligence Unit Suriname", "submission": "Written or digital filing to FIU Suriname; FIU material identifies the REPSYS reporting portal for online reports.", "applicability": "Current FATF follow-up through Jan 2026 reviewed together with FIU/CFATF materials.", "consequence": "Failure to report can lead to enforcement under the Wet MOT / AML supervision framework.", "enforcement": "FIU Suriname / competent supervisors", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat the statutory standard as time-critical, use REPSYS where applicable, and confirm the latest FIU guidance before relying on any grace period.", "evidenceIds": [ "amlb:evidence:80f18e5b", "amlb:evidence:7ad5db0b", "amlb:evidence:d1ad519e" ], "sourceEntityIds": [ "amlb:source-entity:bb8d0a8e", "amlb:source-entity:c4320f87" ] }, { "id": "SR-RECORDS", "jurisdictionCode": "SR", "jurisdictionName": "Suriname", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT customer and transaction recordkeeping", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Service providers subject to Suriname’s AML/CFT identification and reporting laws.", "trigger": "Creation of customer-identification, transaction and reporting records required by current AML/CFT rules.", "deadline": "Retain for the period required by the current applicable law; mapped sources do not carry forward an older universal retention number without current consolidated confirmation.", "recipient": "FIU Suriname / competent supervisor on lawful request", "submission": "Retained internally and made available as required by law.", "applicability": "Current follow-up status reviewed 19 Aug 2026.", "consequence": "Recordkeeping failures can lead to supervisory or statutory enforcement.", "enforcement": "FIU Suriname / competent supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep records on hold until the entity-specific current statutory period and trigger are confirmed.", "evidenceIds": [ "amlb:evidence:7ad5db0b", "amlb:evidence:d1ad519e" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87", "amlb:source-entity:bb8d0a8e" ] }, { "id": "SY-STR-FRAMEWORK", "jurisdictionCode": "SY", "jurisdictionName": "Syria", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction reporting framework", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Syrian AML/CFT regime, subject to current local-law confirmation.", "trigger": "A transaction/activity meets the suspicious-reporting threshold under the applicable Syrian AML/CFT framework.", "deadline": "Current universal filing clock cannot be safely established from the authoritative 2026 public evidence reviewed.", "recipient": "Syrian AML/CFT financial intelligence / competent reporting authority, subject to current local confirmation", "submission": "Use the current local reporting channel required by Syrian law; channel verification is an explicit gap.", "applicability": "FATF monitoring statement dated 19 Jun 2026.", "consequence": "Consequences depend on the current Syrian AML/CFT law and enforcement environment.", "enforcement": "Competent Syrian AML/CFT authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not automate a filing clock or recipient from legacy material alone; obtain current local legal/operational confirmation before acting.", "evidenceIds": [ "amlb:evidence:4eb92f1e", "amlb:evidence:2f09bd8d" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87" ] }, { "id": "SY-PREVENTIVE", "jurisdictionCode": "SY", "jurisdictionName": "Syria", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "CDD and AML/CFT preventive framework", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities under the Syrian AML/CFT framework, subject to current local verification.", "trigger": "Ongoing customer relationships, transactions and AML/CFT risk management.", "deadline": "Ongoing obligations exist at the technical-framework level; current sector-specific cadence, retention and implementation detail require local confirmation.", "recipient": "Competent Syrian AML/CFT supervisors / authorities", "submission": "Maintain controls and records required by current local law; current operational details are not asserted here.", "applicability": "FATF current monitoring statement reviewed 19 Aug 2026.", "consequence": "Consequences depend on current local law and enforcement.", "enforcement": "Competent Syrian AML/CFT authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use this entry as a legal-verification flag, not as permission to copy clocks from historical regulations.", "evidenceIds": [ "amlb:evidence:4eb92f1e" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87" ] }, { "id": "TM-MANDATORY-REPORT", "jurisdictionCode": "TM", "jurisdictionName": "Turkmenistan", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Report transactions subject to mandatory control", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons carrying out operations that fall within Turkmenistan’s AML/CFT mandatory-control reporting perimeter.", "trigger": "A transaction with money or other assets is subject to mandatory control or meets suspicious-operation criteria established under the AML/CFT framework.", "deadline": "Submit in accordance with the rules set by the Financial Monitoring Service; exact current universal numeric clock and threshold mix require entity/transaction-specific confirmation.", "recipient": "Financial Monitoring Service at the Ministry of Finance and Economy of Turkmenistan", "submission": "Information submitted under the rules and automated/accounting systems established by the FMS.", "applicability": "Current FMS website reviewed 19 Aug 2026.", "consequence": "Failure to provide required information may lead to enforcement under the AML/CFT legislation.", "enforcement": "Financial Monitoring Service / relevant state supervisor", "evidenceStatus": "verified-with-gap", "operationalImpact": "Map transaction type to the FMS mandatory-control rule and maintain evidence of timely submission under the applicable procedure.", "evidenceIds": [ "amlb:evidence:61873f04" ], "sourceEntityIds": [ "amlb:source-entity:a368239e" ] }, { "id": "TM-CONTROLS", "jurisdictionCode": "TM", "jurisdictionName": "Turkmenistan", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT internal control rules and training", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons carrying out operations within the Turkmenistan AML/CFT framework.", "trigger": "Ongoing operation as a reporting/obliged person.", "deadline": "Ongoing; maintain internal-control rules and staff preparation/training meeting FMS and relevant supervisory requirements. Exact universal testing/retention cadence is not stated on the current public FMS page.", "recipient": "Financial Monitoring Service / relevant state supervisory body", "submission": "Internal control rules, employee training and records; provide information when legally required.", "applicability": "Current FMS website reviewed 19 Aug 2026.", "consequence": "Control deficiencies may result in enforcement under applicable legislation.", "enforcement": "Financial Monitoring Service / relevant state supervisors", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain a documented AML programme and verify sector-specific testing, training and retention frequencies with the competent supervisor.", "evidenceIds": [ "amlb:evidence:61873f04" ], "sourceEntityIds": [ "amlb:source-entity:a368239e" ] }, { "id": "TV-STR", "jurisdictionCode": "TV", "jurisdictionName": "Tuvalu", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious transaction report", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions and other entities within Tuvalu’s AML/CFT reporting perimeter.", "trigger": "A transaction/activity meets the applicable statutory suspicious-reporting test.", "deadline": "Report under the current Tuvalu AML/CFT rules; exact universal numeric clock was not safely established from the current APG public material reviewed.", "recipient": "Tuvalu financial intelligence / competent reporting authority", "submission": "Use the reporting channel prescribed by the current Tuvalu framework.", "applicability": "APG current member page and May 2026 implementation-support update reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to enforcement under applicable Tuvalu law.", "enforcement": "Competent Tuvalu AML/CFT authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep immediate internal escalation and obtain current local filing instructions before external submission.", "evidenceIds": [ "amlb:evidence:3da19d37", "amlb:evidence:6687944d" ], "sourceEntityIds": [ "amlb:source-entity:a5ffefa6" ] }, { "id": "TV-CONTROLS", "jurisdictionCode": "TV", "jurisdictionName": "Tuvalu", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT/CPF preventive implementation", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other reporting entities within Tuvalu’s developing/current AML/CFT framework.", "trigger": "Ongoing customer relationships, transactions and institutional AML/CFT risk management.", "deadline": "Ongoing; apply current Tuvalu preventive measures. Exact cross-sector retention and periodic-review rules require local-law confirmation.", "recipient": "Competent Tuvalu AML/CFT supervisor / FIU", "submission": "Internal controls, records and regulatory reporting as required by current law.", "applicability": "Current APG implementation-support evidence reviewed 19 Aug 2026.", "consequence": "Deficiencies may lead to enforcement under applicable local law.", "enforcement": "Competent Tuvalu AML/CFT authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Treat the jurisdiction as requiring current local legal validation before changing retention or reporting automation.", "evidenceIds": [ "amlb:evidence:3da19d37", "amlb:evidence:6687944d" ], "sourceEntityIds": [ "amlb:source-entity:a5ffefa6" ] }, { "id": "VA-SAR", "jurisdictionCode": "VA", "jurisdictionName": "Vatican City", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report to ASIF", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Obliged/reporting entities under Vatican Law No. XVIII, including entities and authorities within the applicable Holy See/Vatican City perimeter.", "trigger": "Knowledge or suspicion meeting the Law No. XVIII suspicious-activity reporting threshold.", "deadline": "Submit in accordance with Law No. XVIII and current ASIF rules; a single numeric universal outer limit is not asserted from the current public profile/report material reviewed.", "recipient": "Supervisory and Financial Information Authority (ASIF)", "submission": "Submit a SAR to ASIF through the reporting method prescribed by current ASIF rules.", "applicability": "Current Vatican ASIF profile and 2025 reporting evidence reviewed 19 Aug 2026.", "consequence": "Failure to comply may lead to supervisory, administrative or other consequences under Vatican law.", "enforcement": "ASIF / competent Vatican authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain direct ASIF escalation and verify the precise applicable reporting timing for the reporting-entity type.", "evidenceIds": [ "amlb:evidence:46c60bf8", "amlb:evidence:d0b6610f" ], "sourceEntityIds": [ "amlb:source-entity:6de1d849", "amlb:source-entity:0b13f1f3" ] }, { "id": "VA-HIGH-RISK", "jurisdictionCode": "VA", "jurisdictionName": "Vatican City", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "High-risk jurisdiction transaction suspension/reporting", "timingType": "event-driven", "sectors": [ "financial-institutions" ], "appliesTo": "Entities professionally carrying out activities of a financial nature that fall within ASIF Instruction No. 1.", "trigger": "A transaction or operation is directly or indirectly connected with a jurisdiction included in the ASIF list of High-Risk Jurisdictions / Increased Monitoring, under the instruction’s scope.", "deadline": "Suspend covered transactions unless specifically authorised by ASIF; attempted covered transactions are to be reported immediately to ASIF under the instruction.", "recipient": "ASIF", "submission": "Suspend/escalate under Instruction No. 1 and report to ASIF through the applicable reporting route.", "applicability": "Current ASIF annual-report discussion reviewed for the 2025 reporting period; scope kept to professional financial activities.", "consequence": "Non-compliance may trigger supervisory or legal consequences under Vatican law and ASIF rules.", "enforcement": "ASIF", "evidenceStatus": "verified-scope", "evidenceNote": "Current ASIF reporting describes the instruction as requiring suspension and immediate reporting of attempted operations connected to listed high-risk jurisdictions.", "operationalImpact": "Screen jurisdiction exposure before execution, place covered activity on hold and route attempted transactions immediately to ASIF.", "evidenceIds": [ "amlb:evidence:d0b6610f", "amlb:evidence:46c60bf8" ], "sourceEntityIds": [ "amlb:source-entity:0b13f1f3", "amlb:source-entity:6de1d849" ] }, { "id": "YE-STR", "jurisdictionCode": "YE", "jurisdictionName": "Yemen", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious Transaction Report to the FIU", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Financial institutions, non-financial institutions and designated professions within the AML/CFT law, subject to the current operating/jurisdictional context.", "trigger": "A suspicious transaction relevant to money laundering, terrorist financing or associated predicate offences is identified.", "deadline": "Submit under the current applicable Yemeni AML/CFT rule; the 2025 FIU report confirms operational receipt but does not establish a safe universal numeric clock for this Calendar.", "recipient": "Financial Information Unit (Aden-based current operating FIU described in the 2025 report)", "submission": "Banks and exchange entities have a practical electronic STR form/direct electronic link launched in 2025; other sectors must use the currently prescribed FIU route.", "applicability": "FIU Annual Report 2025 published in 2026; FATF monitoring statement 19 Jun 2026.", "consequence": "Failure to report may lead to action under the AML/CFT law, subject to the current enforcement environment.", "enforcement": "Financial Information Unit / Central Bank / relevant supervisors", "evidenceStatus": "verified-with-gap", "operationalImpact": "For banks/exchange entities, maintain access to the current electronic form; all entities should confirm the live filing clock and authority given the operating fragmentation.", "evidenceIds": [ "amlb:evidence:e7efda3f", "amlb:evidence:4eb92f1e" ], "sourceEntityIds": [ "amlb:source-entity:10f69385", "amlb:source-entity:c4320f87" ] }, { "id": "YE-CONTROLS", "jurisdictionCode": "YE", "jurisdictionName": "Yemen", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT compliance, monitoring and FIU readiness", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial and non-financial institutions/designated professions within the applicable Yemeni AML/CFT perimeter.", "trigger": "Ongoing operation, customer monitoring and compliance with AML/CFT policies/procedures.", "deadline": "Ongoing; maintain CDD, monitoring, compliance and reporting controls under the current applicable law. Exact universal retention and review clocks require entity/local confirmation.", "recipient": "FIU / Central Bank / relevant supervisory authority", "submission": "Internal AML/CFT policies, monitoring systems, records and FIU reporting mechanisms.", "applicability": "Current FIU operational report and FATF monitoring reviewed 19 Aug 2026.", "consequence": "Control failures may lead to statutory/supervisory consequences, subject to current operating conditions.", "enforcement": "FIU / Central Bank / relevant supervisory authorities", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep jurisdiction-specific manual review for legal changes, regulator reach and filing route rather than treating the framework as a single stable national workflow.", "evidenceIds": [ "amlb:evidence:e7efda3f", "amlb:evidence:99a5a45f" ], "sourceEntityIds": [ "amlb:source-entity:10f69385", "amlb:source-entity:c4320f87" ] }, { "id": "AQ-AML-SCOPE", "jurisdictionCode": "AQ", "jurisdictionName": "Antarctica", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Applicable national AML/CFT regime determination", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Operators, contractors, financial institutions and other entities supporting activity in Antarctica where financial-crime obligations may arise under a home-state or other national legal nexus.", "trigger": "Before relying on Antarctica itself as the jurisdictional hook for onboarding, payments, procurement or other regulated activity.", "deadline": "Before the relevant activity or compliance decision; refresh when the operator, entity, contracting chain or legal nexus changes.", "recipient": "Internal compliance / legal; applicable national supervisor where required.", "submission": "Document the governing national AML/CFT law and regulated-entity nexus in the compliance file.", "applicability": "Antarctic Treaty system current; scope reviewed 19 Aug 2026.", "consequence": "Using a non-existent standalone Antarctic AML regime can cause missed duties under the actual home-state law and defective risk classification.", "enforcement": "Applicable home-state AML/CFT supervisor / FIU.", "evidenceStatus": "verified-with-gap", "operationalImpact": "The jurisdiction engine should route Antarctic exposure to the proven operator/entity legal nexus rather than assigning a fictional local FIU.", "evidenceIds": [ "amlb:evidence:9d4262dd", "amlb:evidence:bb722473" ], "sourceEntityIds": [ "amlb:source-entity:80f58e0d" ] }, { "id": "AQ-STR-ROUTING", "jurisdictionCode": "AQ", "jurisdictionName": "Antarctica", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicion-report routing under the applicable national regime", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Any reporting entity whose suspicious activity involves Antarctic operations, logistics, counterparties or payments.", "trigger": "A suspicion-reporting threshold is met under the reporting entity’s proven governing AML/CFT law.", "deadline": "Use the filing clock of the applicable national regime. No Antarctic-specific numeric clock is asserted.", "recipient": "The FIU or competent authority designated by the applicable national law.", "submission": "Use the reporting channel prescribed by the governing national regime.", "applicability": "Current routing rule reviewed 19 Aug 2026.", "consequence": "Failure to route the case to the correct national regime may cause late or missing mandatory reports.", "enforcement": "Applicable national FIU / supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Case management should resolve legal jurisdiction before calculating the external reporting deadline.", "evidenceIds": [ "amlb:evidence:9d4262dd" ], "sourceEntityIds": [ "amlb:source-entity:80f58e0d" ] }, { "id": "BV-AML-SCOPE", "jurisdictionCode": "BV", "jurisdictionName": "Bouvet Island", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Norwegian AML-law territorial applicability check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Any reporting entity or operator proposing to rely on Norwegian AML/CFT obligations solely because an activity is connected with Bouvet Island.", "trigger": "A financial service, transaction or reporting question has a Bouvet territorial nexus.", "deadline": "Resolve before treating a mainland Norwegian AML deadline as territorially applicable.", "recipient": "Internal legal/compliance; competent Norwegian authority if a formal determination is required.", "submission": "Record the statutory/regulatory extension or other legal nexus supporting application.", "applicability": "Norwegian dependency framework current; reviewed 19 Aug 2026.", "consequence": "Assuming every mainland statute applies automatically can produce an incorrect recipient, filing clock or control perimeter.", "enforcement": "Competent Norwegian authority / sector supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Do not inherit Norway’s AML calendar from geography alone; preserve an explicit territorial-law check.", "evidenceIds": [ "amlb:evidence:2484273b" ], "sourceEntityIds": [ "amlb:source-entity:b5e0bc99" ] }, { "id": "BV-MF-CONDITIONAL", "jurisdictionCode": "BV", "jurisdictionName": "Bouvet Island", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Conditional suspicious-circumstances report under Norwegian AML law", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A reporting entity that is independently within the Norwegian Anti-Money Laundering Act and has a Bouvet-linked matter.", "trigger": "After closer investigations, circumstances remain that give grounds for ML/TF suspicion and the Norwegian AML Act is legally applicable to the entity/activity.", "deadline": "As soon as possible under the Norwegian AML baseline, but only after the legal applicability hook is established.", "recipient": "FIU / Økokrim", "submission": "Electronic Økokrim reporting route / Altinn access where the Norwegian regime applies.", "applicability": "Conditional parent-regime mapping reviewed 19 Aug 2026.", "consequence": "If the Norwegian AML Act applies, late reporting can trigger the enforcement consequences of that regime; this row does not assert territorial application by itself.", "enforcement": "Økokrim / competent Norwegian AML supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Compliance tooling may display the Norwegian clock only after the territorial/entity applicability flag is resolved.", "evidenceIds": [ "amlb:evidence:8d05b514", "amlb:evidence:f8eaa28a", "amlb:evidence:2484273b" ], "sourceEntityIds": [ "amlb:source-entity:6944b9f3", "amlb:source-entity:1fcc9ce3", "amlb:source-entity:b5e0bc99" ] }, { "id": "IO-STATUS-CHECK", "jurisdictionCode": "IO", "jurisdictionName": "British Indian Ocean Territory", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "BIOT / Chagos legal-status and governing-law check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities mapping AML/CFT, sanctions or financial-regulatory duties to activity connected with the Chagos Archipelago / Diego Garcia.", "trigger": "Before assigning a UK, Mauritian or territory-specific compliance rule to the activity.", "deadline": "Before onboarding, transaction execution or regulatory filing; re-check after any treaty-entry-into-force notice or implementing legislation.", "recipient": "Internal legal/compliance; relevant UK/Mauritius authority where needed.", "submission": "Retain the status source and legal nexus used for the compliance decision.", "applicability": "Current UK status evidence checked 19 Aug 2026.", "consequence": "A status transition can change the governing regulator, legal basis and reporting route.", "enforcement": "Relevant UK or Mauritian authority according to the status and activity.", "evidenceStatus": "verified-with-gap", "evidenceNote": "Current UK material says sovereignty transfers when the treaty enters into force and BIOT continues as a UKOT until then. No later official entry-into-force notice was established in mapped sources.", "operationalImpact": "Treat BIOT status as a versioned jurisdiction dependency, not a static country attribute.", "evidenceIds": [ "amlb:evidence:2f7cc9a3", "amlb:evidence:e49a7fed" ], "sourceEntityIds": [ "amlb:source-entity:386abd73" ] }, { "id": "IO-AML-ROUTING", "jurisdictionCode": "IO", "jurisdictionName": "British Indian Ocean Territory", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "AML/CFT reporting route under proven governing law", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A regulated entity handling a suspicious BIOT/Chagos-linked relationship or transaction.", "trigger": "The entity’s applicable AML/CFT reporting threshold is met.", "deadline": "Use the clock under the governing law proved after the BIOT status/scope check; no standalone universal BIOT filing-day clock is asserted here.", "recipient": "FIU / competent authority under the governing law.", "submission": "Use the reporting channel required by the governing law.", "applicability": "Routing control reviewed 19 Aug 2026.", "consequence": "Using an outdated sovereignty assumption could misroute a mandatory report or control obligation.", "enforcement": "Competent authority under the applicable regime.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Compliance systems should block automatic deadline inheritance until the status and entity-law nexus are resolved.", "evidenceIds": [ "amlb:evidence:2f7cc9a3", "amlb:evidence:e49a7fed" ], "sourceEntityIds": [ "amlb:source-entity:386abd73" ] }, { "id": "CX-SMR", "jurisdictionCode": "CX", "jurisdictionName": "Christmas Island", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Matter Report (SMR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "AUSTRAC reporting entities whose designated-service activity is within the Australian AML/CTF Act and has a Christmas Island nexus.", "trigger": "Reasonable grounds for suspicion, including relevant criminal activity or terrorism-financing suspicion.", "deadline": "Within 24 hours of forming a terrorism-financing suspicion; otherwise within 3 business days after the day the suspicion was formed.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Late or missing reports can attract civil penalty and enforcement action. A single monetary figure is not generalised because the applicable provision and entity facts matter.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Case-management escalation should distinguish the 24-hour terrorism-financing clock from the 3-business-day clock for other suspicions.", "evidenceIds": [ "amlb:evidence:946b2ae0", "amlb:evidence:83ddd7d5", "amlb:evidence:70db34c1" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "CX-TTR", "jurisdictionCode": "CX", "jurisdictionName": "Christmas Island", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Australian AML/CTF Act conducting a reportable physical-currency threshold transaction connected with Christmas Island.", "trigger": "Transfer, receipt or payment of A$10,000 or more in physical currency, including foreign currency of equivalent value.", "deadline": "Within 10 business days after the day the transaction takes place.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Failure to lodge a required TTR can lead to AUSTRAC enforcement and civil penalties; the Calendar does not substitute one generic maximum for the full statutory penalty regime.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Cash-detection logic should aggregate only as required by the applicable reporting rule and send reportable physical-currency events into a 10-business-day filing workflow.", "evidenceIds": [ "amlb:evidence:2799d585", "amlb:evidence:83ddd7d5", "amlb:evidence:70db34c1" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "CC-SMR", "jurisdictionCode": "CC", "jurisdictionName": "Cocos (Keeling) Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Matter Report (SMR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "AUSTRAC reporting entities whose designated-service activity is within the Australian AML/CTF Act and has a Cocos (Keeling) Islands nexus.", "trigger": "Reasonable grounds for suspicion, including relevant criminal activity or terrorism-financing suspicion.", "deadline": "Within 24 hours of forming a terrorism-financing suspicion; otherwise within 3 business days after the day the suspicion was formed.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Late or missing reports can attract civil penalty and enforcement action. A single monetary figure is not generalised because the applicable provision and entity facts matter.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Case-management escalation should distinguish the 24-hour terrorism-financing clock from the 3-business-day clock for other suspicions.", "evidenceIds": [ "amlb:evidence:946b2ae0", "amlb:evidence:83ddd7d5", "amlb:evidence:e45d3b09" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "CC-TTR", "jurisdictionCode": "CC", "jurisdictionName": "Cocos (Keeling) Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Australian AML/CTF Act conducting a reportable physical-currency threshold transaction connected with Cocos (Keeling) Islands.", "trigger": "Transfer, receipt or payment of A$10,000 or more in physical currency, including foreign currency of equivalent value.", "deadline": "Within 10 business days after the day the transaction takes place.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Failure to lodge a required TTR can lead to AUSTRAC enforcement and civil penalties; the Calendar does not substitute one generic maximum for the full statutory penalty regime.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Cash-detection logic should aggregate only as required by the applicable reporting rule and send reportable physical-currency events into a 10-business-day filing workflow.", "evidenceIds": [ "amlb:evidence:2799d585", "amlb:evidence:83ddd7d5", "amlb:evidence:e45d3b09" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "NF-SMR", "jurisdictionCode": "NF", "jurisdictionName": "Norfolk Island", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Matter Report (SMR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "AUSTRAC reporting entities whose designated-service activity is within the Australian AML/CTF Act and has a Norfolk Island nexus.", "trigger": "Reasonable grounds for suspicion, including relevant criminal activity or terrorism-financing suspicion.", "deadline": "Within 24 hours of forming a terrorism-financing suspicion; otherwise within 3 business days after the day the suspicion was formed.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Late or missing reports can attract civil penalty and enforcement action. A single monetary figure is not generalised because the applicable provision and entity facts matter.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Case-management escalation should distinguish the 24-hour terrorism-financing clock from the 3-business-day clock for other suspicions.", "evidenceIds": [ "amlb:evidence:946b2ae0", "amlb:evidence:83ddd7d5", "amlb:evidence:ec69e875" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "NF-TTR", "jurisdictionCode": "NF", "jurisdictionName": "Norfolk Island", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Threshold Transaction Report (TTR)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities within the Australian AML/CTF Act conducting a reportable physical-currency threshold transaction connected with Norfolk Island.", "trigger": "Transfer, receipt or payment of A$10,000 or more in physical currency, including foreign currency of equivalent value.", "deadline": "Within 10 business days after the day the transaction takes place.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Current Australian AML/CTF framework and territorial governance checked 19 Aug 2026.", "consequence": "Failure to lodge a required TTR can lead to AUSTRAC enforcement and civil penalties; the Calendar does not substitute one generic maximum for the full statutory penalty regime.", "enforcement": "AUSTRAC", "evidenceStatus": "verified", "operationalImpact": "Cash-detection logic should aggregate only as required by the applicable reporting rule and send reportable physical-currency events into a 10-business-day filing workflow.", "evidenceIds": [ "amlb:evidence:2799d585", "amlb:evidence:83ddd7d5", "amlb:evidence:ec69e875" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d", "amlb:source-entity:ab717b42" ] }, { "id": "FK-DRUG-ML-DISCLOSURE", "jurisdictionCode": "FK", "jurisdictionName": "Falkland Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-08-19", "title": "Disclosure of drug-money-laundering knowledge or suspicion", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A person who learns in the course of trade, profession, business or employment information giving knowledge or suspicion that another person is engaged in drug money laundering, subject to statutory exceptions.", "trigger": "Knowledge or suspicion based on information or matter coming to attention in the course of trade, profession, business or employment.", "deadline": "As soon as is reasonably practicable after the information or matter comes to attention.", "recipient": "Police officer; an employee may use the appropriate employer reporting person/procedure as provided by the Ordinance.", "submission": "Disclosure to police or qualifying internal reporting route under the Ordinance.", "applicability": "In-force local text checked 19 Aug 2026.", "consequence": "Section 52 provides criminal penalties for failure to disclose; exact sentencing depends on the offence and court.", "enforcement": "Royal Falkland Islands Police / courts.", "evidenceStatus": "verified", "evidenceNote": "Current Falkland legislation site shows the Ordinance in force and section 50 states the “as soon as is reasonably practicable” disclosure duty.", "operationalImpact": "Escalation workflows should preserve when the information came to attention and support immediate internal/police disclosure where the provision applies.", "evidenceIds": [ "amlb:evidence:486c5692" ], "sourceEntityIds": [ "amlb:source-entity:044989e8" ] }, { "id": "FK-TIPPING-OFF", "jurisdictionCode": "FK", "jurisdictionName": "Falkland Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-08-19", "title": "Tipping-off prohibition after money-laundering disclosure/investigation", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons aware of specified money-laundering investigations or disclosures under the Drug Trafficking Offences Ordinance.", "trigger": "Knowledge or suspicion of an investigation or qualifying disclosure where onward information could prejudice investigation.", "deadline": "Continuous from the relevant knowledge/disclosure; do not make a prejudicial disclosure.", "recipient": "Internal compliance / law enforcement as appropriate.", "submission": "Prevent disclosure to affected customer/third parties except where a statutory exception applies.", "applicability": "In-force local text checked 19 Aug 2026.", "consequence": "Section 52 provides criminal penalties for tipping-off offences.", "enforcement": "Royal Falkland Islands Police / courts.", "evidenceStatus": "verified", "evidenceNote": "The current in-force Ordinance separately criminalises specified prejudicial disclosures after investigation/disclosure triggers.", "operationalImpact": "Case access and customer-communication controls should suppress information that could prejudice a money-laundering investigation.", "evidenceIds": [ "amlb:evidence:486c5692" ], "sourceEntityIds": [ "amlb:source-entity:044989e8" ] }, { "id": "TF-FR-SCOPE", "jurisdictionCode": "TF", "jurisdictionName": "French Southern Territories", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "French AML/CFT territorial-extension check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Any entity or operator seeking to apply a metropolitan French AML/CFT rule to activity located in the French Southern and Antarctic Lands.", "trigger": "A financial, procurement, logistics or professional activity creates a possible French AML/CFT nexus in TAAF.", "deadline": "Before applying a metropolitan filing clock or professional obligation solely by territorial assumption.", "recipient": "Internal legal/compliance; competent French/TAAF authority where required.", "submission": "Document the Code provision, extension/adaptation rule and professional perimeter relied upon.", "applicability": "Current TAAF status reviewed 19 Aug 2026.", "consequence": "Legislative specialty means unsupported automatic inheritance can misstate the applicable rule.", "enforcement": "Competent French authority / TAAF administration according to the issue.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Keep the jurisdiction profile as scope-gated rather than showing a metropolitan deadline as automatically local.", "evidenceIds": [ "amlb:evidence:08657023", "amlb:evidence:494942d4" ], "sourceEntityIds": [ "amlb:source-entity:cec4e89f" ] }, { "id": "TF-TRACFIN-CONDITIONAL", "jurisdictionCode": "TF", "jurisdictionName": "French Southern Territories", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Conditional TRACFIN suspicious-report routing", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A person/entity independently shown to fall within the French Article L.561-2 AML perimeter for the relevant TAAF-linked activity.", "trigger": "Suspicion meeting Article L.561-15 is established and the French AML provision is shown to apply to the entity/activity.", "deadline": "French baseline: without delay; territorial/professional applicability must be confirmed first.", "recipient": "TRACFIN", "submission": "ERMES / applicable TRACFIN procedure where French reporting law applies.", "applicability": "Conditional parent-regime mapping reviewed 19 Aug 2026.", "consequence": "Where French reporting law applies, delayed reporting can produce supervisory/legal consequences; this row does not itself prove territorial extension.", "enforcement": "TRACFIN / competent professional supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Only calculate the TRACFIN clock after the French-law applicability flag is resolved.", "evidenceIds": [ "amlb:evidence:71680dd1", "amlb:evidence:b83d2f36", "amlb:evidence:08657023" ], "sourceEntityIds": [ "amlb:source-entity:3973c456", "amlb:source-entity:989e83c3", "amlb:source-entity:cec4e89f" ] }, { "id": "HM-AML-SCOPE", "jurisdictionCode": "HM", "jurisdictionName": "Heard & McDonald Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Commonwealth AML/CTF territorial-extension check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Any reporting entity or operator seeking to treat a Heard Island / McDonald Islands nexus as automatically within the AML/CTF Act 2006.", "trigger": "A transaction, service or compliance decision depends on the Territory as the geographic legal hook.", "deadline": "Before inheriting an Australian AML/CTF obligation solely from territory geography.", "recipient": "Internal legal/compliance; AUSTRAC where interpretive/supervisory confirmation is required.", "submission": "Document the statutory extension, separate constitutional/entity nexus or other legal basis relied upon.", "applicability": "Current Federal Register texts checked 19 Aug 2026.", "consequence": "Ignoring section 7 can produce an unsupported local reporting calendar.", "enforcement": "Australian Government / AUSTRAC according to the proven legal nexus.", "evidenceStatus": "verified", "evidenceNote": "Section 7 expressly states that a Commonwealth Act does not apply as such in the Territory unless expressed to extend there or another Act provides otherwise.", "operationalImpact": "Block automatic AUSTRAC deadline inheritance where the only nexus is HM territory until an extension or independent entity/service hook is established.", "evidenceIds": [ "amlb:evidence:56b5235a", "amlb:evidence:83ddd7d5" ], "sourceEntityIds": [ "amlb:source-entity:867ced3d" ] }, { "id": "HM-SMR-CONDITIONAL", "jurisdictionCode": "HM", "jurisdictionName": "Heard & McDonald Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Conditional AUSTRAC suspicious-matter reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "An AUSTRAC reporting entity that is independently subject to the AML/CTF Act for a designated service involving a Heard/McDonald-linked matter.", "trigger": "Reasonable grounds for suspicion under the Australian AML/CTF regime and a valid Act/entity/service nexus independent of unsupported territorial inheritance.", "deadline": "If the Australian regime applies: within 24 hours for terrorism-financing suspicion; otherwise within 3 business days after the day the suspicion was formed.", "recipient": "AUSTRAC", "submission": "AUSTRAC Online.", "applicability": "Conditional clock mapping reviewed 19 Aug 2026.", "consequence": "Where Australian AML/CTF law applies, late SMRs can attract AUSTRAC enforcement; territorial application is not based on HM geography alone.", "enforcement": "AUSTRAC", "evidenceStatus": "verified-with-gap", "operationalImpact": "Show the SMR deadline only after the reporting-entity/legal-nexus test passes.", "evidenceIds": [ "amlb:evidence:946b2ae0", "amlb:evidence:56b5235a" ], "sourceEntityIds": [ "amlb:source-entity:440b0ece", "amlb:source-entity:867ced3d" ] }, { "id": "KP-FATF-COUNTERMEASURES", "jurisdictionCode": "KP", "jurisdictionName": "North Korea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "DPRK FATF countermeasures / enhanced risk controls", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Financial institutions and other obliged entities where their home jurisdiction implements the FATF call for countermeasures or heightened DPRK controls.", "trigger": "Customer, beneficial owner, transaction, correspondent, geography or other exposure involving the DPRK or persons acting on its behalf.", "deadline": "Before establishing/continuing exposure and throughout the relationship; exact legal measures and deadlines follow the home jurisdiction’s implementation.", "recipient": "Internal compliance and the competent home-state supervisor/FIU as applicable.", "submission": "Apply the home-state countermeasure/EDD framework, document decisions and make regulatory filings where domestic law requires.", "applicability": "Current FATF call-for-action state verified 19 Aug 2026.", "consequence": "Failure to implement domestic DPRK countermeasures can expose the institution to supervisory, sanctions and financial-crime enforcement.", "enforcement": "Home-state AML/CFT and sanctions authorities.", "evidenceStatus": "verified-scope", "operationalImpact": "Risk engines should treat DPRK exposure as a distinct countermeasure workflow, not merely a generic high-risk-country score.", "evidenceIds": [ "amlb:evidence:cedeaa7c" ], "sourceEntityIds": [ "amlb:source-entity:c4320f87" ] }, { "id": "KP-UNSC-TFS", "jurisdictionCode": "KP", "jurisdictionName": "North Korea", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "UNSC 1718 targeted financial sanctions / asset freeze", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Institutions subject to a UN Member State’s domestic implementation of the DPRK sanctions regime.", "trigger": "A person, entity, asset or economic resource falls within the applicable DPRK designation/ownership-control restrictions.", "deadline": "Freeze and restrict as required by the Member State’s implementing law; operationally without allowing prohibited dealing. Any authority-reporting clock is jurisdiction-specific.", "recipient": "Competent national sanctions authority / FIU according to domestic implementation.", "submission": "Screen, freeze/block and report using the domestic sanctions process implementing UNSC 1718 measures.", "applicability": "Current UN 1718 sanctions architecture checked 19 Aug 2026.", "consequence": "Breaches can produce severe civil/criminal sanctions under domestic implementing law.", "enforcement": "National sanctions authority / law enforcement.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Sanctions screening must identify designations and ownership/control before funds or economic resources are made available.", "evidenceIds": [ "amlb:evidence:30ee8b12", "amlb:evidence:df8257ce" ], "sourceEntityIds": [ "amlb:source-entity:a810e9cd", "amlb:source-entity:c0aba190" ] }, { "id": "PN-AML-SCOPE", "jurisdictionCode": "PN", "jurisdictionName": "Pitcairn Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Pitcairn AML/CFT legal-perimeter check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities handling activity connected with Pitcairn where a local, UK-extended or entity-home-state financial-crime rule may apply.", "trigger": "Before assigning a local/UK suspicious-report clock or financial-services obligation to the Pitcairn nexus.", "deadline": "Before onboarding, transaction execution or external filing based solely on Pitcairn geography.", "recipient": "Internal legal/compliance; relevant Pitcairn/UK authority as required.", "submission": "Document the local ordinance, UK Order in Council or entity-home-state rule that creates the obligation.", "applicability": "Scope reviewed 19 Aug 2026.", "consequence": "Treating UK mainland MLR/POCA as automatically applicable could create a false deadline or recipient.", "enforcement": "Relevant Pitcairn / UK / home-state authority.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Use a legal-perimeter gate before inheriting any parent-country calendar rule.", "evidenceIds": [ "amlb:evidence:fa01bf93" ], "sourceEntityIds": [ "amlb:source-entity:386abd73" ] }, { "id": "PN-SANCTIONS", "jurisdictionCode": "PN", "jurisdictionName": "Pitcairn Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "UK sanctions controls extended to Pitcairn by Overseas Territories Orders", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons/entities within the territorial scope of a UK sanctions Order extended to Pitcairn.", "trigger": "A transaction, customer, beneficial owner, asset or activity is caught by an applicable sanctions regime extended to the territory.", "deadline": "Apply prohibitions/freezes at the point the applicable Order requires; reporting/licensing clocks vary by regime and are not collapsed into one number.", "recipient": "Competent Pitcairn/UK authority specified by the applicable Order.", "submission": "Screen against the relevant sanctions list and follow the reporting/licensing procedure in the extended Order.", "applicability": "Current OT sanctions architecture checked 19 Aug 2026.", "consequence": "Breach can result in criminal/civil consequences under the applicable sanctions instrument.", "enforcement": "Authority specified in the applicable Overseas Territories Order.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Sanctions controls should be rule-by-regime rather than based on a single generic Pitcairn deadline.", "evidenceIds": [ "amlb:evidence:85f441b5", "amlb:evidence:7c310d3e" ], "sourceEntityIds": [ "amlb:source-entity:9d050209" ] }, { "id": "GS-UK-AML-SCOPE", "jurisdictionCode": "GS", "jurisdictionName": "South Georgia & South Sandwich Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "UK direct AML legislation applicability check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities/persons conducting activity in or connected with South Georgia and the South Sandwich Islands where UK direct legislation may create an AML/CFT duty.", "trigger": "Before applying an AML reporting, CDD, recordkeeping or other deadline from a UK instrument to the Territory.", "deadline": "Before compliance execution; re-check when the relevant UK/local instrument is amended.", "recipient": "Internal legal/compliance; competent SGSSI/UK authority under the instrument.", "submission": "Identify and retain the exact UK instrument and territorial extension provision.", "applicability": "Current SGSSI laws portal checked 19 Aug 2026.", "consequence": "Instrument-specific extension means a generic UK mainland calendar can be overbroad or wrong.", "enforcement": "Government of SGSSI / authority specified by applicable legislation.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Attach the precise territorial instrument to every SGSSI calendar item before assigning a deadline.", "evidenceIds": [ "amlb:evidence:5420fda3" ], "sourceEntityIds": [ "amlb:source-entity:4fb2e30d" ] }, { "id": "GS-SANCTIONS-SCREEN", "jurisdictionCode": "GS", "jurisdictionName": "South Georgia & South Sandwich Islands", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "UK sanctions-list screening under applicable territorial measures", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Persons and operators subject to SGSSI/extended UK sanctions measures.", "trigger": "Entry, contracting, payment or asset activity involving a person/entity potentially subject to the UK Sanctions List or an extended sanctions regime.", "deadline": "Before permitting the relevant activity and continuously where an applicable asset freeze/prohibition remains in force; exact reporting clock is instrument-specific.", "recipient": "Government of SGSSI / competent authority specified by the applicable sanctions Order.", "submission": "Screen against the UK Sanctions List and follow the applicable territorial sanctions instrument.", "applicability": "Current territorial legislation checked 19 Aug 2026.", "consequence": "Sanctions breaches can result in refusal/prohibition and criminal or other enforcement under the relevant instrument.", "enforcement": "Government of SGSSI / competent UK authority as specified.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Maintain live UK-list screening for territory-linked counterparties and do not collapse different sanctions Orders into one deadline.", "evidenceIds": [ "amlb:evidence:5420fda3", "amlb:evidence:1616cf3c" ], "sourceEntityIds": [ "amlb:source-entity:4fb2e30d" ] }, { "id": "SS-LCTR", "jurisdictionCode": "SS", "jurisdictionName": "South Sudan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Large cash transaction report to Bank of South Sudan", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Banks, non-bank financial institutions and agents covered by Circular No. DCB/BOD/1/2017 as amended 2022.", "trigger": "A single cash transaction or exchange of financial instruments with cash equal to or exceeding US$10,000 (or equivalent), under the circular.", "deadline": "Within 5 days following receipt or withdrawal of the large cash transaction.", "recipient": "Bank of South Sudan · Supervision Department", "submission": "Submit the declared report in the format prescribed by the Bank of South Sudan circular.", "applicability": "Current BoSS-hosted circular verified 19 Aug 2026.", "consequence": "Non-compliance can trigger supervisory action under the banking/AML framework; No single value is shown where the applicable result depends on sector, provision or facts.", "enforcement": "Bank of South Sudan", "evidenceStatus": "verified-with-gap", "operationalImpact": "Cash-monitoring systems should capture the transaction date and route threshold events to the Supervision Department before the five-day deadline.", "evidenceIds": [ "amlb:evidence:c1953d70" ], "sourceEntityIds": [ "amlb:source-entity:4104bf4a" ] }, { "id": "SS-CROSS-BORDER-CASH", "jurisdictionCode": "SS", "jurisdictionName": "South Sudan", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Cross-border currency declaration and financial-institution approval/reporting", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Persons carrying currency across the border and financial institutions importing/exporting cash within the scope of BoSS Circular No. 2 of 2025.", "trigger": "Any person carries US$10,000 or equivalent or more into/out of South Sudan; financial institutions have additional requirements for cash imports/exports above US$50,000.", "deadline": "Declaration at the border/airport when carrying US$10,000+; financial institutions must obtain prior BoSS approval for cash import/export above US$50,000 and maintain/file the circular’s required reports, including monthly reporting.", "recipient": "Customs/border authorities and Bank of South Sudan according to the requirement.", "submission": "Cross-Border Currency Declaration Form; BoSS approval/reporting route for financial institutions.", "applicability": "Current BoSS circular verified 19 Aug 2026.", "consequence": "Undeclared or unauthorised cross-border cash can be subject to regulatory/customs enforcement under the applicable framework.", "enforcement": "Bank of South Sudan / border and customs authorities.", "evidenceStatus": "verified", "evidenceNote": "The 2025 BoSS circular states the US$10,000 declaration threshold and prior-approval requirement for financial-institution cash movements above US$50,000.", "operationalImpact": "Treasury/cash-logistics teams should obtain approval before qualifying institutional cash movements and reconcile monthly reporting records.", "evidenceIds": [ "amlb:evidence:066b0d3f", "amlb:evidence:b669826c" ], "sourceEntityIds": [ "amlb:source-entity:4104bf4a", "amlb:source-entity:c4320f87" ] }, { "id": "SJ-MF", "jurisdictionCode": "SJ", "jurisdictionName": "Svalbard & Jan Mayen", "coverageStatus": "verified", "lastReviewedDate": "2026-08-19", "title": "Report of suspicious circumstances (MF-report)", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Norwegian Anti-Money Laundering Act operating/established in Svalbard or Jan Mayen, within the Act’s entity scope.", "trigger": "After closer investigations, circumstances remain that give grounds for suspicion of money laundering or terrorist financing.", "deadline": "As soon as possible.", "recipient": "FIU / Økokrim", "submission": "Electronically through Økokrim’s reporting form; high-volume reporters may use an API. Access/role management is handled through Altinn.", "applicability": "Current Norwegian AML Act expressly applies to Svalbard and Jan Mayen; checked 19 Aug 2026.", "consequence": "AML Act sanctions depend on the breached provision and facts; this row does not generalise a single monetary amount across all reporting entities.", "enforcement": "Økokrim / competent AML supervisor according to the enforcement route.", "evidenceStatus": "verified", "evidenceNote": "Lovdata states that the 2018 Anti-Money Laundering Act applies to Svalbard and Jan Mayen; Økokrim provides the current “as soon as possible” MF-report route.", "operationalImpact": "Ensure Altinn roles and reporting access are pre-provisioned so technical access does not delay an MF-report.", "evidenceIds": [ "amlb:evidence:8d05b514", "amlb:evidence:f8eaa28a" ], "sourceEntityIds": [ "amlb:source-entity:6944b9f3", "amlb:source-entity:1fcc9ce3" ] }, { "id": "SJ-RISK", "jurisdictionCode": "SJ", "jurisdictionName": "Svalbard & Jan Mayen", "coverageStatus": "verified", "lastReviewedDate": "2026-08-19", "title": "Business-wide ML/TF risk assessment", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Reporting entities under the Norwegian Anti-Money Laundering Act in Svalbard or Jan Mayen.", "trigger": "Ongoing activity and changes to the entity’s products, services, customers, channels and geographic risk.", "deadline": "Ongoing. Section 7 requires reporting entities to identify and assess their ML/TF risk; no single universal calendar due date is asserted.", "recipient": "Relevant AML supervisor through supervision.", "submission": "Maintain the documented risk assessment and associated procedures internally; provide evidence under the applicable supervisory regime.", "applicability": "Current Norwegian AML Act expressly applies to Svalbard and Jan Mayen; checked 19 Aug 2026.", "consequence": "Supervisory and administrative consequences depend on the sector and breach. A universal penalty amount is not shown for the generic risk-assessment duty.", "enforcement": "Finanstilsynet and/or another competent AML supervisor depending on sector.", "evidenceStatus": "verified", "evidenceNote": "The current AML Act applies to Svalbard and Jan Mayen and section 7 supplies the standing risk-assessment obligation.", "operationalImpact": "Use the business-wide assessment as the basis for procedures and control intensity; update when the risk picture changes.", "evidenceIds": [ "amlb:evidence:cfc602eb", "amlb:evidence:f8eaa28a" ], "sourceEntityIds": [ "amlb:source-entity:1fcc9ce3" ] }, { "id": "TK-AML-SCOPE", "jurisdictionCode": "TK", "jurisdictionName": "Tokelau", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Tokelau / New Zealand AML-law applicability check", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities/persons handling Tokelau-linked financial activity where a Tokelau rule, expressly extended New Zealand statute or entity-home-state law may apply.", "trigger": "Before assigning a New Zealand AML/CFT deadline based only on Tokelau’s relationship with New Zealand.", "deadline": "Before onboarding, regulated service, transaction or external filing.", "recipient": "Internal legal/compliance; Tokelau / New Zealand competent authority where required.", "submission": "Record the Tokelau rule, express statutory extension or entity-based New Zealand legal nexus.", "applicability": "Official Tokelau legal-scope statement checked 19 Aug 2026.", "consequence": "Automatic parent-law inheritance can produce a false reporting clock.", "enforcement": "Competent Tokelau / New Zealand authority under the proven legal basis.", "evidenceStatus": "verified", "evidenceNote": "Tokelau’s government explicitly states that New Zealand statute law does not apply unless expressly extended to Tokelau.", "operationalImpact": "Require a legal-extension flag before displaying New Zealand AML deadlines as Tokelau obligations.", "evidenceIds": [ "amlb:evidence:232a0eb1", "amlb:evidence:f0b5cb86" ], "sourceEntityIds": [ "amlb:source-entity:dc66c6d9" ] }, { "id": "TK-NZ-SAR-CONDITIONAL", "jurisdictionCode": "TK", "jurisdictionName": "Tokelau", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Conditional New Zealand SAR route for a New Zealand reporting entity", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A New Zealand AML/CFT reporting entity whose own legal status makes the AML/CFT Act applicable to a Tokelau-linked activity, or where the relevant New Zealand provision is proven expressly extended.", "trigger": "Reasonable grounds for suspicion are formed and the New Zealand AML/CFT reporting duty is legally applicable.", "deadline": "If the NZ regime applies: no later than 3 working days after reasonable grounds for suspicion are formed.", "recipient": "New Zealand Police Financial Intelligence Unit", "submission": "goAML Web.", "applicability": "Conditional parent-regime mapping reviewed 19 Aug 2026.", "consequence": "If the entity is within NZ law, late SAR reporting can trigger AML/CFT Act enforcement; Tokelau geography alone is not the legal hook.", "enforcement": "New Zealand Police FIU / DIA where NZ law applies.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Calculate the NZ SAR clock only when the reporting entity/legal-extension test is satisfied.", "evidenceIds": [ "amlb:evidence:50174664", "amlb:evidence:232a0eb1" ], "sourceEntityIds": [ "amlb:source-entity:8cab850a", "amlb:source-entity:dc66c6d9" ] }, { "id": "UM-SAR", "jurisdictionCode": "UM", "jurisdictionName": "U.S. Outlying Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Suspicious Activity Report (SAR)", "timingType": "event-driven", "sectors": [ "banking", "payments", "securities" ], "appliesTo": "BSA-covered financial institutions where the federal rule and United States/territory/insular-possession definitions cover the relevant U.S. Minor Outlying Islands activity.", "trigger": "Detection of facts meeting the applicable suspicious-activity reporting threshold.", "deadline": "Generally within 30 calendar days after initial detection; up to 60 days where no suspect is identified under the applicable rule.", "recipient": "Financial Crimes Enforcement Network (FinCEN)", "submission": "BSA E-Filing System.", "applicability": "Current federal BSA framework and eCFR territorial definitions checked 19 Aug 2026.", "consequence": "Missing or late SARs can lead to FinCEN civil enforcement and, depending on the conduct, other regulatory or criminal consequences.", "enforcement": "FinCEN and the relevant functional regulator / law-enforcement authority", "evidenceStatus": "verified-with-gap", "operationalImpact": "Preserve the initial-detection date and escalate investigations early enough to meet the federal SAR clock.", "evidenceIds": [ "amlb:evidence:4fde97d7", "amlb:evidence:83c2e6fd", "amlb:evidence:70676487", "amlb:evidence:d85754cd" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:1acba317", "amlb:source-entity:54430121" ] }, { "id": "UM-CTR", "jurisdictionCode": "UM", "jurisdictionName": "U.S. Outlying Islands", "coverageStatus": "verified", "lastReviewedDate": "2026-09-04", "title": "Currency Transaction Report (CTR)", "timingType": "event-driven", "sectors": [ "banking", "payments" ], "appliesTo": "Financial institutions within the federal CTR rule where the relevant activity is within U.S. territory/insular-possession scope.", "trigger": "Cash-in or cash-out transaction(s) exceeding US$10,000 in one business day, subject to aggregation/exemptions.", "deadline": "Within 15 calendar days of the reportable transaction(s).", "recipient": "FinCEN", "submission": "BSA E-Filing System.", "applicability": "Current federal BSA framework and eCFR territorial definitions checked 19 Aug 2026.", "consequence": "Late or missing CTRs can lead to FinCEN enforcement and civil monetary penalties.", "enforcement": "FinCEN", "evidenceStatus": "verified", "evidenceNote": "FinCEN directly states the 15-day CTR filing period; the territory profile uses federal BSA definitions and uses the federal BSA authority framework.", "operationalImpact": "Cash aggregation controls should retain the business-day context used for filing.", "evidenceIds": [ "amlb:evidence:929c31a5", "amlb:evidence:d85754cd", "amlb:evidence:65ddd453", "amlb:evidence:ece0e76f" ], "sourceEntityIds": [ "amlb:source-entity:ede8195a", "amlb:source-entity:54430121" ] }, { "id": "EH-GOVERNING-REGIME", "jurisdictionCode": "EH", "jurisdictionName": "Western Sahara", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Western Sahara governing AML/CFT regime determination", "timingType": "ongoing", "sectors": [ "all" ], "appliesTo": "Entities onboarding customers, assets, counterparties or operations with a Western Sahara territorial nexus.", "trigger": "Before selecting a regulator, FIU, country risk control or filing deadline for the activity.", "deadline": "Before onboarding/transaction execution and whenever the location, controlling authority, entity establishment or legal nexus changes.", "recipient": "Internal legal/compliance; competent authority under the proven governing regime.", "submission": "Document de facto location, entity establishment, governing law and the authority/FIU selected.", "applicability": "UN status and current dispute context reviewed 19 Aug 2026.", "consequence": "Assuming a single regime for the whole territory can cause misrouting of CDD, sanctions or suspicious-report obligations.", "enforcement": "Competent authority under the proven legal/entity nexus.", "evidenceStatus": "verified-scope", "evidenceNote": "Current UN material continues to identify Western Sahara as a Non-Self-Governing Territory. No sovereignty position or universal FIU is assigned.", "operationalImpact": "The jurisdiction engine should require a governing-regime decision before calculating any AML deadline.", "evidenceIds": [ "amlb:evidence:ea64a9fc" ], "sourceEntityIds": [ "amlb:source-entity:ea43ccf7" ] }, { "id": "EH-STR-ROUTING", "jurisdictionCode": "EH", "jurisdictionName": "Western Sahara", "coverageStatus": "verified-with-gap", "lastReviewedDate": "2026-09-04", "title": "Suspicious-report routing under proven governing/entity law", "timingType": "event-driven", "sectors": [ "all" ], "appliesTo": "A reporting entity handling suspicious activity connected with Western Sahara.", "trigger": "The entity meets a suspicious-transaction/activity reporting threshold under the law that actually governs it.", "deadline": "Use the filing clock of the proven governing/entity-home-state law; no universal Western Sahara-specific deadline is asserted.", "recipient": "FIU / competent authority under the applicable law.", "submission": "Use the reporting channel required by the applicable regime.", "applicability": "Routing rule reviewed 19 Aug 2026.", "consequence": "A wrong jurisdiction assignment can cause late or misdirected reporting.", "enforcement": "Applicable FIU / supervisor.", "evidenceStatus": "verified-with-gap", "operationalImpact": "Resolve governing law before calculating the report due time or recipient.", "evidenceIds": [ "amlb:evidence:ea64a9fc" ], "sourceEntityIds": [ "amlb:source-entity:ea43ccf7" ] } ] }