Content Type: Article

  • From confidential to careless: The case of the unprotected customer list

    From confidential to careless: The case of the unprotected customer list

    ARTICLE

    From confidential to careless: The case of the unprotected customer list

    Aug 14, 2025

    Read time: 6 min

    Key takeaways
    Overview

    The US Court of Appeals for the Tenth Circuit affirmed a summary judgment dismissal of a trade secret misappropriation complaint, finding that the plaintiff failed to take reasonable measures to maintain the secrecy of a customer list. The Court also reversed the district court’s Daubert ruling, finding that it improperly exceeded the scope of Fed. R. of Evid. 702. John Snyder v. Beam Technologies Inc., Case No. 24-1136 (10th Cir. Aug. 5, 2025) (Matheson, Bacharach, Federico, C.J.)

    John Snyder downloaded a national customer list containing more than 40,000 names from his former employer’s client-relationship management system. According to metadata analysis, Snyder last modified the file only three minutes after its creation, strongly suggesting that no meaningful changes or additions were made after the download. Snyder’s employment with the company ended in 2016. Following a two-year period of unemployment, he accepted a position with Beam in 2018.

    Synder claimed that Beam induced him to join the company by promising compensation in exchange for customer information he obtained from his former employer. After beginning his employment at Beam, Synder created derivative documents containing subsets of the customer list. However, he inadvertently included the entire customer list as a separate tab in each of the documents he emailed to Beam employees. The documents were sent without any confidentiality markings or indications that they contained trade secrets. Snyder did not restrict access to the documents, apply password protection, or notify Beam that any of the content was proprietary or confidential.

    After realizing he had distributed the full list to multiple Beam employees, Snyder took no action to object to Beam’s use of the data or attempt to retrieve the documents. He also failed to inform Beam that he considered any of the materials to be trade secrets. Instead, Snyder appeared to ratify the disclosure, telling Beam’s chief executive officer that he had intentionally shared the customer list with the recipients. A few months later, Beam terminated Snyder for unexplained reasons.

    Synder sued Beam for trade secret misappropriation and several state law claims. Beam moved for summary judgment on the trade secret claims, which the district court granted, finding that Synder failed to show that he owned the customer list. The district court denied Beam’s motion on Synder’s other claims.

    Both parties filed motions to exclude expert witness testimony at trial. The district court granted Beam’s motion to exclude Snyder’s damages expert under Fed. R. of Evid. 702, ruling that the expert could not support Snyder’s claimed damages for the remaining causes of action.

    The district court found that Synder failed to show that he could obtain lost wages damages on any of the surviving claims. Expanding the scope of its ruling, the district court excluded not only the expert testimony, but also all evidence and fact witnesses related to lost wages damages at trial. Following the court’s ruling, Snyder and Beam settled one of the claims and jointly moved to dismiss the remaining claims. Snyder then appealed.

    Synder argued that the district court erredin its summary judgment ruling in finding that he provided insufficient evidence of his “ownership” of the customer list. He argued that under the Colorado Uniform Trade Secrets Act (CUTSA), he only needed to prove possession, not ownership, of a trade secret. The Tenth Circuit agreed, relying on its own precedent, and reversed summary judgment based on the “ownership” element of the CUTSA claim.

    The Tenth Circuit next addressed whether Synder took reasonable measures to maintain secrecy and whether Beam misappropriated the customer list. Snyder argued that his efforts to maintain secrecy included saving the list on his personal computer, on a USB drive, and on his password-protected work laptop. However, the Court found these actions insufficient, describing them as “benign” and falling short of the reasonable steps required to preserve trade secret protection. The Court emphasized that merely storing the alleged trade secret on an employer-provided laptop, without password-protecting the document or labeling it as a trade secret or even as confidential, was not a reasonable measure to ensure secrecy. The Court also noted that Snyder admitted he did not mark any of the state-specific lists as confidential, did not use password protection, did not require Beam employees to sign confidentiality agreements, failed to inform recipients at Beam that the broker information was confidential, and failed to claw back the list after accidentally disclosing it. The Court found that Snyder had affirmatively ratified his disclosure by telling Beam’s CEO that he had intentionally shared the customer list with Beam employees. Based on the undisputed facts, the Court concluded that no reasonable jury could find that Snyder’s actions met the minimum threshold for reasonable measures to protect a trade secret. Accordingly, the Court held that summary judgment was appropriate on the issue of secrecy. Having resolved the matter on that ground, the Court declined to address whether Beam had misappropriated the list.

    The Tenth Circuit reviewed the district court’s order excluding Snyder’s expert witness and barring all evidence and testimony regarding his alleged lost earnings and wages damages. The Tenth Circuit explained that the district court’s use of Fed. R. of Evid. 702 to exclude all such evidence exceeded the rule’s scope, which applies only to expert witnesses. The Court noted that the district court failed to provide Snyder with fair notice that he needed to present all fact evidence and legal arguments in response to what was framed as a motion to exclude expert testimony. Concluding that the district court effectively entered summary judgment without following the proper procedures under Fed. R. of Civ. Pro. 56, the Court reversed the exclusion order. The Court emphasized that dispositive rulings on damages should be made through a summary judgment process that ensures proper notice and opportunity to respond, rather than under the expert witness exclusion standard.

    Authors

    Jodi Benassi

    Partner

    San Francisco

    More insights
    Endnotes

  • This Insight Headline Should Be 10 Words or Fewer – H1

    This Insight Headline Should Be 10 Words or Fewer – H1

    ARTICLE

    This Insight Headline Should Be 10 Words or Fewer – H1

    January 30, 2025

    Read time: 4 min

    Key takeaways
    Overview

    In partnership with [CompanyName] – add only if co-branded.

    The Overview module is required for all Insights pages and introduces the content. Limit this section to a few short paragraphs:

    • Lead with the top two or three takeaways
    • Answer the questions “What’s new?” and “Why does it matter?”

    Whether using the Overview and Table of Contents (TOC) modules or the Overview and In Depth modules, you have the opportunity to incorporate heading styles throughout your content, up to H6. We’ve modeled each style below, for reference.

    If using Overview and TOC, readers will be able to navigate through each TOC item heading from navigation at the top of the page (appearing to the left of “Overview”). The accordion function is only available when using Overview and In Depth.

    This is a standard sub-heading – H2

    The content included here should fall within the sub-heading topic.

    This is a sub-sub heading – H3

    As you get more granular within a given topic, use additional heading styles. Styles should always be used in descending order with the smallest number representing the highest level.

    Get more granular with this level heading – H4

    For example, only use the H4 style after an H3. If it’s not preceded by an H3, do not use the H4 style. To take it further…

    Use this level heading – H5

    Or…

    Use our sixth and final style – H6

    Most importantly, be strategic in how you use each. This concludes our overview of heading styles.

    Note: If you choose to work with Creative to include images within content, please note that images must be optimized for web and the width must be 825 pixels.

    In depth

    For insights using the In Depth section, input main content here. If desired, you can hide the automated In Depth heading title, which appears in the H2 style, by checking the box next to “Hide Title Section” in the backend.

    When using this module, delve into greater detail about the key items here. It also features an accordion function, which we’ve modeled below. If an article has multiple topics or needs to be broken up, use sub-headings to do this (again, up to H6).

    Finally, within this or any other (free text) module you can use a blockquote style to showcase pull quotes. Blockquote styles are modeled below. The following are recommended guidelines for pull quotes:

    • Pull quotes must be pulled from the text on the page – this means that the pull quote will duplicate some of the text in the body copy (this is deliberate so that, if the pull quote is removed from a page, the content remains the same)
    • Pull quotes should aid reader flow and help call out important snippets of content (limit: one per Word doc page, or three max per web page)
    • Ideal length: three lines or fewer
    • Do not include quotation marks around your pull quote – those are added automatically in the formatting
    • A pull quote must be placed before the content it is referencing
    • For consistency, only one pull quote style should be used within a single page (i.e., style 1 or style 2 never both styles together)

    Pull quote style 1:

    This is a sample pull quote in the standard style.

    Pull quote style 2:

    This is a sample pull quote in a second style.

    Button style:

    Accordion item 1 body text.

    Authors

    Aashish Kapadia

    Partner

    Austin

    More insights

  • Key takeaways | Navigating financial distress: Strategies for hospitals and health systems

    Key takeaways | Navigating financial distress: Strategies for hospitals and health systems

    ARTICLE / CLIENT ALERT

    Key takeaways | Navigating financial distress: Strategies for hospitals and health systems

    August 13, 2025

    Read time: 7 min

    Key takeaways
    Overview

    Hospitals and health systems are facing significant financial and operational challenges, including inadequate reimbursements, rising labor costs, and regulatory and economic uncertainties. These hurdles, coupled with the One Big Beautiful Bill Act (OBBBA or the Act), create the potential for government actions aimed at cutting Medicare and Medicaid spending to increase the risk of hospital closures, particularly rural and safety net hospitals. Our webinar detailed the current healthcare financial distress landscape, explored potential options, and highlighted early planning strategies to improve long-term sustainability.

    In depth

    The current financial distress landscape

    Rural and safety net hospitals are at a heightened risk of closure. The financial strain is particularly pronounced among certain organizations, which often serve a high percentage of Medicaid, Medicare, and uninsured patients. Many industry publications have reported that more than 700 rural hospitals are at potential risk and, of those, more than 300 are at immediate risk. These facilities are facing tightened liquidity caused by the financial and operational challenges listed below, making it difficult to meet financial obligations such as paying debt service, vendors, or even payroll.

    Key financial and operational challenges

    • Labor and other operating costs have significantly increased, especially during the COVID-19 pandemic. While the rate of increase has slowed, the impact remains substantial and lasting. Some facilities often must pay more to attract and retain staff because of smaller labor pools, exacerbating their financial challenges. Additionally, the aging of the healthcare provider labor force and increased number of retirements has negatively impacted the size of the labor pool, resulting in upward pressure on wages and reduced access to care. Further, the high level of inflation and recently implemented tariffs will continue to have a significant impact on supplies and other operating costs.
    • Reimbursement rate increases from the Centers for Medicare & Medicaid Services (CMS) and other payors are not keeping up with the rising cost of care, causing operating margin deterioration and challenges meeting capital investment requirements.
    • OBBBA contemplates sweeping Medicaid eligibility requirements and a reduction in federal funding for states, among other changes, all of which will negatively impact hospitals and exacerbate the challenges healthcare providers are already facing. These uncertainties can lead to delays in strategic decisions and mergers and acquisitions deals, as decision-makers need clarity to plan effectively.

    The importance of early planning and action

    Detection and a realistic assessment of the distressed situation and related ramifications are critical for creating an opportunity to navigate a potential solution or mitigate the negative impacts. Planning ahead and taking steps to address financial distress early can lead to substantially better results for hospitals and health systems and the communities they serve. Early planning allows hospitals to evaluate their financial situation, consider various strategies, implement cost savings initiatives, identify liquidity needs, and potentially negotiate better terms for transactions or reorganizations.

    Without early detection and planning, hospitals may face increased costs, reduced options, and a higher risk of closure, which can have a significant impact on the community, especially in rural areas where hospitals are often the largest employers and provide essential access to healthcare. The uncertainty surrounding Medicaid cuts, tariffs, and rising operating costs can paralyze decision-making. Therefore, addressing financial distress and taking measured action as soon as possible can help hospitals address these challenges more effectively.

    Strategies for navigating financial distress

    • Implementing cost reduction and cash conservation initiatives, improving revenue cycle management (including coding and documentation), and eliminating unprofitable services may be necessary to extend the liquidity runway and enable a hospital to achieve stabilization. However, there is a balance to be mindful of to preserve clinical services to remain an attractive partner for a future affiliation or merger with a larger system.
    • Forming affiliations and partnerships with larger health systems can provide financial stability and operational support. Larger systems can offer economies of scale, shared resources, and better negotiating leverage with vendors and payors. However, the current economic uncertainty and reduced capital expenditure budgets have made it harder for these deals to materialize. Implementing immediate cost reductions and identifying performance improvement opportunities may make an organization a more attractive affiliation or merger partner.
    • For hospitals that qualify, converting to a rural emergency hospital (REH) is a potential solution. This model can reduce financial burden by focusing resources on essential emergency care, which is often the most critical service in rural areas. However, the conversion process requires careful planning and regulatory approval.
    • To attempt to mitigate the substantial impact of the OBBBA Medicaid cuts on the healthcare industry, the Act incorporates the Rural Health Transformation Program, which will allot $10 billion to states for each fiscal year from 2026 to 2030, for a total of $50 billion for the five years. States must apply to receive funds from the program, and rural health providers will need to be proactive and coordinate with the state to obtain funding. For each of the fiscal years, 50% of program funds will be equally divided among the 50 states, but CMS will have substantial discretion as to the amount each state receives from the other 50%.
    • Hospitals may use chapter 11 bankruptcy to reorganize and address financial distress. It provides a structured process to fix issues, leave behind debt, and reject unfavorable contracts. It can also increase the value of a sales process because it allows a buyer to pick which assets it wishes to purchase and leave behind certain liabilities. While bankruptcy can be an effective solution, it is an expensive and complex process that can have uncertain outcomes. Early planning and negotiation can lead to more favorable results. Prepackaged bankruptcy sales, where agreements are entered into before filing, can help streamline the process and minimize disruption while allowing hospitals to evaluate their financial situation, consider various strategies, and potentially negotiate better terms for transactions or reorganizations.

    As noted during the webinar, these financial challenges paradoxically create opportunities for better-situated hospitals and health systems to pursue growth strategies while challenged rural and safety net hospitals may need to wind down and close.

    Regulatory and transaction considerations

    • Hospitals and health systems face regulatory and antitrust hurdles that can complicate their restructuring efforts. Antitrust concerns can arise when multiple hospitals in the same community consider merging or affiliating, leading to regulatory scrutiny and a challenging approval process. The failing firm exception in antitrust law can be helpful, but it requires clear evidence of financial distress and a lack of another suitor.

    Regulatory and operational wind-down considerations

    • Closing a hospital involves multiple regulatory hurdles, including licensure issues and state approvals. Health systems must coordinate with various stakeholders and be prepared for public scrutiny and the likelihood of negative public relations. Different states also have varying regulatory and approval requirements for hospital closures, which can complicate the process, extend the time before action on the closure plan is authorized, and exhaust the limited resources needed to effectuate a wind down and closure. Government and elected officials may also attempt to intervene, formally or informally, risking additional delays. Having a carefully crafted communication plan is essential to the wind down and closure process.
    • Hospitals should pay close attention to the post-closure management of medical records, accounts receivable, employee and provider records, hazardous materials, the disposition of equipment and supplies, and security and maintenance of facilities. Ensuring compliance with all legal and regulatory requirements is crucial to avoid additional issues and maintain the trust of the community.

    Conclusion

    Navigating financial distress in the healthcare sector requires a multifaceted, proactive approach. Hospitals and health systems can stay ahead of the curve by evaluating their financial health, exploring strategic partnerships, and understanding the regulatory landscape. Timely and transparent communication with regulators and stakeholders can maximize restructuring options and facilitate smoother transitions. By proactively addressing financial issues, hospitals enhance their chances of long-term sustainability and continued service to their communities.

    Additional authors:

    Authors
    More insights

  • France’s Digital Services Tax Faces Constitutional Crossroads

    France’s Digital Services Tax Faces Constitutional Crossroads

    ARTICLE / CLIENT ALERT

    France’s Digital Services Tax Faces Constitutional Crossroads

    August 13, 2025

    Read time: 4 min

    Key takeaways
    Overview

    In a significant development for multinational companies operating in the digital space, France’s Supreme Administrative Court (Conseil d’État) has referred the country’s Digital Services Tax (DST) regime to the Constitutional Court for review. On June 17, 2025, the Conseil d’État issued Decision No. 502728, referring Articles 299, 299 bis and 299 quater of the French Tax Code, provisions that define the scope, tax base, and assessment procedures of the DST, for constitutional scrutiny. The referral arises from a challenge submitted by Digital Classifieds France, which contends that the current design of the DST violates key principles enshrined in the French Constitution, namely the principle of equality before the law.

    In depth

    This legal challenge, known as a priority constitutional question (QPC), has the potential to significantly alter the DST landscape in France. The Constitutional Court now has until September 17, 2025, to issue its ruling. Depending on the outcome, the Court may uphold the DST in its current form, declare certain provisions unconstitutional, or strike down the entire regime. Notably, French constitutional jurisprudence often limits the retroactive effect of its decisions, applying them only to claims pending at the time of judgment. As such, companies that have paid DST in prior years and wish to preserve their rights to reimbursement must act swiftly. Taxpayers are strongly advised to file formal claims with the French tax authorities before the September 17 deadline, in order to ensure their eligibility for any future refund that might result from a favorable ruling.

    At the heart of the challenge are several fundamental issues. The claimant argues that the DST unfairly distinguishes between French and non-French companies, as well as between digital and non-digital services, thus violating the principle of equality before the law. Additional concerns include the DST’s group-based thresholds, the method for determining taxable presence in France via the so-called “coefficient of national presence,” and the potential for disproportionate treatment of foreign operators, who may be disadvantaged in enforcement and audit procedures. The case also raises concerns over the way the DST captures revenues (only applying above certain revenue thresholds) which can lead to distortions in treatment between similarly-situated businesses.

    This judicial review has broader implications not just for companies currently subject to France’s DST, but also for policymakers and tax professionals tracking the evolution of unilateral digital taxation across Europe. France’s DST, introduced in 2019 and applied retroactively to that year, was among the first in Europe and has since been a focal point in global discussions about fair taxation in the digital economy. If the Constitutional Court finds significant fault with the DST, the ruling may prompt legislative revisions and could even influence similar measures across the European Union.

    In the interim, legal and tax teams at affected companies, particularly general counsel, CFOs and group tax directors, should be closely monitoring developments. Those considering filing for a DST refund are encouraged to consult legal advisors and submit claims promptly, as any delay could forfeit their right to benefit from a favorable decision. While the future of the DST remains uncertain, the Constitutional Court’s decision is expected to set a crucial precedent in the intersection of digital regulation and constitutional tax law in France.

    Authors

    Romain Desmonts

    Partner

    Paris

    More insights

  • Washington’s advertising services tax: Sourcing rules clear as mud

    Washington’s advertising services tax: Sourcing rules clear as mud

    ARTICLE

    Washington’s advertising services tax: Sourcing rules clear as mud

    Aug 12, 2025

    Read time: 6 min

    Key takeaways
    Overview

    Washington’s sales tax on advertising services takes effect October 1, 2025, and comes in two forms: a tax on digital automated services and a tax on retail sales of advertising services. Both impositions apply to digital advertising services delivered using the internet. This makes Washington an outlier as currently only two other states impose a tax on sales of advertising services: Hawaii and New Mexico.

    Washington State is a member of the Streamlined Sales Tax (SST) Governing Board. As an SST member state, it is required to follow – and does follow – the Streamlined Sales and Use Tax Agreement’s (SSUTA) sourcing regime.[1] This sourcing regime uses the familiar hierarchical approach:

    • If the buyer receives the product at the seller’s business location, the sale is sourced to the seller’s business location.
    • If the product is not received at the seller’s business location, the sale is sourced to the location where receipt by the purchaser (or the purchaser’s donee, designated as such by the purchaser) occurs, including the location indicated by instructions for delivery to the purchaser (or donee) known to the seller.
    • If neither apply, the sale is sourced to the location indicated by an address for the purchaser that is available from the seller’s business records (typically the purchaser’s billing address).

    As applied to sales of services, the terms “receive” and “receipt,” as used in the sourcing hierarchy, mean “making first use of services.”[2]

    As applied to sales of advertising services delivered using the internet, the first rung of the sourcing hierarchy generally would not apply because the first use of the advertising service would not occur at a business location of the purchaser.

    The Washington Department of Revenue (DOR) is in the process of developing interim guidance on how sellers are to source sales of advertising services. DOR representatives told us they are taking a close look at whether it is appropriate to source these sales to the location where the advertisement is viewed. They said they are focusing on how to interpret the phrases “receipt by the purchaser” and “known to the seller” in the second rung of the sourcing hierarchy.

    In the context of internet advertising, how and where does a purchaser “make first use of” the service?

    Internet advertising is a largely automated function capable of serving up millions of advertisements to millions of viewers per minute. Typically, the technology serving the ads is not connected to the service provider’s billing system. Does the second rung of the sourcing hierarchy require such granularity that the sale of the advertising service be sourced to the locations of the myriad ad viewers? Does the supply of each internet ad constitute a separate sale that must be individually sourced? Or does the purchaser make first use of the advertising service at its headquarters? If the answers to the first two questions are “yes,” it would put unbelievable complexity and administrative burden on the seller, make audits unnecessarily time-consuming, and undermine SSUTA’s fundamental purpose of reducing compliance burdens.[3] If the answers to the first two questions are “no” and the answer to the third question is “yes,” then there is little to no difference in the sourcing result between the second and third rungs of the sourcing hierarchy.

    One could suggest that the references to “purchaser’s donee” in the sourcing rule indicate that ad viewers might be “donees” of the advertising service purchaser, requiring sourcing to the ad viewer’s location. However, the issue paper developed by the Streamlined Sales Tax Project (SSTP) drafters of the sourcing hierarchy reveals the purpose of the reference to “purchaser’s donee” in the second rung of the sourcing hierarchy:

    The parenthetical language referring to a donee is intended to apply a destination rule to gifts involving shipment. It is a condition of applying this sourcing principle to gifts that the seller know both that a gift is occurring and the address of delivery. If the product is being shipped to someone other than the purchaser who is not known by the seller to be a donee, this rule does not apply. In these circumstances the seller does not know a location for receipt by the purchaser.[4]

    That same issue paper supports sourcing internet advertising services to the purchaser’s billing address under the third rung of the sourcing hierarchy. The issue paper discusses sourcing “digital goods” (a term not defined in the SSUTA) and how advertising services delivered via the internet are in the nature of digital goods:

    We believe subsections (a) and (b) will apply to most sales of tangible personal property and services, because usually either the sale will occur at the seller’s store or the seller will know the location to which to send the property that she is selling or servicing to the purchaser. But there still will be some instances involving tangible personal property where this knowledge will be missing, to say nothing of the potential for not having the pertinent information for some sales of digital goods. The potential for subsections (a) and (b) not to apply undoubtedly increases when the digital product is not sold on tangible media but is delivered electronically. Subsections (c), (d) and (e) are essentially intended to cover sales where the seller does not know the location at which receipt by the purchaser occurs.[5]

    Regardless of whether the purchaser of internet-delivered advertising services is considered to make first use of the service at its location (justifying sourcing to that location), or the seller lacks sufficient information as to the location of receipt (justifying sourcing to the purchaser’s billing address), there are bases under both rules for not requiring these services be sourced to the ad viewer’s location.

    Authors

    Stephen P. Kranz

    Partner

    Washington, DC

    Mark Nebergall

    Counsel

    Washington, DC

    Jonathan C. Hague

    Associate

    Austin

    More insights
    Endnotes

    [1] SSUTA §§ 310.A, 311, RCW § 82.32.730(1), (9)(f).

    [2] SSUTA § 311.B, RCW § 82.32.730(9)(f).

    [3] SSUTA § 102.

    [4] SSTP, Sourcing Issue Paper, January 2002, Page 9.

    [5] Id.


  • Cooperate, protect, and challenge: Responding to dawn raids conducted by EU competition authorities

    Cooperate, protect, and challenge: Responding to dawn raids conducted by EU competition authorities

    ARTICLE / CLIENT ALERT

    Cooperate, protect, and challenge: Responding to dawn raids conducted by EU competition authorities

    August 13, 2025

    Read time: 15 min

    Key takeaways
    Overview

    Dawn raids conducted by antitrust authorities are stressful events. Among other issues, the ensuing investigations consume significant time and effort and often result in high fines for the companies involved. It is therefore not surprising that antitrust dawn raids often attract pitched legal battles – including recent raids conducted against well-known players in the tyre and fragrance industries.

    In depth

    Inspections in the tyre industry

    On July 9, 2025, the General Court (GC) issued a judgment involving the French tyre manufacturer Compagnie Générale des Établissements Michelin (Michelin). Michelin and other global tyre manufacturers were subject to dawn raids conducted by the European Commission (Commission) in January 2024, as part of a broader investigation into anticompetitive practices in the tyre sector. In its application, Michelin sought the annulment of the inspection decision, and the return of all documents seized.

    The interesting element to this case is that the dawn raid was not based on complaints from competitors or customers (as is often the case) but on evidence that the Commission extracted from a large number of earnings calls by the tyre companies concerned. The Commission had set up a monitoring tool “in order to analyse several hundred thousand earnings calls in various sectors and geographical areas”. These earnings calls were analysed through key word searches, using terms like “price discipline” or “industry following”. Based on this analysis, the Commission came to the conclusion that these key words popped up frequently in the earning calls of the tyre companies concerned, and according to the Commission this evidence was sufficient to justify dawn raids.

    Michelin challenged the legality of the Commission’s dawn raid decision, arguing that the contested decision lacked a sufficiently detailed statement of reasons, as required under Article 296 of the Treaty on the Functioning of the European Union (TFEU) and Article 20(4) of Regulation No 1/2003. Michelin argued at the GC hearing that the dawn raid decision was so vague it allowed the Commission “to seize any document over a very long period.” Hence, the inspection essentially amounted to a “fishing expedition.”

    In its judgment, the GC confirmed in general that the Commission must indicate as precisely as possible what it is looking for and the elements to be verified. By contrast, it is not necessary to specify the exact scope of the market concerned, the exact legal classification of the alleged infringements or the exact period during which those infringements were allegedly committed, provided that the inspection decision contains the essential elements. The reason is that inspections take place at the beginning of the investigation, at a time when the Commission does not generally have precise information enabling it to make a specific legal assessment.

    Having clarified these general principles, the GC distinguished two different periods.

    For the main period, the Commission had gathered sufficiently serious evidence suggesting that Michelin and other tyre manufacturers may have coordinated pricing strategies through these earnings calls, including unilateral declarations from major tyre manufacturers. This evidence was sufficient to justify the inspections.

    By contrast, for an earlier period, the Commission was unable to identify any such earnings calls and relied primarily on retrospective references made in more recent calls. The various statements submitted for the earlier period did not mention any future intentions or respective pricing strategies that might be implemented during that period. Consequently, the GC concluded that the Commission’s assumption of price coordination among major tyre manufacturers during the earlier period was not sufficiently supported by evidence.

    As a result, the GC partially annulled the inspection decision, thereby excluding evidence collected for the unjustified period. However, it upheld the validity of the inspection for the main period, confirming that the Commission had met the threshold of “sufficiently serious indicia” for that timeframe.

    Inspections in the fragrance industry

    On March 7, 2023, the Commission caried out dawn raids on several companies active in the fragrance industry.

    This inspection and the underlying decision have resulted in various issues. First, during one of the inspections, an employee of one of the companies raided, International Flavors & Fragrances (IFF), allegedly deleted WhatsApp messages. leading to a sanction decision by the Commission. Second, another raided company, Symrise, challenged the legality of the inspection decision itself, claiming a violation of the right of inviolability of private premises and privacy and an infringement of the Commission’s obligation to state reasons for the inspection.

    Alleged Obstruction of inspections by IFF

    During the inspection at the premises of IFF, the Commission alleged that an IFF employee had deleted WhatsApp messages from his professional mobile phone. The deleted messages contained communications with a competitor and related to the Commission’s ongoing antitrust investigation.

    This conduct resulted in a decision issued on June 24, 2024, in which the Commission imposed a fine of EUR 15.9 million for obstructing the inspection (Decision of the Commission of 24 June 2024, IFF, case AT.40882). This sanction underscores the severity of the Commission’s position when it comes to obstruction of inspections, for which a company can be fined up to 1% of its total worldwide turnover.

    This is not the first time the Commission has sanctioned a company for such conduct. In 2012, Czech companies active in the energy market were fined EUR 2.5 million by the Commission after a password, used by the Commission’s officials to access a company’s email accounts, was changed and attempts were made to redirect incoming emails while the company was under investigation (Decision of the Commission of 28 March 2012, EPH, case AT.39793). Two other important Commission decisions for obstructing inspections were issued in 2008 and 2011, both due to the breaking of, or “tampering with”, seals, for which the Commission issued fines of EUR 8 million and EUR 38 million, respectively (Decision of the Commission of 24 May 2011, Suez Environment, case AT.39796 ; and decision of the Commission of 30 January 2008, EON, case AT.39326).

    Challenge of the inspection decision by Symrise

    Symrise brought an action before the GC contesting the legality of the Commission’s inspection decision. The company alleged (i) a violation of the right of inviolability of private premises and privacy and (ii) an infringement of the Commission’s obligation to state reasons.

    On April 30, 2025, the GC issued its judgment (Judgment of the General Court of 30 April 2025, Symrise AG v European Commission, T-263/23, EU:T:2025:417) in which it rejected Symrise’s appeal and considered that the Commission’s dawn raid was lawful. The following examines the two bases of the appeal and the GC’s response:

    First ground of appeal: Violation of the right of inviolability of private premises and privacy

    The first ground of appeal alleged that the Commission decision was arbitrary and that there was a disproportionate interference with the right to privacy.

    Symrise argued that the inspection decision was arbitrary since the Commission did not have “sufficiently serious evidence to suspect its involvement in any competition law infringement and accordingly justify an inspection of its premises” (Symrise decision previously cited, para 54). The company characterised the dawn raid as a “fishing expedition,” a term referring to an inspection conducted by the Commission without justification. This was the situation, for example, in the 2012 Nexans case, where the GC partially annulled an inspection decision, holding that the Commission had no reasonable grounds to conduct the inspection (see below; Judgment of the General Court of 14 November 2012, Nexans and Nexans France v. Commission, T‑135/09, EU:T:2012:596).

    However, the GC rejected the argument of a “fishing expedition” and recalled that “the various indicia which make suspecting an infringement possible must not be assessed separately but as a whole, and can be mutually supportive” (Symrise decision previously cited, para 60). According to the GC, the Commission had presented an open-source intelligence report that made clear that it:

    “possessed sufficiently specific and clear indicia for it to suspect that the four largest fragrance manufacturers, which include the applicant, aligned, imposed and defended their industrial policy to the detriment of their other competitors through IFRA [the International Fragrance Association], shared, during or on the occasion of IFRA meetings, sensitive business information concerning those competitors, aligned their business behaviour in respect of their customers and, lastly, were able to coordinate their strategic behaviour regarding tenders” (Ibid, para 72).

    Symrise also alleged that the inspection decision lacked a specified end date for the inspection, which “constitutes disproportionate interference with the right to privacy” (Ibid, para 91). The GC dismissed this argument considering that, as stated in the Nexans decision (Judgment of the General Court of 12 July 2018, Nexans France and Nexans v Commission, T‑449/14, EU:T:2018:456, para 69), the “absence of any specific date by which the inspection has to be completed does not mean that the inspection can go on indefinitely, since the Commission is, in that regard, required to observe a reasonable time limit” (Symrise decision previously cited, para 94).

    The applicant also claimed that its right to privacy was infringed because the Commission could have sent a request for information instead of conducting inspections, which were qualified as a “disproportionate interference in its fundamental rights of inviolability of its private premises and of privacy” (Ibid, para 103). The GC rejected this argument on the ground that the applicant failed to explain how the inspection could have been adequately replaced by a request for information (Ibid, para 104).

    Second ground of appeal: Infringement of the Commission’s obligation to state reasons

    Symrise alleged a lack of precision as to the subject matter and purpose of the inspection, and an absence of clear and unequivocal reasoning.

    The GC rejected Symrise’s argument on the lack of precision as to the subject matter and purpose of the inspection. The GC considered that the market was clearly indicated in the decision (Ibid, para 30) and that there was sufficient precision regarding the suspected practices (Ibid, para 32). Furthermore, the GC recalled that “the Commission is not required to indicate the period within which the suspected infringements were allegedly committed” (Ibid, para 41).

    Symrise also alleged that Article 1 of the inspection decision was not clear and unequivocal. Article 1 stated that:

    “among the alleged agreements [or] concerted practices are, inter alia, the exchange of sensitive business information, the coordination of commercial [behaviour] and commercial strategies, directly [or] through IFRA, regarding the supply of consumer fragrances and fragrance ingredients to customers and competitors as well as the potential coordination, together with or with the support of IFRA, of the setting of IFRA standards with the intention to exclude other suppliers of fragrance [or] fragrance ingredients from the market.”

    Symrise based its reasoning on an absence of clarity of the expressions “among the alleged agreements” and “inter alia.” However, the GC rejected this reasoning, recalling that “inter alia” does not infringe “the obligation to state reasons, since the Commission does not yet have precise information to issue a specific legal opinion, but must first of all verify the substance of its suspicions and also the extent of the facts that have taken place” (Ibid, para 46).

    The 2012 Nexans decision considered that the wording “amongst others,” referring to products in relation to which Nexans could be requested to submit documents, could have been “less ambiguous.” In Symrise, however, the GC clarifies that this statement does not mean that the wording “amongst others” in the dawn raid decision was ambiguous – it simply referred to a list of behaviours that may constitute an infringement (Symrise decision previously cited, para 47). Thus, the GC rejected the allegation.

    In summary, the GC recalled that statement of reasons must be appropriate to the measure at issue and must disclose in a clear and unequivocal way the reasoning followed by its author. Therefore, the GC reiterated the Commission’s obligations regarding inspection decisions:

    • They must indicate the subject matter and purpose of the inspection.
    • They must rely on reasonable grounds for suspecting an infringement of competition rules (which is a prerequisite to order an inspection).
    • They must be necessary to detect an infringement of the competition rules.

    Thus, the Commission must have sufficiently serious evidence to justify an inspection and ensure that it is proportionate to the objectives pursued. As the GC has made clear, this obligation to give specific reasons is a fundamental requirement, not only to show that the investigation is justified, but also to enable the companies to understand the scope of their duty to cooperate, while at the same time safeguarding their rights of defence.

    Hence, the GC rejected Symrise’s appeal in full.

    Insights from other appeals of dawn raid decisions

    In recent years, several decisions regarding dawn raids have been challenged in court, giving the ECJ the opportunity to clarify the legal principles that define the Commission’s powers during investigations.

    In 2012, the GC partially annulled the Commission’s dawn raid decision in the Nexans case (Judgment of the General Court of 14 November 2012, Nexans and Nexans France v. Commission, T‑135/09, EU:T:2012:596). The Commission conducted an inspection in January 2009 at Nexans’ premises, suspecting competition law infringement in the electric cable sector. Nexans challenged the inspection decision, alleging (i) a vague and broad product and geographic scope of the decision, and (ii) that the Commission had sufficiently detailed information to justify the inspection only in the underwater cable sector, and not in the broader cable sector stated in the Commission decision.

    In its 2012 judgment, the GC rejected Nexans’ first argument and approved the broad geographic scope of the Commission’s decision, the GC approved investigations outside of the European Union, considering that “there is nothing to prevent [the Commission] from examining documents relating to those markets [referring to markets outside of the EU] in order to detect conduct which is liable to affect trade between Member States and which has as its object or effect the prevention, restriction or distortion of competition within the common market” (Ibid, para 99). The GC considered that indicating “probably a global reach” of the cartel was sufficient and that the Commission did not have to show more detail in its dawn raid decision (Ibid, para 97).

    This consideration was upheld by the ECJ in 2014 (Judgment of the Court of 25 June 2014, Nexans and Nexans France v. Commission, C-37/13 P, EU:C:2014:2030) and recalled in 2024 by the GC in the Nuctech case (Order of the President of the General Court of 12 August 2024, Nuctech Warsaw v. Commission, T‑284/24 R, EU:T:2024:564). In this case, the Commission raided Nuctech’s offices in the EU under the Foreign Subsidies Regulation. Nuctech challenged the inspection, arguing it required access to data stored in China which could violate Chinese law. The GC rejected Nuctech’s request to suspend the inspection, ruling that the Commission could demand access to data held outside the EU.

    By contrast, the GC upheld Nexans’ argument that the Commission did not have sufficient information to investigate all types of cables (Judgment of the General Court of 14 November 2012, Nexans and Nexans France v. Commission, T‑135/09, EU:T:2012:596, para 91). The GC found that the Commission’s decision was insufficiently reasoned with respect to all types of cables other than underwater cables, as the evidence only justified an inspection in these specific areas. As a result, the GC partially annulled the inspection decision insofar as it concerned other types of cable, emphasising that the Commission must provide reasonable grounds for suspicion.

    The French Supermarkets case (Judgment of the Court of 9 March 2023, Intermarché Casino Achat v. Commission, C‑693/20 P, EU:C:2023:172) is another example of a dawn raid decision annulled by the ECJ. The decision was annulled in 2023 on the ground that it was based on interviews from competitors that had not been recorded. The Commission was investigating potential anticompetitive practices by French supermarkets, particularly information exchanges related to discounts negotiated with suppliers and future commercial strategies. After interviewing suppliers, the Commission decided to conduct an inspection, justifying its inspection with the information already collected from the suppliers.

    However, the French supermarkets challenged this decision, alleging a lack of evidence of the infringement. On appeal, the ECJ annulled the Commission’s decision, considering that the interviews had not been recorded and that notes taken during the interviews by the case handlers were not enough evidence of the infringement, thus “the Commission did not have in its possession sufficiently serious indicia” to justify the inspection (Ibid, para 142). The Court underlined that:

    • The Commission should have recorded the interviews with suppliers, since they were intended to gather information on the subject of a potential investigation.
    • This obligation applies irrespective of whether the interview in question took place before the formal opening of an investigation, in order to gather indications of an infringement, or afterwards, in order to gather evidence of an infringement.

    This decision reaffirms the Commission’s obligation to record interviews and demonstrates the willingness of the ECJ to enforce companies’ rights during a Commission investigation by ensuring that the Commission has sufficient justification to conduct the dawn raid.

    The recent Red Bull case further illustrates companies’ tendency to challenge inspection decisions. In March 2023, the Commission conducted dawn raids at Red Bull’s premises across several EU countries, investigating potential abuse of dominance and concerted practices in the energy drinks market. Red Bull considers that the Commission did not have sufficient elements to justify dawn raids and that the dawn raids were disproportionate. Red Bull’s request for interim measures was rejected by the GC in September 2023 and a hearing on the merits took place in May 2025.

    Conclusion

    Dawn raids continue to be a source of legal uncertainty and challenges before the GC and ECJ. Recent judgments reinforce the Commission’s broad powers to conduct dawn raids while also clarifying the standards that must be met to justify such inspections.

    In particular, the Commission must have sufficient evidence in terms of product and geographic scope as well as the time period concerned to justify a dawn raid. Sometimes the Commission meets this threshold (e.g. in the Symrise case), sometimes it does not (e.g. in Nexans and the French Supermarket cases). Therefore, in case of a dawn raid, it is imperative for the companies concerned and their advisor to scrutinise a dawn raid decision carefully and then take the appropriate steps to defends their rights.

    Finally, it is interesting to see that the Commission is trying to compensate the lack of leniency applications by setting up a market monitoring tool. This is an approach that the CMA has already taken, but it’s a new approach for the Commission. Companies have, therefore, be careful in their public statements. Even if unintended, certain public announcements can amount to a suspicion of an antitrust infringement and trigger dawn raids.

    Authors

    Stéphane Dionnet

    Partner

    Brussels

    More insights

  • UK Reforms National Security and Investment Regime: Streamlining or Expansion?

    UK Reforms National Security and Investment Regime: Streamlining or Expansion?

    ARTICLE / CLIENT ALERT

    UK Reforms National Security and Investment Regime: Streamlining or Expansion?

    August 8 2025

    Read time: 7 min

    Key takeaways
    Overview

    On 22 July 2025, the UK Government announced a set of targeted reforms to the National Security and Investment Act 2021 (NSI Act) and launched a consultation into proposed further changes. Alongside the reforms, the 2024-25 Annual Report was published. Overall, the UK government has been pragmatic in clearing deals and accepting remedies to get deals through and this approach is set to continue. However, the UK regime has so far required too many filings due to an overly broad regime and a lack of clarity in the guidance – the current and proposed changes provide welcome relief for some of these issues, but the legislation and guidance still lack clarity in places and some of the changes will result in more filings particularly in relation to data centres. The government should thus now use the results of the consultation to further clarify the regime.

    In depth

    Annual Report shows increase in filings but pragmatic approach to investigations

    The 2024-25 Annual Report shows that the number of notifications increased to 1,143, most of which were resolved within 30 working days. Most notifications concerned UK acquirers. This was followed by China and the United States.
    Only 4.5 % were “called-in” for review:

    • 28 as part of mandatory notification (i.e. falling within one of the 17 relevant sectors);
    • 20 due to voluntary notification (which includes deals where the target’s activities are closely related);
    • 1 as a result of a remedial notification (i.e. a missed notification potentially identified by an acquirer); and
    • 7 identified proactively by the government agency responsible for enforcing the NSI Act, the Investment Security Unit (ISU), highlighting an active monitoring policy (including close co-operation with other enforcers particularly in the United States).

    The UK to-date has issued eight final orders in 2025 (the latest on Thursday, 24 July 2025). This is in line with the number of final orders issued in 2024 at the same time and continues to be up from 2022 and 2023.

    The final orders do not include a prohibition. Rather, the UK Government has accepted a variety of remedies, including, amongst other things, reporting obligations, corporate-governance requirements (including vetting clearance for certain directors, sub-committees or compliance plans), limiting procurement to certain pre-approved geographies, ensuring continuity of supply and maintenance, or securing and limiting access to data. The final orders related to activities in a range of highly relevant sectors (e.g. defence, critical suppliers to the UK Government, semiconductors, advanced materials).

    The ISU also identified 60 breaches of the NSI Act, but these did not lead to civil or criminal penalties. Rather, in each case, the acquirers were able to provide assurances or took remedial action to avoid recurrence. However, the imposition of penalties may only be a matter of time as the regime matures.

    Changes to the NSI Act today and to its future scope and application

    The changes aim to reduce compliance burdens while maintaining robust protections for national security.

    Importantly, and most welcome to businesses, under the newly launched “Plan for Change”, mandatory notifications will no longer be needed for certain internal company reorganisations and transactions involving liquidators, special administrators and official receivers. Experience has shown that these types of deals are low risk and thus seldom lead to intervention, which has led to calls for such “technical” filings to be abolished. These calls have now been heeded but we have yet to see the details in a formal proposal.

    Separately, the Government is also launching a public consultation until 14 October 2025 to review and potentially revise the scope of sectors subject to mandatory screening. Proposed changes to the current NSI Act (Notifiable Acquisitions) (Specification of Qualifying Entities) Regulations focus on reshuffling the existing “relevant” sectors in order to:

    1. Create three new standalone mandatory areas:
      1. Semiconductors. Responding to calls for greater clarity regarding semiconductors, the UK Government proposes to extract the semiconductor-related definitions from the Advanced Materials and Critical Hardware areas and merge them under a new sector. To close gaps in the existing definitions, the new sector will also cover advanced packaging techniques, R&D design activities, and materials that “can demonstrate semiconductor-like behaviour”.
      2. Critical Materials. The new definition will be extracted from the Advanced Materials area and will be aligned with the UK List of Critical Minerals, updated following the latest criticality assessment conducted by the Critical Mineral Intelligence Centre.
      3. Water. Introduced as a new sector, responding to increasing resilience risks faced by national water infrastructure. The UK Government plans to cover within this sector companies whose statutory powers and duties include water supply and/or sewerage services. Companies operating solely as retailers in the non-household retail water market will be excluded from the scope of the notification requirement.
    2. Update the definitions in eight of the seventeen sectors (Advanced Materials, Artificial Intelligence (AI), Communications, Critical Suppliers to Government, Data Infrastructure, Energy, Suppliers to the Energy Services, and Synthetic Biology). The update aims to declutter the definitions by removing or narrowing activities that have required notification but did not raise concerns, while at the same time adding activities that have become relevant as technology develops, in particular:
      1. AI. The new definitions will exclude “off-the-shelf” low-risk consumer AI systems (i.e., used as a tool within internal processes, without any further material research and development of the underlying AI technology) from the scope of notification. At the same time, several new AI systems will be added, such as those increasing computation speed or used to test AI safety.
      2. Data Infrastructure. The UK Government proposes to expand this section by adding third-party-operated data centres, such as data-processing and storage facilities. New providers subject to the notification requirement will include certain Cloud Service Providers (CSPs) and Managed Service Providers (MSPs) offering Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS).
      3. Synthetic Biology. Despite feedback from industry stakeholders that the sector is “a long and complex” one, the UK Government decided not to narrow its scope or introduce exhaustive lists. Existing exemptions for gene and cell therapies will, however, be simplified.

    The Government’s focus on improving clarity and proportionality in the Regulations is welcome. However, the assessment of whether the announced measures are sufficient to respond to feedback received since the introduction of the NSI Act is more nuanced. Some measures are positive or at least neutral (including the tidying-up of the Advanced Materials sector, the use of clearer terms relating to semiconductors, or the exclusion of certain no-risk AI systems). Others will likely be seen as overly expansive (such as the addition of PaaS and IaaS providers to the Data Infrastructure sector) or a missed opportunity (such as the absence of meaningful changes to the Synthetic Biology sector).

    Overall, even with the proposed amendments, some of the definitions under the NSI Act will remain complex and difficult to assess. In the context of potential criminal liability for violations of the NSI Act and in the absence of any published decisions, the UK Government’s objective to make “the updated draft schedules […] sufficiently clear to enable investors and businesses to self-assess whether they must notify” is the right one but has not yet been achieved with these changes. The Government should therefore use the results of the consultation to further clarify the regime.

    Authors

    Max Küttner

    Associate

    Düsseldorf

    More insights

  • CMS proposes RPM reimbursement updates, requests information on reimbursing for SaaS

    CMS proposes RPM reimbursement updates, requests information on reimbursing for SaaS

    ARTICLE / CLIENT ALERT

    CMS proposes RPM reimbursement updates, requests information on reimbursing for SaaS

    August 5, 2025

    Read time: 14 min

    Key takeaways
    Overview

    Over the past several years, the Centers for Medicare & Medicaid Services (CMS) has expanded payment for remote monitoring services in an effort to recognize and pay for non-face-to-face services that improve care management for Medicare beneficiaries. In connection with the CY 2026 Medicare Physician Fee Schedule (MPFS) proposed rule (the Proposed Rule), CMS proposes several payment policy changes for remote monitoring services, including recognizing new modifications to the remote physiological monitoring (RPM) and remote therapeutic monitoring (RTM) codes. Most significantly, CMS proposes payment rates for new RPM and RTM codes established by the American Medical Association’s (AMA) CPT Editorial Panel last year that, if finalized, would be effective January 1, 2026.

    CMS also requests comments on how to establish pricing for software as a service (SaaS) under the MPFS, which has implications for the proposed reimbursement amounts for certain RPM and RTM codes. Comments on the Proposed Rule are due to CMS by 5:00 pm EDT on September 12, 2025.

    In depth

    Background

    CMS pays for remote monitoring services, which generally use digital technologies (medical devices, together with software) to collect medical and other forms of health data from a patient in one location and electronically transmit the information to the patient’s healthcare provider in a different location for assessment and care management. The data collected is electronically transmitted to health professionals for review and can be used in ongoing patient management. In some cases, the technologies can either trigger direct patient engagement or facilitate that communication.

    RPM services involve monitoring physiological measurements (e.g., weight, blood pressure, blood sugar) through medical devices, which automatically transmit data obtained from patients remotely to healthcare providers for assessment and recommendations. In contrast, RTM services involve the use of medical devices to monitor a patient’s health or response to treatment using non-physiological data. RTM services can monitor medication adherence, response to therapy, musculoskeletal activity, and respiratory activity. Unlike RPM, devices for RTM are not limited to transmitting data automatically obtained from patients but can also transmit data self-reported by patients.

    Separately, many healthcare services have begun to include software algorithms and other software-based technologies to support clinical services in recent years. Under the existing MPFS payment methodology, most computer software and associated analysis and licensing fees are considered to be “indirect costs” associated with hardware costs. This creates challenges in appropriately valuing and paying for SaaS that is incorporated into healthcare services payable under the MPFS.

    On July 14, 2025, CMS released the CY 2026 Revisions to Payment Policies Under the Physician Fee Schedule and Other Revisions to Medicare Part B Proposed Rule, which includes proposed changes to payment for RPM and RTM services and requests information regarding payment for SaaS devices.

    RPM proposals

    Coding

    The RPM code set currently includes CPT codes 99453, 99454, 99091, 99457, 99458, 99473, and 99474. CMS proposes payment rates for new RPM codes and changes to existing codes accepted by the AMA’s CPT Editorial Panel last year.

    For CY 2026, the CPT Editorial Panel created two new RPM codes to describe RPM services that include fewer than 16 days of data transmission per 30-day period and fewer than 20 minutes of interactive communication per month: CPT codes 99XX4 and 99XX5, respectively. In the Proposed Rule, CMS proposes to accept these codes and establish payment rates effective January 1, 2026. The CPT Editorial Panel also made edits to specify the minimum days of data transmission per 30-day period for CPT code 99454, which CMS proposes to adopt. The current, revised, and new RPM code descriptions are summarized in Table 1.

    CMS notes that many of the codes (99091, 99474, 99XX5, 99457, and 99458) will have to be resurveyed after one year of utilization data becomes available because the codes did not meet minimum survey requirements for the CPT Editorial Panel’s January 2025 Relative Value Scale Update Committee (RUC) meeting. CMS also notes that all remote monitoring codes are expected to be reviewed at the CPT Editorial Panel’s January 2028 meeting.

    Table 1: RPM codes
    Code Code Category CY 2025 Long Descriptor Proposed Code Descriptor Changes for CY 2026
    99453 Patient education and device set-up Remote monitoring of physiologic parameter(s) (e.g., weight, blood pressure, pulse oximetry, respiratory flow rate), initial; set-up and patient education on use of equipment No changes for CY 2026
    99XX4 Data transmission and device supply codes N/A, new proposed code for CY 2026 Remote monitoring of physiologic parameter(s) (e.g., weight, blood pressure, pulse oximetry, respiratory flow rate), initial; device(s) supply with daily recording(s) or programmed alert(s) transmission, 2 – 15 days in a 30-day period
    99454 Remote monitoring of physiologic parameter(s) (e.g., weight, blood pressure, pulse oximetry, respiratory flow rate), initial; device(s) supply with daily recording(s) or programmed alert(s) transmission, each 30 days Remote monitoring of physiologic parameter(s) (e.g., weight, blood pressure, pulse oximetry, respiratory flow rate), initial; device(s) supply with daily recording(s) or programmed alert(s) transmission, 16 – 30 days in a 30-day period
    99091 Treatment management services Collection and interpretation of physiologic data (e.g., ECG, blood pressure, glucose monitoring) digitally stored and/or transmitted by the patient and/or caregiver to the physician and/or other qualified healthcare professional, qualified by education, training, licensure/regulation (when applicable), requiring a minimum of 30 minutes of time each 30 days No changes for CY 2026
    99XX5 N/A, new proposed code for CY 2026 RPM treatment management services, clinical staff/physician/other qualified healthcare professional time in a calendar month requiring real-time interactive communication with the patient/caregiver during the calendar month; first 10 minutes
    99457 Remote physiologic monitoring treatment management services by clinical staff/physician/other qualified healthcare professional time in a calendar month requiring interactive communication with the patient/caregiver during the month; first 20 minutes No changes for CY 2026
    99458 Remote physiologic monitoring treatment management services by clinical staff/physician/other qualified healthcare professional time in a calendar month requiring interactive communication with the patient/caregiver during the month; each additional 20 minutes (list separately in addition to code for primary procedure) No changes for CY 2026
    99473 Patient education and device set-up Self-measured blood pressure using a device validated for clinical accuracy; patient education/training and device calibration No changes for CY 2026
    99474 Data transmission, device supply, and treatment management services Self-measured blood pressure using a device validated for clinical accuracy; separate self-measurements of two readings one minute apart twice daily over a 30-day period (minimum of 12 readings), collection of data reported by the patient and/or caregiver to the physician or other qualified healthcare professional with report of average systolic and diastolic pressures and subsequent communication of a treatment plan to the patient No changes for CY 2026

    Payment valuations

    In the Proposed Rule, CMS uses three different approaches to payment valuation for the RPM codes. For most existing codes (99453, 99457 – 99458, and 99473 – 99474), CMS proposes no changes in the work or practice expense (PE) relative value unit (RVU), in part because the codes did not meet the minimum survey requirements established by the RUC.

    For 99454 and 99XX4, CMS acknowledges that the RUC recommended a new PE input: “digital remote physiologic monitoring device app.” This proposed form of direct PE is a per-click vendor fee. However, CMS did not accept this new input, expressing concerns about establishing a price for a PE input in a field that has evolving technology and is based on a limited number of inputs (i.e., substantive invoices and other supportive data to establish the pricing for the input).

    Based on these concerns, CMS proposes a new approach to valuation that is a variation on the crosswalk approach that CMS has used in prior rulemaking cycles. For CY 2026, CMS proposes to use hospital claims data for 99454 (specifically the total geometric mean cost that CMS calculates from the submitted cost data) to set the PE RVU for 99454. CMS proposes this approach based on the stated rationale that the data submitted via hospital claims more accurately reflects the cost of the service and, because this code is a PE-only code, the costs should be consistent across the different settings. Based on the RVU values posted in Addendum B, CMS uses the total geometric mean cost published in the CY 2025 Outpatient Prospective Payment System (OPPS) final rule and divides that value by the CY 2026 PFS conversion factor. CMS proposes to use the same approach and same PE RVU for 99XX4. For CY 2026, this approach leads to a proposed increase in the payment rate for 99454 ($47.06, up from $43.02).

    CMS did not accept the RUC recommendations for 99XX5 and proposes to establish a linear relationship between 99XX5 and 99457. As the work and intensity of work are similar and the primary difference is the time associated with the codes, CMS proposes to set the work RVU for 99XX5 at 50% of that for 99457, because the time required (10 minutes) is 50% of that for 99457 (20 minutes).

    RTM proposals

    Coding

    The RTM code set currently includes CPT codes 98975, 98976, 98977, 98978, 98980, and 98981. Like the RPM proposals above, CMS proposes payment rates for the new codes and changes to existing RTM codes consistent with the changes made by the CPT Editorial Panel.

    For CY 2026, the CPT Editorial Panel created four new RTM codes to describe RTM services that include fewer than 16 days of data transmission per 30-day period and fewer than 20 minutes of interactive communication per month: CPT codes 98XX4, 98XX5, 98XX6, and 98XX7. CMS proposes to adopt these codes. The CPT Editorial Panel also made edits to specify the minimum days of data transmission per 30-day period for CPT codes 98976, 98977, and 98978. CMS proposes to adopt these edits.

    All codes in the RTM family are considered new technology and will be placed on the new technology list to be reviewed after three years of data are available, which will be in April 2030.

    Table 2: RTM codes
    Code Code Category CY 2025 Long Descriptor Proposed Code Descriptor Changes for CY 2026
    98975 Patient education and device set-up Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic remote therapy); initial set-up and patient education on use of equipment No changes for CY 2026
    98XX4 Data transmission and device supply codes N/A, new proposed code for CY 2026 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of respiratory system, 2 – 15 days in a 30-day period (emphasis added)
    98976 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of respiratory system, each 30 days Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of respiratory system, 16 – 30 days in a 30-day period (emphasis added)
    98XX5 N/A, new proposed code for CY 2026 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of musculoskeletal system, 2 – 15 days in a 30-day period (emphasis added)
    98977 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of musculoskeletal system, each 30 days Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of musculoskeletal system, 16 – 30 days in a 30-day period (emphasis added)
    98XX6 N/A, new proposed code for CY 2026 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of cognitive behavioral therapy, 2 – 15 days in a 30-day period (emphasis added)
    98978 Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of cognitive behavioral therapy, each 30 days Remote therapeutic monitoring (e.g., therapy adherence, therapy response, digital therapeutic intervention); device(s) supply for data access or data transmissions to support monitoring of cognitive behavioral therapy, 16 – 30 days in a 30-day period (emphasis added)
    98XX7 Treatment management services N/A, new proposed code for CY 2026 Remote therapeutic monitoring treatment management services, physician or other qualified healthcare professional time in a calendar month requiring at least one real-time interactive communication with the patient or caregiver during the calendar month; first 10 minutes (emphasis added)
    98980 Remote therapeutic monitoring treatment management services; physician or other qualified healthcare professional time in a calendar month requiring at least one interactive communication with the patient or caregiver during the calendar month; first 20 minutes (emphasis added) No changes for CY 2026
    98981 Remote therapeutic monitoring treatment management services; physician or other qualified healthcare professional time in a calendar month requiring at least one interactive communication with the patient or caregiver during the calendar month; each additional 20 minutes (list separately in addition to code for primary procedure) (emphasis added) No changes for CY 2026

    Payment valuations

    For the RTM codes, CMS uses four different approaches to payment valuation. For a subset of the existing codes (98975, 98980, and 98981), CMS does not propose any changes to the work or PE RVU in part because the codes did not meet the minimum survey requirements established by the RUC.

    For 98977 and 98XX5 (RTM for musculoskeletal system), CMS proposes to use the same approach that it proposes for the RPM device supply codes (99454 and 99XX4). CMS proposes to use hospital cost data submitted under the OPPS to establish the PE RVU. For CY 2026, CMS proposes to use the hospital claims data for 98977 (specifically the total geometric mean cost that CMS calculates from hospital-reported cost data) to set the PE RVU for 98977. In the Proposed Rule, CMS uses the total geometric mean cost published in the CY 2025 OPPS final rule and divides it by the CY 2026 MPFS conversion factor. CMS proposes to use the same approach and same PE RVU for 98XX5. For CY 2026, in contrast to RPM, this approach leads to a proposed decrease in the payment rate for 98977 ($39.77, down from $43.02).

    CMS did not accept the RUC recommendations for 98XX7 and proposes to establish a linear relationship between 98XX7 and 98980. As the work and intensity of work are similar and the primary difference is the time, CMS proposes to set the work RVU for 98XX7 at 50% of that for 98980, because the time required (10 minutes) is 50% of that for 98980 (20 minutes).

    Finally, CMS proposes to have 98978 and its new corresponding code, 98XX6, contractor priced – an approach used for 98978 in 2025. In response to the RUC recommendations, CMS also proposes to have 98976 contractor priced (a change from 2025) and to use the same approach for its new accompanying code, 98XX6.

    Request for comments

    CMS seeks comments on whether there are differences in the valuation of RPM and RTM services, specifically whether the services have similar costs and/or PE inputs. CMS proposes similar valuations for what it has historically viewed as similar remote monitoring services (for example, RTM and RPM treatment management, RTM and RPM device supply, RTM and RPM data transmission), but is interested in gaining more information regarding any differences in work (in the case of timed codes, whether there are varying levels of intensity between RTM and RPM), clinical staff time, supplies or equipment. CMS notes that it is particularly interested in comments that include data or evidence to support their position.

    Separately, CMS seeks comment on payment under the MPFS for SaaS. CMS requests public comment on what factors the agency should consider when paying for SaaS, alternative pricing methodologies that could be used to accurately pay for SaaS and artificial intelligence devices under the MPFS, and whether there are alternative data sources that accurately reflect the costs of SaaS technologies.

    Analysis

    CMS proposes a novel valuation methodology for the device supply codes for both RPM and RTM that would rely on hospital cost data submitted under the OPPS to determine the reimbursement rate under the MPFS. Although CMS has the ability to utilize cost, charge, or other data from service providers to establish reimbursement rates under the MPFS, it is unique that CMS proposes to take information from a higher cost setting (hospitals) and apply that cost data to establish reimbursement rates for services furnished in a lower cost setting (physician offices). Indeed, we are not aware of CMS ever previously using OPPS data to establish payment rates under the MPFS. CMS notes that it believes the OPPS cost data is more accurate than the PE inputs recommended by the RUC, although RPM and RTM services are typically (although not always) furnished in a physician office setting.

    The proposed use of OPPS cost data to establish PE RVUs raises additional questions. How will CMS account for the less frequent use of RPM and RTM services in hospital settings (leading to potentially understated hospital cost report data) compared to physician office settings? It also remains unclear how CMS plans to adjust the PE RVU for the RPM and RTM device supply codes in the future and how frequently updated OPPS cost data would be incorporated into the rate setting methodology.

    With respect to CMS’s request for additional information on payment for SaaS under the MPFS, CMS requests comments on whether its proposed approach for remote monitoring services should be followed more broadly for other SaaS devices (i.e., integrating OPPS geometric mean costs for SaaS to determine the device rate).

    Healthcare providers who furnish RPM and RTM services and vendors that rely on the RPM and RTM codes should carefully review CMS’s proposals and consider providing comments. Comments are due at 5:00 pm EDT on September 12, 2025.

    Authors

    Caroline Reignley

    Partner

    Washington, DC

    Grayson I. Dimick

    Associate

    Washington, DC

    More insights

  • Colorado remains active, proposes amendments to CPA rules

    Colorado remains active, proposes amendments to CPA rules

    ARTICLE / CLIENT ALERT

    Colorado remains active, proposes amendments to CPA rules

    August 5, 2025

    Read time: 4 min

    Key takeaways
    Overview

    On July 29, 2025, the Colorado Department of Law (Department) published a draft of its latest proposed Colorado Privacy Act (CPA) regulations, focused on children’s privacy. The Department is seeking comment on the proposed rule amendments by September 10, 2025. Businesses that regularly process the information of Minors (under 18 years of age) should review and consider submitting written comments on the proposed rules.

    In depth

    Introduction of “knowledge” standard

    A recent amendment to the CPA, SB24-041, which takes effect October 1, 2025, introduces a new definition of a “Minor” to the CPA, which is “any consumer who is under eighteen years of age.” The draft rules provide guidance as to when a business ought to know that a consumer is a minor. Specifically, the rules provide that the following factors will be used to determine if a business is willfully disregarding the fact that a consumer is a Minor: (i) the Controller received the information from a parent or consumer indicating that the consumer was a Minor, (ii) the business has a website or service directed to Minors, and (iii) the business has categorized the consumer as a minor for business purposes.

    In addition to these factors, the draft rules would allow the Colorado attorney general to consider other states’ factors when evaluating if a consumer is a Minor. This is an interesting addition, given the proliferation of children’s online-privacy laws.

    Significantly, however, the draft rules make clear that businesses are not required to implement age-verification or age-gating systems.

    High-engagement features and consent mechanics

    An online or app-based design feature requires consent if it was built to “significantly increase, sustain, or extend” a Minor’s use. The draft rules provide that the following factors would be used to evaluate whether the feature meets that standard: (i) whether the feature was designed to increase, sustain, or extend a Minor’s use; (ii) whether the feature has been shown to increase use or engagement; and (iii) whether the feature has been shown to be addictive.

    Under the draft rules, a feature would not trigger the consent requirements if (i) the Minor expressly requested the specific media, (ii) media is returned in response to search requests by the user, (iii) the feature is not core to the online service or product, (iv) the feature is based on information that is not persistently associated with a Minor or their device, (v) the feature does not consider the Minor’s previous actions, and (vi) the feature contains mitigation features such as time of day or use limits.

    The draft rules also provide that if a feature that significantly increases, sustain, or extends a Minor’s use is off by default, but toggled on by the Minor, that act is considered valid consent.

    ***

    If you have questions about the Colorado Privacy Act, these proposed amendments, or how your business may be affected, or if you would like to submit a comment to the draft rules, please contact your regular McDermott Will & Schulte lawyer or the authors of this client alert.

    Authors

    David P. Saunders

    Partner

    Chicago

    Dalyn D. Dessaure

    Associate

    Washington, DC

    More insights

  • Cross-Atlantic Impact: DOJ and SFO Self-Reporting and Enforcement Priorities

    Cross-Atlantic Impact: DOJ and SFO Self-Reporting and Enforcement Priorities

    ARTICLE / CLIENT ALERT

    Cross-Atlantic Impact: DOJ and SFO Self-Reporting and Enforcement Priorities

    August 5 2025

    Read time: 13 min

    Key takeaways
    Overview

    The enforcement environments in the US and UK are evolving at rapid pace. In the US, the Criminal Division of the Department of Justice (DOJ) issued a new White-Collar Enforcement Plan and several revised policy documents on 12 May 20251.  This was followed on 9 June 2025 by new guidelines for investigating and enforcing the US Foreign Corrupt Practices Act (FCPA)2.  In the UK, the Serious Fraud Office (SFO) has forged new international alliances, issued significant guidance on corporate self-reporting and co-operation, and has expansive new legislation in its arsenal.

    In this alert, we highlight three key cross-Atlantic takeaways from these recent updates:

    1. further incentives to voluntary self-disclosure;
    2. a strong focus on fraud as an enforcement priority; and
    3. a commitment to continued anti-bribery enforcement, with a narrower focus on certain industries and types of conduct.
    In depth

    Self-Disclosure

    The DOJ’s revised Corporate Enforcement and Voluntary Self-Disclosure Policy (CEP) offers companies greater incentives to voluntarily self-disclose misconduct, and additional certainty about the form of resolution they will face. The SFO issued new guidance in April 2025 which sought to achieve the same goals3. However, as summarised in the table below, the benefits offered by the DOJ remain more extensive and certain:

    Category DOJ CEP (May 2025) SEO Guidance (April 2025)
    1. Voluntary self-disclosure4 and Full co-operation (including remediation) and No “aggravating circumstances”5 (CEP) or “exceptional circumstances”6 (SFO Guidance) Declination SFO will invite company to negotiate a Deferred Prosecution Agreement (DPA) – ultimately, a DPA also remains subject to Court approval.
    2. “Near Miss” self-report:
    Full co-operation (including remediation) but ineligible for a declination because:(i) self-report was made in good faith but did not qualify as a voluntary self-disclosure7 or (ii) aggravating circumstances that warrant a criminal resolution are present8
    Non-prosecution agreement with a term fewer than three years. No independent compliance monitor. Penalty reduction of 75% off the low end of the US Sentencing Guidelines fine range No direct analogy, but broadly: (i) a self-report which is considered deficient9 may fall into category 3 below, (ii) the nature and extent of any aggravating circumstances10 will form part of the SFO’s assessment as to whether a prosecution (rather than a DPA) is in the public interest
    3. No self-report and Full co-operation (including remediation)11 Prosecutors have discretion to determine the appropriate resolution including its form, term length, compliance obligations, and monetary penalty.12 The SFO will “consider” inviting company to DPA negotiations if it provides “exemplary” co-operation13

    Timing Expectations

    Although the size of their self-reporting ‘carrots’ differ, the DOJ CEP and the SFO Guidance have similar expectations as to how quickly a report should be made:

    • The CEP “encourages” reports to be made at the “earliest possible time”, even when a company has not yet completed its own investigation. This translates into a requirement that, to remain eligible for a declination, a report must be made “within a reasonably prompt time” of the company becoming aware of the suspected misconduct.
    • The SFO Guidance states that a “prompt” self-report “always weighs heavily in favour of a DPA”. On the other hand, a failure to self-report suspected offending within “a reasonable time of it coming to light” will negatively impact the SFO’s assessment. As with the DOJ, the SFO does not expect a company to wait to complete any internal investigation. The length of time that a company may reasonably take to investigate will depend on the evidence that emerges. Where there is clear evidence of corporate offending, the SFO Guidance expects a self-report “soon after learning of that evidence” but where the position is “less clear-cut” it accepts that further investigation may be necessary.

    In the UK, it has been suggested that some scope for uncertainty was introduced by SFO Director Nick Ephgrave’s comments that as soon as a company has “reasonable suspicion you’ve got some offending going on – that’s the point at which you stop, that’s the point at which you talk to us.” However, this comment was made extemporaneously at a conference and it is possible that the Director was merely seeking to paraphrase the SFO Guidance. In any event, there is no “reasonable suspicion” threshold in the SFO Guidance. Indeed, in some scenarios, any such lower threshold could be in tension with the requirement that a self-report should provide information enabling the SFO to “understand the nature and extent of the suspected offending”. This would include identifying all known facts and evidence as at the time of reporting, the individuals involved, and the relevant jurisdictions. Providing the SFO with useful information in this respect may only be possible after a degree of internal investigation.

    Ultimately, these issues all require very prompt consideration as soon as relevant information comes to light.

    Practical Implications of Differing Incentives – UK Jurisdictional Triggers

    Under the SFO Guidance, a company which reports suspected offending to any other agency, whether domestic or foreign (e.g., the DOJ), must also report the matter to the SFO “simultaneously or immediately thereafter” or it will not gain credit from the SFO for self-reporting.

    This aspect has received relatively little attention to-date but its implications are illustrated by the CEP.

    In a scenario where a company is considering making a prompt self-disclosure with the aim of obtaining a declination from the DOJ, it should first take steps to understand whether there is any potential UK jurisdiction. Depending on the facts, that may require a complex analysis while the self-disclosure clock is ticking. For example, under the ‘failure to prevent bribery’ (FTP Bribery) and ‘failure to prevent fraud’ (FTP Fraud) offences, UK and non-UK companies are capable of being liable for a wide range of conduct by their employees, agents and other ‘associated persons’ anywhere in the world, provided there is a relevant link to the UK. In short:

    • The FTP Bribery offence can have entirely extra-territorial effect, but for it to apply to any non-UK company, it must ‘carry on a business’ (or part of a business) in the UK. This is a fact-sensitive test but UK government guidance indicates that companies with a “demonstrable business presence” in the UK are caught.
    • The FTP Fraud offence requires the underlying fraud to have some UK nexus – meaning that: (i) part of the conduct took place in the UK; or (ii) gain or loss resulting from the fraud occurred in the UK. “Fraud” has a very wide meaning for the purposes of the FTP Fraud offence. It can encompass a broad range of dishonest conduct including, for example: making false or misleading representations (e.g., to customers or government authorities); failing to disclose information when under a legal duty to do so (e.g., to auditors or investors); improper revenue recognition practices; and falsifying accounting records.

    Where there is a UK jurisdictional nexus, the company would need to weigh up the risks and benefits of a near-simultaneous report to the SFO. Important factors to note in that respect include the fact that any DOJ declination would be made public (so the SFO would likely learn of the matter anyway) and would generally not provide ‘double jeopardy’ protection against prosecution by the SFO or any other agency.

    A company’s overall decision making in relation to self-reporting across multiple jurisdictions will be fact sensitive and strategically nuanced. However, in many cases, a ‘lowest common denominator’ approach tends to apply, with the decision to self-report being driven by the jurisdiction offering the greatest benefits.

    The new prize of a guaranteed declination from the DOJ may therefore have the unintended consequence of driving additional reports to the SFO.

    Focus on Fraud

    Recent messaging from both the SFO and DOJ highlights fraud as a key enforcement priority for both agencies.

    New SFO Powers

    For the SFO, this reflects an eagerness to hold companies accountable using its new powers under the FTP Fraud offence. The offence applies to UK and non-UK companies and comes into force on 1 September 2025. Time is therefore running out to design and implement ‘reasonable fraud prevention procedures’ (the only defence to the FTP Fraud offence) in accordance with recommendations in UK Government guidance. The SFO has consistently stated that it intends to quickly hunt for targets using the new offence. For example:

    • when the UK Government guidance on ‘reasonable fraud prevention procedures’ was published, the SFO Director warned that “time is running short for corporations to get their house in order or face criminal investigation”;
    • the SFO Director has stated that “I want to be the first to prosecute someone under the new provisions…These are great new tools, let’s be bold about using those”; and
    • one of the SFO’s most senior lawyers said that the SFO was “looking forward to using [FTP Fraud] to penalise large organisations who should be doing better”.

    DOJ Priorities

    For the DOJ’s part, the White-Collar Enforcement Plan focuses strongly on the harm that fraud causes to US interests. Accordingly, the ten “high-impact areas” which the DOJ will “prioritize investigating and prosecuting” include fraud in the following guises:

    • waste, fraud, and abuse, including healthcare fraud and federal program and procurement fraud;
    • trade and customs fraud, including tariff evasion;
    • fraud perpetrated through variable interest entities (VIEs), including, but not limited to, offering fraud, “ramp and dumps,” elder fraud, securities fraud, and other market manipulation schemes;
    • fraud that victimises US investors, individuals, and markets, including, but not limited to, Ponzi schemes, investment fraud, elder fraud, servicemember fraud, and fraud that threatens the health and safety of consumers; and
    • crimes involving digital assets that victimise investors and consumers.

    Not only is the DOJ taking an aggressive stance toward certain types of fraud, but the US Supreme Court recently upheld an expansive view of the US wire fraud statute. The Court held in Kousisis v. United States that a defendant may be convicted of wire fraud for inducing a victim to enter a contract under materially false pretences, even if there was no economic loss to the victim. This ruling may allow US prosecutors to pursue a broader range of fraud cases.

    Practical Impacts

    Illustrating the self-reporting dynamic discussed above, all the frauds highlighted in the DOJ’s White-Collar Enforcement Plan are also capable (in principle) of falling within the FTP Fraud offence, provided there is a UK nexus. That might be the case, for example, in the case of a US-orchestrated investment fraud that also had UK victims, or if the customs agents engaged by a US company made fraudulent customs declarations to the UK authorities. If a US company uncovered evidence of fraudulent conduct by its employees or agents and determined to make a voluntary disclosure to the DOJ, the existence of any UK jurisdictional triggers may also prompt a report to the SFO.

    US companies assessing their fraud enforcement risks in light of the DOJ announcements or Kousisis decision may therefore also wish to incorporate a risk assessment aimed at the FTP Fraud offence. Such a risk assessment is a necessary foundation of ‘reasonable fraud prevention procedures’ under ECCTA. Our previous alert contained practical guidance on the methodology for conducting these risk assessments and how to avoid certain common pitfalls (including in relation to legal privilege).

    Commitment to continued anti-bribery enforcement

    In the first half of this year, early actions by the new US administration had put anti-bribery enforcement in doubt. In February 2025, Attorney General Pamela Bondi issued a memo that suggested FCPA enforcement could be significantly narrowed by focusing primarily on bribery that facilitates cartel operations and transnational criminal organisations. Just a few days later, President Trump issued an Executive Order pausing FCPA enforcement for 180 days, prompting some to wonder whether anti-bribery would cease to be a priority in this administration.

    While the DOJ was signalling a potential retreat from anti-bribery enforcement, other jurisdictions were ramping up. The SFO in particular has been acting with renewed vigour in this space. In March 2025, the SFO established an ‘International Anti-Corruption Prosecutorial Taskforce’ with the French Parquet National Financier (PNF) and Office of the Attorney General of Switzerland (OAG) (Taskforce). Through the Taskforce, the SFO, PNF and OAG commit to strengthening their existing co-operation and collaborating to deploy their wide-reaching anti-bribery legislation to prosecute overseas conduct. Hot on the heels of the Taskforce, the SFO announced that it will join the International Anti-Corruption Coordination Centre (IACCC). Hosted by the UK National Crime Agency, the IACCC aims to facilitate international co-operation on ‘grand corruption’ investigations, including with respect to intelligence and evidence gathering.

    The SFO Director stated that the Taskforce reaffirmed the SFO’s “commitment to tackling the pernicious threat of international bribery and corruption, wherever it occurs” and that the SFO would “make use of every power and partnership available to confront this criminality.” True to his word, the SFO is increasing enforcement activity:

    • In November 2024, the SFO announced that it was conducting a joint investigation with the PNF into suspected bribery and corruption at Thales Group, a French headquartered aerospace and defence electronics contractor. The company’s press release states that the investigation relates to the performance of a contract in Asia.
    • In April 2025, the SFO announced two new corporate investigations. First, the SFO announced an investigation into United Insurance Brokers Limited (UIBL) at the same time that UIBL was charged with failing to prevent its associates from bribing state officials in Ecuador.
    • Less than two weeks later, the SFO conducted multiple ‘dawn raids’ and announced an international bribery investigation in relation to Blu-3, a UK headquartered data centre infrastructure provider.

    The DOJ has now reaffirmed its commitment to anti-bribery efforts. The White-Collar Enforcement Plan issued in May 2025 includes bribery and associated money laundering that impacts US interests as a priority focus area.

    Further, the DOJ released its highly anticipated FCPA guidelines in June 2025, accompanied by remarks from the Head of the Criminal Division emphasising that the statute would be enforced “firmly but fairly.” The guidelines indicate that FCPA enforcement will resume, but with a narrower focus on certain industries (such as defence, energy, and infrastructure) and serious misconduct (e.g., sophisticated schemes and substantial bribe payments, rather than “routine business practices” or low-dollar business courtesies). Notably, while the guidelines reflect a desire to protect US business interests, they clarify that enforcement decisions will not be based on an individual’s or company’s nationality – in other words, enforcement will not be limited to non-US companies.

    Together, the new DOJ guidelines and the formation of the Taskforce signal that anti-bribery efforts remain an important focus globally.

    Conclusion

    Rapidly evolving policy and enforcement environments mean it is more important than ever that companies with links to the US and UK take a joined-up approach to evaluating their risk exposure and implementing mitigation strategies. Decisions taken in relation to one jurisdiction can have profound consequences in the other.

    If a situation arises where a discussion regarding potential self-disclosure is necessary, companies should make sure to engage the right people in that discussion – from Legal and Compliance to the board, across the US and UK (and any other potentially relevant jurisdictions) – and to do so quickly. The authorities on both sides of the Atlantic have made it clear that time is of the essence, so strategies for dealing with potential wrongdoing should be firmly in place before their implementation becomes necessary.

    Authors

    Simon Airey

    Partner

    London – 22 Bishopsgate

    Andrew Butel

    Counsel

    London – 22 Bishopsgate

    More insights