Treasury's August 28 actions need separate control clocks
Treasury announced two different August 28 actions: OFAC added Reza Mohammad Taeedi and Kameng Trading Limited to the SDN List, while FinCEN proposed a special measure concerning Banque Misr UAE. The designations create current sanctions consequences; the FinCEN measure remains a proposal with its own comment and rulemaking clock.
Editorial figure by Trade Controls Brief. Source context: U.S. Treasury: Iran's Access to UAE Banks Targeted Under Operation Economic Outcast.
Separate the operative designation from the proposal
The direct answer is that a control program needs two records and two clocks. OFAC's recent-action page identifies Taeedi and Kameng Trading Limited as newly added SDN List entries. Those list changes should enter the organization's current sanctions-content, screening, alert-review, hold, escalation, reporting, and recordkeeping process according to applicable law and policy.
FinCEN's Banque Misr UAE action is different. The official notice identifies it as an NPRM, and Treasury describes a proposed prohibition and special due-diligence measure. A proposal can justify exposure analysis, scenario planning, ownership, and a comment decision. It should not be encoded as though the proposed special measure were already an effective final prohibition.
Screen the designated parties with dated content
A sanctions update record should retain the official list event, published identifiers, source and retrieval time, content-provider version, system ingestion time, matching fields, affected customers and counterparties, payment and trade records, ownership or control analysis where applicable, false-positive decisions, holds, escalations, reports, and later list changes. Reviewers should be able to explain which list version governed each decision.
The Treasury narrative provides context, but it is not a substitute for the authoritative list record, applicable sanctions regulations, or transaction-specific legal analysis. Similar names, incomplete identifiers, transliteration, indirect relationships, and historical activity require controlled review. A match score does not establish identity, and the absence of a direct name match does not resolve every sanctions obligation.
Model the Banque Misr UAE proposal within its stated scope
The proposal record should identify Banque Misr UAE precisely, preserve the NPRM text and Federal Register publication milestone, state the proposed correspondent-account restrictions and due-diligence concept without rewriting them as current requirements, and distinguish the named UAE operation from Banque Misr operations elsewhere. Entity resolution, branch and booking-location data, payment-message fields, correspondent relationships, and indirect transaction paths need separate evidence.
Owners can inventory potential exposure, identify systems and foreign-correspondent relationships that could be affected, document interpretive questions, decide whether to submit comments, and prepare a conditional implementation plan. Each task should state whether it responds to today's controls, the proposal, or a future final rule. If FinCEN changes, withdraws, or finalizes the measure, the later action should supersede the scenario through a dated transition rather than silently changing the earlier record.
Test the two clocks independently
A representative evaluation should ingest the OFAC additions, rescreen active and historical relationships under a documented lookback, place one potential match under review, map a payment path involving Banque Misr UAE, and model the NPRM without activating a final-rule control. Reviewers should reproduce the list version, match evidence, decision authority, current hold or release, proposal scope, comment deadline basis, planned dependencies, and trigger required before any proposed control becomes operative.
Treasury, OFAC, and FinCEN's official records support the described August 28 designation and proposal statuses. They do not establish that a particular customer, transaction, ownership chain, correspondent path, jurisdiction, reporting duty, or control response is in or out of scope. Organizations retain responsibility for sanctions, anti-money-laundering, correspondent-banking, payments, trade, reporting, compliance, and legal judgment.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Trade Controls Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.