Learn more about the latest security and privacy threats
Back

Foreign subsidiary sanctions liability: OFAC settles with Rice Lake over Iran diversion

Michelangelo Frigo Michelangelo Frigo (Co-Founder at Zyphe) Published August 13, 2026 Reviewed by Charlene Wang
Editorial illustration for the article "Foreign subsidiary sanctions liability: OFAC settles with Rice Lake over Iran diversion".

OFAC settled with Rice Lake for 60,764 dollars after its Italian subsidiary shipped goods to Iran through a UAE distributor. What it changes for controls.

Table of contents

OFAC has settled with Rice Lake Weighing Systems for 60,764 dollars over eight shipments its Italian subsidiary sent to Iran through a distributor in the United Arab Emirates. The case turns on foreign subsidiary sanctions rules, which bind entities that United States persons own or control almost as tightly as the parent itself.

  • The Office of Foreign Assets Control announced the settlement on 12 August 2026, resolving eight apparent violations covering roughly 121,527 dollars of goods.
  • The parent told its Italian subsidiary in writing that Iran was off limits, then did not translate the instruction or check that it had landed.
  • Direct sales stopped. Indirect sales through a UAE distributor did not, and OFAC found the subsidiary acted with reckless disregard for United States sanctions requirements.
  • Voluntary self-disclosure and a non-egregious finding set the base penalty at half the transaction value per violation, and OFAC settled at exactly that base figure.
  • At 60,764 dollars this is the smallest of OFAC's six published 2026 enforcement actions, but the foreign subsidiary sanctions lesson applies to any group with entities abroad.

What did OFAC settle with Rice Lake?

Rice Lake Weighing Systems, a Wisconsin manufacturer of scales and weighing equipment, agreed to pay 60,764 dollars to settle its own and its Italian subsidiary's potential civil liability for eight apparent violations. The subsidiary, Dini Argeo S.r.l., shipped eight orders to a distributor in the United Arab Emirates knowing the goods would be reexported to an Iranian customer.

Rice Lake acquired Dini Argeo in November 2016. At that point Dini was already selling to Pand Weighing Control, an Iranian weighing systems company, and continued to do so lawfully under General License H. That authorisation disappeared after the United States announced its withdrawal from the Joint Comprehensive Plan of Action on 8 May 2018. OFAC revoked General License H on 27 June 2018 and allowed wind-down activity only through 4 November 2018.

The settlement is small in money terms and large in principle. OFAC's own summary of the lesson is blunt: "The compliance failures of a foreign subsidiary can create liability for its U.S. parent," the agency wrote in its enforcement release. That single sentence is why foreign subsidiary sanctions exposure belongs on the agenda of every group compliance function, not just the trade team.

Case factDetail
Settlement amount60,764 dollars
Apparent violationsEight, under ITSR section 560.215(a)
Value of goodsApproximately 121,527 dollars
Conduct periodJune 2019 to November 2021
ParentRice Lake Weighing Systems, Inc. (Wisconsin)
SubsidiaryDini Argeo S.r.l. (Italy), acquired November 2016
RouteItaly to a UAE distributor, reexported to Iran
DispositionVoluntarily self-disclosed, non-egregious

How did eight shipments reach Iran?

OFAC split the fault. It found that Dini acted with reckless disregard by making indirect sales it should have known were as prohibited as direct ones, and separately that Rice Lake failed to exercise due caution in explaining the risks of indirect dealings. Dini personnel do not appear to have understood that the indirect channel was covered at all.

On 8 August 2018 Rice Lake's import export coordinator emailed Dini's general manager. The message stated, in part, that the subsidiary was "prohibited from any transactions involving Iran ... no matter where located," and excerpted language from the Iranian Transactions and Sanctions Regulations. OFAC noted that the parent supplied no further explanation and no translation, and did not appear to have taken sufficient steps to confirm the subsidiary understood the prohibition or to monitor adherence to it.

The red flags that followed were not subtle. A Pand Weighing Control employee emailed Dini staff on at least five occasions during 2019 and 2020, and every message from the Iranian company carried references to Iran in the signature block. The UAE distributor eventually confirmed the Iranian company was the intended recipient. Rice Lake acted once a tip reached it in late 2021: it investigated with outside counsel, ordered Dini to stop selling to the distributor, and self-disclosed.

DateEvent
16 January 2016OFAC issues General License H
November 2016Rice Lake acquires Dini Argeo
8 May 2018United States announces JCPOA withdrawal
27 June 2018General License H revoked
8 August 2018Parent emails subsidiary that Iran is prohibited
4 November 2018Wind-down authorisation expires
June 2019 to November 2021Eight indirect shipments reach Iran
Late 2021Tip received, investigation opened, sales halted
12 August 2026Settlement announced

