REPORTING MONTH 2026-10 · PUBLISHED 2026-11-02

The Compliance Current — October 2026

What changed. Why it matters. What to consider.

Monthly AML and sanctions regulatory analysis for financial institutions and their technology providers.

By Stephen D. Marshall · President, ICRM Services Inc. · Four decades of compliance and internal audit experience
Published 2026-11-02

Coverage: 2026-10-01 through 2026-10-31

Executive summary

October’s developments reinforce a central theme: effective compliance depends on how controls operate, not simply whether policies exist. US enforcement highlights weaknesses in transaction monitoring, correspondent due diligence, alert prioritization, escalation and the validation of remediation. The principal risk is a gap between a program’s design and its ability to identify, investigate and report material exposure.

Sanctions changes call for coordinated implementation across screening, payment operations and licensing decisions. Designations, non-SDN restrictions, humanitarian permissions and wind-down authorizations require different responses. Delayed list updates or overly broad interpretations of licences can create avoidable exposure.

Risk-based supervision and technology governance are also prominent. FINTRAC emphasizes evidence connecting risk to controls; AMLA’s crypto-related recommendations signal potential future changes rather than adopted requirements. AI-related supervisory statements reinforce accountability, human oversight and reliable data. For management, the priorities are to test operating effectiveness, assign clear ownership for regulatory change and focus technology investment on specific control needs.

Late-month developments extend these themes: FATF country-list changes require reconciliation with local obligations; OFAC updated blocking and reporting guidance, and ownership-related enforcement highlights screening gaps. FCA action reinforces the need for effective AML controls even at registered lenders. SEC examination priorities and FINTRAC publications support risk-based readiness planning. AMLA’s final draft standards and database consultation warrant preparation while remaining distinct from adopted binding requirements.

Regulatory developments

01 / United States · FinCEN

Bank of America resolution reinforces AML program and reporting effectiveness ↗

Enforcement action · Published 2026-10-13

FinCEN assessed a $1.2 billion penalty against Bank of America for willful failures in its AML program, foreign correspondent-account due diligence and suspicious-activity reporting. The findings included:

  1. Inadequately supported monitoring risk weights, investigation thresholds and alert suppression rules;
  2. Gaps in negotiable-instrument and credit-card monitoring, including potential trade-based money laundering and Chinese money-laundering-network activity;
  3. Ineffective testing and inadequate responses to evidence of missed suspicious activity;
  4. Investigative workload and capacity constraints that influenced monitoring decisions;
  5. Customer reviews and risk profiles that omitted material activity or failed to translate identified concerns into effective controls; and
  6. Insufficient understanding of the purpose, expected activity and risks of correspondent accounts for foreign branches and affiliates.

These weaknesses contributed to more than $5 billion in suspicious activity being unreported or reported late. Banks with complex monitoring systems, high-risk customers and foreign correspondent accounts should assess comparable weaknesses. FinCEN credits the OCC’s coordinated $750 million penalty against its $1.2 billion assessment.

Why it matters:

Confidence in a compliance program must be supported by evidence that it manages actual risks. Internally developed systems require independent challenge strong enough to change decisions when testing exposes weaknesses. Workload pressures, valuable customer relationships and internal affiliation must not substitute for risk-based analysis. Reviews, ratings and validations provide limited assurance unless their findings lead to appropriate diligence, monitoring, resourcing and verified remediation.

Consider:

Certainly a comparison of the findings with your monitoring, correspondent due diligence and SAR processes is warranted along with identifying accountable owners. Where issues are identified ensure remediation is imlemented effectively and there is evidence that remediation works. If issues are found, the question of whether your program is effective must be answered.

Read the primary source ↗

02 / United States · OCC

OCC findings connect monitoring failures to staffing, audit and incomplete remediation ↗

Enforcement action · Published 2026-10-13

The OCC identified systemic weaknesses across Bank of America’s BSA/AML program, resulting in a $750 million penalty. Major deficiencies included:

  • Ineffective transaction monitoring: Gaps in detection models, risk scoring and investigation thresholds left substantial activity inadequately monitored, including potential trade-based money laundering.
  • Failed escalation and SAR reporting: Potentially suspicious activity did not consistently reach investigators, producing missed, late, inaccurate and incomplete SARs.
  • Insufficient investigative capacity: Staffing, expertise and training were inadequate; the investigation backlog approached 200,000 cases in 2024.
  • Weak independent testing: Corporate Audit failed to identify significant deficiencies and adequately assess critical controls.
  • Inadequate correspondent due diligence: Simplified reviews of foreign branches and affiliates failed to capture required information and differing risks.
  • Inaccurate wire-transfer information: Approximately 33,300 outgoing wires totaling $1 billion contained inaccurate sender information.
  • Poor management response: Known weaknesses persisted despite the December 2024 order; management insufficiently prioritized remediation and minimized deficiencies.

The central issue was failure to convert known problems into effective, sustained remediation, allowing weaknesses in monitoring, investigation and reporting to continue.

Why it matters:

Known deficiencies become more serious when management acknowledges them without delivering effective, sustained remediation. Completing reviews or introducing revised processes does not establish that risk is controlled. Institutions need independent testing of underlying assumptions, sufficient investigative capacity, reliable data and clear accountability for acting on adverse findings. Commercial interests and operating costs must not override evidence of unresolved exposure; remediation should be closed only when its effectiveness has been demonstrated.

