UAE A:5 Export Relief Requires an Approved-Recipient Check
BIS moved the UAE into Country Group A:5, but license-free treatment for specified advanced-computing transactions and use of STA now depend on supplement no. 8. Exporters need to match each ultimate consignee and end user to the exact authorization, current list entry, and any expiry.
Primary lensExport controls
Sub-topicLicensing regime
Evidence base6 records used
Use caseExport-control exposure
A BIS final rule published in the July 14 Federal Register took effect on July 10. It moves the United Arab Emirates into Country Group A:5, removes it from Country Groups D:3 and D:4, and widens access to License Exception Strategic Trade Authorization and license-free treatment for specified advanced-computing transactions. Both forms of no-license treatment are limited to recipients approved in supplement no. 8.
Under the BIS UAE A:5 final rule, 91 FR 43034, the UAE destination alone cannot support either form of no-license treatment. The ultimate consignee and every end user must be covered by supplement no. 8 to part 740, and the authorization shown for each recipient must cover the item and route being used. An exporter needs a current transaction record of the parties, their roles and actual locations, the relevant authorization, the source date, and any expiry before it can rely on the relief.
A:5 relief stops at the approved recipient
Moving the UAE to A:5 opens license exceptions that were previously unavailable. It does not remove the underlying Commerce Control List requirements. BIS says expressly that chemical, biological, and missile-technology controls can still require authorization after the D:3 and D:4 designations disappear. More exceptions become available, each under its own conditions.
STA has an extra UAE condition. New section 740.2(a)(26) bars its use when either the ultimate consignee or any end user is outside supplement no. 8 or lacks STA approval there. A purchaser or intermediate consignee does not have to appear on the new list, but that narrow rule does not excuse ordinary restricted-party, end-use, diversion, or destination screening. It only tells the exporter which transaction roles must carry the new approval.
A country code in an order-management system cannot complete this check. The party that buys the item may not be the party that receives it, and the party that receives it may not be its only end user. Each role has to be resolved before the no-license determination can be closed. If the end-user field says only "customer facilities" or names a project rather than a legal entity, the file is not ready for no-license treatment.
Supplement 8 has three authorization tracks
The new supplement does not give every approved recipient the same rights. Under supplement no. 8, UAE government agencies, including the Ministry of Defense and Armed Forces, are approved for covered advanced-computing items and full use of STA. The rule draws a firm perimeter around that class. State-owned corporations, government contractors, and grantees do not inherit the government approval. A purchase order tied to a ministry program therefore does not establish that a commercial recipient is a government agency.
The same supplement places Group 42 Holding Ltd d/b/a/ G42, including G42 Cloud Technology LLC, and Core42 Technology Projects LLC d/b/a/ Core42 on a second track. Their table entries authorize receipt of the advanced-computing items covered by sections 742.6(a)(6)(iii)(A) and (B). The authorization column does not grant full STA. An exporter that sees either name in the supplement still has to ask which authority the transaction needs. An AI server may fall within the advanced-computing treatment, while a different controlled item requiring STA may not.
The table's third track covers Amazon.com, Inc.; Apple, Inc.; Google LLC; Meta Platforms, Inc.; Microsoft Corporation; OpenAI Group PBC; Oracle Corporation; and X.AI LLC, together with their subsidiaries. Their entries cover both the specified advanced-computing items and full STA. Even here, the corporate name cannot substitute for entity resolution. The shipment file should identify the actual UAE ultimate consignee and end users, record their transaction locations, document their relationship to the listed company, and preserve the version of the supplement used for the decision.
Subsidiary status must be supported by a corporate record current on the review date. Similar names, shared branding, minority investments, project partnerships, joint ventures, or customer representations do not establish coverage under a listed parent.
G42 and Core42 carry a 270-day clock
G42 and Core42 also have a time condition that the other listed groups do not. Their advanced-computing authorizations automatically expire on April 6, 2027, unless BIS issues a later notice. The final rule describes the companies as needing to use the section 748.3(c) process to maintain approved status if they have not become U.S. companies by that point.
A change in corporate status does not, by itself, rewrite the supplement. The operative note makes continued authorization depend on subsequent BIS action. A seller should calendar the expiry, monitor BIS notices, and recheck the live supplement before each shipment that would occur near or after the deadline. A saved PDF from July 2026 is evidence of what the rule said then, not proof of authority on a later ship date.
This clock matters for contracts already being negotiated. A delivery schedule that crosses the deadline needs an authorization contingency, a party responsible for monitoring the list, and a decision point early enough to seek a license if the approval lapses. Without that contingency, the delivery obligation may outlast the no-license authorization.
Advanced-computing controls survive the country-group move
BIS is retaining UAE license requirements for the advanced-computing items described in sections 742.6(a)(6)(iii)(A) and (B), despite the A:5 placement. The exception applies only when the ultimate consignee and all end users are approved in supplement no. 8 for the relevant advanced-computing scope. The agency's BIS May 31, 2026 guidance on advanced-computing controls also shows why a destination-only check is unreliable: advanced-computing controls can follow an entity headquartered in, or with an ultimate parent headquartered in, Country Group D:5 or Macau even when the immediate recipient is elsewhere.
Classification comes first. The exporter must confirm the ECCN and determine whether the transaction falls within the advanced-computing provisions named in the supplement. It then needs the full party chain and the exact authorization column. Only after those facts align can the file record a no-license conclusion. An approved recipient does not make every item eligible, and an eligible item does not cure an unapproved end user.
Part 744 remains a separate gate. The rule states that supplement no. 8 approval does not overcome end-use and end-user license requirements there. Military, intelligence, supercomputer, and other restricted uses or users remain subject to the applicable part 744 controls. The same is true of the general restrictions on license exceptions in section 740.2. Recipient approval narrows one question; it does not answer the rest of the EAR.
STA still requires shipment-by-shipment records
STA avoids a license only when the conditions in EAR section 740.20, License Exception STA are satisfied. Before using it, the exporter must furnish the applicable ECCN to the consignee. The party using STA ordinarily must obtain a written prior consignee statement, keep it under part 762, and maintain a record linking each physical shipment to the relevant statement. With each physical shipment, it must also give the consignee written notice that STA is being used and identify the items or shipment covered.
The prior-statement rule has details that matter in the UAE. Government consignees in A:5 are not required to sign or provide the statement. That exception does not remove the ECCN, authorization, shipment-notice, filing, or recordkeeping analysis. Reexporters and in-country transferors using STA take on parallel obligations, so the documentation chain can extend beyond the first U.S. export.
Required Electronic Export Information must identify the correct license-exception code and ECCN under section 740.1. The new rule expects AES filing for STA exports to continue to the same extent as for licensed shipments, while EAR part 758, Export Clearance Requirements and the Foreign Trade Regulations determine when a filing is required. Records for license-exception transactions must be retained under EAR part 762, Recordkeeping. "License-free" is an authorization result, not a description of the paperwork.
A screening result is only one part of the operating file. The record should connect the ECCN, reason for control, ultimate consignee, every end user, actual transaction locations, any address qualification in the current supplement entry, authorization scope, end use, part 744 review, consignee statement or government exception, shipment notice, AES record if required, source version, and expiry. Some fields are stable across repeat shipments. Others, especially party roles, locations, and end use, need transaction-level confirmation.
Approval is not usable until the list changes
Ultimate consignees and end users in the UAE seeking advanced-computing or STA approval, including U.S.-headquartered entities operating there, may request an advisory opinion under EAR section 748.3(c), Advisory Opinions. The new admission process requires the Commerce Secretary, after consulting the Secretary of State and the National Security Adviser, to determine within 30 days of receipt whether the entity should be approved and the scope of any approval. Within five days of that determination, BIS will notify the requester and, if approved, begin the process of adding it to the supplement.
Notification is not the same as a completed public-list update. For an exporter relying on supplement no. 8, the controlling sources should be the operative rule and later BIS notices, not a customer's statement that approval has arrived. The file should capture when the public authorization became usable and exactly what it covers.
MGX is outside the preapproved list. BIS says it intends to review favorably license applications involving the company for semiconductors and servers. That is a licensing posture, not preapproval under supplement no. 8. A favorable-review statement cannot be entered in the recipient ledger as license-free authority.
A company's status, parentage, name, listed scope, or expiry may change. Compliance systems should assign an owner to monitor the list and define how quickly an updated BIS record reaches open orders, export holds, and downstream reexport instructions.
Add a recipient layer to country-group logic
The UAE rule requires country-group logic to be paired with a versioned recipient record. That record should identify each legal entity, transaction role, and actual location, compare those facts with the current supplement entry, and reopen review when a party, address, item, end use, corporate relationship, authorization scope, or deadline changes. Repeat orders should not bypass those triggers simply because an earlier shipment cleared.
BIS estimates that the rule will reduce license applications by about 50 a year while increasing reliance on license exceptions. The estimate points to where compliance work moves: from the agency's license review into the exporter's eligibility record. Companies that treat A:5 as a standing country permission will miss that shift.
Four facts should control the release decision
Before releasing a UAE shipment without a license, the responsible reviewer should be able to answer four questions from the file. What is the item and controlling ECCN? Who is the ultimate consignee and every end user? Which supplement no. 8 authorization covers each of them for this item? What other EAR condition, document, or deadline could still block the route?
If any answer depends on a shorthand customer name, a project affiliation, an old copy of the supplement, or an assumed government connection, the export hold should remain.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.