China Teapot Refinery Sanctions Risk: A Transaction Evidence File for Iran Oil Exposure

Direct Answer

Use this as a follow-up evidence guide, not as a general primer on whether China-based independent refineries are risky. If your team already knows the OFAC teapot refinery alert, the narrower task is to make the transaction record explain itself.

OFAC’s April 28, 2026 alert on teapot refinery sanctions risk separates two problems that often get folded into one. One is current sanctions-list or ownership exposure. The other is a document trail that may point to Iranian crude exposure even when there is no immediate list match.

That distinction matters in a real deal packet. A listed party is a list issue. A non-listed party with weak origin, route, broker, ownership, or payment evidence is an evidence issue. Treating those as the same finding can lead to either overblocking or a transaction record that looks cleaner than it is.

At minimum, the record should connect the invoice or contract, bill of lading, certificate of origin, inspection certificate, storage or blending record, vessel IMO and AIS record, ship-to-ship transfer record, ownership record, and payment instruction. The question is not just who the refinery is. It is whether each document supports the same story.

What Changed, Narrowly

The U.S. Treasury and OFAC warned on April 28, 2026 about sanctions risks linked to China-based independent oil refineries, commonly called teapot refineries. The alert focuses on the role that some independent refineries, including Shandong-linked refineries, may play in importing and refining Iranian crude oil.

The Treasury release says China purchases about 90 percent of Iranian oil exports and that many of those barrels go to teapot refineries. It also notes that some Chinese teapot refineries have used the U.S. financial system for U.S. dollar-denominated transactions and for procurement of U.S. technology and goods.

For transaction-document work, the key point is narrower. OFAC’s alert listed five designated refineries: Shandong Shouguang Luqing Petrochemical Co., Ltd.; Shandong Shengxing Chemical Co., Ltd.; Hebei Xinhai Chemical Group Co., Ltd.; Shandong Jincheng Petrochemical Group Co. Ltd.; and Hengli Petrochemical (Dalian) Refinery Co., Ltd.

OFAC explains that property and interests in property of designated refineries in the United States, or in the possession or control of U.S. persons, are blocked. U.S. persons are generally prohibited from dealing with blocked parties unless an authorization or exception applies.

The alert also points to the 50 percent ownership issue: entities owned, directly or indirectly, individually or in the aggregate, 50 percent or more by blocked persons are also treated as blocked. That is why a transaction record needs an ownership check, not only the trading name printed on an invoice.

Who Is Exposed

The same transaction can expose different teams in different ways. The bank may see the payment inconsistency before anyone sees the cargo record. Logistics may see the route gap before finance sees the beneficiary problem.

Exposed Role	What They May See First	Evidence Question To Ask
Banks and correspondent banks	Payment instruction, beneficiary bank, account holder, currency, customer information	Does the payment path match the commercial parties and the stated role of each intermediary?
Commodity traders	Contract, invoice, broker description, cargo title, refinery counterparty	Do seller, buyer, broker, payee, and refinery names line up across the deal documents?
Insurers	Vessel identity, cargo description, route, transfer history, named insured or beneficiary	Does the insured transaction rely on a clean route and origin story that the documents actually support?
Logistics providers	Loading and discharge details, terminal records, storage notes, ship-to-ship transfer information	Does the cargo path connect from loading to discharge without unexplained gaps or relabeling?
Inspection firms	Inspection certificate, product description, storage or blending references	Does the inspection record support the origin and cargo description used elsewhere in the transaction?
Refinery counterparties	Legal name, aliases, address, ownership, parent or subsidiary links	Is the exact entity clear, and does the ownership record create a 50 percent ownership question?

This is where I would slow down. A single sanctions-screening result can look tidy, while the operational documents remain scattered across commercial, finance, logistics, and inspection teams. The useful work is forcing those records into one claim-by-claim view.

Build The Evidence Row Before Debating The Risk Label

The strongest format is not a generic sanctions checklist. It is a row for each claim the transaction needs to support.