Consider:

Review overdue escalation and remediation, staff capability and audit coverage. Use operating evidence rather than action-plan completion alone to demonstrate improvement.

Read the primary source ↗

03 / United States · FinCEN

A7 Network action combines a proposed special measure with an alert ↗

Proposal and financial intelligence alert · Published 2026-10-01

FinCEN announced a proposed rule concerning fund transmittals involving A7 Network sub-agents and an alert on associated suspicious activity. Treasury also announced an OFAC designation. The proposal and the separate sanctions action should not be treated as the same legal instrument.

Why it matters:

Banks and payment providers need to distinguish proposed restrictions from already operative sanctions while evaluating indirect exposure through payment chains.

Consider:

Review the alert and network exposure, route relevant intelligence to investigators, and track the proposal separately from binding sanctions requirements.

Read the primary source ↗

04 / United States · FinCEN

Two proposed digital-asset rules withdrawn ↗

Withdrawal of proposed rules · Published 2026-10-05

FinCEN withdrew proposals concerning certain convertible-virtual-currency transactions involving unhosted wallets and a special measure concerning virtual-currency mixing. The release does not announce a general exemption from existing AML duties.

Why it matters:

The withdrawals spare affected institutions additional reporting, recordkeeping and systems requirements, potentially reducing future compliance costs and friction for legitimate digital-asset customers. Institutions can reassess preparations made solely for these proposals and focus resources on material risks. Existing AML, suspicious-activity reporting and sanctions obligations remain; the withdrawals do not justify relaxing risk-based controls.

Consider:

Update the regulatory change inventory and assess affected implementation plans. Remain focused on risk and effective controls.

Read the primary source ↗

05 / United States · FinCEN

Alert addresses abuse of Iranian religious charity networks ↗

Financial intelligence alert · Published 2026-10-15

FinCEN issued an alert asking financial institutions to report potential Iranian-regime abuse of religious charity networks, including diversion of religious tithes. The source links to the alert’s indicators and reporting information.

Why it matters:

Risk assessment should consider specific transaction patterns and network exposure without treating all charitable activity as suspicious.

Consider:

Review the linked alert with investigators, assess relevant exposure and update targeted monitoring or escalation guidance where warranted.

Read the primary source ↗

06 / United States · OFAC

Pegasus settlement and ICC designation require different control responses ↗

Enforcement action, designation and general licences · Published 2026-10-09

OFAC announced a $175,015 settlement with Pegasus Worldwide Logistics over apparent blocked-property and reporting violations. The same notice separately designated the International Criminal Court and issued four related general licences.

Why it matters:

Pegasus had a policy requiring the screening of certain data elements in its possession beyond the name alone. Failure to use this information and follow establish policy led to the aggregating factors outlined in the settlement: reckless disregard, reason to know, harm and delay, and sector exposure. This is a clear example of how simply having a policy does not effectively address risk. There must be effective controls in place to ensure adherence to policy.

Consider:

Conduct a risk assessment that includes both the identification of risk and the implementation of effective controls. Assess the ICC designation and licence conditions independently of the unrelated Pegasus settlement.

Read the primary source ↗

07 / United States · OFAC

Bank of America sanctions settlement highlights list-update and alert priorities ↗

Enforcement settlement · Published 2026-10-13

OFAC announced an approximately $11.66 million settlement for 475 apparent sanctions violations. The notice describes payments involving blocked banks, poorly prioritized exact-match alerts, delayed watchlist updates and human error affecting blocked-person accounts. OFAC noted numerous aggregating factors includine: reckless control failures, harm to sanctions objectives, institutional sophistication, and prior warnings.

Why it matters:

The issues identified by OFAC in the enforcement action show that risks may have been known, e.g., the inclusion of sanctioned institutions in a payment routing directory, the controls in place to identify the use of those institutions in a payment flow were ineffective. Those controls were downstream controls to address payments already in the queue. More effective controls may have been to remove those sanctioned institutions from the routing directory, thereby preventing the use of those institutions in a payment order. Further, in another failure, a system misclassified alerts as low or medium priority when there was an exact match between a customers name and date of birth, indicating ineffective ongoing monitoring or validation of system performance. Other matters in the enforcement action point to the need to monitor the performance of third parties.

Consider:

Entities should review their sanctions compliance program with an eye toward implementing the most effective controls, which may, in some cases, be preventive controls vs. detective controls. Additionally, a timely and effective review of system performance with appropriate, timely remediation, is essential to an effecive compliance program.

Read the primary source ↗

08 / United States · OFAC

Iran and Cuba actions accompanied by targeted Russia and Iran licences ↗

Designations, general licences and FAQ changes · Published 2026-10-15

OFAC announced Iran-related and Cuba actions, Russia-related licences 128D and 130B, and Iran-related licence FF. The notice links to authorizations concerning certain Lukoil activities and wind-down transactions involving International Development Bank for Investment and Finance.

Why it matters:

A designation update may arrive with narrowly defined permissions; screening alone does not establish whether a transaction is authorized.

Consider:

