Bill Commons
All policy developments

BIS guidance on license requirements for advanced computing items

BIS says the license requirement continues for specified advanced-computing items for D:5/Macau-headquartered entities or their ultimate-parent entities.

Automated source check: observed.

Issuer
U.S. Department of Commerce, Bureau of Industry and Security
Jurisdiction / parties
United States federal / export transactions
Instrument
agency guidance
Status
issued · as of 2026-05-31
Published
2026-05-31
Last source check
2026-10-31T07:30:18.124533+00:00

What the instrument says

Bounded to the described items/entities; not a universal exporter rule.

  • Exporter

    Seek a BIS license for the described transaction unless the cited exception is available.

    BIS guidance paragraph 3; EAR §742.6(a)(6)(iii)(A), §740.2(a)(9)(ii)

What would need to be proven?

The following mappings are analysis. Candidate evidence is not proof that a vendor satisfies an obligation, and hardware attestation alone does not establish legal compliance.

Claim to examine
A transaction met the cited export-control conditions.
Candidate evidence
Classification, screening, license/exception analysis, and delivery records.
Possible approach
Review against current EAR text and transaction facts.
Assumptions
  • Classification, destination, and ownership facts are accurate.
Limits and open questions
  • Not transaction-specific legal advice.

Original sources

  • BIS guidance

    paragraphs 1-3

    Published: 2026-05-31 · Retrieved: 2026-10-31T07:30:18.124533+00:00

    Manual source audit: 2026-10-31T03:24:41Z

    Retrieval method: automated fetch

    • The guidance describes license requirements for the stated advanced-computing items and D:5/Macau headquarters or ultimate-parent conditions.
    • It cites the relevant EAR provisions and a specified exception.

    Audit limit: Not a transaction-specific export-control conclusion; current EAR text and facts control.

Observation history

This is Bill Commons’ retained observation history, not a complete history of the instrument. A changed source body requires review before its policy meaning is updated.

  1. 2026-10-31T03:24:41Z · registry record created

    Curated registry entry created; this is not a source retrieval.

  2. 2026-10-31T07:30:18.124533+00:00 · source check

    Source fetch outcome; body changes require human review and do not assert a policy change.