BIS just settled with Container Manufacturing, an Ohio-based maker of tops for aluminum beverage cans, for $1 million over ten violations of U.S. export controls tied to Russia. On the surface, this looks like a modest regional manufacturer case involving unglamorous industrial spare parts. Underneath, it’s one of the clearest illustrations I’ve seen this year of a principle every compliance officer needs to internalize: a restricted-party list screening that comes back clean does not end your due diligence obligation, and ignoring red flags that surface after that screening is itself a violation, independent of whatever the screening result showed.

The Underlying Facts

Container Manufacturing had a business relationship going back to 2015 supplying spare and replacement parts for aluminum metalworking tools to the Russian subsidiary of a U.S.-based company. That relationship changed character in 2022, after Russia’s invasion of Ukraine, when the U.S. parent sold its Russian subsidiary to a Russian buyer. Container Manufacturing kept shipping the same parts to the same operation under its new Russian ownership, including shipments in and after March 2023, right after those parts became subject to significantly stricter licensing requirements as part of the broader post-invasion controls regime.

The parts themselves were classified as EAR99, generally the least restrictive classification under the Export Administration Regulations, and became newly controlled for Russia and Belarus destinations under specific Harmonized Tariff Schedule codes covering metalworking machine parts and certain gaskets and washers, once BIS added Russia and Belarus-specific licensing requirements in February and May of 2023. That’s an important detail on its own: items that were previously essentially unrestricted became license-required overnight once BIS updated its Russia-specific controls, and companies with existing customer relationships in Russia needed to actively track those regulatory changes rather than continuing to ship under the assumption that yesterday’s classification still applied.

Container Manufacturing did run the new Russian company’s name against U.S. restricted-party lists and found no match. That screening step matters, and BIS didn’t fault the company for skipping it. But a clean restricted-party screening result answers only one question: is this specific named party currently designated. It does not answer the separate question of whether a license is required for the specific item being shipped to that destination, and Container Manufacturing needed, and never obtained, an export license for shipments under the newly controlled HTS codes. BIS found at least seven unlicensed exports in 2023 and 2024, some routed through a distributor based in the United Arab Emirates, with BIS stating flatly that Container Manufacturing had knowledge in every one of those seven transactions that the ultimate destination was the Russian company.

Where This Case Gets Genuinely Instructive: The Red Flags

The more serious violations, from BIS’s telling, came from what happened after the company’s own bank raised concerns. Around December 2024, Container Manufacturing’s bank declined to process wire payments connected to these exports, citing the Russia embargo directly. That is about as unambiguous a red flag as a company can receive, a financial institution refusing to move money specifically because of Russia sanctions exposure. Container Manufacturing did follow up: it contacted the bank and sought clarification from outside counsel. But according to BIS, the company never actually resolved the underlying red flag, and it kept dealing with the Russian company anyway.

What happened next is the part of this case worth reading closely, because it shows exactly how sanctions evasion schemes get built around a cooperating counterparty’s own inaction. The Russian company emailed Container Manufacturing saying it had structured payment to get around what it called the “embargo mountain.” Shortly after, Container Manufacturing’s shipping letters of instructions changed in a way that should have jumped out to anyone reviewing them: a third-country distributor that had previously been identified as a reseller was now described as the “ultimate consignee” and a “direct consumer.” BIS’s point here is precise and important: Container Manufacturing knew the actual end user was still the Russian company, not the distributor now being relabeled as the ultimate consumer. That relabeling wasn’t a paperwork correction. It was a documentation change designed to obscure the real destination and end user of the shipment, and BIS found that Container Manufacturing simply went along with the change rather than questioning it or escalating it internally.

The email correspondence BIS cites removes any ambiguity about what the Russian company was doing. An employee of the Russian buyer wrote to Container Manufacturing expressing hope that the “embargo mountain” would soon become a “hill,” asked Container Manufacturing to check with its bank periodically for a “green light” on receiving payments from Russia, and asked to work directly without “time consumers.” That is a company explicitly describing its strategy for routing around U.S. financial controls, in writing, to its own supplier. BIS treated this as clear evidence of intent to use the Turkish intermediary specifically to disguise the Russian company’s role in the transaction, and Container Manufacturing continued negotiating payment for these restricted shipments until roughly March 2025, the point at which the company finally sought formal legal clarification on its licensing obligations, right around when BIS itself made contact about the potential violations.

Why “We Asked Our Bank and Our Lawyers” Wasn’t Enough

This is the crux of the compliance lesson in this case. Container Manufacturing didn’t simply ignore its bank’s warning outright. It contacted the bank. It sought outside counsel input. On paper, that looks like a company trying to do the right thing. But BIS’s enforcement order makes clear that taking those steps without actually resolving the red flag, and without pausing the underlying transactions while resolution was pending, does not satisfy an exporter’s obligations. A red flag that generates a phone call and a legal inquiry, but no change in conduct and no suspension of the questionable shipments while the answer is pending, functions the same as a red flag that was never raised at all in BIS’s eyes. The obligation is to resolve the concern before continuing the conduct that triggered it, not to document that you asked a question and then proceed regardless of whether you got a satisfying answer.

The Settlement Terms and What Earned Credit

Container Manufacturing agreed to pay $1 million to resolve the ten violations, and BIS was explicit that the company gets a 30-day window to pay before facing the possibility of a full year’s revocation of its export privileges, a consequence that would be existential for a manufacturer with any meaningful export business. BIS did credit the company for full cooperation once the investigation began, including voluntarily and promptly turning over the emails, transactional records, and correspondence that BIS ultimately used to build its case, and for making genuine compliance program upgrades afterward: new restricted-party and end-user screening safeguards, more rigorous transaction review and escalation procedures, improved recordkeeping, and expanded employee training.

What Every Export Compliance Program Should Take From This

A handful of practical lessons come directly out of this case. Restricted-party list screening is necessary but never sufficient on its own; it answers only whether a specific named party is currently designated, not whether a license is required for a given item and destination, and companies need a separate, ongoing process for tracking HTS-code-specific licensing changes for sanctioned or heavily restricted destinations like Russia and Belarus. A warning from your own bank about sanctions exposure is one of the highest-value red flags an exporter can receive, precisely because financial institutions run their own independent sanctions screening and have no commercial incentive to flag a transaction unless something genuinely concerning surfaced. That kind of warning needs to trigger an actual pause in the underlying transaction while it’s being resolved, not just an inquiry that runs in parallel with continued shipments.

Documentation changes involving intermediaries deserve real scrutiny, not routine processing. A distributor that has always been labeled a reseller suddenly becoming the “ultimate consignee” or “direct consumer” on a shipping document is exactly the kind of change that should trigger internal escalation, particularly when the company preparing the documents knows the actual end user hasn’t changed. And finally, when a counterparty’s own communications describe active efforts to route around sanctions or embargoes, in this case explicitly and in writing, that correspondence is not just evidence a regulator might find later. It’s a real-time signal that should end the relationship, or at minimum halt the specific transactions at issue, well before a company reaches the point of explaining those emails to BIS during an active investigation.