Review affected relationships and the exact licence texts, conditions and reporting requirements. Record authorization decisions and monitor expiry or amendment.

Read the primary source ↗

09 / United States · OFAC

Venezuela earthquake-relief authorization amended ↗

General licence and FAQ amendment · Published 2026-10-16

OFAC issued Venezuela-related General License 60A for transactions related to earthquake relief and amended FAQ 1263.

Why it matters:

Humanitarian payment activity requires assessment against the current authorization rather than an assumption that all Venezuela-related transactions are prohibited or permitted.

Consider:

For relevant activity, read the current licence and FAQ, document eligibility and retain supporting evidence.

Read the primary source ↗

10 / United States · OFAC

PAIPA action requires attention beyond the SDN list ↗

Non-SDN menu-based sanctions and general licences · Published 2026-10-19

OFAC added entities to its Non-SDN Menu-Based Sanctions List under PAIPA and issued related General Licenses 1 and 2. Individual entries specify applicable restrictions.

Why it matters:

Financial institutions must interpret the restrictions attached to a listing; a non-SDN label is not evidence that an entry lacks blocking or transaction restrictions.

Consider:

Confirm relevant non-SDN data is ingested, map the listed restrictions to transaction controls, and review any applicable wind-down authorization.

Read the primary source ↗

11 / United States · OFAC

Shadow-fleet action and new licences require coordinated change management ↗

Designations, removals, general licences and FAQ amendments · Published 2026-10-21

OFAC announced Iranian shadow-fleet-related listings, certain delistings, Iran licences GG and HH, Russia licence 131K and amended FAQs. The licences concern specified wind-down, safety, cargo and Lukoil-related activities.

Why it matters:

Shipping, trade-finance and payment exposure can require simultaneous updates to lists, ownership analysis and licence decision rules.

Consider:

Assess affected counterparties and vessels; review the precise permissions and conditions; coordinate implementation across screening, operations and escalation teams.

Read the primary source ↗

12 / United States · Federal Reserve

American Express action addresses enterprise-wide AML implementation ↗

Enforcement action · Published 2026-10-08

The Federal Reserve identified significant weaknesses in American Express’s enterprise-wide financial-crime program, including failures to detect, investigate and report suspicious activity promptly. Its findings and required remediation cover these major areas:

  • Transaction monitoring: Weaknesses in monitoring effectiveness, including how rules and thresholds were established, tested and documented.
  • Fraud referrals and suspicious-activity reporting: Deficient referral processes and inadequate identification, evaluation and timely reporting across business lines.
  • Customer due diligence: A need for controls proportionate to customers’ money-laundering and other illicit-finance risks.
  • Third-party oversight: Weaknesses in assessing and managing risks involving network partners, ATM partners and compliance-support providers.
  • Governance and escalation: Insufficient enterprise-wide implementation, management accountability, resources and escalation of material issues.
  • Sanctions compliance at AMEX Travel Related Services (TRS): Required improvements to OFAC risk assessment, screening procedures and ongoing, role-specific training.

The order explicitly identifies transaction monitoring, fraud referrals, third-party risk assessment and financial-crime risk management as deficiencies; its corrective requirements provide further detail on the areas needing improvement.

Why it matters:

An enterprise-wide framework must translate into effective controls across subsidiaries, business lines and partners, supported by timely escalation and accountable oversight. Group oversight needs evidence that subsidiary operations implement the enterprise programme effectively.

Consider:

A bank holding company's effective enterprise-wide risk management framework must included not only mechanisms for upward reporting from subsidiaries but a means to evaluate performance and direct remediation of identified issues. The Board of Directors must sssess reporting to group management, subsidiary accountability, escalation of monitoring weaknesses; and timely remediation and validation of identified issues.

Read the primary source ↗

13 / United States · SEC

New examination handbook provides process guidance ↗

Cross-cutting examination process guidance · Published 2026-10-01

The SEC Division of Examinations published a handbook explaining examination stages, engagement and preparation. This is broader compliance-process material, not a new AML or sanctions rule.

Why it matters:

For SEC-regulated firms, an orderly evidence and response process can support examinations involving applicable AML and sanctions controls.

Consider:

Review the handbook with examination coordinators and align document ownership, response quality and issue escalation. Keep substantive legal obligations separate from process guidance.

Read the primary source ↗

14 / United States · NYDFS

SEB settlement emphasizes correspondent due diligence and monitoring backlog risk ↗

Enforcement settlement · Published 2026-10-15

NYDFS announced a $33 million settlement with SEB and its New York branch. Findings included weak high-risk customer and correspondent due diligence, deficient files, risk miscalculation and monitoring backlogs in Baltic subsidiaries.

Why it matters:

Group-level weaknesses and delayed review can expose a local branch and its control environment.

Consider:

Review high-risk files, correspondent procedures, customer-risk logic and backlog aging. Ensure group oversight identifies local consequences and validates remediation.

Read the primary source ↗

15 / United States · OFAC

Extreme Networks settlement highlights ownership-related sanctions exposure ↗

Enforcement settlement · Published 2026-10-27

Extreme Networks agreed to a $1,529,685 settlement for nine apparent violations involving exports to Russian defense manufacturer MMZA between September 2018 and March 2022. MMZA was already blocked through its sanctioned parent’s majority ownership, before its own later designation.

