How the New FinCEN Rule Affects Financial Firms

FinCEN has issued an order prohibiting any covered financial institution from processing a transmittal of funds involving PM2BTC, a financial institution operating outside the United States that the Treasury Department has determined to be of primary money laundering concern in connection with Russian illicit finance. Published as 89 FR 82499 and effective October 11, 2024, the order was issued pursuant to the Combating Russian Money Laundering Act, as amended by the National Defense Authorization Act for Fiscal Year 2022. For financial firms, this is not a future compliance date to plan around — the prohibition is already in force, and the operational question is how quickly a covered institution can confirm it is not processing a transmittal the order already bars.

This guide explains, in plain English, what the order does, who counts as a covered financial institution, what a firm should do given that the effective date has already passed, and how a firm keeps a designation-driven prohibition like this one from slipping through its monitoring over time. It leads with the obligation and the date, not with any product. The goal is to give compliance and BSA/AML teams a clear, sourced picture they can act on without re-reading the full Federal Register entry themselves.

Key Takeaways

• FinCEN issued an order, published at 89 FR 82499 and effective October 11, 2024, that prohibits any covered financial institution from processing a transmittal of funds involving PM2BTC.

• PM2BTC is a financial institution operating outside the United States that has been determined to be of primary money laundering concern in connection with Russian illicit finance, per 89 FR 82499.

• The order was issued pursuant to the Combating Russian Money Laundering Act, as amended by the National Defense Authorization Act for Fiscal Year 2022.

• The prohibition sits within FinCEN's Bank Secrecy Act framework at 31 CFR Part 1010; no separate RIN is assigned to this order.

• This post is informational only and is not legal or tax advice; consult a qualified attorney or compliance professional before acting on any specific situation.

What this rule actually does

Read the order narrowly: it does not add PM2BTC to a general watchlist and leave firms to interpret their own exposure, and it does not phase in over a multi-year runway the way many rulemakings do. 89 FR 82499 prohibits any covered financial institution from processing a transmittal of funds involving PM2BTC, effective October 11, 2024. FinCEN issued the order pursuant to the Combating Russian Money Laundering Act, as amended by the National Defense Authorization Act for Fiscal Year 2022 — authority Treasury has used before to act against foreign financial institutions tied to Russian illicit finance.

The table below summarizes the order as published. It adds no date, figure, or requirement beyond what the rule itself states.

Because the published date and the effective date are the same — October 11, 2024 — there was no advance comment period built into this order's timeline. That is typical of a special measure of this kind: the order in 89 FR 82499 took legal force on the day it was published, which means any covered institution reading this now is already inside the compliance window, not ahead of it.

Who is affected

The order reaches "any covered financial institution," which is FinCEN's term of art under the Bank Secrecy Act regulations at 31 CFR Part 1010. Firms should not assume that phrase is limited to traditional banks. FinCEN uses the same covered-financial-institution framework across its special measures, recordkeeping, and suspicious activity reporting rules, and it is drafted to reach a wide range of regulated financial services entities. A firm's first task is to confirm, with its own BSA/AML counsel, whether it falls within that definition — and if it does, to treat the PM2BTC prohibition as already binding rather than pending.

Institutions that maintain correspondent accounts or process cross-border transmittals on behalf of other financial institutions carry the added burden of confirming that no downstream relationship creates indirect exposure to PM2BTC. The order does not describe a phased rollout for that work; because the effective date under 89 FR 82499 has already passed, the practical posture for any covered institution is to treat this as a standing screening requirement rather than a project with a future start date.

What financial firms should do before the date

Because 89 FR 82499 is already effective, "before the date" in this case means before the next transaction, not before some point on a future calendar. A financial firm should first confirm whether it meets the definition of a covered financial institution under 31 CFR Part 1010; if it does, the second step is to update transaction-monitoring and sanctions-screening logic so that PM2BTC is a recognized name across payment, correspondent-banking, and funds-transmittal channels. Third, the firm should review its existing correspondent relationships for any indirect path a transmittal involving PM2BTC could take through a downstream respondent bank. Fourth, it should document the date it implemented the screening change, since a firm's ability to show it acted promptly after the order in 89 FR 82499 took effect is itself part of a sound compliance record.

Throughout, the operative framing is that the rule requires covered financial institutions to refrain from processing transmittals of funds involving PM2BTC, per 89 FR 82499 — it does not instruct any individual firm on how to redesign its screening program, and it is not a substitute for the firm's own legal and compliance judgment about its specific systems and relationships.

