OFAC's 2026 blocked-property report needs June 30 asset state

Freeze the report population at the June 30 cut-off

The direct answer is to reconstruct the assets actually blocked and held on June 30, 2026, then reconcile that population to the reporting entity and the current filing form. OFAC's guidance names that historical date and a September 30 filing deadline. The September 2 recent-actions page repeats the reminder but is not the event date for every underlying block. A live sanctions-list query or today's account balance is a different observation and cannot silently replace the June 30 record.

Keep the holding entity, legal owner, sanctions target, property type, location, account or asset reference, original blocking event, authority or program tag, value as of June 30, valuation method, and subsequent status in separate fields. A later release, delisting, transfer, change in market value, or corrected ownership record may affect what the filer must investigate; it must not overwrite what was held and known at the reporting cut-off. OFAC explicitly excludes property unblocked before July 1 and certain restricted or immobilized assets unless otherwise blocked. Complex holdings need counsel and the exact regulation, not a blanket inclusion rule inferred from this summary.

Make Part B rows trace to discrete blocks

OFAC tells filers to list each discrete block on its own Part B row, including disaggregated assets inside an omnibus account. The reporting design therefore needs a stable asset key linking the ledger position, block instruction, account or custody record, sanctions target, authority, valuation, and earlier report. A portfolio total can reconcile a report but cannot substitute for the underlying row population. Duplicated positions, partial releases, and multiple owners should remain visible as exceptions until a responsible person determines the correct representation.

The same guidance distinguishes the Blocked/Rejected Report ID from the ORS submission ID, the annual-report ID, and internal tracking numbers. A migration or spreadsheet export should retain the original blocked/rejected report identifier and the provenance of any missing value. If the original block was not filed through ORS, the guidance describes an N/A treatment. Teams should test one legacy block, one omnibus account, one corrected prior report, and one property item valued in a foreign currency before trusting a bulk export.

Reconcile guidance, regulation, and filing receipt

The six-page OFAC document is filing guidance, not a new binding rule. It points to 31 CFR section 501.603 and tells filers to use the current TD-F 90-22.50 spreadsheet and OFAC Reporting System. It identifies common reasons submissions are returned, including wrong report identifiers, missing sanctions-target interests, inconsistent Part B fields, and formatting changes. A dashboard state of 'uploaded' is not the same as a complete filing accepted by OFAC; preserve submission, return, amendment, resubmission, and final receipt states separately.

A useful review is a two-way reconciliation: every June 30 blocked asset in the custody or operating ledger has a disposition in the ARBP population, and every Part B line traces back to a source block and authority. Record who resolved exclusions, valuation differences, duplicate identities, program-tag questions, and missing initial report IDs. The trade-control function should not turn a reporting workflow into a transaction-release permission or assume a filing receipt validates a prior blocking decision.

Limits and next decision

This analysis uses OFAC's 2026 guidance and September 2 reminder reviewed September 22, 2026. We did not inspect a filer, blocked account, sanctions target, ORS record, spreadsheet, submission, returned report, or legal interpretation. The guidance itself says it does not modify 31 CFR part 501. The article does not decide who is a holder, what a particular asset is worth, whether a specific property is blocked, or whether any filing is complete.

Before September 30, an accountable reporting owner should confirm the applicable rule and current form, complete the June 30 asset-level reconciliation, resolve open exceptions with qualified advisers, and retain the submitted package and OFAC response. After filing, watch for returned-report instructions and preserve amended versions without creating a false second initial report. The durable control is a traceable historical asset population, not a green indicator on a current sanctions screen.

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.