Underlying deficiencies

  • Acquisition diligence: Review of acquired customer contracts failed to identify MMZA’s blocked ownership, although a contract named it as end-user.
  • Conflicting end-user information: Records named DEMZ, while email addresses, delivery details and direct dealings pointed to MMZA. Compliance accepted a distributor’s revised explanation and end-user statement without resolving the discrepancies.
  • Foreign-affiliate oversight: Russian personnel concealed the actual recipient in customer records and instructed MMZA staff to register under DEMZ’s name.
  • Access controls and follow-through: Portal access was approved despite inconsistent identifiers and, in one instance, an unanswered diligence request. Available ownership-screening resources were not used to resolve the relationship before the conduct ended. Settlement agreement.

OFAC’s aggravating factors in the egregious case

  1. Reckless disregard: Insufficient diligence and failure to act on repeated warning signs identifying the true recipient.
  2. Knowledge: Extreme knew it fulfilled the orders and had reason to know MMZA was the end-user.
  3. Harm to sanctions objectives: The dealings benefited a blocked defense manufacturer and undermined efforts to restrict Russia’s military capabilities.

Disclosure and mitigation

OFAC classified the conduct as egregious but voluntarily self-disclosed. Disclosure placed the base penalty at half the statutory maximum: $1,699,650. OFAC separately credited the absence of enforcement actions during the relevant preceding five years and substantial remediation, including improved ownership and end-user checks, acquisition diligence, staffing and training. The settlement was 10% below the base penalty. OFAC enforcement release.

Why it matters:

Sanctions exposure can enter through acquired customer relationships and continue when group-wide controls fail to establish who actually receives goods or services. Name screening and an end-user statement provide limited assurance when ownership, email addresses, delivery details or affiliate conduct tell a different story. OFAC’s findings show that repeated warning signs must lead to investigation and resolution—not acceptance of a convenient explanation.

A centralized compliance function must have the authority, information and resources to challenge overseas operations and withhold approval while concerns remain unresolved. Voluntary disclosure and substantial remediation can reduce penalties, but they do not prevent conduct from being classified as egregious.

Consider:
  • Before acquisitions: Assess inherited customers, contracts, end-users and ownership, including transactions blocked under OFAC’s 50 Percent Rule. Address identified risks before continuing acquired business.
  • Resolve conflicting evidence: Compare declared end-users with ownership information, delivery locations, email domains, support activity and other records. Independently verify explanations rather than relying solely on distributor assurances or signed statements.
  • Control escalation and approval: Establish who can pause transactions or portal access, require documented resolution of red flags, and prevent commercial staff or affiliates from bypassing review.
  • Test foreign-affiliate oversight: Check whether local sales and support practices match central records and policies; train customer-facing and compliance staff to recognize concealment and escalate concerns.
  • When failures emerge: Investigate their scope and root causes, consider prompt voluntary self-disclosure with appropriate advice, implement interim safeguards and verify that remediation works.
Read the primary source ↗

16 / Canada · FINTRAC

FINTRAC emphasizes documented risk-based supervision and programme outcomes ↗

Supervisory speech · Published 2026-10-09

FINTRAC described modernization of supervision, increased analytical capability and a focus on demonstrable connections between identified risk and programme measures. The speech discusses enrolment and enforcement changes but is not itself implementing legislation.

Why it matters:

Canadian reporting entities should be able to explain how risk assessment shapes controls, reporting and changes as their business evolves.

Consider:

Map material risks to controls and evidence of results; assess data and reporting quality. Verify enacted provisions and commencement dates separately before treating discussed initiatives as current requirements.

Read the primary source ↗

17 / Canada · OSFI

AI governance statement is relevant to technology-enabled compliance ↗

Cross-cutting supervisory statement · Published 2026-10-15

OSFI endorsed FSB sound practices for responsible AI adoption, emphasizing accountability, human oversight, data governance and proportionate controls throughout the AI lifecycle. This is a cross-cutting statement, not an AML-specific rule.

Why it matters:

OSFI’s emphasis on accountability, effective human oversight and lifecycle governance aligns with good governance and the development of trustworthy, manageable AI. AI should extend human capability while people retain authority over its objectives, decisions and actions.

For AI-enabled compliance workflows, meaningful oversight requires more than an approval click. Reviewers need the time, information, expertise and authority to challenge outputs, escalate concerns and intervene effectively. Governance should define permitted uses, limits on autonomy, decisions requiring human authorization, accountable owners, and traceable actions supported by reliable data.

Institutions should be able to constrain, override or stop AI where necessary and test that these controls work as use cases and risks evolve. These are practical governance considerations, not additional requirements created by OSFI’s statement. Responsibility remains with the institution; “the AI decided” does not discharge accountability.

Consider:

