TIMEWELL
Solutions
Free ConsultationContact Us
TIMEWELL

Unleashing organizational potential with AI

ISO/IEC 27001 (ISMS) certification mark (SGS / ISMS-AC)

ISO/IEC 27001:2022 certified Certificate No. JP26/00000255 Scope: Planning, development and operation of SaaS products utilizing AI technology

Services

  • ZEROCK
  • TRAFEED
  • TIMEWELL BASE
  • WARP
  • WARP 1Day
  • WARP NEXT Corporate
  • WARP BASIC
  • WARP ENTRE
  • Alumni Salon
  • WARP for Schools
  • Alumni Ventures
  • FDE
  • AI Consulting
  • EMC GLOBAL

Company

  • About Us
  • Team
  • Why TIMEWELL
  • News
  • Contact
  • Free Consultation

Content

  • Insights
  • Knowledge Base
  • Case Studies
  • Whitepapers
  • Events
  • Solutions
  • AI Readiness Check
  • ROI Calculator

Legal

  • Privacy Policy
  • Manual Creator Extension
  • WARP Terms of Service
  • WARP NEXT School Rules
  • Legal Notice
  • Security
  • Anti-Social Policy
  • ZEROCK Terms of Service
  • TIMEWELL BASE Terms of Service

Newsletter

Get the latest AI and DX insights delivered weekly

Your email will only be used for newsletter delivery.

© 2026 株式会社TIMEWELL All rights reserved.

Contact Us
HomeTRAFEED MediaScreening Entity List Address-Only Entries: Testing and Documenting Your Screening Tool Settings
TRAFEED Media

Screening Entity List Address-Only Entries: Testing and Documenting Your Screening Tool Settings

Published2026-11-22Checked against sources2026-11-22Ryuta Hamamoto
Export ControlsEntity ListRestricted Party ScreeningAddress ScreeningScreening SoftwareBISSettlement OrdersLarge EnterprisesExport ComplianceTRAFEED

The U.S. Entity List has 19 entries that list only an address, with no company name (eCFR as of November 19, 2026). This piece covers the June 2024 rule and how 15 CFR 744.11 and 744.16 work, why name-only screening misses these entries (settlement E3047), eight tests to confirm your screening tool settings with a record template, and how to re-screen past shipments.

Screening Entity List Address-Only Entries: Testing and Documenting Your Screening Tool Settings
Share

Hello, this is Ryuta Hamamoto from TIMEWELL.

When your team screens thousands of counterparties a month, nobody goes back over the results that came back clean. Here is the catch. The U.S. Entity List has 19 entries that list only an address, mostly in Hong Kong, with no company name, and the name field of each one holds a label like "Address 04." If your tool compares customer names, it cannot hit these entries at all. So my advice is simple: do not stop at asking your vendor. Run your own tests using the address strings that are actually on the list, and keep a record of what you found.

The short version

  1. Address-only entries come from 15 CFR 744.16(f), added by a rule that took effect on June 12, 2024. When an entity using a listed address is a party to the transaction (purchaser, intermediate consignee, ultimate consignee or end user), the license requirement in that entry applies. As of the November 19, 2026 eCFR there are 19: 18 Hong Kong addresses under China and one under Turkey.
  2. In settlement E3047, a company that had checked with its screening software vendor still shipped eight times to a Hong Kong address on the list. A vendor's answer does not tell you whether your own configuration actually screens addresses.
  3. The way to find out is to test with the listed address strings and variations of them, and to record the results along with the list version. Re-screen past shipments from each address's effective date.

This piece does not evaluate the buildings that appear on the list or any business operating in them. Placement on the Entity List is a regulatory designation under the Export Administration Regulations (EAR). It is not a judgment on the building owner, on other tenants in the same building, or on any counterparty. The introductory text of 744.11 itself says BIS may remove an address once it is no longer a high diversion risk, for example if companies operating at the address are educated on export compliance or if clients are effectively screened for diversion risk1. I quote address strings only to show how to test a screening tool, and only as they appear in the official text.

What an address-only entry is: the June 2024 rule and the roles of 744.11 and 744.16