Evidence Row	Source Document	Identifier Searched Or Matched	Date Checked	Unresolved Question	Next Refresh Trigger
Party identity	Invoice, sales contract, legal-name record, aliases, address details	Refinery, seller, buyer, broker, payee, and payment-instructing party names	Record the date of each list or entity check	Are these the same entities across the transaction, or different parties with unclear roles?	Revised invoice, new broker, changed counterparty, updated entity record
Ownership	Ownership record, parent or subsidiary information, OFAC search result	Parent names, subsidiary names, blocked-person names if relevant	Record the date of ownership and OFAC list checks	Could the 50 percent ownership rule apply even if the exact invoice name is not listed?	New ownership information, merger or restructuring record, OFAC list update
Vessel identity	Bill of lading, AIS record, vessel owner, operator or manager record	Vessel name, IMO number, owner, operator, manager	Record the AIS pull date and sanctions-search date	Do the vessel name, IMO number, owner, and manager align?	Vessel substitution, AIS gap, new owner or manager data, added transfer record
Route continuity	Bill of lading, loading and discharge details, AIS record, ship-to-ship transfer record, storage record	IMO number, loading point, discharge point, transfer date, counterpart vessel if available	Record the date route data was checked	Does the cargo path connect without an unexplained gap or unsupported relabeling?	New operations note, port or terminal record, updated AIS data, new STS detail
Cargo origin	Certificate of origin, inspection certificate, storage or blending record, invoice product description	Origin wording, blend description, storage or inspection references	Record the date each document version was reviewed	Does the origin claim survive comparison with route, storage, inspection, and blending records?	Revised origin certificate, new inspection certificate, updated storage or blending record
Intermediary and payment path	Contract, invoice, broker description, payment instruction	Broker legal name, invoice payee, beneficiary bank, account holder, currency	Record the payment-instruction check date	Does the beneficiary match the commercial role described elsewhere?	Amended payment instruction, new bank, new intermediary, changed beneficiary

The column that gets skipped too often is the refresh trigger. A transaction record that was coherent on Monday may become incomplete after a new vessel update, a revised certificate of origin, or a changed payment instruction.

Where The Story Usually Breaks

Picture a common first-pass review, not a verified case. A cargo is bound for a China-based independent refinery. The invoice names one seller, the contract references a broker, the payment instruction sends funds to a different beneficiary, and the product description uses third-country blend language.

The certificate of origin may look orderly on its own. But the bill of lading names a tanker that later appears in an operations note with a ship-to-ship transfer. The AIS record has to be checked against the IMO number, not only the vessel name. The inspection certificate and storage record then become the bridge between the origin claim and the route claim.

None of those facts, standing alone, proves Iranian crude. That is the point. The transaction record should not jump from one red flag to a conclusion. It should identify which link is missing: cargo origin, route continuity, vessel identity, intermediary role, ownership, or payment beneficiary.

The easy mistake is asking whether the transaction involves a Chinese refinery and stopping there. The sharper question is whether the documents can show who owned or handled the cargo, how it moved, whether any transfer changed the origin story, and who ultimately receives the money.

Separate List Status From Evidence Gaps

Start list checks with OFAC’s Sanctions List Service, which provides access to SDN List and non-SDN consolidated list data. Preserve the search target, search terms, identifiers used, date checked, and result in the transaction record.

Search targets should be separated. A broad counterparty search is weaker than a record that separately checks the refinery, parent or subsidiary names, vessel name and IMO number, broker, terminal, inspection provider, logistics provider, invoice payee, and payment beneficiary.

Finding	What It Means	What To Preserve
Current list match	A refinery, vessel, broker, terminal, bank, payee, or other party appears to match OFAC list data	Search terms, identifiers, result, date checked, and ownership questions that follow from the match
50 percent ownership concern	The exact trading name is not listed, but ownership may connect it to blocked persons	Ownership record, parent or subsidiary names, date checked, and reasoning used to test the connection
Origin evidence gap	The origin certificate does not line up cleanly with route, transfer, inspection, or storage records	Certificate, bill of lading, STS transfer record, inspection record, storage record, unresolved question, and refresh trigger
Vessel identity gap	Vessel name, IMO number, AIS record, operator, or manager information does not align	IMO-based search result, AIS record, ownership or management record, inconsistent identifiers, and date checked
Payment-path gap	The beneficiary, account holder, or payment-instructing party does not match the commercial story	Payment instruction, invoice payee, bank details, currency, explanation of the intermediary role, and next refresh trigger