Assisted Intelligence means AI that extends human capability while remaining subject to meaningful human control. People retain authority to set its objectives, limit its permissions and decide which actions require human authorization. It can operate autonomously within a defined task, but delegating execution does not mean surrendering control or accountability. Oversight must enable people to understand, challenge, constrain and stop the system effectively—not simply click “approve.”

  • Define each AI use case’s purpose, accountable owner, permitted actions and limits on autonomy, including decisions requiring explicit human authorization.
  • Ensure reviewers have the time, information, expertise and authority to challenge outputs and escalate concerns; test whether human review is meaningful rather than a rubber stamp.
  • Establish and test practical intervention, override and stop mechanisms, with clear escalation paths and traceable decisions.
  • Assess data quality, model limitations and third-party dependencies; apply controls proportionate to the consequences of error or misuse.
  • Reassess oversight throughout the AI lifecycle, including after changes in models, data, permissions or operating conditions. Require evidence that controls remain effective and retain institutional accountability for outcomes.

These are practical governance considerations, not new requirements imposed by OSFI’s statement.

Read the primary source ↗

18 / United Kingdom · FCA

FCA describes AI-enabled AML supervision and accountability expectations ↗

Supervisory speech · Published 2026-10-19

The FCA described building AI tools for planned oversight of approximately 60,000 AML firms entering its remit in 2028. The speech also emphasizes accountability and planning for failures as AI use evolves. It does not create a new AML rule.

Why it matters:

Data quality and explainable operating evidence may become increasingly important to interactions with a technology-enabled supervisor.

Consider:

Assess the quality of compliance evidence and governance for focused AI use cases; track formal supervisory-transition materials separately from this speech.

Read the primary source ↗

19 / United Kingdom · HM Treasury and OFSI

FAQ update addresses specific licences after delisting ↗

Guidance update · Published 2026-10-09

OFSI’s dated update log records the addition of FAQ 205 on what happens to specific licences when a designated person is delisted. This entry refers to the October 9 update rather than the original 2024 publication date.

Why it matters:

Delisting and licensing changes need a controlled reassessment of affected transactions and records.

Consider:

Read FAQ 205 and the applicable designation and licence documents before changing restrictions or releasing funds. Preserve the reasoning and approval record.

Read the primary source ↗

20 / European Union · AMLA

AMLA recommends targeted AML/CFT changes in MiCA review ↗

Consultation response announcement · Published 2026-10-07

AMLA announced its contribution to the MiCA review, addressing staking/lending, DeFi control, unauthorized stablecoins, certain token issuers and cross-border supervision. The underlying response is dated September 30; the publication announcement is October 7. These are recommendations, not adopted amendments.

Why it matters:

Crypto providers and product teams should track possible perimeter changes without treating consultation positions as current law.

Consider:

Map relevant product activities and legal assumptions, monitor the Commission review and distinguish prospective requirements from existing controls.

Read the primary source ↗

21 / European Union · AMLA

AMLA and OLAF formalize cooperation and information exchange ↗

Inter-agency cooperation announcement · Published 2026-10-21

AMLA and OLAF signed a working arrangement covering operational and strategic information exchange and cooperation relevant to money laundering, terrorist financing, fraud and corruption. It provides for OLAF expertise in relevant joint analyses with participating FIU consent.

Why it matters:

The development signals a more connected intelligence and supervisory environment; it does not itself impose a new reporting requirement on every firm.

Consider:

Consider whether internal fraud and AML intelligence-sharing arrangements allow relevant patterns to inform risk assessment and investigation, within applicable legal boundaries.

Read the primary source ↗

22 / International standards · FATF

October plenary updates country monitoring and prioritizes virtual-asset and fraud risks ↗

International standards and plenary decisions · Published 2026-10-30

The October 28–30 FATF plenary concluded with decisions on country monitoring, virtual assets and fraud. FATF removed Bulgaria, Côte d’Ivoire, the Democratic Republic of the Congo and Monaco from increased monitoring, updated its statements on Iran and Myanmar, accelerated virtual-asset implementation reviews, and approved a scam-compound report for subsequent publication. It adopted the US and Mexico mutual evaluation reports, scheduled for publication in December. These verified outcomes supersede the earlier meeting announcement.

Why it matters:

Institutions should base country-risk and programme changes on verified FATF outcomes rather than anticipated decisions. Country-risk settings, due diligence and fraud typologies warrant review, but FATF decisions do not automatically amend domestic sanctions or customer requirements.

Consider:

Reconcile the country-list changes with applicable local requirements and your customer and geographic exposure. Assess relevant virtual-asset and fraud risks, and track forthcoming reports without inferring unpublished evaluation ratings or findings.

Read the primary source ↗

23 / United States · FinCEN

FinCEN explains the US implications of FATF country-list changes ↗

Regulatory notice · Published 2026-10-30

FinCEN confirms four increased-monitoring removals and unchanged call-for-action jurisdictions. Iran and DPRK remain subject to countermeasures; Burma remains subject to enhanced due diligence rather than countermeasures.

Why it matters:

Existing US sanctions and correspondent-account restrictions remain relevant independently of FATF decisions.

Consider:

Review risk-based country controls, foreign correspondent due diligence and SAR escalation; avoid indiscriminate de-risking.

Read the primary source ↗

24 / United States · FinCEN

New alert and notice address cross-border MSB payments and misuse of charities ↗

Alert and notice · Published 2026-10-30

FinCEN issued two complementary publications on October 30 addressing cross-border payment and non-profit abuse risks.

Foreign-agent-directed transactions — FIN-2026-Alert009

