A US-headquartered manufacturer settles an OFAC enforcement matter. As part of the settlement, it agrees to appoint an independent compliance monitor. Twelve months later, the same business faces a parallel BIS / EAR inquiry for export-control violations involving the same shipments. Now it is managing two concurrent monitorships – one focused on financial-sanctions compliance, one on export-control procedures – and the obligations, timelines, and reporting structures do not align. This is not an unusual situation. It is, however, one that can overwhelm a compliance function that has not prepared for the divergence between the two regimes.
Managing a compliance monitorship under OFAC requires a business to demonstrate, to an independent monitor's satisfaction, that it has implemented an effective sanctions-compliance programme across the five elements OFAC identifies in its framework. BIS / EAR monitorships, imposed through settlements with the Bureau of Industry and Security, are export-control-focused and apply a different technical standard – the monitor tests export classification, licence determination, end-use controls, and screening against the Denied Persons and Entity Lists rather than the OFAC SDN List. As of early 2026, both agencies use monitorship as a resolution tool in significant enforcement settlements, but the structural differences between the two programmes create material operational risk for any company managing obligations under both.
This analysis maps the two monitorship regimes side by side, identifies the points of practical divergence, and sets out what a cross-border business must address to manage concurrent or sequential monitorships without compounding its enforcement risk.
What is a compliance monitorship, and when do OFAC and BIS impose one?
A compliance monitorship is an independent oversight mechanism imposed as a condition of an enforcement settlement, under which a court-approved or agency-approved third party tests and reports on the business's compliance with the terms of the settlement and the underlying regulatory requirements. Under OFAC, a monitorship typically arises in settlements where the agency has assessed an egregious apparent violation, where systemic programme failures were present, or where the subject lacks a credible record of sustained compliance. Under BIS, monitorship appears in settlements involving significant export-control failures – mis-classified items, unlicensed exports to restricted destinations, or inadequate end-use screening.
The trigger for each regime is different in emphasis. OFAC is primarily concerned with whether a sanctioned party received value, whether the compliance failure was wilful or reckless, and whether management was aware of or concealed the violation. BIS weighs the sensitivity of the exported item, the destination, the end user, and whether the exporter had reason to know that the transaction was prohibited. Both agencies assess the "five factors" relevant to aggravation and mitigation, but the content of those factors is shaped by each agency's distinct statutory mandate – sanctions compliance on one side, export-control compliance on the other.
In our cross-border practice, we regularly advise businesses that have received a subpoena or a pre-penalty notice from one agency and are simultaneously under investigation by the other. The two investigations may be triggered by the same transaction, but they are resolved on different legal bases, with different evidentiary standards, and – if they result in monitorships – with monitors who report to different parts of the US government.
How does the OFAC monitorship standard work in practice?
An OFAC monitorship measures compliance against the agency's published framework for an effective sanctions-compliance programme, which identifies management commitment, risk assessment, internal controls, testing and auditing, and training as the five essential components. The monitor's mandate, set out in the settlement agreement, will specify which elements are in scope, the reporting period, the frequency of reports to OFAC, and the standard of evidence required.
The monitor operates with access to the business's systems, its screening configuration, its ownership-and-control analysis, and its transaction records. In practice, the monitor functions as both auditor and educator: reporting deficiencies to OFAC, but also flagging to management what remediation is required. This creates a structural tension. The monitor owes its duties to the agency, not the company. Management must therefore treat every monitor communication as a quasi-regulatory interaction – not a privileged advisory conversation.
Key procedural points for the OFAC monitorship:
- The monitor's selection is typically subject to OFAC approval; the company may propose candidates but cannot appoint unilaterally.
- Monitor reports are submitted to OFAC on the agreed schedule; they are not protected by privilege and should be drafted accordingly.
- If the monitor identifies a new apparent violation during the monitorship period, that finding creates a reporting obligation that sits alongside – and may accelerate – the original settlement timeline.
- The monitorship period is fixed by the settlement agreement; extension is possible where OFAC assesses that the programme has not reached the required standard by the agreed end date.
Have you stress-tested your screening configuration before the monitor's first access review? In our experience, businesses that conduct a pre-monitorship gap analysis retain more control over the remediation narrative.
How does the BIS / EAR monitorship differ from the OFAC model?
The BIS / EAR monitorship is technically oriented toward export-control compliance: the monitor tests Export Control Classification Number (ECCN – the code identifying an item's position on the Commerce Control List and its associated licence requirements) determinations, licence exception reliance, end-use and end-user screening, and the business's procedures for identifying red flags under the EAR. The monitor does not assess sanctions-compliance in the OFAC sense; the subject of the review is the export-control programme.
This distinction has structural consequences. A BIS monitor will examine the classification logic applied to dual-use goods, the process by which the business determines whether a validated export licence or a licence exception applies, and the end-use control procedures that govern post-export monitoring of goods on the Commerce Control List. These are not elements that an OFAC monitor will assess in detail. The converse is equally true: an OFAC monitor will scrutinise ownership-and-control analysis and SDN-proximity exposure that lies outside the BIS monitor's mandate.
Three operational differences are worth flagging explicitly:
- Reporting chain: the BIS monitor reports to the Office of Export Enforcement (OEE); the OFAC monitor reports to OFAC's Compliance and Enforcement division. These are distinct government counterparts with different expectations, different preferred formats, and different levels of technical fluency in each other's area.
- Technical standard: BIS monitor testing is item-centric – it asks whether each export transaction was properly classified and licenced. OFAC monitor testing is entity-centric – it asks whether each counterparty and beneficial owner was properly screened.
- Document production scope: a BIS monitor will require access to the company's export-compliance documentation, including shipping records, commodity-jurisdiction rulings, and licence applications. An OFAC monitor requires transaction records, screening logs, and ownership analysis. The records overlap partially but are not co-extensive.
The bridge position in both cases is voluntary self-disclosure (VSD – a disclosure to the relevant agency of an apparent violation, typically before the agency discovers it independently). A VSD to OFAC does not satisfy any BIS reporting obligation, and vice versa. Where the same transaction triggers both, separate disclosures are required to separate agencies, on different templates, with different evidentiary content.
The position above covers the standard case. Your facts – the goods, the counterparty, the destination, the settlement terms – change the analysis materially. For an assessment of your exposure under either regime, contact Calder & Vance at info@caldervance.com.
Where do the two monitorships create the greatest risk of concurrent exposure?
The most acute concurrent risk arises where a single compliance failure is analysable under both regimes simultaneously. A shipment of controlled goods to an entity on both the Entity List and a relevant OFAC sanctions list triggers BIS export-control liability and OFAC sanctions liability in the same transaction. If that transaction is discovered during the monitorship period for one settlement, it may constitute a new apparent violation reportable to both agencies.
What does a business do when the OFAC monitor and the BIS monitor each request overlapping documentation simultaneously? The answer requires careful coordination – not because the requests conflict in law, but because the sequencing of disclosures and the framing of remediation can be used to manage the narrative across both proceedings. Poorly sequenced disclosure can make a contained BIS matter appear as aggravating evidence in an OFAC context, and vice versa.
Additional concurrent-risk areas include:
- Screening architecture: an integrated screening system that queries both OFAC and BIS lists is common, but the two checks use different matching logic and flag different attributes. A monitor from either agency may identify list-matching gaps that expose liability to the other agency.
- Ownership-and-control analysis: under OFAC, the 50 percent rule (the rule treating entities owned 50 percent or more in the aggregate by blocked persons as themselves blocked) governs whether a counterparty is treated as blocked. BIS applies a related but non-identical standard to entities on the Entity List. A gap in ownership analysis that an OFAC monitor identifies may also bear on whether a BIS red flag was properly assessed.
- Training records: both monitors will review training materials and attendance records. Training that addresses OFAC prohibitions but is silent on EAR red-flag indicators – or vice versa – exposes the programme to criticism from the monitor whose area is under-addressed.
- Personnel accountability: OFAC settlements with a monitorship element typically require the business to implement consequences for violations by individual employees. BIS can impose analogous requirements. Where both are in force, HR and legal need a unified policy that satisfies both agencies without creating internal inconsistency.
The cross-border dimension: how do UK, EU, and other regimes interact with a US monitorship?
A US enforcement settlement and monitorship bind only the parties to the settlement under US law. They do not of themselves impose obligations under UK OFSI financial-sanctions rules, the relevant EU Council sanctions regulations, or the export-control regimes of other jurisdictions. But in practice they have cross-border operational consequences that a compliance counsel advising a multinational cannot ignore.
First, the monitorship creates a documented record of compliance posture that is visible to other regulators. If OFSI or an EU competent authority is reviewing the same group's UK or EU operations, the OFAC settlement and monitor reports – to the extent they are publicly disclosed or producible under an information-sharing request – will inform that review. A remediated OFAC programme that is demonstrably effective can be a mitigating factor in a parallel OFSI or EU proceeding. A programme that the OFAC monitor has criticised as deficient is an aggravating factor.
Second, a monitorship may require the business to extend programme changes globally, not just to the US legal entity that settled. Where the OFAC settlement covers conduct by non-US affiliates acting in a US nexus – processing US-dollar transactions, using US financial infrastructure, or re-exporting US-origin goods – the remediated programme must address those affiliates' procedures. This overlaps with the scope of OFSI's ownership and control test (the UK standard for determining whether a non-listed entity is caught through a designated person) and with EU requirements around group-level compliance.
Third, the BIS EAR's extraterritorial reach – through the de minimis rule and the foreign direct product rule, both of which can bring non-US goods and transactions within BIS jurisdiction where they incorporate or are produced using controlled US technology – means that a BIS monitorship may require remediation of export-classification procedures in non-US entities that handle goods with a US-origin component. Those same entities may have independent export-control obligations under EU dual-use rules or UK export-control regulations, and the standards may diverge.
We regularly advise European and Asian multinationals that are simultaneously managing OFAC monitorship obligations in the United States and separate compliance-improvement programmes under OFSI or EU guidance. The practical challenge is to design a single global programme that satisfies all relevant standards, rather than running separate siloed responses that satisfy each agency in isolation but create inconsistency at the group level. Where a gap in the UK or EU programme is identified during a US monitorship, that finding can constitute a separate reporting trigger in those jurisdictions.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. For a confidential review of your monitorship obligations and their cross-border implications, write to info@caldervance.com.
Common programme failures that monitors identify – and how to address them before the first report
Monitors in both OFAC and BIS engagements return repeatedly to a core set of programme deficiencies. Knowing what they look for before the monitorship begins is not a tactical advantage over the regulator; it is basic preparation that any compliance counsel advising on a monitorship should have completed.
Under OFAC, the failures that draw the heaviest criticism cluster around three areas. The first is screening architecture: lists are not updated at the required frequency, fuzzy-matching thresholds are set too narrowly, and subsidiary and affiliate screening is inconsistent. The second is ownership-and-control analysis: businesses screen the direct counterparty but do not map the ownership chain to identify whether a blocked person holds a sufficient interest through intermediate entities. The third is escalation: potential hits are identified at the operational level but are not escalated to legal or compliance for a proper determination, often because the escalation procedure is unclear or the training does not reach front-line staff.
Under BIS, recurring failures involve ECCN classification: goods are classified using an obsolete commodity jurisdiction ruling, or the classification process relies on a supplier's representation without independent verification. Red-flag procedures are a second consistent weakness – staff identify a suspicious end-use inquiry but the red-flag procedure does not require them to escalate before accepting the order. Licence-exception reliance is a third area: the business applies a licence exception without documenting the analysis, creating an evidentiary gap that the monitor cannot verify and that defaults to a finding of non-compliance.
Remediating these areas before the monitor's first access review serves two purposes. It limits the number of findings in the monitor's initial report, which affects the trajectory of the monitorship. And it allows the business to present a credible remediation narrative – evidence that it has identified the failures independently and has already begun correcting them – which is a mitigating factor in both OFAC and BIS assessments of programme responsiveness.
Myth, misconception, and the monitorship the business did not expect
A common misconception among clients entering a monitorship for the first time is that the settlement has resolved the exposure. It has not. The settlement fixes the civil penalty for the conduct that has already occurred. The monitorship is the mechanism by which the agency satisfies itself that the same conduct will not recur. If the monitor identifies new apparent violations during the monitorship period, those are fresh enforcement matters – not covered by the settled penalty – and they may be assessed against a business that is now on record as having had systemic programme failures.
A related myth is that the monitor is a neutral expert whose findings are equally available to the company and the agency. The monitor's primary duty runs to the agency that approved the appointment. Monitor reports go to OFAC or BIS first. The company's access to those reports, and its ability to comment on draft findings before submission, are governed by the terms of the settlement agreement – and those terms are negotiated at the settlement stage, before the monitor is appointed. By the time the monitorship begins, the procedural framework is fixed. This is why the settlement negotiation is where compliance counsel earns its keep.
In our experience, businesses that engage sanctions and export-control counsel at the pre-settlement stage – before the penalty order is executed – consistently achieve better monitorship terms: broader rights to review draft reports, clearer scope limitations, shorter initial periods, and more precise definitions of the standard against which the programme will be tested. The equivalent counsel engaged after settlement can manage the monitorship, but cannot renegotiate its terms.
How Calder & Vance approaches compliance monitorship mandates
Calder & Vance acts for businesses at each stage of an OFAC or BIS enforcement and monitorship engagement. At the pre-settlement stage, we review the apparent violation, advise on voluntary self-disclosure, and negotiate the terms of the settlement and the monitorship mandate. At the monitorship stage, we scope the apparent violation record, map the programme against the monitor's expected testing methodology, and represent the business in its interactions with the monitor and the agency.
For cross-border businesses facing concurrent exposure under OFAC, BIS, OFSI, or the EU sanctions regulations, we design a unified global compliance programme that meets each agency's standard without creating internal inconsistency. We test the screening logic, map ownership and control, and redesign the programme to the five-element standard required by OFAC – while ensuring that the export-classification and end-use controls required by BIS are embedded in the same operational framework.
In a recent matter, a financial-services business was managing an OFAC monitorship when a BIS investigation was opened covering export-related payments processed through its correspondent-banking network. We assessed the overlap between the two proceedings, coordinated the disclosure sequencing, and restructured the group's global compliance programme to address both agencies' requirements within a single remediation timeline. The matter reached a stable monitorship position within the expected period without escalating to a second enforcement proceeding.
Related practices
- EU Apparent Violation Assessment – expert assessment of apparent violations under EU sanctions regulations, from initial scoping to remediation advice.
- OFAC vs EU Compliance Monitorship Analysis – side-by-side comparison of OFAC and EU monitorship structures and procedural obligations.
- OFAC vs EU Monitorship: Further Analysis – extended analysis of divergence points and group-level programme design.