Sanctions and Export-Control Screening for China-Linked Companies

Direct answer

Before shipment, payment, service, re-export, in-country transfer or technology release, create one transaction record covering parties; ownership/control; item or activity; technical classification; jurisdictions; route; banks and payment; end user; end use; downstream recipients; authorisations; red flags; screening results; and execution conditions. Then record one of: release · release with controls · hold · escalate · prohibit or do not proceed — as determined by the relevant authorised reviewer. This page does not itself determine a legal outcome. The site’s Export Control and Trade Measures Tracker remains the changing-measures layer, not a screening database.

At a glance: the transaction-screening decision

OPERATING MAP This table replaces a generic “frame / plan / execute / review” strip. Each stage has a question and a fileable output.

Three-layer screening model

Decision: which layer is still open? Hold trigger: treating Layer 1 as Layer 3.

1. Sanctions / denied-party screening. Is a party a potential match to a relevant restricted-party list, or subject to applicable ownership/control restrictions?
2. Export-control screening. Is the item, software, technology, service, destination, end user, end use or controlled act restricted or subject to authorisation?
3. Transaction decision. Do the complete facts, applicable regimes, authorisations, conditions and execution controls permit the transaction to proceed?

Sequence: transaction record → jurisdiction → classification → parties → ownership/control → end use/end user → red flags → hold → scoped legal decision → execution controls → final re-screen → release → evidence retention.

Should this transaction be held?

DECISION TREE Fact-dependent triage. Leaves are workflow results, not legal determinations.

Gate 1 — Are mandatory transaction facts complete?

If no: HOLD. Incomplete party identity, missing end user, unknown installation site, unclear route, unknown bank/payer, missing ownership information, incomplete technical specs, or inconsistent documents.

Gate 2 — Is there a potential list match or unresolved alias?

If yes: HOLD → match-resolution workflow.

Gate 3 — Is ownership/control unresolved?

If yes: HOLD → regime-specific ownership/control review. Do not apply OFAC’s 50 Percent Rule as a global test. See SDN 50% rule for the US example.

Gate 4 — Is item/activity classification unresolved?

If yes: HOLD the controlled act → classification review. An HS code is not an export-control classification.

Gate 5 — Is end use/end user unclear or inconsistent?

If yes: HOLD → enhanced diligence / specialist review.

Gate 6 — Is route or payment commercially unusual or contradictory?

If yes: HOLD → diversion / red-flag review.

Gate 7 — Is there a licence, exception, authorisation, conflict-of-law or countermeasure question?

If yes: HOLD → jurisdiction-specific counsel.

Gate 8 — Have facts changed since approval?

If yes: REOPEN → re-screen / reassess.

Only after all required gates are resolved: FINAL RELEASE REVIEW. This tree does not determine whether a transaction is lawful, prohibited, licensed, exempt, authorised or outside scope.

Required transaction-screening record

This annotated structure is the page’s main practical asset and the counsel-intake object. Missing or inconsistent mandatory fields require a hold.

Which regimes may require analysis?

Core rule: do not search a list first and decide jurisdiction later. Do not treat US-person, EU-person, origin, content, location, routing, currency or re-export concepts as interchangeable. Conflicting legal demands must be escalated, not resolved editorially.

Required output for each possible stack: regime → factual nexus → source → reviewer → open question.

US signals (not conclusions)

• US-origin item, software or technology; US-controlled content
• US-person activity; US financial or payment nexus
• Re-export or in-country transfer; destination / end-use / end-user restrictions
• OFAC sanctions nexus

EU signals

• EU person or entity involvement; EU-origin controlled item or technology
• EU export or brokering activity; relevant Member State implementation
• Sanctions restrictions; dual-use controls

PRC signals

• PRC exporter, entity or person; controlled PRC-origin item or technology
• Dual-use export; technology export; data / state-secret interface
• Sanctions or countermeasure implications; other PRC restrictions

Other signals

• UN measures; destination-country controls; transit-country requirements; bank or commercial controls

Classification evidence

An HS code does not establish export-control classification. Software, technology access, technical assistance and services may need their own analysis.

Classification record — required fields

Item/activity description; technical specifications; manufacturer; model/version; functionality; software/technology components; customs code where relevant; export-control classification; classification source; applicable control list/entry; technical reasoning; version/date; responsible reviewer; assumptions; unresolved questions.

Route detailed classification work to the export-control hub and current tracker.

Who should be screened?

Identify all relevant roles first; then apply the appropriate regime-specific screening rule. Do not imply every role is screened identically under every regime. A clean entity-name search is not approval.

Ownership / control escalation

Required facts: direct and indirect shareholders; percentages where relevant; ownership chain; aggregation where required by the applicable regime; control and management rights; voting arrangements; parent/subsidiary relationships; source reliability; data date; recent ownership changes.