The alert describes foreign agents instructing US money transmitters to pay overseas third parties, sometimes characterized as settlement. Limited information about recipients, commercial relationships and payment purpose can obscure beneficiaries and expose both principal MSBs and their banks to illicit finance. FinCEN identified more than $8 billion in reported suspicious payments during 2021–2025; that figure is not proof of criminal activity.

Indicators include:

  • Payments outside agent agreements or to apparently unrelated businesses.
  • Generic explanations, missing or inconsistent invoices, or reluctance to provide due-diligence evidence.
  • Payment timing, volumes or destinations inconsistent with the expected business.
  • Repeated round-dollar payments and rapid overseas transfers after funds arrive.

Principal MSBs remain responsible for effective agent oversight; contracts do not transfer away AML obligations. Banks should understand the activity underlying settlement payments. Relevant SARs should reference FIN2026FOREIGNAGENT in field 2 and the narrative. Read the alert.

Charities and non-profit organizations — FIN-2026-NTC2

The notice explains sham charities, NPO fraud and embezzlement, with case studies and indicators involving organizational legitimacy, funding and use of funds. Examples include fundraising with little apparent service delivery, imitation of established charities, unverifiable legal status and unexplained large donations followed by substantial transfers. It addresses diversion to terrorism, misuse of government funding and theft of donations.

Institutions should assess each organization individually: most US NPOs present low risk, and neither an indicator nor charitable status alone establishes suspicion. Relevant SARs should reference FIN2026NPO in field 2 and the narrative. Read the notice.

Why it matters:

Fraud, cross-border payment and non-profit risk reviews should connect customer context with transaction patterns.

Consider:

Review the linked original alert and notice when adapting monitoring and reporting procedures; apply risk-based analysis rather than treating all charities as suspect.

Read the primary source ↗

25 / United States · SEC

FY 2027 examination priorities include broker-dealer AML compliance ↗

Examination priorities · Published 2026-10-23

The SEC published its FY 2027 examination priorities, including broker-dealer anti-money laundering compliance, operational resilience and emerging technologies.

Why it matters:

The priorities provide a planning signal, rather than creating a new AML rule.

Consider:

Map applicable priorities to the compliance review plan and evidence of operating effectiveness.

Read the primary source ↗

26 / European Union · AMLA

Final draft standards cover due diligence and group-wide arrangements ↗

Final draft regulatory technical standards submitted to the Commission · Published 2026-10-01

On October 1, AMLA submitted three final draft regulatory technical standards (RTS) to the European Commission, covering EU obliged entities and relevant group arrangements:

  • Business relationships and occasional or linked transactions — AMLR Article 19(9): Clarifies customer-engagement classification and when transactions must be considered together for due diligence thresholds. The accompanying factsheet highlights ongoing access, expected repetition and duration. Transactions can be linked across customers acting together; their combined value matters. For remittance, currency exchange and crypto-asset exchange, it identifies three transactions in 12 months as an indicator of repetition and a one-month period for assessing linked transactions. These criteria supplement the AMLR definitions rather than replace them.
  • Customer due diligence — Article 28(1): Specifies information collection and verification, proportionate lower-risk measures, remote verification, electronic identification, and screening of politically exposed persons, family members and close associates.
  • Group-wide arrangements — Articles 16(4) and 17(3): Addresses governance, risk management, internal controls and secure information sharing, including legal barriers affecting branches or subsidiaries outside the EU. The third-country factsheet describes identifying restrictions on due diligence, information sharing or recordkeeping; notifying supervisors; seeking consent where legally possible; and applying additional safeguards. Examples include enhanced monitoring, independent due diligence and senior-management approval. Unmanageable risks can require restrictions or withdrawal from business.

Status: These are final drafts submitted for Commission adoption, not binding rules merely because AMLA finalized them. The release proposes application six months after entry into force following adoption and Official Journal publication, with July 10, 2029 specified for football agents and professional football clubs. Confirm the adopted text and applicable dates before setting implementation deadlines.

Why it matters:

The stated theme is a more consistent EU AML/CFT rulebook that remains proportionate and risk-based. In practice, firms should consider whether customer classification, due diligence data and group oversight work consistently across entities and jurisdictions, including where local laws obstruct group controls. Preparation can begin now, while adoption and any amendments remain under review.

Consider:
  • Map the three draft standards to onboarding, verification, PEP screening, customer records and group policies; identify data or system changes that may be needed.
  • Test whether systems identify repeat engagements and aggregate potentially linked transactions, including customers acting together, rather than assessing each payment in isolation.
  • Inventory third-country legal barriers to information sharing, due diligence and recordkeeping; assess escalation, supervisor notification and compensating-control options with legal advice.
  • Assign owners for readiness work, document dependencies and track Commission adoption, amendments and final application dates.
Read the primary source ↗

27 / United Kingdom · FCA

Restrictions on six Annex 1 lenders emphasize demonstrable AML controls ↗

Supervisory action · Published 2026-10-23

On October 23, the FCA announced restrictions on six Annex 1 lenders after identifying concerns about AML policies, controls and procedures during application assessments. Annex 1 firms register for Money Laundering Regulations supervision; this is distinct from FCA authorisation and wider regulation.

