Skip to main content
Commerce Security logo, "All 12 PCI DSS Requirements in Plain English," "Get it now for free," "Complete Survival Guide" and a button toclick to get it
When Email Isn't Enough: Rice Lake's $60,700 Sanctions LessonRegulatory Compliance
4 min readFor Compliance Officers

When Email Isn't Enough: Rice Lake's $60,700 Sanctions Lesson

The Challenge

In 2018, Rice Lake Weighing Systems faced a compliance challenge: communicating a major sanctions policy change to its Italian subsidiary, Dini Argeo. The Trump administration's withdrawal from the Iran nuclear deal ended OFAC's general license, which had allowed U.S. companies' overseas subsidiaries to do business with Iranian entities.

Rice Lake's import-export coordinator emailed Dini's general manager, stating, "you are prohibited from any transactions involving Iran, or a citizen of Iran, no matter where located," and included an excerpt from the Iranian Transactions and Sanctions Regulations (ITSR). From Rice Lake's perspective, the instruction was clear.

However, Dini's interpretation differed. While Dini stopped direct sales to its Iranian customer, it continued selling through a Dubai distributor who re-exported the goods to Iran until late 2021. This resulted in $121,500 in prohibited sales and a $60,700 OFAC settlement for Rice Lake.

The Environment and Constraints

Rice Lake acquired Dini Argeo in 2016, inheriting a business relationship with an Iranian weights company. This relationship was legal under OFAC's general license until the 2018 policy change.

Several factors complicated communication:

Language barriers. The email was in English, but Dini's general manager spoke Italian. Rice Lake didn't provide translation or confirm understanding.

Cultural context. U.S. sanctions regulations don't align with European business practices. What seems clear to a Wisconsin-based compliance coordinator may need more explanation for an Italian operations manager.

Operational distance. Rice Lake lacked monitoring mechanisms to verify Dini's compliance. The parent company had no insight into Dini's distributor relationships or end-customer destinations.

Ambiguous scope. The email prohibited transactions with Iran but didn't address indirect sales, third-party distributors, or re-export scenarios. Dini employees interpreted these gaps on their own.

The Approach Taken (and Where It Failed)

Rice Lake's initial response was minimal: send written notice citing the relevant regulation. But OFAC's settlement order highlighted critical execution gaps.

The company "did not include any further explanation or translation," according to OFAC. More importantly, "Rice Lake does not appear to have taken sufficient steps to ensure its subsidiary understood the prohibitions, took steps to comply with them, or monitor their adherence to the renewed restrictions."

Dini employees missed multiple red flags. Iranian customers emailed Dini directly with product questions, and the Dubai distributor disclosed the end customer was Iranian. Yet, these warnings didn't prompt Dini to clarify with Rice Lake.

The violation continued until late 2021, when Rice Lake received an external tip about products appearing in Iran. The company launched an investigation, directed Dini to stop sales to the Dubai distributor, disclosed the violations to OFAC, and began compliance remediation.

Results and Metrics

OFAC settled for $60,700, half the $121,500 in prohibited sales Dini conducted. The reduced penalty reflected Rice Lake's cooperation, lack of prior sanctions violations, and aggressive remediation efforts.

The company implemented several enhancements:

  • Expanded training for employees
  • Enhanced vetting procedures for distributors
  • Re-export control warnings on invoices
  • Improved monitoring of high-risk business relationships, especially with resellers in jurisdictions known for Iranian trade

Rice Lake's swift response likely prevented a more severe outcome. OFAC noted the company was "highly cooperative" throughout the investigation.

What They Would Do Differently

While OFAC's settlement order doesn't prescribe exact remedies, it points to clear gaps Rice Lake would address:

Translate critical compliance instructions. Use translation tools to eliminate language barriers. An Italian-language version of the sanctions notice would have helped.

Explain indirect exposure explicitly. Address distributor relationships, re-export scenarios, and end-use customer verification requirements. Include examples: "You cannot sell to a Dubai distributor if you know or have reason to know the goods will reach Iran."

Require written acknowledgment. Don't assume compliance until the subsidiary confirms understanding in writing, ideally with a description of how they'll implement the restrictions.

Monitor high-risk relationships proactively. Flag Dini's Dubai distributor relationship for review, given Dubai's role in Iranian trade. Regular transaction reviews would have caught the pattern.

Establish escalation protocols. When Dini employees received emails from Iranian customers, they needed a clear path to escalate questions to Rice Lake's compliance team.

Takeaways for Your Team

This case shows that compliance communication isn't complete until you've verified understanding and built monitoring into your control environment.

Test comprehension, don't assume it. After issuing compliance instructions to overseas subsidiaries, require recipients to explain back what actions they'll take. This reveals interpretation gaps before they become violations.

Build translation into your standard process. If you're sending regulatory guidance to non-native English speakers, translate it. The cost is negligible compared to enforcement risk.

Map out indirect scenarios. When explaining a prohibition, walk through common workarounds: third-party distributors, re-export arrangements, joint ventures. Make it explicit that these routes are also blocked.

Monitor distributor relationships in high-risk jurisdictions. If your subsidiary sells through resellers in Dubai, Hong Kong, or other transshipment hubs, you need visibility into end customers. Transaction monitoring should flag patterns consistent with prohibited destinations.

Document your communication trail. Keep records showing not just what you said, but how you verified understanding and monitored compliance. OFAC will review this evidence when evaluating your due diligence.

Rice Lake's story illustrates a broader truth about compliance programs: the illusion of communication creates real regulatory exposure. Your email might be legally precise, but if the recipient interprets it differently than you intended, you own the consequences. Build verification and monitoring into every critical compliance instruction you issue.

Promotional banner for the Pentest Readiness checklist download

You Might Also Like