List checking is not something to perform once and forget. Practical decision points include moments when the transaction changes: a new vessel record, revised origin certificate, added intermediary, changed payment instruction, or updated ownership information. OFAC’s alert describes risk across individuals, companies, vessels, port-terminal operators, and inspection or logistics providers in this supply chain, so one name non-match should not carry the whole review.

Document Signals That Deserve More Evidence

OFAC describes several evasion patterns connected to Iranian oil moving toward Chinese teapot refineries. These indicators are not necessarily conclusive on their own. They matter more when several appear in the same transaction record.

One signal is the use of Asia- or UAE-based front companies. OFAC says Iran has used front companies in Asia and the UAE to intermediate shipments and payments for Iranian oil. The alert also points to Asia-based brokers with broad or nondescript business purposes acting between Iranian sellers and teapot refineries.

A second signal is a vessel route that does not connect cleanly. OFAC describes reliance on shadow-fleet tankers and deceptive shipping practices, including ship-to-ship transfers and vessel-location manipulation. Checking a vessel name is not enough; the question is whether the IMO number, transfer history, cargo records, and post-transfer origin documents line up.

A third signal is an origin description that reaches a conclusion faster than the route supports. OFAC says Iranian crude can be blended with third-country oil or relabeled through falsified documents as a product from another jurisdiction. It specifically mentions Malaysian blend as a common label. That wording does not prove Iranian origin by itself, but it should push the next request toward loading, transfer, inspection, storage, and blending records.

A fourth signal is unusual vessel identity. OFAC says sanctions-linked vessels may report identifiers belonging to non-sanctioned vessels or vessels that have already been scrapped. That is why the evidence row should keep vessel name, IMO number, operator or manager, AIS record, and sanctions-search result together.

Questions That Narrow The Next Request

When a high-risk indicator appears, broad questions tend to produce broad answers. Better questions aim at the missing document link.

• Which document proves the refinery’s exact legal name, alias history, address, and ownership structure?
• Does the ownership record create a 50 percent ownership question tied to a blocked person or designated refinery?
• What commercial role did the seller, broker, buyer, payee, and payment-instructing party each play?
• Do the vessel name, IMO number, owner, manager, loading date, and discharge date match across documents?
• If there was a ship-to-ship transfer, do the pre-transfer and post-transfer vessel and cargo records connect?
• Do the certificate of origin, inspection certificate, storage record, invoice product description, and route history support the same origin story?
• If Malaysian blend or another third-country blend label appears, is the blending, storage, and inspection path documented?
• Does the payment beneficiary match the commercial role described in the contract and invoice?
• If the transaction record is incomplete, which financial intermediary, correspondent bank, broker, logistics provider, or inspection firm is positioned to clarify the missing link?

These questions do not approve or reject a transaction. They organize the evidence so the record can be revisited if OFAC updates a list, a vessel record changes, or a new document arrives.

What To Watch Next

The first watch point is additional OFAC designations involving refineries, vessels, port-terminal operators, inspection firms, logistics providers, brokers, or front companies. The April 2026 alert is not only about five named refineries; it is also about the supply chain moving Iranian oil into China.

The second watch point is origin language. If Iranian crude can be blended, transshipped, or relabeled, a certificate of origin alone may not be enough. The stronger question is whether the route, transfer history, inspection record, storage record, and invoice description support the same origin claim.

The third watch point is the payment path. OFAC’s alert discusses financial institutions clarifying sanctions-risk expectations to Chinese correspondent banks and collecting additional customer and transaction information. In real transaction records, payment instructions are often where the commercial story and the banking story diverge.

The final checkpoint is simple: every material claim should have a source document, identifier searched, date checked, unresolved question, and next refresh trigger. Without those fields, the transaction may still be missing the evidence needed to explain itself when a list, vessel record, origin document, or payment path changes.

Official Source Path

Use the OFAC alert for the described risk patterns: designated refineries, Shandong-linked exposure, shadow-fleet practices, origin masking, front companies, and broker structures. Use the Treasury release for the agency’s public framing of the risk and financial-institution controls. Use OFAC’s Sanctions List Service as the live official path for SDN List, non-SDN consolidated list, and sanctions-search data.