OFAC Part 505 needs a program-specific citation map

Treat Part 505 as a procedural consolidation

The direct answer is to add Part 505 to the sanctions citation model without recasting it as a new program prohibition. The final rule was published at 91 FR 60821 and took effect September 25, 2026. Its preamble says OFAC is reproducing enforcement procedures and penalty information previously located in individual parts of 31 CFR chapter V. It also says the initial promulgation covers IEEPA and United Nations Participation Act penalty information and makes no substantive changes to those penalty provisions.

That boundary matters for policy, case, and system updates. A September 25 effective date supports using Part 505 for the procedures it now contains; it does not establish that a transaction became newly prohibited, that a license changed, or that every sanctions statute now uses Part 505. Keep the final-rule publication, effective date, covered statutory basis, procedural section, and prior citation in the migration record so reviewers can distinguish a citation move from a substantive sanctions change.

Pair the procedure with the governing program authority

Section 505.101 says Part 505 sets standard sanctions penalty regulations for transactions regulated under other chapter V parts and programs administered by OFAC. The same section states that substantive prohibitions, definitions, interpretations, and licenses particular to each program are not in Part 505. Those authorities remain in the program-specific part, on OFAC's website, or, for a program not yet implemented in regulations, in the applicable executive order or other authority.

A usable citation map should therefore keep at least two linked records: the Part 505 procedure or penalty provision and the authority that governs the underlying program and transaction. Include the sanctions program, statutory basis, program-part section or other authority, applicable definition and license, Part 505 section, Part 501 appendix or reporting reference where relevant, effective dates, and source version. A Part 505 citation alone cannot answer whether a transaction is prohibited or licensed.

Preserve definition and penalty exceptions

Section 505.201 warns that terms may differ across OFAC-administered sanctions regulations and says the appropriate definition is the one in the part associated with the sanctions program. The preamble also identifies penalties under additional statutes that remain in other cited locations. A normalization project should not overwrite program-specific meanings with one global vocabulary or assume that every penalty path moved into Part 505.

Test the map with cases that expose those boundaries: two programs using the same term differently, an IEEPA matter, a UNPA matter, a statute whose penalties remain elsewhere, a license that changes transaction treatment, and a program implemented through an executive order before regulations exist. Each case should resolve both the operative program authority and the procedural citation. Unresolved or conflicting mappings should stop automated citation replacement and route to qualified review.

Version citations through the cross-reference migration

The final rule says OFAC will update chapter V parts after publication to replace existing penalty information with cross-references to the new regulations. That describes a migration that may leave historical records, archived procedures, vendor logic, and current CFR text on different citation versions. Preserve the citation that governed or appeared when a decision was made, then add the current cross-reference and the date it was verified. Do not silently rewrite a historical case file as though the newer citation appeared in the original record.

This analysis uses the official Federal Register PDF reviewed September 27, 2026. We did not test a transaction, sanctions program, license, disclosure, pre-penalty notice, settlement, finding, penalty calculation, screening system, or legal conclusion. Confirm the current CFR text, relevant program authority, OFAC materials, and effective dates for a specific matter. Qualified sanctions counsel should resolve applicability, definitions, licensing, disclosure, enforcement, and transition questions.

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.