What does this change for your obligations?

Nothing in the rulebook changed, but the enforcement reading of four existing duties tightened. Ownership testing, counterparty diligence, the knowledge standard and training records now carry a documented expectation that the parent verifies, translates and monitors, rather than simply instructing. Each maps to a control you can evidence.

Ownership and control mapping. Section 560.215(b)(1) of the Iranian Transactions and Sanctions Regulations defines an entity as owned or controlled by a United States person where that person holds a 50 percent or greater equity interest by vote or value, holds a majority of board seats, or otherwise controls the actions, policies or personnel decisions of the entity. That third limb catches entities no cap table would flag, so your group structure record must capture board composition and control rights, not just percentages. This is the same recursive ultimate beneficial owner resolution problem that UBO screening solves for customers, turned inward on your own group.

Counterparty and end-user diligence. The eight shipments cleared because nobody screened the destination behind the distributor. OFAC was explicit that firms with counterparties in jurisdictions known to be high risk for diversion, naming the UAE, should pay particular attention to indirect dealings. Distributors, freight forwarders and resellers need the same onboarding rigour as customers: incorporation checks, ownership resolution, end-user declarations and periodic re-screening. The sanctions screening guide walks through list scope and match handling, and KYB verification covers the entity side.

The knowledge standard. Under section 560.215(b)(2), knowingly means actual knowledge or reason to know. Reason to know is satisfied by exactly the pattern here: repeated emails from an Iranian company, an Iranian address in a signature block, a distributor in a hub OFAC itself flags. If your screening only reads the named buyer and never the surrounding correspondence, your foreign subsidiary sanctions controls are weaker than they look on paper.

Record-keeping and training. OFAC credited remediation that included training subsidiary employees, vetting end distributors and adding reexport control warnings to commercial invoices. Treat those three as the minimum evidence file. A policy circulated once, in a language that part of the workforce does not read fluently, is not a control, and after this case it will not be scored as one.

What is still uncertain about foreign subsidiary sanctions risk?

Three things remain unsettled: how much of OFAC's prescribed training and monitoring is enough, how much diversion risk sits with the distributor rather than the seller, and whether self-disclosure still pays when the conduct spans years. The first is a question of degree.

OFAC did name the components. It called for clear guidance and regular training of all relevant personnel rather than managers alone, tailored to local language and business customs, backed by centralised monitoring and regular testing and auditing. What it did not say is how much of each suffices for a subsidiary of twenty people. Attestations, sample testing of orders and periodic audits are all plausible, and all cost money a mid-sized manufacturer may not have budgeted.

The second is a liability split. The UAE distributor performed the reexport, yet the settlement lands on the American parent. Contractual end-user undertakings and reexport warnings on invoices shift commercial risk, but they do not transfer regulatory liability. Firms should expect to carry foreign subsidiary sanctions exposure for what their channel partners do, and price the diligence accordingly.

The third is the value of disclosure, and here the arithmetic is instructive. Under the enforcement guidelines, self-disclosure plus a non-egregious finding sets the base at one-half the transaction value, producing 60,764 dollars against 121,527 dollars of goods. Without disclosure the base becomes the applicable schedule amount, which is 25,000 dollars for any transaction between 10,000 and 25,000 dollars. The eight orders averaged about 15,000 dollars, so on those values the base would have run near 200,000 dollars, though OFAC did not publish the individual order values. Had the conduct been called egregious, the base would have started at one-half the IEEPA statutory maximum with disclosure and the full maximum without it. Disclosure was worth roughly 140,000 dollars here. The non-egregious finding was worth an order of magnitude more, which is why the egregiousness determination, not the disclosure decision, is the one that should worry a board.

Two further gaps are worth naming. The conduct ended in November 2021 and the settlement landed close to five years later, so published outcomes are a poor guide to current enforcement appetite. And the case began with a tip, though one that reached Rice Lake rather than the government. Even routed to FinCEN it would have paid nothing: the whistleblower programme the same release advertises requires penalties above 1,000,000 dollars, and this one closed at 60,764.

How does this settlement compare with OFAC's 2026 record?

Rice Lake is the smallest published OFAC enforcement action of 2026 and the sixth of the year. Against a 2026 total of roughly 282.7 million dollars across six actions, it accounts for about two hundredths of one per cent. The small figure reflects self-disclosure and a non-egregious finding, not a soft year of enforcement.