Operationalizing the screening at volume

The hard part of a designation-driven prohibition like this one is rarely the first read of the order — it is making sure a single, oddly-named entity like PM2BTC stays correctly flagged across every screening list, every correspondent relationship, and every new payment channel a firm adds after the fact. That is a monitoring-and-consistency problem, and it is where US Tech Automations fits. Configured against the Federal Register feed, the platform can watch for new documents tied to this order's citation, 89 FR 82499, and flag any related correction or follow-on FinCEN action so a name like PM2BTC does not fall out of a screening list simply because nobody re-read the original notice. You can see how that kind of monitoring and escalation workflow is structured on the US Tech Automations agentic workflows page.

The second half of the work is keeping the screening logic itself current as new payment products, correspondent relationships, and onboarding flows are added. A configured pipeline can route a flagged name change or FinCEN update into a firm's existing case-management or ticketing system, with a short summary and a named reviewer, so an update to a list like this one does not sit in a shared inbox waiting to be manually keyed into a screening engine. The goal is not to replace the firm's compliance judgment; it is to make sure a designation already in force under 89 FR 82499 stays enforced as the firm's own systems change around it.

How this fits the broader regulatory window

This order does not exist in isolation. It is one of 259 U.S. federal rules in our point-in-time index of rules published July 1, 2024 – July 5, 2026 by 10 agencies governing our covered industries. A single special measure like this one is straightforward to read on its own; the harder problem is that financial firms are tracking many FinCEN and Treasury actions at once, several with their own effective dates, their own covered-institution language, and their own downstream screening implications. A firm that only revisits the rules it already knows about will eventually miss a designation that took effect quietly, the way this one did, on its publication date rather than after a comment period.

The takeaway for compliance leadership is straightforward: the prohibition on transmittals involving PM2BTC took effect October 11, 2024, per 89 FR 82499, and it did not come with a runway. Building a durable way to watch the Federal Register and route what matters to a named reviewer — before a transaction happens, not after — is what a rule like this one is really asking of covered institutions. Firms evaluating how that kind of ongoing monitoring fits their own compliance stack can see how the US Tech Automations pricing page breaks down the platform.

Frequently asked questions

What does this FinCEN order actually prohibit?

It prohibits any covered financial institution from processing a transmittal of funds involving PM2BTC, a financial institution operating outside the United States that Treasury has determined to be of primary money laundering concern in connection with Russian illicit finance. The order is published at 89 FR 82499.

When did the prohibition take effect?

The order is effective October 11, 2024, the same date it was published in the Federal Register at 89 FR 82499. There was no separate future compliance date built into the order.

Which financial institutions need to comply with this order?

Any "covered financial institution" as defined under FinCEN's Bank Secrecy Act regulations at 31 CFR Part 1010. That term reaches a broad range of regulated financial services entities, not only traditional banks, so firms should confirm their own status with qualified counsel rather than assume the order does not apply.

What CFR part does this rule fall under?

The order sits within the Bank Secrecy Act regulations at 31 CFR Part 1010, the same part FinCEN uses for its broader special measures and recordkeeping authority. No RIN is assigned to this particular order.

Under what legal authority did FinCEN issue this order?

FinCEN issued the order pursuant to the Combating Russian Money Laundering Act, as amended by the National Defense Authorization Act for Fiscal Year 2022, as stated in 89 FR 82499. That authority allows Treasury to act against foreign financial institutions found to be of primary money laundering concern in connection with Russian illicit finance.

What should a firm do if it is unsure whether a transaction involves PM2BTC?

Treat any uncertain match as a screening escalation rather than a routine clearance, and confirm the analysis with qualified BSA/AML counsel. The order's own text at 89 FR 82499 is the controlling document, and a firm's screening and escalation procedures should be built to catch a name like PM2BTC even when it appears as one counterparty among many in a longer transaction chain.

Related guidance

For related financial-services compliance coverage, see our notes on the FinCEN special measure regarding Al-Huda Bank, the beneficial ownership information reporting requirement revision, and the Equal Credit Opportunity Act compliance guide.

Disclaimer

This article is provided for informational purposes only and does not constitute legal or tax advice. Reading it does not create an attorney-client relationship. Regulatory requirements are fact-specific, and you should consult a qualified attorney or tax advisor before acting on any matter discussed here. Every date, citation, RIN, CFR reference, and figure in this post is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Last reviewed: July 5, 2026.

Source: U.S. Federal Register (89 FR 82499); current text via eCFR, 31 CFR Part 1010.