Address-only entries began with a final rule that BIS (the Commerce Department's Bureau of Industry and Security) published in the Federal Register on June 18, 2024 (89 FR 51644, document number 2024-13148). The rule was mainly about additional measures against Russia and Belarus, and the address entries were one part of it. Its DATES line reads: "This rule is effective on June 12, 2024, except for amendatory instruction 14, which is effective September 16, 2024." Instruction 14 amends 746.8 and has nothing to do with the address entries. The rule went on public inspection at 10:30 a.m. Eastern Daylight Time on June 12, the same day it took effect. In other words, the address entries were in force six days before they appeared in the printed Federal Register2.

Why list addresses at all? Section II.C of the preamble ("Additions to the Entity List and Changes to the Entity List Structure") points to shell companies. Because they lack non-cash assets, employees, fixed addresses and business reputations, the preamble says, they can be dissolved and re-formed easily to evade controls, and they rely on service providers for addresses that can go on corporate paperwork, mailboxes, temporary office space and similar services. BIS had traditionally avoided listing those service providers by name, because that name does not appear on export paperwork and may remain unknown to the seller. Yet some of these addresses show up again and again on the Entity List or the Unverified List under different company names, and conventional, name-by-name additions cannot always deal with that2.

That is where 744.16(f) comes in. It says that in limited circumstances, such as when multiple entities on the Entity List use the same address or when BIS does not know the name of the entity at a particular address, BIS may determine that the address presents a high risk of diversion and publish it without an associated entity name. Such an entry applies the license requirements, license review policy and restrictions on license exceptions to all entities using that address. When applying for a license, the applicant should name the specific entity on the application and state in the additional-information field that the address is on the Entity List3. The preamble adds two points: an entity that has its own separate entry at the same address is governed by that more specific entry, and address-only entries are titled "Address #," numbered in sequence for each destination2.

Other paragraphs of 744.16 were rewritten to cover addresses too. Paragraph (a) says you may not export, reexport or transfer (in-country) the items in an entry's license requirement column without a BIS license when an entity associated with that entry, or any entity using a high-diversion-risk address associated with it, is a party to the transaction as described in 748.5(c) through (f). Those paragraphs define the purchaser (c), intermediate consignee (d), ultimate consignee (e) and end user (f)4. The fact that the intermediate consignee is included matters a great deal when you decide which fields to screen. Paragraph (b) bars license exceptions, except for license exceptions for items listed in 740.2(a)(5) going to listed Indian or Pakistani entities for civil aviation safety, and, for entities added under 744.20, to the extent specified on the Entity List. The June 2024 rule also revised paragraph (e) so that the owner or operator of a listed address may request removal or modification. A second sentence on 50-percent-owned affiliates was later added to the introductory text of (e) by a September 2025 rule (90 FR 47201), and as of the November 19, 2026 eCFR that introductory text carries a note that it is stayed until January 10, 202723.

Section 744.11 is the legal basis for imposing these requirements. Its introductory text says the license requirements, limits on license exceptions and review policies are imposed by adding an entity, or an address that presents a high diversion risk (see 744.16(f)), to the Entity List with a reference to that section. Paragraph (a) brings "any entity using an address identified on the Entity List as presenting a high risk of diversion" within the license requirement, and paragraph (b) includes parties operating at such an address in the criteria for listing. Paragraph (c) lets BIS inform persons, by specific notice or through an amendment to the EAR, that a license is required for transactions involving a high-diversion-risk address1. All four rules that added address entries say in their preambles that the activities at those addresses are contrary to U.S. national security and foreign policy interests under 744.1125. Put simply, 744.11 covers why and on what criteria an entry is added, and 744.16 covers what the entry requires. One small trap: in the November 19, 2026 eCFR the heading of 744.11 does not mention addresses. The address language sits in the introductory text and in paragraphs (a), (b) and (c)1.

Here are the address-only entries by the rule that added them. The license review policy for all 19 is "Presumption of denial"65.

Federal Register (document no.) Public inspection Published Effective Address-only entries added License requirement in the entry (verbatim)
89 FR 51644 (2024-13148) June 12, 2024 June 18, 2024 June 12, 2024 Addresses 01-08 under China (eight in Hong Kong) For items on the CCL and listed in supplement no. 7 to part 746 of the EAR
89 FR 68544 (2024-19130) Aug. 23, 2024 Aug. 27, 2024 Aug. 27, 2024 Addresses 09-11 under China (three in Hong Kong); Address 01 under Turkey (one in Istanbul) For items on the CCL and EAR99 items listed in supplement no. 7 to part 746 of the EAR
89 FR 87261 (2024-25411) Oct. 30, 2024 Nov. 1, 2024 Nov. 1, 2024 Addresses 12-15 under China (four in Hong Kong) Same as above
90 FR 48193 (2025-19508) Oct. 8, 2025 Oct. 9, 2025 Oct. 8, 2025 Addresses 16-18 under China (three in Hong Kong) Same as above

The license requirement covers items on the Commerce Control List (CCL) and items listed in Supplement No. 7 to Part 746. That supplement lists, by six-digit HTS code, the items that need a license under 746.6 (the temporarily occupied Crimea region of Ukraine), 746.7 (Iran) and 746.8 (Russia or Belarus), and those items are a subset of ECCN-classified items and EAR99 items7. Put the other way around, an EAR99 item that is not in Supplement No. 7 is outside the license requirement of these entries, although another provision may still require a license. Of the 19 entries in the November 19, 2026 eCFR, the newest are the three from October 20256. BIS's own guidance page also says the Entity List identifies addresses associated with significant transshipment of sensitive items to countries of concern8.

Why name screening will not stop it: reading settlement E3047

The settlement order BIS issued on February 26, 2026 (case E3047) covers 19 violations by a U.S. maker of thermal imaging cameras and its affiliates. The company admitted the conduct described in the proposed charging letter and settled for a civil penalty of $1,000,000. Eight of the 19 charges (Charges 12 to 19) were shipments to an address-only entry9.

According to the proposed charging letter, one of the affiliates exported thermal cameras classified under ECCN 6A993.a eight times, from on or about June 19, 2024 to on or about December 12, 2024, to an address identified on the Entity List as requiring a license for export. That address was Address 04 in Hong Kong, added by the June 2024 rule. ECCN 6A993 is controlled for AT (anti-terrorism) reasons only. In the Commerce Country Chart (Supplement No. 1 to Part 738) as of June 19, 2024, when the shipments began, there was no row for Hong Kong, and the AT1 column in the China row was blank10. Looking only at the classification and the country chart, the combination looks like it needs no license. Paragraph 20 of the charging letter says, however, that under 744.16 and as specified on the Entity List, a license was required to export items on the CCL to Address 04. The first shipment, dated June 19, 2024 in the schedule of violations, went out the day after the rule was published9.

The charging letter also describes the screening software. Soon after the rule was published, the company asked its screening software vendor to confirm that the software would screen transactions involving the address-only entries. The vendor said it was aware of the new entries and was addressing them internally, and it issued a customer alert in or about August. Even so, it was February 2025 when an employee first identified a notification for a transaction involving Address 04, noting that the license requirement had been in place since June 2024, and reported it to the trade compliance department. The voluntary self-disclosure followed shortly after9. One detail if you go looking for the rule: the charging letter cites it as "81 Fed. Reg. 51644, 51648," but the rule is at 89 FR 5164429.

The order does not say which setting caused the miss. What follows is my own reading. Name-only screening can miss address-only entries in at least four ways, and each one can be checked against the list itself611.

How it gets missed What the official data shows What to check in your tool
The name field is a number In both the CSL files and the BIS Entity List CSV, the name field of these entries reads "Address 01" through "Address 18" Is there a setting that compares party addresses with the list's address field?
Country handling Supplement No. 4 places the Hong Kong addresses under "CHINA, PEOPLE'S REPUBLIC OF." The CSL carries both CN and HK country codes, and the BIS CSV carries two rows, China and Hong Kong Does filtering candidates by the counterparty's country drop Hong Kong addresses?
Spelling variants One commercial building appears in five entries (Addresses 05, 06, 13, 17 and 18) as "Fa Yuen Street," "Fayuen Street" and "Fayuen St," with "Centre" and "Center," and "Flat/RM," "Office," "Room" and "Rm." Your normalization rules and the address match threshold
Repeated numbers "Address 01" exists under both China and Turkey Do false-positive suppressions or deduplication rely on the name alone?

The name field also affects how people use the CSL. The trade.gov page describes the CSL search engine as letting users type in a name, country or source agency, and the "Fuzzy Name Search" it offers is a name search12. If your staff check counterparties by typing company names into the search box, address-only entries will never come up. The CSL downloadable files do include addresses, so address screening has to run on those files or on a screening tool that imports them.

International guidance points the same way. The guidance for industry issued by the G7 Sub-Working Group on Export Control Enforcement, whose members include Japan, recommends running transaction parties against public sanctions lists by separately running both the name and the address. Where an address hits but a company name does not, it recommends additional due diligence, and it notes that an address matching a public list may indicate the use of shell companies or trust and company service providers, commonly called company secretaries13. The June 2024 preamble also says that when a party to a transaction uses the same address as a listed entity, the address is a red flag, and the exporter must do enough due diligence to verify that the co-located entity is not in fact the listed entity and is not acting on its behalf2. So address screening is not only about address-only entries. It also catches counterparties sitting at the same address as a named entry. I walk through catching address additions and removals in a weekly diff in the weekly Entity List and SDN tracking piece.

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.

Download Product CatalogContact About TRAFEED

Eight tests to confirm your screening tool settings yourself

In E3047 the company had asked its vendor, and the vendor had sent out an alert. The order does not say why the miss still happened. In general, though, a vendor's answer tells you how the product handles something. It does not tell you which of your own master data fields are compared, under which rules, with which rows of the list. Field mapping, country filters, match thresholds and suppression lists are all your settings. The only way to know is to test on your own screens, in your own workflow.

There are five steps. First, create test counterparties with clearly fictitious names such as "TEST-ADDR-01 Limited," and either flag them so they cannot be used for orders or shipments or build them in a test environment. Second, count the address-only entries in your tool. The November 19, 2026 eCFR has 19 (18 under China, one under Turkey), so your tool should also have 19, each with its effective date and Federal Register citation6. Third, run the eight tests below. Fourth, record the results and the list version at the time. Fifth, report any failed test to the vendor and decide on an interim check until it is fixed.

The test inputs are address strings taken verbatim from Supplement No. 4, plus variations of them6. Every test uses a fictitious counterparty name.

No. Address to enter What it checks Expected result
T1 Room 803, Chevalier House 45-51, Chatham Road South, Tsim Sha Tsui, Hong Kong (the verbatim string of Address 04) Does the exact string hit? Hit on Address 04
T2 ROOM 803 CHEVALIER HOUSE 45-51 CHATHAM RD SOUTH TSIM SHA TSUI HONG KONG (capitals, no punctuation, Road as Rd) Normalization of case, punctuation and abbreviations Hit on Address 04
T3 Office 4, 16/F Ho King Commercial Centre, 2-16 Fa Yuen Street, Mong Kok, Kowloon, Hong Kong (Address 06 with "Fayuen" changed to "Fa Yuen" and district names added) Street-name spelling variants Hit on Address 06
T4 Room 1605A, Ho King Commercial Centre, 2-16 Fayuen St, Mong Kok, Kowloon, Hong Kong (Address 17 with "Rm." as "Room" and Center as Centre) Room labels and building-name spelling Hit on Address 17. If Address 18 (Room 1605) also appears as a candidate, are the two shown separately by room number?
T5 The T1 address with only the room number changed to one that is not listed A different room in the same building Not auto-cleared; routed for review
T6 No: 52 Hasat Sk., Kamara Iç Kapi No: 1, Merkez Mah., Sisli, Istanbul, 34381, Turkey (Address 01 under Turkey) Numbers that repeat across countries, and characters such as ç Hit on Turkey's Address 01, shown separately from China's Address 01
T7 The T1 address entered only in the ship-to and freight forwarder fields of an order, not in the counterparty's registered address The range of fields screened (parties under 748.5(c)-(f)) Hit in both fields
T8 The T1 address with the country code set to HK, and again set to CN Country filtering Hit both times

On T6: the eCFR text writes "Iç," while the CSL and the BIS CSV write "Ic"611. The same address can change shape depending on which source you import. T5 has no answer in the regulation. The entries go down to the room number, and in the regulatory text and preambles I read I found nothing on how to treat a different room in the same building. Even so, I would route a building-level match for review and ask whether the counterparty receives mail or goods at the listed room. The whole reason address entries exist is that shell companies use the addresses of service providers. If the review shows it is a different business, write down the basis and close it.

Pass or fail is straightforward. If T1 to T4 and T6 to T8 hit and T5 goes to review, the configuration passes. If any test fails, tell the vendor in writing. Until it is fixed, check new orders with Hong Kong or Turkey addresses by hand against the 19 entries in the BIS Entity List CSV before shipment, and record that you did. Once it is fixed, run all eight tests again. Rerun them whenever the vendor updates the product or your settings, whenever BIS adds or changes address entries, and whenever the address fields in your order or shipping systems change. Even if nothing changes, I would run them once a quarter. Templates for per-screening records, a list ledger and name-matching rules are in the counterparty screening record kit (Excel, in Japanese). If you add the count and version of address-only entries to its list ledger sheet (「リスト台帳と再照合」) and your address normalization rules to its name-matching sheet (「名寄せルール」), you can keep this test record in the same ledger.

Confirming with your vendor, and a record template for the settings check

Before testing, put your questions to the vendor in writing. The company in E3047 had also asked its vendor. If the exchange is going to serve as a record, it should be a dated question and a dated answer, not a phone call or a banner in the product. Ask the same things you are about to test. If the answers and your test results disagree, that disagreement is itself something to fix.

Template (inquiry to your screening software vendor; replace names and dates with your own)

Inquiry about address screening This is ___ from the export control team at ___. Please answer the following seven questions in writing regarding your handling of Entity List address-only entries (15 CFR 744.16(f)).

  1. How many address-only entries are in your list? Our count is 19 in the eCFR as of November 19, 2026 (18 under China, one under Turkey).
  2. Which of our master data fields (registered address, bill-to, ship-to, freight forwarder, end user) are compared with these entries? Please also confirm that the setting does not compare only the name field.
  3. What normalization do you apply to addresses (case, punctuation, abbreviations, spelling variants, room and floor labels, characters such as ç), and what is the match threshold?
  4. Are Hong Kong addresses screened under country code CN, HK or both? If candidates are filtered by country, can Hong Kong addresses be dropped?
  5. "Address 01" appears under both China and Turkey. Are false-positive suppressions registered by an identifier for each list entry rather than by name?
  6. For rules that take effect before Federal Register publication, can you provide a record of both the effective date and the date and time the entry was added to your list?
  7. How and when will you notify us of list updates and setting changes? We would appreciate your reply by ___.

Question 6 is there for rules like the June 2024 one, which took effect before it was printed in the Federal Register2. The answer lets you check later whether anything shipped in the gap before the entry reached your vendor's list.

Once you have checked the settings, record the following. A good target is to be able to hand an auditor or inspector both the vendor's written answer and this record when asked "when, against which version of the list, and what did you check?"

Item What to write Example (fictitious)
Date, checker, approver Date, names and titles November 25, 2026; ___, export control team; ___, manager
Tool and settings version Product, version, settings version ___ (version .), settings v3
List version CSL Entity List source update and import timestamps, or the BIS CSV update time CSL source_last_updated 2026-08-21T20:19:33Z, last_imported 2026-11-22T03:15Z
Count of address-only entries Expected count and count in the tool Expected 19, tool 19
Fields screened Master data fields actually compared Registered address, bill-to, ship-to, freight forwarder, end user
Test results Results for T1 to T8, with screenshots T1-T4 and T6-T8 hit; T5 routed for review
Handling of failures Notice to vendor, interim check None
Vendor's answer Date and gist of the written answer Answer dated November 20; Q1-5 and Q7 answered, Q6 pending
Next check Date and triggers for an earlier check End of February 2027, or earlier if address entries change or the tool is updated

The list-version values in the example are what the CSL file I downloaded on November 22, 2026 actually showed, in UTC11. The BIS Entity List CSV also showed August 21, 2026 as its last update.

Template (settings check record; replace the numbers with your own)

Screening tool settings check: November 25, 2026 Checked by ___, export control team. Approved by ___, export control manager. Scope: screening tool ___ (version ., settings v3). List version: CSL Entity List last updated August 21, 2026 (UTC), imported November 22. Results: 19 address-only entries in the tool (19 expected). Seven of the eight tests hit as expected, and T5 (another room in the same building) went to the review queue. T8 hit under both HK and CN. Conclusion: address screening is running on five fields: registered address, bill-to, ship-to, freight forwarder and end user. Open items: the vendor will answer Q6 (rules effective before publication) by December 10. Next check at the end of February 2027, or earlier if address entries change or the tool is updated.

The full set of fields for screening decision records, and the idea of registering suppressions as a pair of "counterparty ID" and "list entry ID," are in the counterparty screening operations design piece. For address-only entries, make the "list entry ID" the country plus the number (for example, "Turkey, Address 01") or the CSL row identifier, not the name.

Re-screening past shipments

Whether your tool passed or failed, it is worth re-screening the shipments that went out before address screening was in place. In E3047, about eight months passed between the first shipment and the employee's discovery9. The period runs from each address's effective date to today.

Address-only entries Re-screen from (effective date)
Addresses 01-08 under China June 12, 2024
Addresses 09-11 under China; Address 01 under Turkey August 27, 2024
Addresses 12-15 under China November 1, 2024
Addresses 16-18 under China October 8, 2025

Set the dates by the Federal Register effective date. Point-in-time versions of the eCFR switch over on the publication date. When I checked, the June 15, 2024 version of 744.16 did not yet have paragraph (f), and it appeared from the June 18 version. For the October 2025 rule, too, the eCFR version date is October 9, the publication date, rather than the October 8 effective date314. If you rely on eCFR versions alone, you will leave out shipments from June 12 to 17, 2024. There is one more wrinkle. A July 18, 2024 interim final rule on standards-related activities (89 FR 58265) inadvertently reverted the address language in 744.11, 744.16 and Supplement No. 4, and BIS restored it in a correction on July 25 (89 FR 60302)15. The July 20, 2024 eCFR version of 744.16(a) indeed lacks the address language3. I have not taken a view on how to read the text in that week, so I would not exclude it from the re-screen.

What you need is the address of every party to each shipment. Pull the addresses of the purchaser, intermediate consignee, ultimate consignee and end user under 748.5(c) through (f), not just from order records but also from invoices, air waybills and bills of lading, packing lists and delivery instructions. If a counterparty's master address has since been changed, use the address as of the shipment date. If overseas affiliates reexported or transferred items subject to the EAR, include those shipments too.

Run the match in bulk with the same normalization rules as T1 to T8, and sort the results into "room-level match," "building-level match" and "no match." For each room-level match, check these five questions in order.

  1. Was the shipment on or after that address's effective date?
  2. Was the item subject to the EAR? (This depends on U.S. origin, the share of incorporated U.S.-origin content, the foreign direct product rules and so on. Items made in Japan can be subject.)
  3. Was the item within the entry's license requirement (items on the CCL and items listed in Supplement No. 7 to Part 746)?
  4. Was the party using that address a party to the transaction under 748.5(c) through (f)?
  5. Was a license obtained? (No address-only entry authorizes any license exception.)

If a shipment meets all five, escalate it to the responsible manager that same day, stop further shipments to the address and preserve the records. The next steps, including a voluntary self-disclosure under 764.5, are in the self-disclosure section of the piece on reading BIS settlement orders as a self-assessment. For checking site by site whether items are subject to the EAR, the overseas site EAR check sheet (「海外拠点 EAR点検表」) in the group and overseas site governance set (Excel, in Japanese) will help, and the thinking behind it is in the piece on reexports from overseas sites and the EAR. For building-level matches, ask the counterparty which room it uses and where it receives mail and goods, then record the answer and your decision and close the item. Whether a license is needed under Japan's Foreign Exchange and Foreign Trade Act is a separate question from Entity List placement.

Report the results to senior management briefly, along these lines.

We compared ___ shipments since June 12, 2024 against the 19 Entity List address-only entries. ___ shipments matched at room level, and ___ of those involved items not subject to the EAR. We will determine whether a license was required for the remaining ___ by ___. For ___ building-level matches, we are confirming details with the counterparties. The address screening in our tool was confirmed to be working in the November 25 test.

Also readCounterparty Screening at Scale: Name Matching, False Positives and Audit TrailsHow do you record false-positive decisions and suppressions for address hits so they hold up as evidence?

Wrapping up, and what I have not confirmed

There are only 19 address-only entries, but they differ from every other entry in one way: name screening alone will not hit a single one. Three things you can do on Monday morning: count whether your tool holds all 19, run T1 to T8 and record the results, and re-screen shipments since June 12, 2024 by address. None of these needs to wait for your vendor.

Here is what I have not confirmed. In the regulatory text and preambles I read, I found nothing on how to treat a different room in the same building. I have not checked the developer documentation (developer.trade.gov) to see whether the CSL API has an address filter. I have not checked whether BIS has published an FAQ on address-only entries. I read the G7 guidance as a PDF on the BIS site. The PDF itself carries no date, but the European Commission announced its publication on September 24, 2024.13 I have not taken a view on how to read the text between July 18 and 25, 2024. Section 744.11(a)(1), the 50 percent rule, which includes how affiliates of entities operating at listed addresses are treated, is stayed until January 10, 20271. Treatment under Japanese law is outside the scope of this piece, and I have not checked the specifications of individual screening products. If address entries are added or removed, I will update this piece.

You can use TRAFEED to run counterparty screening and keep the record of each decision. To talk it through, contact us here.

Further reading

  • Tracking Entity List and SDN updates every week: diffing the Federal Register, OFAC and the CSL, and catching address additions and removals.
  • Counterparty screening operations design: name matching, false-positive suppression and how to keep evidence.
  • Reading BIS settlement orders: nine orders, including E3047, mapped onto your own layers of checks.
  • Tracking Japan, EU, UK and UN lists every week: recording list versions outside the U.S.
  • A primer on diversion and anti-circumvention: the G7 guidance as a whole and checks for transactions through third countries.
  • Reexports from overseas sites and the EAR: checking site by site whether items are subject to the EAR.

Footnotes

  1. 15 CFR 744.11, heading, introductory text and paragraphs (a), (a)(1), (b) and (c), and its Effective Date Note ((a)(1) stayed by 90 FR 50857 and further stayed until January 10, 2027 by 91 FR 70789). The second sentence of (a)(1) says Entity List requirements do not extend to foreign affiliates owned by entities operating at a listed address unless those entities are specifically identified on the Entity List. Retrieved through the eCFR versioner API (November 19, 2026 version) on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-744/section-744.11 ↩ ↩2 ↩3 ↩4

  2. U.S. Department of Commerce, Bureau of Industry and Security (BIS), final rule, "Implementation of Additional Sanctions Against Russia and Belarus Under the Export Administration Regulations (EAR) and Refinements to Existing Controls," Federal Register document 2024-13148, 89 FR 51644-51680, RIN 0694-AJ67, published June 18, 2024. DATES: "This rule is effective on June 12, 2024, except for amendatory instruction 14, which is effective September 16, 2024." Public inspection filed_at June 12, 2024, 10:30 a.m. EDT. Preamble section II.C (1. Background; 2.ii. Entity List Structural Changes), the amendments to 744.11, 744.16 and Supplement No. 4, and amendatory instruction 14 (746.8) were checked against the Federal Register API and full text on November 22, 2026. https://www.federalregister.gov/documents/2024/06/18/2024-13148/implementation-of-additional-sanctions-against-russia-and-belarus-under-the-export-administration ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8

  3. 15 CFR 744.16 (Entity List), introductory text and paragraphs (a), (b), (c)(1), (e) and (f); its Effective Date Note (introductory text of (e) stayed by 90 FR 50857 and further stayed until January 10, 2027 by 91 FR 70789); and the BIS interim final rule that added the second sentence of (e) (document 2025-19001, 90 FR 47201, published September 30, 2025, amendatory instruction 10). The November 19, 2026, June 15, 2024 (no paragraph (f)), June 18, 2024 and July 20, 2024 (no address language in (a)) versions were retrieved through the eCFR versioner API on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-744/section-744.16 ↩ ↩2 ↩3 ↩4

  4. 15 CFR 748.5 (Parties to the transaction), paragraphs (c)-(f). Retrieved through the eCFR versioner API (November 19, 2026 version) on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-748/section-748.5 ↩

  5. BIS, "Revisions to the Entity List" (document 2024-19130, 89 FR 68544, published and effective August 27, 2024; public inspection August 23); "Additions and Revisions of Entities to the Entity List" (document 2024-25411, 89 FR 87261, published and effective November 1, 2024; public inspection October 30); "Additions to the Entity List" (document 2025-19508, 90 FR 48193, published October 9, 2025; DATES "This rule is effective October 8, 2025."; public inspection October 8). The preamble passages on the address additions and the Supplement No. 4 rows were checked against the Federal Register API and full text on November 22, 2026. https://www.federalregister.gov/documents/2025/10/09/2025-19508/additions-to-the-entity-list ↩ ↩2

  6. 15 CFR Part 744, Supplement No. 4 (Entity List), introductory text and the 19 address-only rows (Addresses 01-18 under China and Address 01 under Turkey, with license requirement, license review policy and Federal Register citation). Retrieved through the eCFR versioner API (November 19, 2026 version; Title 15 up_to_date_as_of November 19, 2026) on November 22, 2026. https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-744/appendix-Supplement%20No.%204%20to%20Part%20744 ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  7. 15 CFR Part 746, Supplement No. 7, "Items That Require a License Under § 746.6 When Destined to the Temporarily Occupied Crimea Region of Ukraine, Under § 746.7 When Destined to Iran, and Under § 746.8 When Destined to Russia or Belarus," introductory text. Retrieved through the eCFR versioner API (November 19, 2026 version) on November 22, 2026. ↩

  8. BIS, "Guidance on End-User and End-Use Controls and U.S. Person Controls," Entity List section ("The Entity List also identifies addresses associated with significant transshipment of sensitive items to countries of concern."). Checked November 22, 2026. https://www.bis.gov/licensing/guidance-on-end-user-and-end-use-controls-and-us-person-controls ↩

  9. BIS "Export Violations," case E3047 (February 26, 2026): order, settlement agreement and proposed charging letter. Charges 12-19 (paragraphs 15-20), the schedule of violations (dates, destination, ECCN 6A993.a), the WHEREAS clause in which the company admits the conduct, and FIRST (civil penalty of $1,000,000). The charging letter cites the June 2024 rule as "81 Fed. Reg. 51644, 51648." Checked November 22, 2026. https://www.bis.gov/media/2593 ↩ ↩2 ↩3 ↩4 ↩5

  10. ECCN 6A993 in 15 CFR Part 774, Supplement No. 1 (Reason for Control: AT; AT Column 1), and the China row of the Commerce Country Chart in Part 738, Supplement No. 1 (AT1 blank). Checked in the June 19, 2024 version through the eCFR versioner API on November 22, 2026 (the same in the November 21, 2026 version). ↩

  11. CSL downloadable files (CSV and JSON, https://data.trade.gov/downloadable_consolidated_screening_list/v1/consolidated.json ) and the BIS Entity List CSV (https://media.bis.gov/sites/default/files/documents/entity-list.csv , Last-Modified August 21, 2026). The address-only rows (19 in the CSL, 37 in the BIS CSV), the name and addresses fields, country codes, start_date and sources_used values were checked from files downloaded on November 22, 2026. ↩ ↩2 ↩3

  12. International Trade Administration, "Consolidated Screening List" (Key Considerations, Updates, CSL Search Engine and CSL Downloadable Files). Checked November 22, 2026. https://www.trade.gov/consolidated-screening-list ↩

  13. G7 Sub-Working Group on Export Control Enforcement, "Preventing Russian Export Control and Sanctions Evasion: Updated Guidance for Industry" (PDF on the BIS website; the European Commission announced its publication on September 24, 2024, in "Sanctions vis-à-vis Russia: Commission publishes G7 Industry Guidance on preventing sanctions evasion," https://finance.ec.europa.eu/news/sanctions-vis-vis-russia-commission-publishes-g7-industry-guidance-preventing-sanctions-evasion-2024-09-24_en , checked November 22, 2026; no date in the text). The passages on separately running name and address, additional due diligence for address-only hits and co-location were checked on November 22, 2026. https://www.bis.gov/media/documents/g7-updated-guidance-industry-preventing-russian-export-control-sanctions.pdf ↩ ↩2

  14. eCFR versioner API, list of versions for Part 744. The amendment date for 744.11, 744.16 and Supplement No. 4 under the June 2024 rule is recorded as 2024-06-18, and for the October 2025 amendment to Supplement No. 4 as 2025-10-09. Retrieved November 22, 2026. https://www.ecfr.gov/api/versioner/v1/versions/title-15.json?part=744 ↩

  15. BIS, "Standards-Related Activities and the Export Administration Regulations; Corrections," Federal Register document 2024-16379, 89 FR 60302, published and effective July 25, 2024. It explains that the July 18, 2024 interim final rule (89 FR 58265) inadvertently reverted the June 18, 2024 changes to part 744 and restores the language in 744.11, 744.16 and Supplement No. 4. Checked November 22, 2026. https://www.federalregister.gov/documents/2024/07/25/2024-16379/standards-related-activities-and-the-export-administration-regulations-corrections ↩

This article was produced with the help of AI. A human verified the primary sources and edited the text before publication.

Read next

Articles that answer the question you are likely to have next.

  1. 1Tracking Entity List and SDN Updates Weekly: Federal Register, OFAC, and CSL DiffsHow do you catch, in the Federal Register and your weekly diff, the week an address entry is added or changed?
  2. 2Counterparty Screening at Scale: Name Matching, False Positives and Audit TrailsHow do you record false-positive decisions and suppressions for address hits so they hold up as evidence?
  3. 3How to Read BIS Settlement Orders and Use Them to Self-Assess Your Export Compliance ProgramIf a past shipment turns out to match, what do you decide next, including whether to self-disclose?

This article is part of TRAFEED Media, our practical media on export controls and economic security

Back to TRAFEED MediaThis week's regulatory updates

52% of FY2024 export-control violations stem from classification errors. Is your team covered?

METI FY2024 data shows over half of violations stem from classification. Start with a free 5-question light check (~2 min, no email), then continue to the full 10-question report.

Contact About TRAFEED
Contact About TRAFEEDContact form (about 3 min)TRAFEED product briefFeatures & rollout in PDF

Share this article if you found it useful

Share

Newsletter

Get the latest AI and DX insights delivered weekly

Your email will only be used for newsletter delivery.

Free download

Recommended materials

China MOFCOM Lists (Control & Watch): 80-Entity Reference Sheet (through the 29 Jun 2026 wave)

All 80 entities on China MOFCOM's Control List and Watch List, in official / Chinese / English names. Being listed is a regulatory designation, not a judgment of the company — useful both for counterparty screening and for listed companies to understand where they stand. Based on primary sources (Announcements No. 11/12/27/28); as of 20 November 2026 there had been no additions or removals (checked through No. 56).

The BIS Affiliates Rule (50 Percent Rule) Readiness Checklist (2026)

A fill-in working checklist for trade compliance teams preparing for the BIS Affiliates Rule. Covers what the rule actually does (aggregation across owners and across lists, cascade/carry-forward, the rule of most restrictiveness, and why exactly 50% is in while below 50% is not automatically out), what is stayed and what is in effect now, where ownership data typically breaks, and a six-phase preparation list from scoping through governance. The stay was due to end on 9 November 2026; on that day BIS published a rule extending it to 10 January 2027 (91 FR 70789). The sheet is built to work whether the rule then returns, is stayed again, or is modified (as of 21 November 2026). Based on primary sources (90 FR 47201, 90 FR 50857, 91 FR 70789, 15 CFR, and China's Ministry of Commerce). Designation is a regulatory classification, not a judgement about a company; final determinations rest with your export-control officer and the authorities' current guidance.

EAR Classification Flow & EAR99 Practical Checklist (for exporters from Japan, 2026)

A fill-in working sheet covering "subject to the EAR? → ECCN on the CCL? → EAR99?", the crucial "when EAR99 still needs a license" (embargoes, end-use, end-user), de minimis / FDP, counterparty screening, and the two-track cross-check with Japan's classification (FEFTA / Appended Table 1). Based on primary sources (15 CFR, the Federal Register, BIS, METI); the EAR changes frequently, so treat the authorities' latest guidance and your export-control officer as authoritative.

See all materials

Related Knowledge Base

Export Control Guide

Solutions

Strengthen Export ComplianceStreamline compliance with complex export regulations

Talk with us about export-control operations

Share your screening, classification, or compliance workflow. We will map where TRAFEED can help—via our contact form (no cold booking).

Contact UsDownload Catalog

Related Articles

How to Read BIS Settlement Orders and Use Them to Self-Assess Your Export Compliance Program

How to Read BIS Settlement Orders and Use Them to Self-Assess Your Export Compliance Program

How to read BIS settlement orders and proposed charging letters, what the aggravating and mitigating factors in 15 CFR Part 766 Supplement No. 1 actually say, how voluntary self-disclosure is treated, and a table that maps nine corporate settlements from 2023 to 2026 onto the checks they tested.

2026-11-22
U.S. Export Rule Change Playbook: Read the Federal Register and Triage Impact in Three Hours

U.S. Export Rule Change Playbook: Read the Federal Register and Triage Impact in Three Hours

A playbook for the day a BIS rule lands, worked through on the 19 November 2026 interim final rule: read the Federal Register, triage impact in three hours, and brief management on one page.

2026-11-20
Taiwan SHTC Entity List Explained | Huawei and SMIC Among 601 Additions; Cumulative List Tops 11,480

Taiwan SHTC Entity List Explained | Huawei and SMIC Among 601 Additions; Cumulative List Tops 11,480

I wrote this for officers who know Japan’s FEFTA but not Taiwan’s system. Below I map SHTC structure, the Huawei/SMIC addition timeline, and five practical steps.

2026-05-20
The Hunterbrook Report on AMD and IEIT Firmware: What Is Claimed and What Is Unconfirmed

The Hunterbrook Report on AMD and IEIT Firmware: What Is Claimed and What Is Unconfirmed

On 19 November 2026, a U.S. investigative outlet published a report alleging that a server maker on the Entity List keeps using AMD firmware, and AMD shares fell sharply during the day. The report comes from an organization affiliated with a short seller, and no violation has been established. This article sorts out what the report claims, what it admits it cannot show, why software updates can raise export control questions, and how to judge what comes next.

2026-11-20
Reports of Nvidia Chip Purchases by Chinese Universities: What to Check Before You Trade With One

Reports of Nvidia Chip Purchases by Chinese Universities: What to Check Before You Trade With One

On November 11 and 12, 2026, Reuters and AFP reported that a Chinese university on the US Entity List had procured Nvidia H200 chips. This article separates what the reports establish from what they do not, shows which universities appear on the list and which do not, and sets out the checks a Japanese exporter should run before dealing with a university, based on Federal Register records.

2026-11-13
Tracking Entity List and SDN Updates Weekly: Federal Register, OFAC, and CSL Diffs

Tracking Entity List and SDN Updates Weekly: Federal Register, OFAC, and CSL Diffs

A weekly routine for companies with hundreds or thousands of counterparties to keep up with changes to the U.S. Entity List and SDN List: how fast the Federal Register, OFAC's Recent Actions, and the Consolidated Screening List each move, who checks what on which day, how to run diffs against your customer master, what to do the day a listing hits, and what to record, with real counts from November 2026.

2026-11-20