Why FinCEN’s Delay of the Investment Adviser AML Rule Is a Planning Window, Not a Reprieve

The FinCEN investment adviser AML rule delay moves the rule’s effective date from 1 January 2026 to 1 January 2028. FinCEN’s Investment Adviser AML Rule was finalised in 2024 and was due to bring registered investment advisers and exempt reporting advisers into the Bank Secrecy Act framework from 1 January 2026.

In July 2025, FinCEN announced it would postpone that effective date. It issued an exemptive relief order in August 2025 and then formalised the delay through a final rule on 31 December 2025, moving the effective date to 1 January 2028 while it revisits the rule’s scope.

For firms that also run banking or broker-dealer operations alongside an advisory business, the temptation is to treat the extra two years as two years of inaction. That would be a mistake. It is better read as a limited planning window before adviser monitoring becomes mandatory.

The Investment Adviser AML Rule was finalised in 2024, postponed in 2025 and is now due to take effect on 1 January 2028. The time between now and then is the planning window.

What actually changed, and what did not

The substance of the rule has not gone away. Once effective, covered advisers will still need a written, risk-based AML/CFT programme, independent testing, a designated compliance officer, ongoing training, customer due diligence and suspicious activity reporting to FinCEN, bringing RIAs and ERAs broadly in line with banks and broker-dealers. What has changed is timing and scope. FinCEN has said it intends to revisit both the AML obligations themselves and the related customer identification programme requirements that were jointly proposed with the SEC, based on industry feedback about how the rule fits adviser business models.

That distinction matters for planning. This is not a rollback signal. Regulators have been explicit that the delay does not weaken the underlying expectation, only the timeline for meeting it.

The timeline so far:

Why a delay is not a deprioritisation

Treating a compliance delay as licence to deprioritise a build is a common but costly reading. The firms best placed when the rule takes effect will be the ones that used the intervening years to design a programme deliberately, rather than the ones that wait until the deadline is visible on the horizon and then build under time pressure. FinCEN’s own framing, that the postponement is meant to reduce the industry’s transitional compliance costs, only makes sense if firms actually use the time to prepare properly rather than simply exhale.

The strategic risk of waiting until the deadline is close

For a diversified financial group, the advisory business rarely sits in isolation. It typically shares clients, onboarding data, and sometimes technology infrastructure with a banking or broker-dealer affiliate that is already a BSA-covered institution with its own transaction monitoring programme. Building an adviser-specific monitoring capability from scratch in 2027, disconnected from what the rest of the group already runs, risks recreating exactly the kind of fragmented, inconsistent monitoring estate that regulators are increasingly scrutinising in enforcement actions elsewhere in the industry.

It also creates a governance question of its own: if the advisory arm’s programme is bolted on late and does not share risk-scoring logic or case-management standards with the rest of the group, a group-wide risk committee has little basis for concluding the organisation’s monitoring is coherent, only that each entity separately has something in place.

Building one architecture instead of a second, separate one

The more defensible path is to treat the adviser build as an extension of existing enterprise monitoring capability rather than a new, standalone system. That means using the runway to map how adviser client and transaction data would flow into the group’s existing risk-scoring and case-management approach, so that when the rule takes effect the adviser business is absorbed into a programme that already works, instead of standing up its own.

How Nexiant supports coordinated multi-entity monitoring

This is where a specialist transaction-monitoring capability that can extend across entity types, rather than one built for a single business line, earns its place. FraudShield’s focus on configurable rule logic and case-management workflows is designed to support exactly this kind of extension: bringing a newly scoped entity into a coordinated monitoring approach rather than running a parallel, adviser-only system.

What to do with the extra runway

Firms with adviser affiliates have a genuine, if time-limited, opportunity here. Mapping data flows, aligning risk-scoring logic, and testing how an adviser business would sit inside existing monitoring architecture are all things that can be done now, well ahead of 2028, at a pace the business controls rather than a pace a deadline dictates. Waiting for FinCEN to finish revisiting the rule before starting that work trades a planning window for a compressed one.

Frequently Asked Questions

This article was accurate at the time of publication in October 2026 and is intended for general informational purposes only. It does not constitute legal, regulatory or compliance advice. Organisations should seek qualified professional guidance in relation to their specific obligations.