This page does not summarise every EU or PRC ownership/control test.

Potential match → hold → resolve → decide

1. Capture alert. Name searched, alias, source/list, timestamp, result, search logic. Automatic release is disabled.
2. Identity resolution. Compare reliable identifiers: legal name, aliases, address, jurisdiction, registration number, date of formation, website, industry, and individual identifiers where lawfully available.
3. Ownership/control analysis where relevant: entity chart, beneficial ownership, indirect ownership, control information, source/date.
4. Transaction-context review. Item, route, end user, end use, payment, intermediaries, applicable regime.
5. Scoped legal / authorisation decision recorded as: false positive / non-match; match requiring continued hold; authorisation required; release permitted subject to conditions; transaction prohibited / should not proceed; facts insufficient; specialist counsel required.
6. Execution controls carried into logistics, contract, payment, technology access, shipment documents, downstream instructions and final release.

End user, end use and diversion

An unlisted party can still create an export-control or diversion problem. A licence or hold may be required without an exact list match.

Supply-chain traceability issues: UFLPA audit · origin / customs risk · China+1 hub. Technology or personal-data release: also open the overseas data / SCC path.

When should the transaction be re-screened?

Re-screen when facts change and at the final controlled-act gate. This page does not prescribe one universal periodic cadence.

Final release checklist

Before shipment, payment, service, re-export, in-country transfer or technology release confirm:

• Transaction record is complete; relevant regimes identified; classification current
• Parties screened; aliases resolved; ownership/control conclusion documented
• End user known; end use documented; route/payment coherent; red flags resolved
• Licence / authorisation current where applicable; conditions incorporated
• No material facts changed; final re-screen complete; authorised reviewer recorded; evidence saved

RELEASE if all required controls and approvals are satisfied. RELEASE WITH CONDITIONS if lawful conditions must be operationalised. HOLD if any required fact or decision remains unresolved. ESCALATE if specialist legal review is required. Do not define “release” as a legal safe harbour. End-user statements and contractual controls support diligence; they do not transfer legal responsibility or cure known red flags.

Hold authority / RACI

Business teams may supply facts, but unresolved holds cannot be overridden commercially. Distinguish fact owner / screening owner / legal decision owner / execution owner.

R = responsible, A = accountable, C = consulted, I = informed. R* = execution owner for that channel only after legal/compliance clearance. This RACI is an operating model, not a statutory allocation of liability.

Minimum viable programme for smaller teams

This is an operating baseline, not a statutory safe harbour. BIS, OFAC and EU programme guidance may inform structure; they are not a universal harbour.

Suspected breach or near miss

Stop affected activity → preserve records → contain shipment, access or payment → identify jurisdictions → identify transaction(s) affected → preserve privilege where appropriate → escalate to scoped counsel → determine reporting / disclosure / licence / remediation implications → correct the control weakness → re-screen related transactions.

This guide does not provide universal voluntary-disclosure advice and does not promise immunity or mitigation.

Evidence-preservation checklist

Could a reviewer reconstruct why the company released or held this transaction six months later? If no, the file is incomplete.

Retain: transaction inputs; contract/order; party identifiers; ownership sources; technical classification evidence; screening sources; list/source version; timestamps; match-resolution notes; end-use and end-user evidence; route/payment records; red-flag analysis; licence/authorisation; legal reasoning; internal approval; execution conditions; shipment/payment/access evidence; final re-screen result; change history; incident/corrective action.

Evidence grades used on this page

Common mistakes

Action checklist — counsel intake pack

Send this package so counsel can check conflicts, identify regimes and see whether a hold is already required.

• Transaction purpose and requested release date
• Buyer, seller, consignee, importer, end user, downstream users
• Intermediaries, banks, carriers
• Ownership chart, aliases, registration numbers, addresses
• Item / specification; software, technology or service elements
• HS code if relevant; export-control classification evidence
• Origin, destination, transit route
• Payment structure
• End use and installation site; customer business profile
• Licences / authorisations; current screening results
• Red flags; previous similar transactions
• Internal owner and deadline

FAQs

Selected official sources

• US Export Administration Regulations
• OFAC sanctions programmes
• OFAC 50 Percent Rule FAQs (confirm current page)
• EU Dual-Use Regulation 2021/821
• PRC Regulations on Export Control of Dual-Use Items
• CLP primary-source library

For a live transaction, counsel must still resolve the source-pack questions, including the precise EU Member State, applicable ownership/control rules, authorisation gates, incident routes and the PRC countermeasure, technology-export, state-secret and data interfaces.

Find trade-controls counsel

Use one factual record. Listings are a starting point, not a multi-jurisdictional opinion.

Request counsel Import & export compliance directory