BIS Advanced Computing Guidance: Why Export Teams Must Check Headquarters and Ultimate Parents, Not Just Addresses

Direct answer

A purchase order can look routine: the customer has a third-country address, the delivery location is outside Country Group D:5 and Macau, and the shipment appears to stay within a familiar commercial hub. That is not enough to close the review.

For exports, reexports, or transfers subject to the Export Administration Regulations (EAR) involving covered advanced computing items, the BIS guidance published on May 31, 2026 states that the license requirement continues to apply when the items are for entities headquartered in, or with ultimate parent companies headquartered in, Country Group D:5 or Macau, unless an exception specified in EAR § 740.2(a)(9)(ii) is available.

The practical mistake is putting address, headquarters, and ownership into one field and treating them as the same fact. They are separate screening inputs.

What changed on May 31?

BIS did not present the May 31 guidance as a new license requirement. It clarified the continued application of earlier requirements, including where a relevant entity is located outside Country Group D:5 and Macau.

According to BIS, the requirements were first introduced on November 17, 2023, through the end-user controls in EAR § 744.23(a)(3). The guidance identifies items classified under ECCNs 3A090.a and .b, 4A090.a and .b, and related .z paragraphs.

A later policy development created room for confusion. In January 2025, the AI Diffusion Rule moved requirements for .a items into part of the worldwide license requirement under § 742.6. BIS later announced in May 2025 that it would not enforce the AI Diffusion Rule’s new compliance requirements.

The May 31 guidance separates those layers. The AI Diffusion Rule non-enforcement policy should not be read as removing the earlier license requirements for covered items for entities headquartered in, or with ultimate parent companies headquartered in, Country Group D:5 or Macau.

Layer	What teams should take from it
Existing license requirements	The headquarters and ultimate-parent connection originated in requirements introduced on November 17, 2023.
May 31, 2026 guidance	BIS clarified that those requirements continue to apply to covered transactions involving relevant third-country entities.
AI Diffusion Rule non-enforcement policy	It should not be treated as a blanket removal of the earlier requirements.

Who should review their screening workflow?

The guidance is relevant to teams reviewing exports, reexports, or transfers subject to the EAR involving covered advanced computing items. It does not mean that every semiconductor, server, cloud, or data-center transaction is covered.

The highest-friction files are often the ones where the paperwork points in different directions. A typical example is a third-country subsidiary with a local registered address and a delivery location outside Country Group D:5 and Macau. The file can look complete until someone asks where the entity is headquartered and where its ultimate parent company is headquartered.

That is the detail I would separate first. A registered address may be the starting point for screening, but it is not the conclusion.

What should the transaction file separate?

Treating entity location as one checkbox creates avoidable blind spots. At minimum, record these fields separately.

Review field	Operational question	Common mistake
EAR scope	Is the export, reexport, or transfer subject to the EAR?	Starting with a product label instead of the applicable regulatory scope.
Counterparty address	What address appears in the contract and purchase order?	Ending the review after checking the local address.
Headquarters	Where is the counterparty headquartered?	Assuming the registered address and headquarters are identical.
Ultimate parent	Where is the ultimate parent company headquartered?	Stopping at an intermediate subsidiary.
ECCN	What Export Control Classification Number applies to the item?	Relying on a product name or marketing description.
Destination	Where is the item actually going?	Combining destination review with ownership review.
End user and end use	Who will use the item, and for what purpose?	Assuming the recipient and actual user are the same.
Exception analysis	Is an exception specified in § 740.2(a)(9)(ii) available?	Jumping directly to an allowed-or-prohibited conclusion.

This checklist is a screening workflow, not a transaction-level determination. As the BIS guidance makes clear, applicability still depends on EAR scope, item classification, party structure, destination, and whether an available exception applies.

BIS states that exporters should continue to apply for licenses where required. The guidance points readers to EAR part 748 for license applications and EAR § 764.5 for voluntary self-disclosures.

Where are the interpretation boundaries?

Three distinctions keep the review disciplined.

First, shipment destination and corporate structure are different questions. A third-country delivery does not remove the need to review headquarters and ultimate-parent connections.

Second, screening is not approval. The confirmed headquarters rule still has to be applied to transaction-specific facts, including whether the items are covered and subject to the EAR.

Third, the AI Diffusion Rule non-enforcement policy and the earlier license requirements do not have the same scope. The May 31 guidance matters because it separates those layers.

What does the guidance say about data centers?

BIS also provides a limited clarification for bona fide data center operators conducting activities consistent with the EAR. According to the guidance, those operators do not need to discontinue continued use, storage, disposal, or servicing of advanced computing items solely because of this guidance. BIS says this applies until further notice.

That statement should be read narrowly. A clarification about existing data-center operations is not a general authorization for new exports, reexports, or transfers.

What should teams monitor next?

The immediate monitoring point is whether BIS publishes additional clarification, particularly because the data-center language applies until further notice. The BIS homepage and Special Issues notices provide the official update path.

Within a transaction file, reopen the screening review when:

• the counterparty changes;
• headquarters or ultimate-parent information changes;
• the item’s classification changes;
• the destination, end user, or end use changes; or
• the basis for an available exception changes.

The durable rule is narrow but practical: for EAR-covered exports, reexports, or transfers involving covered advanced computing items, the address may be the first field you check, but it cannot be the last.

Official sources

• BIS guidance: Guidance Regarding Enforcement of License Requirements for Advanced Computing Items for Entities Headquartered in Country Group D:5 and Macau
• BIS homepage and Special Issues notices