Hello, this is Ryuta Hamamoto from TIMEWELL.
Picture the week before tape-out. The design team pings the export control desk: "Before we upload the GDSII to the foundry's portal, is there anything we need to do? The foundry has already sent us questions about our location under some U.S. rule. Is that the same thing?" It is not. The foundry's questions are about whether the foundry itself can ship the finished IC under the EAR. Sending the design data is a separate act. Under Japanese law it is a provision of technology, and if the data is subject to the EAR, it is also a reexport from the U.S. point of view.
Here is the short answer. On the Japanese side, check whether the IC and its design data fall under item 7 of the appended table to the Foreign Exchange Order, and if not, item 16. On the U.S. side, first check whether the Japanese-made data is subject to the EAR at all. Only if it is do you move on to 3E001 and 3D001, the license requirements and the end-use controls in 15 CFR 744.23.
Key points
- An overseas foundry or OSAT (an outsourced assembly, packaging and test company) is a non-resident under Japan's Foreign Exchange and Foreign Trade Act (FEFTA). Handing it design data can be a transaction under Article 25(1) (what METI's Service Transaction Circular calls a service transaction), and sending the data by e-mail or upload is also a transmission under Article 25(3).
- In Japan, look at items 7 and 16. Do not let the U.S. "Category 3" lead you to "item 3": item 3 of Japan's appended table covers chemical-weapons-related goods.
- The EAR does not attach automatically to design data made in Japan. Check U.S.-origin content, commingling with controlled U.S.-origin technology, and the foreign direct product rules, in that order. 3E001, 3D001 and 744.23 matter only once the data is subject to the EAR.
This article does not judge any country or company. Country groups, headquarters tests and list entries are regulatory classifications, not verdicts on the companies concerned. All companies in the examples are fictional. I cover Japan's FEFTA and the U.S. EAR only, not the law of the country where the foundry sits. How to answer a foundry's questions about your location and ultimate parent is in the guide for IC designers, and drawings in general are in the guide to drawings and design data.
What kind of "technology" is design data?
Start with what you are actually handing over. METI's Service Transaction Circular, in its interpretation of terms at 1(3), defines technology as "specific information necessary for the design, manufacture or use of goods," provided as technical data or technical assistance. Its definition of design is long: design research, design analysis, design concepts, building and testing prototypes, pilot production plans, design data, the process of turning design data into a product, appearance design, overall design, layout, and every other stage before manufacturing. Manufacture covers construction, production engineering, productization, integration, assembly, inspection, testing and quality assurance. Technical data means blueprints, drawings, diagrams, models, formulas, design specifications, manuals, instructions and similar forms, or programs.1
Open the EAR definitions in 15 CFR 772.1 and the wording looks almost the same. "Development" covers all stages before serial production, listing "design data, process of transforming design data into a product, configuration design, integration design, layouts." "Production" covers "product engineering, manufacture, integration, assembly (mounting), inspection, testing, quality assurance." Note 1 to the definition of technology lists "engineering designs and specifications, computer-aided design files" among its forms, and Note 2 says that modifying the design of an existing item creates a new item, so technology for the modified design is technology for the development or production of the new item.2
Put side by side, I read a GDSII or OASIS layout as design technical data in Japan and as development technology under the EAR. A test program is a program in Japan and software under the EAR, and inspection and testing sit inside Japan's "manufacture" and the EAR's "production." The table is our own sorting, not a ruling on any file.
| What you hand over (examples) | Service Transaction Circular (our reading) | EAR (our reading) |
|---|---|---|
| GDSII or OASIS layout, mask order specifications | Design technology (technical data) | Development technology |
| Netlist, RTL, design specifications | Design technology (technical data) | Development technology |
| Test programs, test conditions | Program or technical data for manufacture (inspection, testing) | Production software or technology |
| Package drawings, assembly specifications | Design and manufacturing technology | Development and production technology |
| Published datasheets | Check the public-domain exception (Trade-Related Ordinance Art. 9(2), item 9) | Check published information (734.3(b)(3), 734.7) |
Technology also tends to follow the goods it is used to make. METI's guidance for universities (fifth edition) notes that, in principle, technology related to list-controlled goods is controlled, but warns that some technology is controlled on its own without a direct tie to list-controlled goods.3 Chip technology has several of these stand-alone entries, which the next section walks through.
Watch the strength of the words, too. The EAR defines "required" as only the portion of technology "peculiarly responsible" for achieving or exceeding the controlled performance levels, characteristics or functions, and even gives a 400 MHz example.2 Japan's ordinance also says "technology necessary for design or manufacture," but METI keeps its interpretation of terms in the appended table in a separate PDF referenced from Annex 1 of the circular, and I had not been able to check that original when writing this. If your data sits near a boundary, read that interpretation first.
Japan's FEFTA: is it a service transaction, and which item applies?
The overseas foundry is a non-resident
Article 25(1) of FEFTA requires a METI license for a transaction aimed at providing specified technology in a specified country, and for a transaction aimed at providing specified technology to a non-resident of a specified country.4 The circular explains the second type as one where a resident provides technology to a non-resident of a specified country "regardless of where the technical information is received."1 Whether you send the data from Japan or the foundry's engineer receives it on a visit to Japan, the counterparty's status is what counts. METI's Q&A on technology (Q1-13) says the same: even if the provision takes place in Japan, provision to a non-resident requires a check against the appended table.5
Residents and non-residents are defined in Article 6(1), items 5 and 6. A corporation with its principal office in Japan is a resident, and a Japanese branch or office of a non-resident is deemed a resident even if its principal office is abroad.4 So the foundry itself, abroad, is a non-resident, while its Japanese branch or Japanese subsidiary is a resident. For individuals, METI's university guidance (III.4) summarizes the criteria: a foreign national who works at an office in Japan, or who has been in Japan for six months or more, is a resident.3 A foundry engineer on a short business trip will normally be treated as a non-resident.
Article 17(1) of the Foreign Exchange Order defines the specified countries as the regions in the right-hand column of the appended table. For item 7, which covers chip design and manufacturing technology, that column says "all regions." For item 16 it says "all regions (excluding the regions listed in Appended Table 3 of the Export Trade Control Order)."6 Design data that falls under item 7 therefore needs a license wherever the foundry is, unless an exception in Article 9(2) of the Trade-Related Ordinance applies.
Item 7: when the IC itself is listed, and stand-alone entries
First, a numbering trap. The U.S. CCL puts electronics in Category 3, but in Japan's appended table, integrated circuits are item 7. Item 3 covers technology for goods in item 3 of the Export Trade Control Order's Appended Table 1, which are raw materials for military chemical agents and equipment for making them. It has nothing to do with semiconductors.67 If an internal classification sheet says "item 3" for a chip, question it.
Item 7(1) covers technology for the design or manufacture of goods in item 7 of the Export Order, with the scope set by Article 19(1) of the Goods and Technologies Ordinance. Item 2 of Article 19(1) covers "technology (excluding programs) necessary for the design or manufacture" of goods in Article 6, with three exclusions. Two matter for chips: ICs under Article 6, item 1, (ha) to (ru) with a minimum line width of 0.130 micrometers or more and a multilayer structure of three or fewer metal layers (ro), and process design kits, unless they include libraries implementing functions or technology of goods in Article 6, items 1 to 8-4 (ha). A process design kit (PDK), in the words of the CCL's technical note, is a software tool a semiconductor manufacturer provides so that the required design practices and rules are taken into account for a specific process.8 (Japanese ordinances label sub-items with kana, イ, ロ, ハ and so on; I write them as (i), (ro), (ha).)9 In short, if your IC falls under Article 6, item 1, its design data is, as a rule, item 7(1) technology.
Article 6, item 1 lists radiation-hardened ICs (i), microprocessors, ADCs and similar ICs designed for wide temperature ranges (ro, excluding ICs designed for civilian cars or railway vehicles), ADCs and DACs above certain performance levels (ho), FPGAs and similar devices meeting certain conditions (to), and more. Design houses tend to miss two. Under (ri), a custom IC is listed if it has more than 1,500 terminals, a basic gate propagation delay under 0.02 nanoseconds, or an operating frequency above 3 GHz; "custom IC" is defined to exclude ICs whose status under (ha) to (chi) or (ru) to (yo) can be determined. Under (yo), an IC with one or more digital processor units and a total processing performance (TPP) of 6,000 or more is listed.9 The U.S. 3A090.a thresholds (TPP of 4,800 or more, or TPP of 1,600 or more with a performance density of 5.92 or more) are different numbers, so classify for each country separately.8
Programs are handled elsewhere. Item 5 of Article 19(1) covers programs designed to design or manufacture Article 6 goods, but it excludes, among others, the ICs in Article 6, item 1.9 Read that exclusion before deciding whether a test program is item 7(1).
Even if the IC itself is not listed, item 7(3) has stand-alone entries. Picking only the ones a design house is likely to meet, Article 19(3) covers: technology necessary to design or manufacture microprocessor and similar cores with a 32-bit or wider arithmetic logic unit and certain vector or floating-point features (item 3); ECAD programs specially designed for ICs with GAAFET structures, such as those that implement RTL into GDSII or an equivalent format (item 6); programs that extract GDSII or equivalent layout data from scanning electron microscope images, align the layers and generate multilayer GDSII data or a netlist (item 7); technology necessary to design or manufacture ICs or semiconductor devices with GAAFET structures, excluding process design kits and technology used for tool qualification or maintenance (item 8); and ECAD programs for integrating multiple chips with floorplanning and similar functions, and for ICs that use multipatterning (items 9 and 10).9 Design and manufacturing technology for microwave ICs designed for telecommunications also appears in item 9(3).6
Here the two countries word things differently. The U.S. entry 3E905 (technology for ICs with GAAFET structures) says in its Related Controls that it applies to process technology at a wafer fabrication facility and does not control, for example, an IC design such as the physical layout file in GDSII format, or EDA tools.8 I could not find the same carve-out in Japan's Article 19(3), item 8 when I checked the current text on e-Gov on November 22, 2026. If you send design data for a GAAFET-node chip, settle whether that paragraph applies by reading METI's interpretation and asking METI.
Item 16: design data for ICs that are not list-controlled
If item 7 does not apply, check item 16, the catch-all. Integrated circuits appear in item 16(1)8 of Appended Table 1 of the Export Order, and Article 14-2, item 3 of the Goods and Technologies Ordinance limits that to goods under heading 85.42 of the customs tariff (excluding subheading 8542.90).79 The design, manufacturing and use technology for those goods is item 16 technology (Article 28).69
Whether a license is needed is set by Article 9(2), item 7 of the Trade-Related Ordinance. Among transactions providing technology for goods in item 16(1), those that involve no documents, media or telecommunication, and those that meet none of conditions (i) to (ni), are designated as needing no license. Sending design data to a foundry always involves documents or transmission, so a license is needed if any of (i) to (ni) applies. Conditions (i) and (ha) cover cases the METI minister defines by public notice where the technology may be used for developing weapons of mass destruction or goods in item 1 of Appended Table 1. Conditions (ro) and (ni) cover cases where the minister has notified you that you must apply, including where the risk arises because the recipient may fail to manage the information properly. For a foundry in one of the 27 countries in Appended Table 3 (including the United States, South Korea and Germany), only (ro) and (ni) apply.107 Taiwan is not in Appended Table 3, so all four conditions apply there.
Delivery methods and when the license is needed
Article 25(3) of FEFTA separately provides for licensing the export of documents or media recording specified technology, and transmissions from telecommunications equipment in Japan intended to be received abroad.4 But Article 17(3) of the Foreign Exchange Order (17(4) for item 16 technology provided to Appended Table 3 regions) excludes a person who already holds the license for the underlying transaction, and Article 9(1) of the Trade-Related Ordinance excludes transmissions tied to transactions that need no license.610 With the transaction license in hand, you do not need a new license for every transmission.
When is the technology provided? Circular 1(3)(ta) answers: "provision means placing it in a state where others can use it." Paragraph 1(4) sets the timing: before provision for data and technical assistance, and before delivery to the counterparty for data in physical form. If you export media or transmit without the transaction license, the license for that act is needed before loading onto a ship or aircraft, or before transmission.1
| Delivery method | What it is under FEFTA | When the license is needed (Circular 1(4)) |
|---|---|---|
| E-mail or file transfer to the foundry | An Article 25(1) transaction plus an Article 25(3) transmission | Before provision. No separate transmission license if you hold the transaction license (FEO Art. 17(3)) |
| Upload to the foundry's portal | Same. Provided once the foundry can use it | Before uploading |
| Giving the foundry access to your server | Placing it where others can use it (1(3)(ta)) | Before the access goes live |
| Handing over or shipping media | An Article 25(1) transaction plus export of media under Article 25(3) | Before delivery to the counterparty |
| Storing in an overseas cloud for your own use | In principle not a service transaction if storage is the only purpose (Annex 1-2(1)) | Contracting while knowing the provider can view, obtain or use the data makes it a transaction aimed at provision |
| Showing it to a visiting foundry engineer | Provision to a non-resident (Q1-13) | Before showing it |
Also pin down where the data is received. Circular 1(3)(su) says the place where the counterparty receives the technical information is the place of performance under the contract, and absent a specific provision, the counterparty's residence or principal office.1 If the foundry's Japanese subsidiary is your contact point, check in the contract and specifications which legal entity you are contracting with and which fab will actually use the data. If the Japanese subsidiary receives it and forwards it to an overseas fab, that forwarding is the subsidiary's own transaction. On the designer's side, my view is that if your contract counterparty is the overseas parent, it is safer to treat the transfer as provision to a non-resident even when the contact point is in Japan. That is our view, not METI's.
Besides individual licenses, there are bulk licenses. Circular 2(1) names the special general bulk service transaction license, the general bulk service transaction license and others, and refers to METI's bulk license handling rules, which define their scope by the "combinations of technology and place of provision" in their Appended Table B.111 For cases with no contract yet, such as sending drawings for a quote, METI's Q&A (Q4-8) takes outsourced production abroad as its example. It asks for e-mails or faxes showing the agreed quote, and notes that METI checks individually how the counterparty will manage and handle design and manufacturing technology.5
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.
The EAR: when does Japanese-made design data become subject to it?
Four routes
On the U.S. side, the first question is not the ECCN. It is whether the data is subject to the EAR at all. Section 734.3(a) lists five categories: items in the United States, U.S.-origin items wherever located, foreign-made items incorporating or commingled with controlled U.S.-origin items (for technology, foreign technology commingled with controlled U.S.-origin technology), foreign-produced direct products under 734.9, and products of a plant that is itself a direct product.12 Design data written by Japanese engineers in Japan is foreign-made technology. In practice, these are the routes that matter.
| Route | Provision | How it shows up in design data (our reading) |
|---|---|---|
| U.S. origin | 734.3(a)(2), 770.3(c)(1) | The data contains an IP block received from a U.S. vendor, or circuits developed at a U.S. site, as is |
| Commingling with U.S.-origin technology | 734.3(a)(3), 734.4(c)(3), (d)(3) | The value of controlled U.S.-origin technology copied into or drawn on exceeds the de minimis level |
| Foreign direct product | 734.3(a)(4), 734.9 | The data is a direct product of specified U.S. technology or software and itself falls in the rule's product scope |
| None of the above | Same | Not subject to the EAR, so no EAR licensing question arises for the transfer |
Section 770.3(c)(1) says U.S.-origin technology does not lose its U.S. origin when it is redrawn, used, consulted or otherwise commingled abroad, and technical data based on it is subject to the EAR like the original unless the de minimis rules take it out.13 If part of your design was co-developed with a U.S. site, start there. Sending U.S.-origin technology from Japan to a foundry in Taiwan is a reexport under 734.14(a)(1). Showing it in Japan to an engineer of another nationality can be a deemed reexport under 734.14(b), with exceptions in 734.20.12 One more check: the list in 734.4(a) of items with no de minimis level, paragraphs (1) to (9), does not include IC design technology. I checked this in the version as of November 19, 2026.
What goes into the de minimis numerator: a fictional example
The commingling route turns on the arithmetic. De minimis is the rule that takes a foreign item out of the EAR when its controlled U.S.-origin content stays at or below a set percentage. Under 734.4(d)(3), foreign technology commingled with or drawn from controlled U.S.-origin technology is not subject to the EAR for reexports to countries outside E:1 and E:2 if the U.S. content is valued at 25 percent or less of the total value of the foreign technology. Under (c)(3), the threshold is 10 percent for reexports anywhere. Either way, a one-time report must be filed before you rely on de minimis for technology.12
What counts in the numerator is set by paragraph (a)(1) of Supplement No. 2 to Part 734. Identify the ECCN of each U.S.-origin item and count only those that would need a BIS license if exported or reexported, in the form received, to the destination. Use the Commerce Country Chart (Supplement No. 1 to Part 738) and part 746, not the end-user and end-use controls in part 744. Do not count items that could go without a license (NLR) or under License Exception GBS.13
Here is a fictional case. Design company A in Japan has classified its own IC under 3A001 and sends the design data to fictional foundry B in Taiwan. Taiwan is in Country Groups A:6 and D:3, not E:1 or E:2, so the 25 percent rule applies.14
| Part of the design data | Origin and classification (fictional assumptions) | License needed to Taiwan? | In the numerator? |
|---|---|---|---|
| (1) IP block from a U.S. vendor | U.S. origin; vendor classifies it 3E991 | 3E991 is controlled for AT only (AT Column 1), and Taiwan has no X under AT 1 in the Country Chart. No license | No |
| (2) Circuit block developed by A's U.S. subsidiary in the United States | U.S. origin; A classifies it 3E001 (technology for 3A001 items, NS reason) | 3E001 NS is NS Column 1, and Taiwan has an X under NS 1. License required | Yes |
| (3) Work by A's engineers in Japan | Foreign technology | Not applicable | No (but it is in the denominator) |
If the fair market value of the whole design is JPY 120 million and part (2) is JPY 24 million, the ratio is 20 percent, at or below 25 percent. Even so, A can rely on de minimis only after filing the one-time report and hearing nothing from BIS for 30 days.13 If part (2) were JPY 36 million, the ratio would be 30 percent, the design data as a whole would be subject to the EAR, and A would need to work out whether reexporting that 3E001 technology to Taiwan requires a license or qualifies for a license exception.12814 Put part (1) into the numerator and you overstate the ratio and treat data as controlled when it is not. Leave part (2) out and you make the opposite mistake. Writing down the ECCN and the Country Chart column behind each line of the numerator prevents both.
The one-time report describes the scope and nature of the foreign technology, its fair market value with the rationale for the valuation, the destination when controlled U.S. content exceeds 10 percent, and a BIS contact person. It goes to BIS's Regulatory Policy Division, for example by e-mail to rpd2@bis.doc.gov. It does not ask about end uses or end users. If BIS contacts you within 30 days, you cannot rely on the calculation until BIS says it was done correctly.13 Keep the method you used to set the percentage in your records under part 762, and say whether the values are arm's-length market prices or derived from comparable transactions or costs (734.4(g)).12 For checking EAR applicability across a group, the EAR classification flow and EAR99 checklist is a good starting point.
De minimis for the IC as a commodity and de minimis for the design data as technology are separate calculations. Supplement No. 2 to Part 734 states that technology and source code used to design or produce foreign-made commodities are not considered incorporated into them.13 Using U.S. EDA tools does not put anything into the chip's numerator.
Design data for 3A090 chips: check the foreign direct product rule too
Design data for a 3A090 IC has one more route. The advanced computing foreign direct product rule in 734.9(h) sets the product scope as items that are the "direct product" of technology or software subject to the EAR and specified in listed ECCNs (3D001, 3D991, 3E001 and 3E991 are among them), and that are themselves specified in 3A090, 3E001 (for 3A090), 4A090 and so on. Under (h)(2)(i), the destination scope is any location worldwide.12 Section 772.1 defines a direct product as the immediate product, including processes and services, produced directly by the use of technology or software.2
So a 3A090 layout written by engineers in Japan can still be subject to the EAR if it is a direct product of specified U.S. technology or software. Whether your EDA tools fall in a listed ECCN is something to confirm from the vendor's classification. I have not found a primary source in which BIS says outright whether it treats a layout produced with U.S. EDA tools as a direct product. How to read the product and destination scopes is covered in the FDPR guide.
3E001, 3D001, and the 3A090 and 744.23 layers
Reading the 3E001 and 3D001 headings
Once design data is subject to the EAR, you classify it. 3E001 is technology, according to the General Technology Note, for the development or production of 3A items (except 3A069, 3A901, 3A904, 3A980, 3A981, 3A991, 3A992 and 3A999), 3B items (with exceptions) and 3C items (with exceptions). Its Note 2 excludes technology for ICs in 3A001.a.3 to a.14 or .z that use technology at or above 0.130 micrometers and have three or fewer metal layers. A separate note says 3E001 and 3E905 do not apply to process design kits unless they include libraries implementing functions or technologies for 3A001 items.8 That is close to the shape of exclusions (ro) and (ha) in Japan's Article 19(1), item 2.
The General Technology Note adds that technology required for the development or production of a controlled product stays controlled even when it applies to a product controlled at a lower level.2 Microprocessor core technology also has its own entry, 3E002 (32-bit or wider ALUs with certain vector or floating-point features), worded much like Japan's Article 19(3), item 3.89 3E002's Note 2 excludes cores at or above 0.130 micrometers with five or fewer metal layers; I could not find the same exclusion in Japan's item 3.
3D001 is software specially designed for the development or production of items in 3A001.b to 3A002.h, 3A090 and 3B (with exceptions).8 ICs in 3A001.a are not in that list. A GDSII layout is a computer-aided design file, one of the forms of technology named in the 772.1 note, so it is most naturally technology rather than software.2 3D001 comes in for things you hand over as software, such as test programs for 3A090 ICs. "Specially designed" is decided by the step-by-step analysis in 772.1, so classify test programs that way.
License requirements for 3E001 technology for 3A090
3E001 technology for 3A090 (other than 3A090.c) needs a license, for regional stability reasons, to or within the destinations in 742.6(a)(6)(iii)(A): (1) Indonesia, Malaysia, Singapore, Brazil and Thailand, and (2) Country Groups D:1, D:4 and D:5 (excluding countries also in A:5 or A:6) and the UAE. Paragraph (1) has an exclusion for ultimate consignees or end users headquartered in the United States, or whose ultimate parent is, provided the 743.10 reports are filed. Paragraph (2) has an exclusion where the ultimate consignee and all end users are UAE entities listed in Supplement No. 8 to Part 740 and approved for these items. 3E001 technology for 3A090.c needs a license to Macau and D:5.158 Neither Japan nor Taiwan is on these lists.14
There is more. Section 742.6(a)(6)(ii) requires a license for exports from abroad, originating in Macau or D:5, to any destination worldwide except A:5 and A:6, of 3E001 technology for 3A090 that was developed by an entity headquartered in Macau or D:5 (or whose ultimate parent is), is the direct product of software subject to the EAR, and is for the production of 3A090 and similar items. Paragraph (iv) says the license requirements in (a)(6)(i) to (iii) do not apply to deemed exports or deemed reexports.15 The 3E001 entry also says License Exception TSR is not available for technology for 3A090 items, and STA cannot be used to send that technology to A:5 or A:6.8
744.23: the fab end use and the design end use
Even with no license requirement on the CCL, the end-use controls in 744.23 remain. Paragraph (a)(2)(i) requires a license for any item subject to the EAR when you know it will be used in the development or production of ICs destined to a facility in Macau or D:5 where advanced-node ICs are produced. Paragraph (a)(2)(ii) does the same for Category 3 items in Product Groups B, C, D and E when you know they will be used for ICs at a Macau or D:5 facility that produces ICs but you do not know whether it produces advanced-node ICs. Paragraph (a)(2)(iii) covers ECAD and TCAD software and technology you know will be used to design an advanced-node IC to be produced in Macau or D:5.16 Section 772.1 defines advanced-node ICs as logic ICs with non-planar transistors or a production technology node of 16/14 nanometers or less, NAND with 128 or more layers, and DRAM meeting certain cell-area, density or through-silicon-via criteria.2
Applied to design data, that means data subject to the EAR, handed over knowing it will be used at an advanced-node fab in Macau or D:5, needs a license whatever its ECCN. BIS's FAQ of December 29, 2023 (IV.A2), answering under the rule as it then stood, said EAR99 technology is included because (a)(2)(i) covers "any item subject to the EAR."17 The current (a)(2)(i) still says "Any items subject to the EAR." There are exceptions. Paragraph (a)(2)(iv) takes items in (i) and (ii) destined to entities with a Footnote 5 designation on the Entity List out of this section's license requirements. Paragraph (a)(5) excludes back-end steps such as assembly, test and packaging that do not alter the IC technology level from "production" for (a)(2). Paragraph (c) says no license exception overcomes the prohibitions, except that (a)(4) and (a)(3)(i) may be overcome by the license exceptions in 740.2(a)(9)(i) and (ii), respectively. Under (d)(1), applications for Macau, D:5 and entities headquartered there (or with an ultimate parent there) are reviewed with a presumption of denial, unless (d)(2) or (d)(3) applies.16
Paragraph (a)(3)(ii) requires a license for 3E001 technology for 3A090 (other than 3A090.c) only when all four conditions are met: (A) it was developed by an entity headquartered in Macau or D:5, or whose ultimate parent is; (B) it is subject to the EAR under 734.9(h)(1)(i)(B)(1) and (h)(2)(ii); (C) it is for reexport or in-country transfer from or within D:1, D:4 or D:5 (excluding A:5 and A:6) to anywhere; and (D) it is for the production of 3A090 and similar items.16 Data sent from Japan does not meet condition (C).
It also helps to know what happens on the receiving end. In an FAQ dated August 16, 2022, BIS advised foundries to consider screening design files they receive (it names GDSII files) against their library of previously received designs, to see whether any approximate or match designs from a party on the Entity List.18 Expect questions about where a design came from and who you have co-developed with in the past. How to answer a foundry's questions is in the guide for IC designers.
Before you hand it over: steps and records
Seven questions before tape-out
Here is the order of checks. Do not let one country's answer stand in for the other's; record both in one place.
| Step | Question | Japan (FEFTA) | United States (EAR) |
|---|---|---|---|
| 1 | What is the IC? | Goods and Technologies Ordinance Art. 6, item 1, (i) to (yo) | ECCN (3A001, 3A090, 3A991 and so on) |
| 2 | What technology is the design data? | Item 7(1) (Art. 19(1)), item 7(3) (Art. 19(3)), item 9(3), otherwise item 16 | 3E001, 3E002, 3E991, 3D001 and so on, if subject to the EAR |
| 3 | Who is the counterparty? | Non-resident or not, place of performance, user | Country group of the location, headquarters and ultimate parent headquarters, list entries |
| 4 | Is the data subject to the EAR? | Not applicable | U.S. origin, commingling and de minimis, 734.9 |
| 5 | Is a license needed? | Individual or bulk (Appended Table B); for item 16, conditions (i) to (ni) of Art. 9(2), item 7 | Country Chart, 742.6(a)(6), 744.23, license exceptions |
| 6 | How and when is it delivered? | Before provision; media before delivery (1(4)) | Reexport, release, encrypted storage (734.18(a)(5)) |
| 7 | What is kept on file? | Classification sheet, license, application attachments | Classification basis, de minimis calculation, report copies |
A word more on step 6 for the U.S. side. Section 734.15 treats visual inspection by a foreign person and oral or written exchanges as a "release," and says an act that causes a release through access information requires the same authorization. Section 734.19(a) requires comparable authorization to transfer access information with knowledge that it will result in an unauthorized release. On the other hand, 734.18(a)(5) says sending, taking or storing technology that is unclassified, secured with end-to-end encryption and FIPS 140-2 (or successor) cryptographic modules, and not intentionally stored in a D:5 country, is not an export or reexport.12 Encrypted storage is not an export in itself, but plan on the release happening when you give the foundry the means to decrypt or permission to view. The line looks a lot like Japan's Annex 1-2 on storage.
What to record for each transfer
Building the record from Japan's application documents and the EAR's recordkeeping rules leaves fewer gaps. Annex 3 of the circular lists, as attachments to a service transaction license application, a statement of reasons, a transaction summary, a description of the technology, a comparison table against the appended table, copies of contracts and similar documents, and a copy of an undertaking not to retransfer the technology (some can be omitted depending on the case). The transaction summary form has a field for "sales regions of products manufactured using the technology (for design or manufacturing technology)."1
| Item | Example entry (fictional) |
|---|---|
| IC and data version | Company A IC model X, GDSII version number and hash, tape-out date |
| Japanese classification | Item and sub-item number in the appended table and article, paragraph and item of the ordinance, or non-listed plus the item 16 check |
| U.S. classification | Subject to the EAR or not, and by which route. ECCN if subject |
| Counterparty and user | Company B (contract party), Company B's fab (user), locations, country groups, headquarters and ultimate parent headquarters |
| Place of performance and delivery | Place of performance, portal upload, date and time, who sent it |
| License or basis for no license | License number, or the article of the Trade-Related Ordinance, or the NLR basis |
| De minimis calculation | ECCN and Country Chart column for each numerator line, values and their basis, one-time report filing date |
| Approver | Name of the export control officer and approval date |
On retention, METI's introductory guidance (version 3.0) asks companies to keep documents for items 5 to 16 for at least five years from the export or technology provision (at least seven years for items 1 to 4).19 The EAR requires five years from the latest of the times in 762.6(a), and the de minimis method must also be kept under part 762.2012 For screening the counterparty, the five sanctions-list systems screening procedure shows where and how to check each list.
Add a clause on how the recipient handles the data. One version: "The Recipient shall use the Design Data solely for the manufacturing and testing described in this Agreement, shall not disclose it to any third party without the Provider's prior written consent, and shall handle it in compliance with the Foreign Exchange and Foreign Trade Act of Japan, the U.S. Export Administration Regulations and other applicable laws." This is our own wording, so have your legal team review it before use.
What I could not confirm
As of November 22, 2026, these points remain open for me. Whether an individual IC layout is "technology necessary for the design or manufacture of ICs with GAAFET structures" under Article 19(3), item 8, and whether Japanese practice has a carve-out like the U.S. 3E905 note. The original text of METI's separate interpretation of terms such as "necessary." Whether BIS treats a layout produced with U.S. EDA tools as a direct product. A METI Q&A that addresses design data for foundries head-on (in my search, Q4-8 on outsourced production is the closest). How a transfer through a foundry's Japanese subsidiary should be treated (the text above gives our view). The law of the foundry's country. The interim final rule of November 19, 2026 (91 FR 74970) is open for comments until January 19, 2027, and its text may change afterwards.21 I will update this article when new facts come in.
Summary
- An overseas foundry or OSAT is a non-resident. Sending it design data can be an Article 25(1) transaction, and any license is needed before the foundry can use the data.
- In Japan, check items 7 and 16: Article 19(1) if the IC falls under Article 6, item 1, Article 19(3) for GAAFET and similar entries, and otherwise item 16 with Article 9(2), item 7 of the Trade-Related Ordinance.
- The EAR applies through U.S. origin, commingling above de minimis, or a foreign direct product rule. Count only U.S.-origin technology that needs a license to the destination, and file the one-time report before relying on technology de minimis.
- If the data is subject to the EAR, check 3E001, 3D001 and 742.6(a)(6), and 744.23(a)(2) for advanced-node fabs in Macau or D:5.
If I had to pick one thing to do before tape-out, it would be listing the U.S.-origin parts of the design: who supplied each IP block, which circuits a U.S. site wrote, and how your EDA tools are classified. The de minimis numerator and the foreign direct product check both start from that list. Keep it in the same ledger as your answers to the foundry's questions, and the explanation six months later is much easier. For screening counterparties and keeping a record of each decision, you can use TRAFEED; you can reach us here.
Read next
- When a foundry asks for your location and ultimate parent: why foundries ask IC designers, with reply templates in Japanese and English.
- ECCN 3A090 in practice: TPP, performance density and transistor count calculations.
- The foreign direct product rule: product scope and destination scope.
- Reexports from overseas subsidiaries: checks by site, including the technology de minimis report.
- Is remote GPU access an "export"?: service transactions, remote access and Annex 1-2.
- Drawings and design data: classification of drawings in general and deemed exports.
Footnotes
-
METI, Service Transaction Circular (4 Bokyoku No. 492; last amended by Export Notice 2025 No. 27, promulgated November 14, 2025 and effective February 14, 2026). https://www.meti.go.jp/policy/anpo/law_document/tutatu/t10kaisei/ekimu_tutatu.pdf . We checked 1(1), 1(2), 1(3), 1(4), 2(1), Annex 1 (the separate interpretation PDF not checked), Annex 1-2, Annex 3 and Reference Form 2 in a copy obtained on November 20, 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6
-
eCFR, 15 CFR 772.1 (Development, Production, Technology and its Notes 1 and 2, Software, Program, Required, Direct product, Advanced-Node Integrated Circuits) and Supplement No. 2 to Part 774 (General Technology Note). 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-772/section-772.1 ↩ ↩2 ↩3 ↩4 ↩5 ↩6
-
METI, Guidance on Sensitive Technology Management for Universities and Research Institutions, fifth edition (September 2025). https://www.meti.go.jp/policy/anpo/daigaku/guidance5.pdf . Sections III.3 and III.4 (residency criteria based on Ministry of Finance notice No. 4672), checked in a copy obtained on November 20, 2026. ↩ ↩2
-
Foreign Exchange and Foreign Trade Act (Act No. 228 of 1949), Article 6(1), items 5 and 6, and Article 25(1) and (3). e-Gov: https://laws.e-gov.go.jp/law/324AC0000000228 . We retrieved and checked the current version (as amended by Act No. 64 of 2026, effective August 12, 2026) through the e-Gov law API v2 on November 22, 2026. ↩ ↩2 ↩3
-
METI, Q&A on technology (last updated April 23, 2026). https://www.meti.go.jp/policy/anpo/qanda25.html . Q1-12, Q1-13, Q3-1 and Q4-8, checked in a copy obtained by browser on November 21, 2026. ↩ ↩2
-
Foreign Exchange Order (Cabinet Order No. 260 of 1980), Article 17(1) to (4) and (8), and the appended table (items 3, 7, 9 and 16). https://laws.e-gov.go.jp/law/355CO0000000260 . Current version (as amended by Cabinet Order No. 296 of 2026, effective September 16, 2026), checked on November 22, 2026. ↩ ↩2 ↩3 ↩4 ↩5
-
Export Trade Control Order (Cabinet Order No. 378 of 1949), Appended Table 1 items 3, 7 and 16, and Appended Table 3. https://laws.e-gov.go.jp/law/324CO0000000378 . Current version (as amended by Cabinet Order No. 325 of 2026, effective October 16, 2026), checked on November 22, 2026. Appended Table 3 lists 27 countries and does not include Taiwan. ↩ ↩2 ↩3
-
eCFR, Supplement No. 1 to Part 774 (Commerce Control List), ECCNs 3A090, 3D001, 3E001 (Notes 1 and 2 and the PDK note), 3E002, 3E905 (Related Controls) and 3E991. 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-774/appendix-Supplement%20No.%201%20to%20Part%20774 ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9
-
Ministerial Ordinance Specifying Goods and Technologies (MITI Ordinance No. 49 of 1991), Article 6, item 1; Article 14-2, item 3; Article 19(1) and (3); Article 28. https://laws.e-gov.go.jp/law/403M50000400049 . Current version (as amended by METI Ordinance No. 72 of 2025, effective February 14, 2026), checked on November 22, 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7
-
Ordinance on Trade-Related Transactions Other Than Trade (MITI Ordinance No. 8 of 1998), Article 9(1) and Article 9(2), items 7, 9 and 12. https://laws.e-gov.go.jp/law/410M50000400008 . Current version (as amended by METI Ordinance No. 71 of 2025, effective November 15, 2025), checked on November 22, 2026. ↩ ↩2
-
METI, Bulk License Handling Rules (last amended by Export Notice 2025 No. 27), scope of the general and special general bulk service transaction licenses (Appended Table B). https://www.meti.go.jp/policy/anpo/law_document/tutatu/tutatu24fy/houkatu_toriatukaiyouryou.pdf . Checked in a copy obtained on November 20, 2026. ↩
-
eCFR, 15 CFR 734.3, 734.4, 734.9(h), 734.13 to 734.15, 734.18, 734.19 and 734.20. 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-734 ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8
-
eCFR, Supplement No. 2 to Part 734 (Guidelines for De Minimis Rules, paragraphs (a)(1), (a)(2) and (b)) and 15 CFR 770.3(c)(1). 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-734/appendix-Supplement%20No.%202%20to%20Part%20734 ↩ ↩2 ↩3 ↩4 ↩5
-
eCFR, Supplement No. 1 to Part 740 (Country Groups: Japan is in A:1 to A:5; Taiwan is in A:6 and D:3) and Supplement No. 1 to Part 738 (Commerce Country Chart: Taiwan has an X under NS 1 and none under AT 1). 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-738/appendix-Supplement%20No.%201%20to%20Part%20738 ↩ ↩2 ↩3
-
eCFR, 15 CFR 742.6(a)(6)(i)(B), (ii), (iii)(A) and (iv). 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-742/section-742.6 ↩ ↩2
-
eCFR, 15 CFR 744.23(a)(2), (a)(3), (a)(5), (c) and (d). 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-744/section-744.23 ↩ ↩2 ↩3
-
BIS, "Frequently Asked Questions (FAQs) for 'Export Controls on Semiconductor Manufacturing Items' (SME IFR) and 'Implementation of Additional Export Controls: Certain Advanced Computing Items; Supercomputer and Semiconductor End Use; Updates and Corrections' (AC/S IFR)," FAQ date December 29, 2023, IV.Q2 and IV.A2. https://media.bis.gov/media/documents/2023-frequently-asked-questions-003-clean-posting.pdf . Retrieved and checked on November 22, 2026. ↩
-
U.S. Department of Commerce, Bureau of Industry and Security (BIS), FAQ dated August 16, 2022, "If I am a semiconductor foundry, are there any special red flags...". https://media.bis.gov/media/documents/2022-faq-foundries-red-flags.docx0812clean.pdf . Retrieved and checked on November 22, 2026. ↩
-
METI, Security Export Control Guidance (introductory edition), version 3.0 (March 2026), p. 55, document retention. https://www.meti.go.jp/policy/anpo/guidance/guidance.pdf . Checked in a copy obtained on November 20, 2026. ↩
-
eCFR, 15 CFR 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 ↩
-
BIS, interim final rule "Addressing Remote Access to Advanced Semiconductors," 91 FR 74970, published and effective November 19, 2026. DATES (comments due January 19, 2027) checked in the GPO version. https://www.federalregister.gov/documents/2026/11/19/2026-23529/addressing-remote-access-to-advanced-semiconductors ↩





![Japan's Certificate of Non-Applicability Explained — What Foreign Suppliers Must Provide Japanese Buyers [Feb 14, 2026 Update]](/images/columns/non-applicable-certificate-guide/cover.en.png?dpl=dpl_BPWm5yhB81qA89XEG88chasQfGZN)