In the complex ecosystem of international trade, companies often fear the regulatory scrutiny of the U.S. Department of the Treasury’s Office of Foreign Assets Control (OFAC). However, a recent enforcement action serves as a stark reminder that the primary investigation is often only half the battle. A company’s response to an administrative subpoena can—and often does—trigger a secondary, independent enforcement crisis.
On October 9, 2026, OFAC announced a $175,015 settlement with Pegasus Worldwide Logistics, a small integrated logistics firm with a modest headcount of approximately twelve employees. While the underlying sanctions violations were notable, the agency’s findings highlighted a more systemic failure: the company’s inability to provide a complete and accurate response to an official information request. This case underscores a critical operational reality: businesses facing sanctions inquiries must treat the investigative response process with the same level of legal rigor as the underlying transaction itself.
The Chronology of an Administrative Failure
The Pegasus case serves as a cautionary tale regarding the dangers of complacency and the risks of fragmented information sharing between internal stakeholders and external counsel.
The Initial Inquiry
The trouble began when OFAC served Pegasus with an administrative subpoena. The agency was investigating a specific equipment shipment facilitated by the firm, which involved a supplier that had recently undergone a name change. To assist the company in identifying the relevant files, the subpoena provided specific identifiers, including multiple potential supplier aliases, a dedicated email address, and a specific telephone number.
The First Response: A Fatal Oversight
On February 1, 2024, Pegasus submitted a certified response to OFAC. Despite the specificity of the subpoena, the company denied possessing any responsive information. This assertion was not merely an error of judgment; it was a formal declaration under oath that, according to the company’s internal review, no records of the transaction existed within their systems.
The "Smoking Gun" and the Correction
OFAC’s investigative machinery, however, had already captured evidence that contradicted the company’s denial. Shortly after the February submission, the agency presented Pegasus with an import-related record that explicitly identified the logistics firm as the freight forwarder for the transaction in question.
Faced with this irrefutable evidence, Pegasus scrambled to conduct a secondary search. The company ultimately located the responsive records, later admitting that it had failed to provide its legal counsel with the necessary information to prepare an accurate initial response. On August 8, 2024—more than six months after the initial deadline—the company submitted a revised, corrected response. OFAC subsequently attributed six distinct reporting violations to that six-month delay.
Supporting Data: The Anatomy of the Penalty
The settlement amount of $175,015 represents a culmination of both substantive and procedural failures. While the total penalty reflects the underlying sanctions violations, the six reporting violations stemming from the incomplete response significantly exacerbated the company’s liability.
Regulatory Framework
The governing authority for this enforcement action is 31 C.F.R. § 501.602, which mandates that companies provide complete and accurate information under oath when demanded by OFAC. The regulation is intentionally broad, defining "documents" to include:
- Electronic Communications: Emails, text messages, and chat logs.
- Operational Records: Invoices, bills of lading, and shipping manifests.
- Metadata: Electronic footprints that track the creation and modification of files.
For a small business like Pegasus, the failure to reconcile these disparate data sources proved catastrophic. The discrepancy between the company’s February claim of "no responsive records" and the actual existence of the documents provided to OFAC later served as a textbook example of a deficient inquiry.
Official Responses and Compliance Considerations
In its Enforcement Release, OFAC did not mince words regarding the "Compliance Considerations" for firms subject to investigation. The agency emphasized that the "nature and extent of a subject’s cooperation" is a primary factor in determining the ultimate resolution of an investigation, including the calculation of financial penalties.
The Value of "Fulsome" Cooperation
OFAC stated that timely and comprehensive cooperation demonstrates that a firm takes its compliance obligations seriously. Conversely, the failure to provide a "complete and satisfactory" response risks two major consequences:
- Forfeiture of Mitigation Credit: A company that forces OFAC to "prove" its case by presenting evidence that the company should have disclosed voluntarily loses the opportunity to receive a reduction in penalty based on cooperative behavior.
- Standalone Penalties: The failure to respond accurately can trigger separate enforcement actions under the Reporting, Procedures, and Penalties Regulations, essentially creating a "second layer" of fines that are independent of the original sanctions infraction.
Implications for Cross-Border Businesses
The Pegasus case is not merely an outlier; it is a blueprint for how regulatory bodies handle information requests. For global businesses, the implications are clear: the defense of a sanctions investigation begins the moment the subpoena hits the desk, not when the legal brief is drafted.
1. Mapping the Data Before Drafting
A "search" is not a singular event. It is a systematic mapping of information. Firms must identify:
- The Custodians: Which employees handled the transaction?
- The Systems: Where are records stored? (Cloud, server, local hard drives, or third-party platforms).
- The Aliases: Are there variations in counterparty names, email addresses, or phone numbers that could bridge the gap between a seemingly "clean" transaction and a restricted entity?
2. The Bridge Between Facts and Counsel
One of the most damaging admissions by Pegasus was that it "had not provided its attorney necessary information." This highlights a dangerous silo effect. Outside counsel can only provide as much value as the information they are given.
- Explicit Information Flow: Companies must establish a clear, documented channel for transmitting internal data to counsel.
- Informed Certification: Before an officer signs a certification, they must be able to explain the factual inquiry supporting each answer. If they cannot explain how a document was found or why a record was excluded, the certification is inherently high-risk.
3. Proactive Management of Gaps
If a company discovers that it cannot meet a deadline or that the scope of a subpoena is ambiguous, the worst course of action is to submit a "placeholder" or incomplete response.
- Engage Early: Raise scope disputes or requests for extensions with OFAC immediately.
- The Duty to Supplement: If an initial response is found to be deficient after the fact, the company should immediately notify counsel and draft a supplemental response. Self-correction, while not a total "get out of jail free" card, is viewed significantly more favorably than discovery by the agency.
4. Testing the "No Responsive Records" Defense
In the world of government enforcement, the "no responsive records" response is the most heavily scrutinized. If OFAC has issued a subpoena, they almost certainly have a factual basis for believing the documents exist. Before a company claims a record does not exist, they must be able to demonstrate that they have conducted a "searching inquiry"—not just a cursory search of a single database.
Conclusion
The Pegasus Worldwide Logistics settlement serves as a potent reminder that in the eyes of regulators, procedural integrity is just as important as substantive compliance. For firms operating across borders, the capacity to respond to an OFAC inquiry with precision, transparency, and speed is a core business competency. As the Pegasus case illustrates, a company’s failure to manage its own internal investigative process can turn a manageable compliance inquiry into an unnecessary and expensive enforcement nightmare. The lesson for the future is clear: when the government comes knocking, the quality of your internal audit trail will define the outcome.
