Hello, this is Ryuta Hamamoto from TIMEWELL.
Picture this. A questionnaire arrives from a foundry you work with. "Where are your headquarters and your ultimate parent located?" "Is any parent, subsidiary or ultimate beneficial owner headquartered in Macau or a D:5 country?" "Do you agree to submit the information we report to the U.S. Commerce Department?" The deadline is two weeks out. Sales is worried the next lot will slip if you don't answer. Legal wants to know how much you can safely share.
Each of those questions has a basis in the U.S. Export Administration Regulations (EAR). Once you know which provision sits behind a question, it becomes much easier to decide how far to answer and how to reply when you can't. I wrote this for fabless and IC design companies on the receiving end of these requests, based on the regulatory text as I checked it on November 22, 2026.
The short version
- The reason you are being asked is Note 1 to ECCN 3A090.a. Only foundries and OSATs face the presumption, but which of the three ways to overcome it is available depends on the designer's headquarters, location, and the headquarters of its ultimate parent.
- Most of the requested information lines up with the reporting items in 15 CFR 743.9(b) and the KYC vetting form in Supplement No. 2 to Part 743 (four sections, 21 questions). Check the provision behind each question before you decide how far to answer.
- After December 31, 2026, staying "authorized" also requires an application to become an approved IC designer, and the status ends 180 days after you submit it. I'd recommend deciding before year-end whether to apply, or whether the foundry can rely on a transistor count attestation (paragraphs b. and c.).
This article doesn't judge any country or company. Country groups and headquarters tests in the rules are regulatory categories; falling into one is not a verdict on a company. I assume throughout that you judge people and counterparties by the regulatory criteria, never by nationality or origin. The scope is the U.S. EAR only. Japan's Foreign Exchange and Foreign Trade Act and Taiwan's rules are out of scope. For how Japan's rules treat the design data itself when you send it to a foundry, see Sending chip design data to a foundry.
Why designers get these questions: the Note 1 presumption and three routes
Only foundries and OSATs face the presumption
Start with Note 1 to ECCN 3A090.a. It says that when a front-end fabricator (the EAR's term for a company that builds circuits on the wafer surface) or an OSAT (a company that assembles, packages and tests ICs) exports, reexports or transfers in-country an "applicable advanced logic integrated circuit," the item is presumed to be 3A090.a and designed or marketed for datacenters. If the foundry or OSAT can't overcome that presumption, it must comply with all license requirements that apply to 3A090.a items1.
Section 772.1 defines "applicable advanced logic integrated circuits" as logic ICs produced at the 16/14 nm node or below, or with a non-planar transistor architecture2. The 3A090.a thresholds themselves are a total processing performance (TPP) of 4800 or more, or a TPP of 1600 or more with a performance density of 5.92 or more. So even a chip whose real performance sits far below those numbers starts out, on the foundry's side, presumed to be 3A090.a if it is made at an advanced node.
The key line for designers is that Note 1 says the presumption "does not apply to any entity other than the front-end fabricator or OSAT company." When you classify your own product, you use its actual specifications, not the presumption. But whether the foundry can ship without a license depends on which category you fall into as the designer. That is why the questions come to you. Conversely, if your logic IC is made on a planar process older than 16/14 nm, the Note 1 presumption doesn't kick in at all. Settling that first tells you how much of the questionnaire really concerns you. If you first need to work out whether your product is subject to the EAR at all and where it sits on the CCL, the EAR classification flow and EAR99 checklist walks through the order of the questions, including when EAR99 items still need a license.
Three ways to overcome it, and which designer attributes matter
Note 1 limits the ways to overcome the presumption to paragraphs a. through c. Paragraph d. says relying on the attestation of the end user or another party to the transaction isn't enough1.
| Route | Who shows what | Which designer attributes matter |
|---|---|---|
| Paragraph a. | An approved or authorized IC designer shows, with a datasheet or other attestation of TPP and performance density, that the IC is not 3A090.a | Whether you are on the approved list (Supplement No. 6 to Part 740) or meet the authorized criteria |
| Paragraph b. | The foundry attests that the aggregated approximated transistor count of the final packaged IC is below the threshold (when the foundry itself packages outside Macau and D:5) | Neither your location nor your ultimate parent's headquarters is in D:1, D:4, D:5 or the five countries in 742.6(a)(6)(iii)(A)(1) |
| Paragraph c. | An approved OSAT (Supplement No. 7 to Part 740) attests the same | Same as paragraph b. |
The threshold in paragraphs b. and c. is below 30 billion transistors. For a packaged IC without high-bandwidth memory (HBM), it is below 35 billion for exports completed in 2027, and below 40 billion for 2029 or later. The text doesn't give a separate no-HBM threshold for 2026 or 2028, so as I read it, only the 30 billion figure applies in those years. The five countries are Indonesia, Malaysia, Singapore, Brazil and Thailand1. Country groups are the EAR's way of sorting destinations; D:5 covers U.S. arms-embargoed countries, among others. Check which country falls where in the tables of Supplement No. 1 to Part 7403.
If none of the routes works, two license requirements reach the foundry. One is 742.6(a)(6)(iii)(A), which requires a license for exports to the five countries, D:1, D:4 and D:5 (excluding destinations also in A:5 or A:6), and the UAE, with exceptions written into the text, such as the one for parties headquartered in the United States and the one for approved UAE entities. The other is 744.23(a)(3)(i)(C), added on November 19, 2026. It requires a license, to or within any destination, when a foundry or OSAT exports a 3A090.a IC designed by a company that is neither an approved nor an authorized IC designer1.
How three rules fit together
The designer framework wasn't built in one rule. Here is the sequence.
| Date | Rule | What it did for designers |
|---|---|---|
| January 16, 2025 | 90 FR 5298 | Created the Note 1 presumption and the three routes, the approved designer and OSAT lists, the 743.9 reporting and KYC vetting form, and the 748.16 application process. The switch date for authorized designers was originally April 13, 2026 |
| April 9, 2026 (effective April 7) | 91 FR 17851 | Moved the switch date and the application deadline to December 31, 2026 |
| November 19, 2026 | 91 FR 74970 | Added designer location and ultimate parent conditions to paragraphs b. and c., created 744.23(a)(3)(i)(C), and revised 742.6(a)(6)(iii)(A) |
| December 31, 2026 | (from the extension above) | An application becomes part of the authorized designer criteria |
| January 19, 2027 | 91 FR 74970 | Comment deadline for the November 19 rule |
The November 19 rule reprinted the whole 3A090 entry, but paragraphs a.(1) through (3) of Note 1, which carry the December 31 date and the 180 days, read the same as the November 18 version. I compared the November 18 and November 19 eCFR versions and confirmed that what changed was the designer condition in paragraphs b. and c.4 The February 2025 correction explained that, before November 19, 742.6(a)(6)(iii)(A) imposed a worldwide license requirement for 3A090.a items5. The November 19 rule narrowed 742.6 to the five countries and others, and its preamble says the new paragraph (C) "ensures that a license requirement continues to apply" to foundries and OSATs making advanced ICs for non-approved, non-authorized designers1. For a side-by-side of the foundry provisions before and after, see my article on the foundry rule.
What you are asked for, and the provision behind each item
Map each question to its provision
Every foundry uses its own form. Even so, most of the content maps to a specific provision. Here is how I sort it. When a request comes in, slot each question into a row first. You will quickly see which items are regulatory requirements and which are the foundry's own diligence.
| Information requested | Provision | What the foundry uses it for |
|---|---|---|
| Where your headquarters are | Note 1 a.(2)(i) | Authorized criteria (headquarters in Taiwan, A:1 or A:5) |
| Where you are located, and where your ultimate parent is headquartered | Note 1 a.(2)(i), b., c. | Checking Macau, D:5, D:1, D:4 and the five countries |
| Your agreement to submit the 743.9(b) information | Note 1 a.(2)(ii), 748.16(c) | Authorized criteria |
| Name, address, point of contact | 743.9(b)(1) | Quarterly report to BIS |
| Product names, model numbers, quantities | 743.9(b)(4) | Same |
| Material for the KYC vetting form | 743.9(b)(3), Supplement No. 2 to Part 743 | Same. An unresolved "yes" is a red flag |
| Datasheet or attestation of TPP and performance density | Note 1 a. | Route a. |
| Package composition (number of dies, HBM or not) and packaging location | Note 1 b. and c., Technical Note 1 | Routes b. and c. (attested by the foundry or OSAT) |
| Whether you are approved, and whether and when you applied | Note 1 a.(1) and (3), Supplement No. 6 to Part 740 | Whether route a. is available; tracking the 180 days |
Section 743.9 requires a foundry producing 3A090.a ICs (including presumed ones) for authorized IC designers to report to BIS. There are four reporting periods: May 1 to July 31, August 1 to October 31, November 1 to January 31, and February 1 to April 30, each due within 30 days of the period's end. Reports go to EAR.Reports@bis.doc.gov with "Authorized integrated circuit designer" in the subject line. Transactions with a designer that is both approved and authorized don't need to be included6. From the designer's side, the practical takeaway is simple: your name, product names, model numbers and quantities reach the U.S. government through the foundry every quarter.
Inside the KYC vetting form (four sections, 21 questions)
Supplement No. 2 to Part 743 is the "Authorized Integrated Circuit Designer Know Your Customer (KYC) Vetting Form." The foundry completes it as part of its 743.9 reporting. It has 21 questions in four sections, with a column to explain how any "yes" was resolved6. The preamble to the January 2025 rule says an unresolved "yes" is considered a red flag, and the foundry must do additional due diligence before proceeding7.
Section 1 covers whether the designer is legitimate: no website; a website IP address in a different region from the physical address; a phone country code that doesn't match the address; an email address without the company domain; an invalid address; a supposed civilian end user co-located with a military facility; and public corporate records that contradict the company's claims. That's seven questions. Section 2 is screening against the Consolidated Screening List: name, address, and overlap of senior management or technical leadership, three questions. Section 3 is additional party screening: whether any company in the corporate hierarchy (parent, subsidiary, ultimate beneficial owner) is headquartered in Macau or D:5, whether any of them matches the list, and whether other parties to the transaction are located or headquartered in Macau or D:5, three questions. Section 4 is general red flags: end use inconsistent with the business, quantity inconsistent with size, a freight forwarder as final destination, multiple forwarders in third countries, refusal to answer end-use questions, documents listing other parties, overpaying, and payments from uninvolved third-country entities, eight questions.
There's more a designer can prepare in advance than you might expect. For Section 1, simply replying from your company domain, and adding one line if your website is hosted on an overseas cloud, makes the foundry's job easier. Watch the word "subsidiary" in Section 3. It is broader than the Note 1 test, which looks at the designer's location and its ultimate parent. The form gives you a column for how a "yes" was resolved; it doesn't forbid answering "yes." In my view, the best preparation is to be able to state, as facts, which group companies are where, and whether each one is involved in this transaction.
One more point on wording. I could not find definitions of "ultimate parent" or "headquartered" in 772.1 (checked November 22, 2026). So don't stop at "Our ultimate parent is X." Show how far up the chain you traced, with each tier's name, location and ownership percentage, so the foundry can check the basis itself. The ownership logic in my BIS 50% rule guide helps here, and the BIS 50 percent rule checklist gives you a fill-in format for tracing ownership chains. Keep in mind that the 50% rule is an ownership test, while Note 1 is a headquarters and location test. Treat them as separate checks.
Replace siloed classification work with AI.
METI's FY2024 data shows 52% of foreign exchange law violations stem from classification errors. Download the TRAFEED product catalog covering features and rollout.
Approved and authorized IC designers, December 31 and the 180 days
Approved IC designers and how to apply
Approved IC designers are the companies listed in Supplement No. 6 to Part 740. As of the November 19, 2026 eCFR, 33 companies are listed, and the supplement has only one version, dated January 16, 2025, so I could not find any additions since8. The approved OSAT list (Supplement No. 7) has 24 companies. If you want to know whether your company or your group is listed, check the list itself and watch for variations in how names are written.
Section 748.16 sets out the process. You apply in the form of an advisory opinion request, emailed to approved_supply_chain@bis.doc.gov with the subject line "Approved supply chain entities request." The End-User Review Committee (ERC) reviews it. Entities headquartered, or with an ultimate parent headquartered, in Macau or D:5 are not considered. Only entities that have designed, assembled, tested or packaged ICs, or have credible plans to do so, are considered9.
Supplement No. 4 to Part 748 lists six items to include: (a) identity, including all business names, every physical address and contacts; (b) ownership and business, including subsidiaries, joint ventures and any relationship with government or military organizations; (c) the applicable advanced logic ICs you expect to design or handle, with ECCNs, technical parameters including performance, and end uses; (d) how your recordkeeping will comply; (e) a certification on letterhead, signed by someone who can legally bind the company, that it will comply with 748.16; and (f) a statement acknowledging that use or diversion contrary to the EAR is prohibited, agreeing to recordkeeping, and agreeing to on-site reviews by U.S. officials9.
Among the factors the ERC may consider, 748.16 lists the applicant's record of exclusive engagement in appropriate end-use activities, compliance with U.S. export controls, the need for an on-site review, the ability to meet the requirements of listing, the ability to guard against misuse and diversion of computing resources, and relationships with U.S. and foreign companies. The ERC also considers the export controls of the country where the applicant is headquartered and that country's support for the multilateral regimes. The section states plainly that a denied request doesn't create new license requirements, doesn't make the applicant ineligible for licenses, and doesn't prevent a later request. Listing can be revised, suspended or revoked, the information submitted counts as continuing representations, and material changes must be reported promptly to the ERC9.
The April 2026 rule estimated that the extension would bring a net increase of 75 advisory opinions and 20 more approved IC designers10. Those are BIS estimates. I haven't found any published figures for actual applications or approvals.
Authorized IC designer criteria and December 31
Authorized IC designers aren't a list. They are defined by the criteria in Note 1 a.(2) and (3). Before December 31, 2026, an authorized designer meets two conditions. First, it is headquartered in Taiwan or a Country Group A:1 or A:5 destination, and is neither located in nor has an ultimate parent headquartered in Macau or D:5. Second, it has agreed to submit the information described in 743.9(b) to the foundry. The foundry must then report that information to BIS1. Japan is in both A:1 and A:5, and Taiwan is named in the text3.
After December 31, the designer must also have submitted an application to become an approved IC designer. And any company deemed authorized after December 31 stops being authorized 180 days after submitting that application1. The DATES section of the April 2026 rule says: "Applications must be received by December 31, 2026, after which time, applicants may be considered authorized IC designers for 180 days."10 The preamble to the January 2025 rule said that after the switch date (then April 13, 2026), the main way to be exempted would be to become an approved IC designer, other than the 180-day route7.
When do the 180 days start?
There are two possible readings here. Note 1 a.(3) says "180 days after the submission of its application." The DATES section's "after which time ... for 180 days" can also be read as counting from December 31. If you apply on December 1, counting from submission gives May 30, 2027, and counting from December 31 gives June 29, 2027 (both are my own calculations). I haven't found any BIS document explaining which reading it applies. My advice is to set your internal deadline using the shorter reading, counting from your submission date. If the real date turns out later, nothing breaks. If it turns out earlier and you didn't plan for it, the foundry's shipping decisions lose their basis without anyone noticing.
Then there's the question of a decision arriving within the 180 days. If you are approved, you are added to the list and treated as an approved designer under a.(1). If you are denied, the text doesn't say what happens to the remaining authorized period. Nor can I tell from the wording which side December 31 itself falls on.
Which routes remain for the foundry, by designer category
Applying the text designer category by designer category, this is how I'd sum up the routes left to the foundry. It is my reading of the rules, not a ruling on any transaction.
| Designer category | Until December 31 | After December 31 |
|---|---|---|
| On the approved list | Route a. (datasheet or other attestation) | Same |
| Meets the authorized criteria (headquarters in Taiwan, A:1 or A:5; not located in, and no ultimate parent headquartered in, Macau or D:5; agreed to provide the 743.9(b) information) | Route a. | Route a. for 180 days after submitting an application. Without an application, no route a. |
| Of those, location and ultimate parent headquarters outside D:1, D:4, D:5 and the five countries | Route a., or routes b. and c. | Even without an application, routes b. and c. if the transistor count and packaging location conditions are met |
| Of those, ultimate parent headquartered in one of the five countries | Route a. | Route a. within the application and 180-day window. No routes b. or c. |
| Headquarters not in Taiwan, A:1 or A:5 (and not in Macau or D:5) | No route a. unless approved. Routes b. and c. depend on location | Same |
| Headquarters, or ultimate parent headquarters, in Macau or D:5 | None of routes a., b. or c. | Same (not eligible for the approved list) |
Even with headquarters elsewhere, a designer that is itself located in Macau or D:5 falls outside both the authorized criteria and the conditions of routes b. and c.
The table shows where the decision really sits for a designer. If your final packaged transistor count is comfortably below the threshold and the packaging location condition is met, the foundry may still be able to overcome the presumption under b. or c. after December 31. If your product is above the threshold, or close enough that the foundry will struggle to confirm the count, you'll be relying on route a., and applying to become an approved IC designer starts to matter. Products with HBM have only the 30 billion threshold, which is worth keeping in mind. I walk through transistor counts, TPP and performance density with worked examples in my 3A090 classification guide.
Reply templates: can answer, still checking, cannot answer
Five things to settle before you write
Before you reach for a template, settle five things internally. First, who approves the reply. Decide at the start whether design, legal or the export control lead signs off. Second, the "as of" date. Locations and ownership change, so every reply should say "as of [date]." Third, the evidence. Registry extracts, shareholder records, the datasheet revision: have something behind every line. Fourth, the line between facts and plans. "We have applied" and "we plan to apply" lead the foundry to very different decisions. Fifth, how much you can actually verify about your parent and subsidiaries. Not writing as if you know what you don't is what keeps the reply credible.
A reply filled in with guesses becomes the basis for the foundry's decision. If it later turns out to be wrong, the foundry has to redo its shipping decision, and the relationship takes the hit. Honestly, I think writing "we can't answer this" protects the business better in the end.
Template A: you can answer
Use this when you can answer every item.
[Template A] Further to your request dated [date], [Company] (the "Company") confirms the following facts as of [date]. 1. The Company is headquartered in [city, country], and its design sites are located in [locations]. 2. The Company's ultimate parent is [name], headquartered in [country]. The ownership chain from the Company to its ultimate parent is shown in Attachment 1. 3. Neither the Company nor its ultimate parent is located in, or headquartered in, Macau or any country in Country Group D:5 of the EAR. 4. The Company agrees to submit to you the information described in 15 CFR 743.9(b). 5. The total processing performance and performance density of [product] (model [ ]) are as stated in datasheet revision [ ] dated [date], and the Company has classified the product as not specified in ECCN 3A090.a. 6. The Company submitted an application to become an approved IC designer on [date] (or: has not submitted such an application). We will notify you promptly of any change to the above.
Template B: still checking
Use this when you are still confirming some items. Always give a date and whatever you can share now.
[Template B] Thank you for your request dated [date]. Our answers to items 1 to 3 and item 5, as of [date], are attached. Items 4 (our agreement to submit the information described in 15 CFR 743.9(b)) and 6 (whether we have applied to become an approved IC designer) are going through internal approval, and we will reply in writing by [date]. If you need to make a shipment decision before then, please contact [name]. For the questions in Section 3 of the vetting form about our subsidiaries, we are compiling a list of our subsidiaries and their role, if any, in this transaction, and will send it by the same date.
Template C: you cannot answer, or can answer only in part
Use this when there are items you can't answer. State the reason, what you can offer instead, and that you understand the effect on the foundry's options.
[Template C] Regarding your request dated [date], we are unable to answer item [ ] ([topic]) at this time because [reason]. As an alternative, we can offer [for example, a summary of our ownership structure under a non-disclosure agreement, or confirmation through our legal counsel]. We understand that, as a result, you may not be able to rely on our attestation under Note 1 to ECCN 3A090.a of the EAR. If you proceed by another route, such as a transistor count attestation or a license application, please let us know what information we can provide to support it.
These templates are a starting point for internal approval, not text to send as is. Fill in the company and product facts only after checking them against your documents. A request from a Japanese customer for a certificate of non-applicability under Japanese law is a different situation; see my reply templates for that case. The request discussed here is about EAR categories, not a Japanese classification.
Records to keep, and what I have not been able to confirm
What to record for each request
Once the reply has gone out, keep a record for each request. The goal is to be able to explain, six months or a year later, when you answered whom, what you said, and on what basis. Tracking the 180 days and notifying the foundry of ownership changes both start from this record.
| Item | Example entry |
|---|---|
| Date received and sender | 2026-11-24, export control team at [foundry] (contact name, email) |
| Products covered | Product name, model number, datasheet revision and date |
| Questions and their provisions | Each question, mapped to Note 1 a.(2), 743.9(b) and so on |
| What you answered | Reply version, date sent, "as of" date |
| Supporting documents | Registry extracts, ownership chart, datasheet, internal classification record |
| Approver | Name of the export control lead and approval date |
| Your status | Approved or not; assessment against each authorized criterion |
| Application date and 180-day end | Application date; 180th day counted from submission (internal deadline) |
| Review triggers | Ownership change, move of headquarters or design sites, rule changes |
Section 748.16 requires the requester to keep records relating to its request in line with part 7629. The part 762 retention references include records relating to 748.16 requests and the KYC vetting form (Supplement No. 2 to Part 743), and the retention period is five years, counted as provided in 762.62. I haven't been able to confirm whether a designer that hasn't applied has a regulatory obligation to keep its replies to a foundry. I'd still keep them for the same five years. If the foundry's records and yours ever disagree, your own records are the only thing you can explain from.
The trigger people forget most is an ownership change. Section 748.16 requires a listed company to file a modification request if control or its name changes, and any material change relating to a request must be reported promptly to the ERC, whether the company is already approved or still under consideration9. If you answered a foundry as an authorized designer, I think the same courtesy applies: tell the foundry when the facts behind your answer change. For what to do on the day a rule changes, see my rule change playbook.
What I have not been able to confirm
As of November 22, 2026, here is what I couldn't confirm. Whether the 180 days run from the submission date or from December 31. What happens to the remaining authorized period if an application is denied. How December 31 itself is treated. Any BIS FAQ or guidance on this framework (I didn't find one). How BIS interprets "headquartered" and "ultimate parent." The actual number of applications and approvals. What forms foundries use in practice to confirm approved or authorized status, and how often (I expect this varies by company). How Japan's export control law treats providing design data to a foundry. How Taiwan's rules interact with all this. The November 19 rule is open for comment until January 19, 2027, and its content may change afterward. I'll update this article when new facts come out.
Summary
- The basis for these requests is Note 1 to ECCN 3A090.a. The presumption falls on the foundry and the OSAT, but which routes are open depends on the designer's headquarters, location and ultimate parent.
- Most questions line up with the 743.9(b) reporting items and the 21 questions of the KYC vetting form. Check the provision behind each one before answering.
- After December 31, staying authorized requires an application, and the status ends 180 days after you submit it. Set your internal deadline using the shorter reading.
- Give every reply an "as of" date and supporting documents. For anything you can't answer, say why and what you can offer instead. Keep the records for five years.
Personally, I'd treat these requests less as "the foundry's problem" and more as a chance to put your ownership chain and product categories into one clean register. If you decide before December 31 whether your products can go through routes b. and c. or will rely on route a., answering the next round of questions in January will take far less time. You can use TRAFEED to screen against each country's lists and keep a record of the decisions. To talk it through, get in touch here.
What to read next
- The reported TSMC and Samsung shipment pause and the new BIS foundry rule: the foundry and OSAT provisions, before and after.
- ECCN 3A090 classification in practice: TPP, performance density, approximated transistor counts and a classification record format.
- The BIS 50% rule guide: tracing ownership and doing the math.
- What the AI chip diversion reports teach about thin counterparties: how the red flags in the KYC form show up in practice.
- The U.S. export rule change playbook: sorting impact and briefing management on the day a rule lands.
Footnotes
-
U.S. Department of Commerce, Bureau of Industry and Security (BIS), interim final rule, "Addressing Remote Access to Advanced Semiconductors." Federal Register document 2026-23529, 91 FR 74970-74999. Published and effective November 19, 2026; comments due January 19, 2027. https://www.federalregister.gov/documents/2026/11/19/2026-23529/addressing-remote-access-to-advanced-semiconductors . I checked Note 1 to ECCN 3A090.a (paragraphs a. through d.) and the 3A090.a thresholds, 742.6(a)(6)(iii)(A), 744.23(a)(3)(i)(C), and preamble sections III.B, IV.D and V against a copy of the GPO published version (retrieved November 20, 2026) on November 22, 2026. Preamble III.B (the conforming change to §744.23 for removing the worldwide license requirement) reads: "This addition ensures that a license requirement continues to apply to 'front end fabricators' and 'OSATs' creating advanced ICs for non-approved, non-authorized IC designers wherever located." ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7
-
eCFR, 15 CFR 772.1 (definitions of "Applicable advanced logic integrated circuits," "Front-end fabricator," "Outsourced Semiconductor Assembly and Test (OSAT)" and "Aggregated approximated transistor count"; I found no definition of "ultimate parent" or "headquartered"), 762.2(b)(61) and (62), and 762.6(a) (Five year retention period), version as of November 19, 2026, retrieved on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-762/section-762.6 ↩ ↩2
-
eCFR, Supplement No. 1 to Part 740 (Country Groups), version as of November 19, 2026. Japan is marked in A:1 and A:5; Taiwan is marked in A:6 and D:3. Retrieved on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-740/appendix-Supplement%20No.%201%20to%20Part%20740 ↩ ↩2
-
eCFR, Note 1 to ECCN 3A090.a in Supplement No. 1 to Part 774. I retrieved the November 18, 2026 and November 19, 2026 versions through the eCFR versioner API and compared them on November 22, 2026. Paragraphs a.(1) through (3) are identical; paragraphs b. and c. gained the designer location and ultimate parent conditions. ↩
-
BIS, "Implementation of Additional Due Diligence Measures for Advanced Computing Integrated Circuits; Amendments and Clarifications; and Extension of Comment Period; Correction." Federal Register document 2025-02655, 90 FR 9604, published February 14, 2025. https://www.federalregister.gov/documents/2025/02/14/2025-02655/implementation-of-additional-due-diligence-measures-for-advanced-computing-integrated-circuits . I checked the preamble sentence "That provision provides that there is a worldwide license requirement for ECCN 3A090.a items." in the GPO HTML version on November 22, 2026. ↩
-
Electronic Code of Federal Regulations (eCFR), 15 CFR 743.9 and Supplement No. 2 to Part 743 (Authorized Integrated Circuit Designer Know Your Customer (KYC) Vetting Form), version as of November 19, 2026, retrieved through the eCFR versioner API on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-743/section-743.9 , https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-743/appendix-Supplement%20No.%202%20to%20Part%20743 ↩ ↩2
-
BIS, interim final rule, "Implementation of Additional Due Diligence Measures for Advanced Computing Integrated Circuits; Amendments and Clarifications; and Extension of Comment Period." Federal Register document 2025-00711, 90 FR 5298-5321, published and effective January 16, 2025. https://www.federalregister.gov/documents/2025/01/16/2025-00711/implementation-of-additional-due-diligence-measures-for-advanced-computing-integrated-circuits . I checked preamble sections I, III.B through III.D and III.F (authorized designer criteria, treatment of "yes" answers on the vetting form, and the 748.16 process) in the GPO HTML version on November 22, 2026. ↩ ↩2
-
eCFR, Supplement No. 6 to Part 740 (Approved Integrated Circuit Designers) and Supplement No. 7 to Part 740 (Approved "OSAT" Companies), version as of November 19, 2026, listing 33 and 24 companies. I confirmed through the eCFR versioner API's version list on November 22, 2026 that each supplement has only one version, dated January 16, 2025. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-740/appendix-Supplement%20No.%206%20to%20Part%20740 ↩
-
eCFR, 15 CFR 748.16, 748.3(c)(4) and Supplement No. 4 to Part 748 (Information Required To Be Submitted With a § 748.16 Request), version as of November 19, 2026, retrieved on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-748/section-748.16 ↩ ↩2 ↩3 ↩4 ↩5
-
BIS, final rule, "Extension of Authorized Integrated Circuit (IC) Designer Status and Application Deadline To Become an Approved IC Designer." Federal Register document 2026-06851, 91 FR 17851-17852, published April 9, 2026, effective April 7, 2026. https://www.federalregister.gov/documents/2026/04/09/2026-06851/extension-of-authorized-integrated-circuit-ic-designer-status-and-application-deadline-to-become-an . I checked the SUMMARY, DATES, the amendatory instruction (replacing "April 13, 2026" with "December 31, 2026" in Note 1 a.(2) and (3)) and the burden estimates in the GPO HTML version on November 22, 2026. ↩ ↩2