The restrictions, imposed at the firms' request, differ:

  • Kingscrown Finance Ltd: Further September restrictions limit customer payments and require an orderly loan-book wind-down.
  • MOMSB Ltd and Momentus Capital Ltd: October restrictions limit new customers, lending and customer payments, with limited exceptions, and require independent AML reviews.
  • Grosvenor Funding Ltd and Grosvenor Funding (North West) Ltd: Similar limits on new business and payments, plus independent AML reviews.
  • Abbital Ltd: Specified conditions for new customers, lending and payments, plus an independent AML review.

The FCA is also assessing information from around 900 registered Annex 1 firms. Its announcement identifies broad AML concerns, without detailing each lender's underlying control failures.

Why it matters:

The central message is demonstrable risk management: weak AML controls can constrain business activity. Registration does not replace a regulated counterparty's own due diligence, independent checks and assessment of the relationship's risks.

Consider:
  • Annex 1 lenders: Test whether AML risk assessments, policies and controls fit the actual lending business and operate effectively. Escalate gaps, assign remediation owners and validate improvements independently where appropriate.
  • Affected firms: Review the precise restrictions applicable to the business before onboarding customers, extending credit or accepting payments; translate them into operational controls and staff instructions.
  • Regulated counterparties: Confirm registration status directly, independently verify information, and assess the lender's business, restrictions and financial crime exposure before establishing or continuing the relationship.
  • Management: Retain evidence of control effectiveness and remediation, with clear escalation where weaknesses could affect continued business activity.
Read the primary source ↗

28 / Canada · FINTRAC

Annual report and audit response reinforce risk-based supervision and intelligence quality ↗

Annual report and supervisory context · Published 2026-10-26

FINTRAC's 2025–26 Annual Report is accompanied by an October 29 audit-response statement confirming that its new Supervision Framework has been finalized and implemented. It affects businesses subject to the Proceeds of Crime (Money Laundering) and Terrorist Financing Act.

The statement describes strengthened risk tools, questionnaires and sector profiles to improve risk information and understanding of sector-specific threats and vulnerabilities. FINTRAC also reports expanded supervisory activity and additional supervisory resources. It does not publish the framework's detailed assessment methodology or scoring model.

FINTRAC's October 9 supervisory speech explains the broader approach:

  • A dynamic risk picture: Combine examination findings, control effectiveness, reporting and data-quality concerns, enforcement history, voluntary disclosures and partner intelligence to assess sector and entity risks.
  • Proportionate supervision: Use guidance, compliance promotion or monitoring where risk is lower; deepen engagement as risk increases; intervene more firmly for significant or persistent non-compliance.
  • Documented decisions and results: Connect identified risks to supervisory planning, examinations, interventions and their contribution to stronger compliance.
  • Professional judgment: Consider each business's circumstances rather than applying a uniform model.

The speech also discusses planned technology, analytics and enrolment improvements. These modernization plans should be distinguished from the implemented framework and checked separately for applicable legal commencement dates.

Why it matters:

The stated theme is a documented connection from risk to action to outcomes: supervisory attention and intervention should reflect the risks identified and contribute to stronger compliance. For Canadian reporting entities, the practical implication is to demonstrate how their own risk assessment drives controls and evolves with their business. The annual report and statement describe supervisory direction; they do not themselves create new statutory duties.

Consider:
  • Risk: Refresh the assessment of money laundering, terrorist financing and sanctions-evasion exposure using current business information, sector threats, reporting quality, control testing and prior findings. Record the evidence and judgment supporting risk ratings.
  • Action: Map material risks to specific controls, monitoring and reporting measures. Direct resources and testing toward higher-risk areas, with clear ownership, deadlines and escalation for significant or recurring deficiencies.
  • Outcomes: Assess whether those measures improve detection, reporting quality and remediation effectiveness. Use testing and management information to distinguish completed tasks from sustained improvements in compliance.
  • Governance: Give management a documented view of risk, action and results; challenge gaps, verify remediation and update the program as the business and threat environment change. Retain evidence explaining why the response is proportionate to the risk.
Read the primary source ↗

29 / United States · OFAC

Blocking, rejecting and reporting FAQs amended ↗

Updated guidance · Published 2026-10-26

Why it matters:

Operational procedures must distinguish the treatment and reporting of different sanctions outcomes.

Consider:

Compare the revised FAQs with payment handling, escalation and reporting instructions; confirm requirements from the applicable rule and current guidance.

Read the primary source ↗

30 / United Kingdom · HM Treasury and OFSI

General licence addresses certain property service-charge and ground-rent payments ↗

General licence · Published 2026-10-12

OFSI issued General Licence INT/2026/10050568 concerning specified ground rent, service charges and late-payment fees for relevant properties in England or Wales. The licence applies under the listed UK autonomous sanctions regulations.

Why it matters:

Banks and property-related payment teams need to distinguish the licence’s limited permissions from a broad authorization for designated-person transactions.

Consider:

Review the full licence, scope and conditions before reliance; retain evidence that a payment qualifies and route exceptions to the sanctions team.

Read the primary source ↗

31 / European Union · Council of the EU sanctions

EU adds 1,569 Russia-related military-industrial listings ↗

Restrictive measures announcement · Published 2026-10-12

