The emergency unwind is narrower than "Hong Kong special status" suggests. Executive Order 13936, The President's Executive Order on Hong Kong Normalization, 85 FR 43413, July 17, 2020 put several legal moves in one document. It declared an emergency, suspended differential treatment under the U.S.-Hong Kong Policy Act for specified laws, directed agencies to change policy, and authorized property blocking under IEEPA. Those moves arrived together in 2020. They do not have to leave together in 2026.
The Presidential Notice Continuing the National Emergency With Respect to Hong Kong, 90 FR 31129, July 11, 2025 extended the emergency for one year beyond July 14, 2025. With no new continuation, the anniversary rule in United States Code 50 USC 1622 on termination of national emergencies ended it on July 14, 2026. Neither source supplies an intraday cutoff or time zone. A transaction file should therefore record the official date without inventing an hour.
The immediate error would be to change a company-wide Hong Kong setting from restricted to restored. A sanctions name, a blocked asset, an export, and an imported article can now have different answers. This is distinct from IEEPA's surviving transaction-control authority when a valid emergency remains in place. The issue here is how to unwind one expired emergency from a control stack built on several other authorities.
A Non-SDN Move Can Still Mean Blocked
The list label creates the operational risk in OFAC's action. People still sanctioned under the HKAA moved from the SDN List to the Non-SDN Menu-Based Sanctions List. A team that treats every removal from the SDN List as relief can clear a party that remains fully blocked. OFAC's July 17 Hong Kong-related entries expressly carry property-blocking and transaction-prohibition language.
Each NS-MBS entry carries its own applied measure. Menu-based statutes allow different measures for different targets. For these Hong Kong entries, Public Law 116-149 Hong Kong Autonomy Act supplies an independent statutory basis for blocking. Expiry of the EO 13936 emergency did not repeal that law. Screeners must capture the blocking measure shown on the entry rather than infer treatment from the list name.
A vendor can ingest the right names and still produce a false negative if it treats NS-MBS as a low-severity watch list. The sanctions team should test known HKAA names against the production rules, confirm that OFAC's 50 Percent Rule for blocked entities still runs for the HKAA blocking entries, and inspect the disposition applied by downstream payment and onboarding systems. A successful file update says nothing about whether the downstream rule blocked the match.
A person whose property had been blocked solely under IEEPA was removed from the SDN List. That list deletion does not establish that the person has no match under another sanctions program, nor does it resolve every hold, rejected transaction, license question, or separate non-blocking measure. The record should show the old authority, the current authority, the list event, and the decision taken because of that event.
A Blocked Asset Keeps Its Own History
For HKAA targets who remain subject to Section 6 blocking, the NS-MBS entries state that all property and interests in property are blocked. OFAC separately confirmed that assets blocked before July 14 remain blocked. The earlier block date belongs in the historical case record, but it should not be used to infer that later property is outside the continuing HKAA measure. A current screening snapshot cannot reconstruct that history.
For a defensible transition record, banks and companies should retain the date of the original block, the owner at the time, the designation authority, the OFAC report reference, and any license that affected the property. They should also retain the date and source of the July 17 list update. Without that chain, an operations team may release property because a name disappeared from the SDN file, or keep an unrelated hold because it never identified the basis for the original action.
"Delisted" is too coarse for the case-management field. The useful fields include removal from an IEEPA-only blocking basis, continuing HKAA blocking, the historical date of a property block, and a possible match under another program. Each supports a different decision. None can be derived safely from a single current-list flag.
OFAC also said an amendment to 31 CFR Part 585 would follow and that Hong Kong-related FAQs were under review. Those pending materials may answer release, reporting, license, and record-retention questions more precisely. Until they arrive, each blocked-property decision should distinguish what the July 17 notice settles from the questions it leaves open.
Export Controls Still Run on Commerce Rules
The sanctions change does not rewrite the EAR. Current U.S. Commerce BIS Hong Kong Export Controls country guidance says that exports, reexports, and in-country transfers to Hong Kong are treated under the EAR as transactions destined for China unless a rule says otherwise. It also says that specified recordkeeping requirements for multilaterally controlled items remain in place. A system may use the China destination setting for EAR license requirements while a transaction file may still need Hong Kong import or export licenses, consignee information, and the records required for multilaterally controlled items. The BIS page identifies missing local licenses, implausible end use, logistics addresses, and inconsistent end-user information as red flags that exporters must resolve before shipment.
EO 13936 directed Commerce to begin appropriate actions in 2020. Commerce then changed the regulations. The emergency's expiry is not itself a new Commerce rule. A company should not restore license exceptions, country policy, or routing logic until it can point to an operative BIS amendment or guidance that supports the change.
The control owner should therefore freeze broad country-table edits and open a change ticket by regulatory program. The ticket should identify the EAR provision or BIS instruction now in production, the new official instrument, the effective date, the affected items and destinations, and the test transaction used to validate the change. If there is no new Commerce instrument, the existing EAR logic remains the defensible operating baseline.
Country Marking Has Its Own Switch
Customs marking is another independent rail. U.S. Customs and Border Protection, CBP Decision 20-15, Country of Origin Marking of Products of Hong Kong, 85 FR 48551, August 11, 2020 requires covered goods produced in Hong Kong to be marked "China" for purposes of 19 USC 1304. U.S. Customs and Border Protection CSMS 43729326, Extension of Transition Period for Compliance With Country of Origin Marking of Goods Produced in Hong Kong, August 21, 2020 later extended the compliance transition through November 9, 2020. The marking requirement applied after that period. The notice ties the result to the suspension of differential treatment for the marking statute under the U.S.-Hong Kong Policy Act.
United States Code 22 USC 5722 on suspension and termination of Hong Kong differential treatment lets the President suspend application of particular laws when Hong Kong is not sufficiently autonomous. It separately provides for terminating a suspension after a presidential determination that sufficient autonomy has returned, with notice published in the Federal Register. The emergency expiry is not that determination or notice.
No replacement presidential or CBP instrument was located by the July 17 research cutoff. Importers should not tell suppliers to change labels based on the OFAC action alone. The marking rule also carries its own exposure. CBP Decision 20-15 states that failure to comply with 19 USC 1304 can result in a 10 percent ad valorem marking duty, subject to the statute and its exceptions.
Marking and tariff origin must remain separate fields. Current U.S. Customs and Border Protection Section 301 Trade Remedies FAQs explain that legitimate goods of Hong Kong origin are not subject to the additional Section 301 duties imposed on China-origin goods solely because they are exported from Hong Kong. The same article can therefore carry "China" for the marking statute while retaining Hong Kong origin for a separate tariff analysis. A jurisdiction-wide reset would erase that distinction.
Trade-Talk Claims Do Not Change U.S. Compliance Rules
The China Ministry of Commerce, Spokesperson Responds to the U.S. Decision Not to Renew the Hong Kong National Emergency, July 17, 2026 said the United States had made a Hong Kong-related commitment during economic and trade consultations and that the executive order would terminate. The Hong Kong SAR Government, Statement on the U.S. Decision Not to Renew the National Emergency Relating to Hong Kong, July 17, 2026 likewise presented the lapse as implementation of a bilateral consensus. Those are official statements of the Chinese and Hong Kong governments. They can frame the negotiating context, but they do not establish the terms of a bilateral agreement under U.S. law or substitute for an OFAC action, a Commerce rule, a CBP notice, or a presidential determination. The U.S. Department of the Treasury, Secretary of the Treasury Scott Bessent to Travel to Europe, September 11, 2025 confirmed that talks were scheduled but did not describe a Hong Kong bargain.
A negotiating commitment may be carried out through several domestic steps with different dates. The emergency lapsed on July 14 and OFAC changed its lists on July 17. The record does not show a synchronized restoration across the other agencies.
Compliance teams should monitor the implementation instruments rather than debate whether the political bargain was broad or narrow. A presidential document affecting the remaining EO provisions, a Federal Register notice under 22 USC 5722, an OFAC Part 585 amendment, and new BIS or CBP instructions would each answer a different question. Until those records appear, the Chinese account should remain an attributed explanation of intent, not the control logic in a U.S. compliance system.
Build the Transition File Before Changing a Flag
Start with a search for every Hong Kong jurisdiction flag. In sanctions tooling it may call screening rules. In an export system it may set EAR country policy. In import data it may feed marking, tariff origin, or both. One label should not conceal those separate decisions.
Build one transition row for each control. Sanctions records need the name, current authority, list action, and any block date. Export records need classification, destination policy, license logic, end user, and local Hong Kong documents. Import records need separate marking and tariff-origin determinations. Every row should also name the agency instrument, effective date, owner, and test result.
The first change ticket covers the list event. It removes EO-only blocking entries and moves HKAA entries to NS-MBS while preserving their blocking treatment. Keep BIS country logic and CBP marking unchanged. Those settings move only when Commerce or CBP issues its own instrument, or when the President publishes a determination under 22 USC 5722. The same discipline applies to the forthcoming OFAC Part 585 amendment. Read the operative text, map the affected records, and test the result before release.
As of the July 17 cutoff, the operating result is narrow. Update the sanctions records and preserve block history. Do not perform a jurisdiction-wide Hong Kong reset.