The contrast with the year's largest action is instructive, and it runs deeper than severity. In May 2026 Adani Enterprises settled for 275 million dollars, roughly four and a half thousand times larger, in a case OFAC called egregious and not self-disclosed. Both cases involve Iranian-origin trade routed through the Gulf, but the liability theories differ: Adani was reached as a non-United States person that caused United States banks to process dollar payments, while Rice Lake was reached through the owned-or-controlled foreign entity prohibition. OFAC's release flags that distinction itself. For groups mapping their own foreign subsidiary sanctions exposure, the Rice Lake theory is the one that travels.

DatePartyAmount (USD)Penalty posture
12 August 2026Rice Lake Weighing Systems, Inc.60,764Self-disclosed, non-egregious
1 June 2026FTI Consulting, Inc.1,050,000
18 May 2026Adani Enterprises Limited275,000,000Egregious, not self-disclosed
17 March 2026TradeStation Securities, Inc.1,110,661
25 February 2026An individual3,777,000
12 February 2026IMG Academy, LLC1,720,000
2026 year to dateSix actions282,718,425

Source: OFAC civil penalties and enforcement information, as at 12 August 2026.

Readers tracking designations rather than penalties should read our coverage of the Prince Group designations, where OFAC and FinCEN moved together. Penalty actions and listing actions test different controls: one asks whether you screened, the other whether you understood who you were dealing with.

How should compliance teams respond?

Start with structure rather than screening: which entities in your group meet the 50 percent, majority-board or effective-control test, and who maintains that list? In groups with more than a handful of subsidiaries, the register usually stops at the top two tiers. Fix it first, because foreign subsidiary sanctions duties attach entity by entity.

Then work through the channel. Map every distributor, reseller and forwarder touching restricted-destination adjacent geographies, and check whether end-user diligence exists for each. Screen the correspondence trail, not only the invoice header. Reissue prohibition notices in local languages with acknowledgement, and put a sampling check in the audit plan so the notice is tested rather than assumed. Add reexport warnings to commercial documents, and set a review trigger whenever a general license is amended or revoked, since that is how this exposure began.

Zyphe handles the identity layer of that work. Recursive UBO resolution runs against 240+ corporate registries worldwide, with a 25 per cent beneficial ownership default that is configurable per risk tier. Thresholds settle the equity limb, while directorship sits on the same entity record, so the board limb is evidenced rather than assumed. Sanctions and PEP screening runs against that record, so counterparty checks and group-structure checks share one exportable audit trail. Integration takes as little as 15 minutes through a single API, with usage-based pricing and no minimums. Book a demo if you want to see how it fits an existing programme.

The bottom line

The money in this case is trivial and the mechanism is not. A parent gave a correct instruction once, in the wrong language, without checking that it was understood or followed, and carried the liability for what happened next across two years and eight shipments. For teams running KYC and AML programmes the read-across is direct: foreign subsidiary sanctions exposure sits in group structure and in the channel, as much as in the customer file. Knowing which entities you control, and who sits behind the counterparty on the invoice, is the control that would have caught this. Both are identity problems before they are trade problems.

Cited sources

Michelangelo Frigo Michelangelo Frigo (Co-Founder at Zyphe) Michelangelo Frigo is a privacy and identity infrastructure expert and co-founder of Zyphe.

Frequently Asked Questions

Section 560.215(a) binds the foreign entity, not the parent directly. [Note 4 to that section](https://www.ecfr.gov/current/title-31/section-560.215) then exposes the United States parent to civil penalties under section 206(b) of the International Emergency Economic Powers Act, at 50 U.S.C. 1705(b), whenever a foreign entity it owns or controls breaches the prohibition. That note is the hook that made Rice Lake pay.

Not uniformly. The Iran programme is unusual in reaching owned-or-controlled foreign entities this directly through section 560.215. The Cuba regulations use a different construct, applying to persons subject to United States jurisdiction, while many other programmes bind United States persons and their conduct rather than their overseas subsidiaries. Map your exposure programme by programme rather than assuming one rule.

A United States person owns or controls a foreign entity if it holds a 50 percent or greater equity interest by vote or value, holds a majority of the board seats, or otherwise controls the actions, policies or personnel decisions of that entity. The third test is the one firms miss, because it captures effective control that does not appear on a shareholding register.

Not on its own. OFAC treated the untranslated, unexplained and unmonitored email as part of the conduct it faulted. The expectation is that a parent gives clear guidance and regular training to all relevant personnel rather than managers alone, tailored to local language and business customs, and then monitors adherence through centralised oversight, testing and auditing.

Build an accurate register of which entities the group owns or controls under the applicable tests, including board composition and control rights rather than percentages alone. Then extend counterparty screening to distributors and end users, and re-screen whenever a general license changes.

See privacy-first KYC in action

Verify identity without storing a single document. Reusable credentials, an exportable audit trail, and a 15-minute integration.

Book a demo