The Council announced listings of 826 companies and 743 individuals in Russia’s military-industrial complex. Its release describes asset freezes and prohibitions on making funds or economic resources available, and links to the legal acts. The Commission also reported the same package.

Why it matters:

The scale of the change places emphasis on timely list updates, ownership analysis and affected-relationship review.

Consider:

Confirm list ingestion, assess relevant exposure and review the legal acts before transaction decisions.

Read the primary source ↗

32 / United States · OFAC

Iran General License FF-1 replaces the prior bank wind-down authorization ↗

Amended general licence · Published 2026-10-29 · Key date: Authorization runs through 12:01 a.m. EST on December 1, 2026; consult the original licence.

FF-1 replaces the October 15 licence and authorizes specified wind-down transactions involving International Development Bank for Investment and Finance and its covered subsidiaries.

Why it matters:

The permission is limited; payments to blocked persons must enter blocked accounts and other prohibitions remain.

Consider:

Identify affected transactions and document compliance with every condition in the licence.

Read the primary source ↗

33 / United Kingdom · HM Treasury and OFSI

New legal-services general licence replaces the expiring authorization ↗

General licence publication · Published 2026-10-26

OFSI published Legal Services General Licence INT/2026/11112108 to succeed the licence expiring on October 28. It permits qualifying payments to UK legal firms or counsel under specified sanctions regimes, subject to its conditions.

Why it matters:

A replacement licence requires a fresh check of scope and conditions before payments are released.

Consider:

Read the operative licence and annexes; verify the relevant regime, payment eligibility and reporting conditions.

Read the primary source ↗

34 / European Union · AMLA

Consultation addresses a central EU AML/CFT supervisory database ↗

Consultation on draft regulatory technical standards · Published 2026-10-07 · Key date: Public hearing: November 3, 2026, 14:00–16:00 CET.

AMLA announced consultation on draft standards for a central supervisory database, including information scope, reporting and material breach thresholds. The design primarily uses information supervisors already hold or collect.

Why it matters:

Consistent risk and breach information can support more coordinated supervision; the announcement does not create a new direct reporting obligation for firms.

Consider:

Review data quality and consistency in existing supervisory submissions; distinguish the consultation from adopted requirements.

Read the primary source ↗
Source coverage and review limitations

Research scope and access limitations are recorded separately from the developments above. An access gap is not a finding that no change occurred.

FinCEN · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

OFAC · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

Federal Reserve · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

OCC · Developments included

Annual news register and AML bulletin listing checked; existing Bank of America finding retained.

Access / verification:

American Express OCC action duplicates the existing Federal Reserve group development and is retained as a coverage source. October 21 GENIUS rule expressly leaves BSA/AML and OFAC provisions to separate rulemaking.

FDIC · Access incomplete

Earlier review retained; full-month direct-source check incomplete.

Access / verification:

The FDIC news page returned HTTP 403 during this follow-up; absence of additional developments has not been established.

SEC · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

FINRA · Partial review

Topic page and targeted October publication search checked.

Access / verification:

No additional material October item verified in the retrieved material; publication and disciplinary records were not exhaustively reviewed.

NYDFS · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

FINTRAC · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

Department of Finance · Partial review

Department news landing page and indexed October news checked.

Access / verification:

The live news listing did not expose all dated entries; late-October coverage is incomplete.

Global Affairs Canada sanctions · Partial review

Sanctions landing and announcement pages checked.

Access / verification:

The dynamic announcement page rendered filter controls without results; no conclusion that October had no announcements is drawn.

OSFI · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

FCA · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

HM Treasury and OFSI · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

Bank of England and PRA · Partial review

Topic page and targeted October publication search checked.

Access / verification:

No additional material October item verified in the retrieved material; publication and disciplinary records were not exhaustively reviewed.

NCA UKFIU · Partial review

Topic page and targeted October publication search checked.

Access / verification:

No additional material October item verified in the retrieved material; publication and disciplinary records were not exhaustively reviewed.

AMLA · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

European Commission · Covered in a related source section

October source listing and relevant publications checked; earlier reviewed items retained.

Council of the EU sanctions · Developments included

October source listing and relevant publications checked; earlier reviewed items retained.

EUR-Lex · Access incomplete

Operative legal-text access remains incomplete.

Access / verification:

EUR-Lex returned a JavaScript/robot-verification page. Council announcements are not a substitute for checking operative instruments and annexes.

EBA related and legacy guidance · Covered in a related source section

EBA AML/CFT transition notice checked; AMLA developments covered separately.

Access / verification:

Direct EBA topic page returned HTTP 403; official indexed content confirms the AMLA transition. Related prudential updates were not exhaustively reviewed.

FATF · Developments included

October 30 plenary outcomes reviewed; the earlier meeting announcement has been consolidated into the outcomes development.

Wolfsberg Group · No material developments identified

Live news index recovered; no October-dated release appears in the displayed current list.

Access / verification:

Resources index timed out; news index and homepage recovered. Earlier 2026 guidance remains background, not an October release.

Coverage reflects sources reviewed for this edition. This digest does not replace daily sanctions-list screening or institution-specific analysis.

What does a development mean for your program?

Discuss the effect on policies, controls, data, technology or implementation priorities with Steve.

Contact Steve ↗