Content Type: Article

  • What’s Shaking? Not an Interlocutory Appellate Decision on Damages

    What’s Shaking? Not an Interlocutory Appellate Decision on Damages

    ARTICLE

    What’s Shaking? Not an Interlocutory Appellate Decision on Damages

    Jan 30, 2025

    Read time: 5 min

    Key takeaways
    Overview

    The US Court of Appeals for the Fifth Circuit dismissed and remanded a district court certified interlocutory appeal concerning the standard for calculating a reasonable royalty under the Defend Trade Secrets Act (DTSA). The Court explained that the rate instruction issued by the district court was erroneous because the parties had not yet gone to trial and the plaintiff had not yet proven liability. Therefore, the issue of damages might never arise. Silverthorne Seismic, L.L.C. v. Sterling Seismic Servs., Ltd., Case No. 24-20006 (5th Cir. Jan. 3, 2025) (Smith, Clement, Higginson, JJ.) (Higginson, J., dissenting).

    Silverthorne licensed seismic data to Casillas Petroleum Resource Partners II, LLC, an oil and gas exploration company. Under this arrangement, Silverthorne provided data to Sterling, a seismic data processer, which processed the data and sent it to Casillas. Because Sterling’s data processing required more data than what Casillas had paid for, Sterling was only permitted to forward the data that Casillas had licensed. However, Sterling sent Casillas unlicensed data, which Casillas allegedly showed to potential investors.

    Silverthorne sued Sterling for trade secret misappropriation under the DTSA and sought reasonable royalties for Sterling’s improper disclosure. Shortly before trial, the district court issued an order adopting the Fifth Circuit’s definition of “reasonable royalty” in University Computing (1974), which, in this case, would have required Silverthorne to prove what the parties “would have agreed to for . . . use [of] the alleged trade secret.” University Computing predates the DTSA, which provides for reasonable royalties for “disclosure or use of a trade secret.” Silverthorne appealed the order, noting that it would not be able to prove what Sterling would have agreed to pay to use the data, since Sterling was a data processor and not an end user. The district court certified the following question for appeal:

    [W]hether a plaintiff is entitled to prove reasonable royalty damages under the DTSA using willing buyer(s) detached from the parties to the litigation when willing buyers (here, oil and gas exploration companies) exist for plaintiff’s alleged trade secret (here, seismic data), but the defendant and comparable entities (here, seismic processors) do not buy or license that trade secret.

    An administrative panel of the Fifth Circuit granted leave to appeal.

    Majority Opinion

    The Fifth Circuit dismissed the appeal as not involving a controlling question of law. The Court explained that interlocutory appeals are only permitted where an order involves a controlling question of law, the resolution of which would materially and immediately affect the outcome of litigation in the district court. The Fifth Circuit emphasized that a question is not controlling just because the answer would complicate a litigant’s ability to make its case or because the answer could save the parties from a post-judgment appeal. Applying these principles, the Court reasoned that damages issues generally do not control a case until the plaintiff establishes liability, unless the damages issue would be dispositive. Because Silverthorne had not yet established liability and was not barred from proving damages under the district court’s definition of  “reasonable royalty,” the Fifth Circuit concluded that answering the certified question would not immediately and materially affect the outcome of the litigation. The Court thus vacated the order granting leave to appeal, dismissed the appeal for want of jurisdiction, and remanded for further proceedings without expressing an opinion as to the reasonable royalty standard.

    Dissent

    In dissent, Judge Higginson emphasized that the appeal was certified by a veteran district judge who felt compelled to adhere to outdated Fifth Circuit caselaw, and that a unanimous panel of Fifth Circuit judges agreed to revisit the issue and clarify the reasonable royalty standard under the DTSA. Despite this, the majority dismissed that grant as “imprudent” and returned the case to the lower court with no answer, almost a year later. Because the reasonable royalty standard was decisive for the litigation, and because University Computing was inconsistent with the DTSA, Judge Higginson stated that the Fifth Circuit should have answered the district court’s question.

    Judge Higginson explained that the majority opinion was out of step with 28 U.S.C. § 1292(b), which gives the court significant discretion to address an isolated point of law “upon which in a realistic way the whole case or defense will turn” in order to avoid wasting judicial time and resources. Under this pragmatic approach, the case did pivot on the reasonable royalty standard, because it impacted the scope of evidence and the availability of testimony concerning Silverthorne’s damages. Judge Higginson also reasoned that discretion weighed in favor of finishing what the Fifth Circuit had started – to do otherwise would “amount[] only to ‘acquiescing in a useless trial and later appeal.’”

    Turning to the certified question, the dissent explained that the DTSA authorizes reasonable royalties not just for the use of trade secrets, but also for disclosure. The district court’s application of University Computing, which limits reasonable royalties to commercial use, foreclosed this option. Judge Higginson also found that the district court erred in concluding that a party-specific hypothetical negotiation was the sole available measure of reasonable royalties. Rather, in Judge Higginson’s view, a court has discretion in selecting the methodology for arriving at a reasonable royalty under DTSA and may consider factors such as industry standards and prices paid by third parties.

    Authors
    More insights
    Endnotes

  • How Employers and Healthcare Providers Can Navigate Immigration Enforcement

    How Employers and Healthcare Providers Can Navigate Immigration Enforcement

    CLIENT ALERT / US POLICY

    How Employers and Healthcare Providers Can Navigate Immigration Enforcement

    January 30, 2025

    Read time: 10 min

    Key takeaways
    Overview

    Despite the anticipation of increased enforcement of US immigration laws, the rules and practical advice related to an employer’s legal duties under the Immigration Reform and Control Act (IRCA) and what to do if US Immigration and Customs Enforcement (ICE) officers present themselves at your place of business have not changed.

    This client alert provides a brief overview, proactive suggestions, and practical tips for employers, as well as for healthcare providers, whose patients may be the target of an ICE visit.

    In depth

    Employer’s Legal Duties Under the IRCA, and DHS-ICE Authority to Enforce Immigration Laws

    Under the IRCA, it is unlawful in the United States to hire, recruit, or continue to employ a person who is not in the country legally and not authorized to work (“an unauthorized alien,” as defined by law). An employer has a defense if it, in good faith, reviewed and accepted Form I-9 documentation that reasonably appeared to be genuine on its face.

    The US Department of Homeland Security (DHS) has the authority to conduct worksite inspections and audits. ICE, the DHS component responsible for enforcing the IRCA, has the authority to appear at a worksite with a notice of inspection or subpoena, demanding the production of various documents within three days, including:

    • Historical lists of workers
    • Payroll and tax records
    • Company ownership information
    • Staffing vendor information
    • I-9 forms
    • Copies of identity and authorization documents presented by employees

    During an audit, ICE may issue a “Notice of Suspect Documents” for workers believed to be unauthorized based on database checks, even if the Form I-9 was completed correctly. Employers must either contest the finding or terminate the workers, often with little time for resolution. ICE is rarely wrong about suspect documents, and confronting the worker often results in the worker not returning to work.

    DHS may investigate employers, plant undercover agents within the workforce, and conduct raids with armed agents, presenting search and seizure warrants. They may seize documents, computers, and phones, and arrest unauthorized workers. The department may also prosecute employer owners and managers on charges such as harboring and trafficking unauthorized workers, mail and wire fraud, document fraud, and tax evasion. Criminal charges can result in significant fines and imprisonment.

    ICE has the authority to arrest and detain most non-citizens, including those with arrest histories and certain long-term permanent residents. It can conduct workplace raids and other enforcement activities to effectuate these arrests. ICE must present a judicial warrant to enter nonpublic areas of a workplace. A judicial warrant is signed by a federal judge, not an immigration officer. The warrant must provide specific details, such as the name of the individual to be arrested, the location, and the reason for the arrest. Without a warrant, ICE is only allowed to be in public areas of the workplace.

    According to a recent DHS memorandum, the department is availing itself of law enforcement components of the US Department of Justice (DOJ) – including the US Drug Enforcement Administration (DEA), the ATF, the US Marshals Service, and the Federal Bureau of Prisons (BOP) – to carry out “functions” of an immigration officer to enforce immigration law. Historically, only the US Marshals were tapped to assist when a migrant became a fugitive. Although it remains to be seen how these DOJ law enforcement resources will be directed, it is possible that DHS’s immigration enforcement capacity will be more far-reaching than under previous administrations.

    Potential Sanctions and Penalties

    Employers are subject to sanctions for incorrectly completed I-9 forms, missing forms, or knowingly hiring unauthorized workers, which can range from $300 to $30,000 per worker, as well as debarment from federal contracts. Employers are allowed 10 days to correct technical errors, but certain substantive errors cannot be corrected to avoid penalties. ICE can also fine employers for failing to comply with technical requirements for electronic storage of completed forms.

    Interfering with an ICE arrest warrant can also lead to criminal charges for obstructing justice. This can include fines and imprisonment, depending on the severity of the interference.

    General Tips for All Employers

    • Maintain and enforce a comprehensive, compliant immigration policy.
    • Identify coordinators and designated points of contact in the event of any visit by ICE agents, including an ICE raid.
    • Conduct annual self-audits of I-9 forms to identify and address any issues before enforcement actions occur. Note: An employer is required to accept a List A document, or a List B and C document, from employees. Accepting and keeping copies of too many documents is also an IRCA violation.
      • Hint: If an employee presents a document from all three lists, return them and ask them to either provide a List A document, or provide a List B and a List C document. Let the employee choose, then review the requisite and correct number of documents for the Form I-9 Verification.
    • Ensure proper Form I-9 verification and storage, including in digital format. Designate and train individuals in I-9 verification and retention.
    • Enroll in E-Verify to verify social security numbers and names and ensure compliance with the IRCA. E-Verify is a platinum standard protection for employers. But it is not a safe harbor. Employers can still be fined for I-9 violations.
    • Use the Social Security Administration (SSA) website, if your organization is not enrolled in E-Verify, to confirm social security numbers match the employee’s name and identification.
    • Comply with no-match letters from the SSA by presenting the letter to the employee and asking them to present correct and valid documentation. Check that new documentation matches the name using the SSA website.
    • Identify and stop systematic improprieties in hiring practices.
    • Pay employees and submit tax withholding payments correctly, using real and correct social security numbers.
    • Educate staff on how to interact with ICE, DHS, or other law enforcement agents, including calling counsel and managing the situation calmly and professionally.

    Special Considerations for Hospitals and Other Healthcare Facilities

    In 2011 and 2021, ICE established a policy that generally prohibited engaging in enforcement actions at “sensitive locations,” such as healthcare facilities, schools, and religious institutions, unless exigent circumstances existed (namely, public safety threats, imminent risk of death, violence, physical harm, or destruction of evidence material to an ongoing investigation). On January 20, 2025, the Trump administration rescinded that policy, and ICE may again conduct enforcement actions in these locations. Enforcement actions may include interviews, arrests, searches, inspections, surveillance, and requests for protected health information (PHI). The Privacy Rule adopted under the Health Insurance Portability and Accountability Act of 1996 (HIPAA) permits (but does not require) disclosure of PHI in accordance with a valid court order or court-ordered warrant or a subpoena or summons issued by a judicial officer.

    Healthcare professionals may have state law or ethical obligations to consider the best interests of patients. Accordingly, healthcare workers should consider any state law or ethical responsibilities to protect patients’ health with their obligations to comply with federal law. For example, in a case where ICE presents a valid judicial warrant for the arrest of a patient, if that patient is in a life-threatening or severe state, the healthcare provider could explain this to ICE officers and request that ICE officials work with the healthcare provider to determine a safe course of action for the patient.

    Tips for Healthcare Facilities

    • Ensure staff members are familiar with the organization’s policies on patient confidentiality and the rights of both patients and healthcare providers.
    • Comply with the law and be mindful of emerging state laws on this issue. California is advising healthcare providers not to document patients’ immigration status on bills and medical records and advising patients and providers that they do not have to assist federal agents in arrests. Florida and Texas, by contrast, require healthcare facilities that accept Medicaid to ask the immigration status of patients (although a patient may decline to answer) and tally the cost to taxpayers of providing care to immigrants living in the United States without authorization.
    • Develop and train on protocols that outline the steps to be taken in the event of an ICE raid.
    • Designate specific roles to appropriate staff members, such as who will act as the point of contact with ICE agents and who will interact with patient(s) in question.
    • Healthcare facilities may post signage about patient rights, including that exam-room conversations are confidential and that privacy laws protect information in the medical record (including identifying information), and patients’ right to remain silent in the event of an ICE raid.
    • Healthcare facilities that are HIPAA-covered entities must provide patients an opportunity to decline to be listed in a facility directory or otherwise restrict or prohibit use of PHI for facility directory purpose.

    What To Do If an ICE Agent Visits, or if Raids Occur at a Healthcare Facility

    • All staff members should remain calm and composed.
    • Only the designated points of contact should interact with ICE agents. These individuals should be well-versed in the organization’s policies and the legal rights of patients and staff.
    • Designated points of contact should have ICE agents identify themselves by name and badge number. While healthcare workers and organizations have no affirmative legal obligation to report undocumented immigrants to officials, healthcare workers must lawfully abide with providing information and access to facilities where a valid warrant is presented.
    • Designated points of contact should politely request to see and review any warrants presented by ICE agents and ensure the warrants are valid and specific to the premises before permitting access to any private areas. For the warrant to be valid, it must be signed by a federal judge (a judge’s signature will indicate such).
      • Hint: If the warrant is a DHS Form I-200 or I-205 signed by an immigration officer, this is not a judicial warrant. In this case, the healthcare provider can advise the ICE agent that the warrant is not a valid judicial warrant and that the ICE agents may not enter any private areas – they must remain only in public areas.
    • Points of contact should provide information or documents required by a valid warrant but need not provide information or records falling outside of the warrant to maintain patient confidentiality.
    • After the ICE visit or raid, document the event by immediately identifying the names and badge numbers of ICE agents who were present, the time and duration of their presence, and any actions taken by the agents. Secure all patient records that may have been accessed during the event.
    • Patient liaisons may reach out to all patients affected by the raid to inform them of what occurred and reassure them of their safety and the confidentiality of their records. Patient liaisons may also provide impacted patients and their families with information to immigration advocacy organizations and legal aid groups who can provide legal support, particularly if a patient is taken into immigration custody.

    Conclusion

    Employers and healthcare providers must remain vigilant and proactive in managing immigration compliance to avoid significant penalties and disruptions. By following these tips and working closely with experienced counsel, organizations can be in legal compliance, navigate the complexities of immigration control, and protect their businesses and managers.

    Authors

    Joan-Elisse Carpentier

    Partner

    New York – One Vanderbilt Avenue, San Francisco

    Yesenia M. Gallegos

    Partner

    Los Angeles

    Joseph Mulherin

    Partner

    Chicago

    Maria C. Rodriguez

    Partner

    Los Angeles

    Mary Schnoor

    Partner

    Washington, DC

    More insights

  • EU AI Regulation: When AI competence becomes mandatory.

    EU AI Regulation: When AI competence becomes mandatory.

    ARTICLE

    EU AI Regulation: When AI competence becomes mandatory.

    January 30, 2025

    Read time: 2 min

    Key takeaways
    Overview

    The HR News blog provides regular updates on recent developments in German employment law (in German). The latest blog post provides insights on “EU AI Regulation: When AI competence becomes mandatory“.

    Visit the blog and/or register now for regular HR NEWS updates (in German).

    In depth
    Authors

    Dr. Philip Uecker

    Associate

    Düsseldorf

    More insights

  • New York Executive Budget Proposes Patient Consent to Payment Law Updates

    New York Executive Budget Proposes Patient Consent to Payment Law Updates

    ARTICLE / CLIENT ALERT

    New York Executive Budget Proposes Patient Consent to Payment Law Updates

    January 29, 2025

    Read time: 6 min

    Key takeaways
    Overview

    Key Update

    The recently released New York State Executive Budget for Fiscal Year 2026 contains proposed revisions to a recently enacted law impacting how healthcare providers obtain patients’ consent to payment.

    NY Public Health Law (PHL) § 18-c currently requires that patients provide consent for payment separate from consent to receive healthcare services. That consent to payment cannot be given before the provider discusses treatment costs with the patient and the patient receives services. The statute has significant ambiguity, and no formal guidance or regulations have been issued to date regarding PHL § 18-c. The New York State Department of Health (DOH) has indicated that it does not intend to enforce PHL § 18-c pending further indication of legislative intent. The current iteration of PHL § 18-c is discussed at greater length in our previous On the Subject.

    The proposed revisions would help address stakeholder concerns by removing the requirement that consent to payment be obtained after the patient has received the healthcare services.

    Why It Matters

    • Providers have expressed concerns that requiring services to be delivered prior to obtaining consent to payment poses logistical and operational challenges.
    • The proposed revisions would allow consent to payment to be given before the patient receives services, as long as treatment costs have been discussed. The proposed revision also would clarify that consent to payment requirements are applicable only to non-emergency healthcare services.
    • Providers should monitor the status of PHL § 18-c as the Executive Budget is finalized. While DOH previously indicated that implementation of PHL § 18-c’s requirements is on hold, providers should continue to monitor for DOH guidance and be prepared for the possibility that DOH will begin enforcing the law if the revisions are enacted. Providers should assess their current consent and billing processes and determine how they may need to change to comply with PHL § 18-c.
    In depth

    Requirements for Patient Consent to Payment

    PHL § 18-c provides that a patient’s consent to pay for healthcare services must be obtained separately from the informed consent for such healthcare services, and that consent to payment may only be obtained after the patient has received the applicable services and discussed treatment costs. Although PHL § 18-c was effective October 20, 2024, the next day the Medical Society of the State of New York (MSSNY) announced that it had received a copy of guidance issued by DOH directed to hospital CEOs indicating that the implementation of these consent-related requirements was put on hold pending further guidance. To date, no guidance or regulations have been issued or proposed on how to implement the law, and significant ambiguities remain.

    The MSSNY, several medical specialty organizations, and other stakeholders raised concerns regarding the logistical and operational challenges of requiring that consent to payment be obtained after healthcare services are rendered. Stakeholders noted that obtaining consent to payment after services are rendered is not consistent with typical medical practice workflows, where consents and necessary paperwork are completed upon arrival. Stakeholders also raised concerns about whether a patient could receive services and then simply refuse to consent to payment.

    The executive budget’s proposed revisions would address these stakeholder concerns by removing the requirement that the consent to payment be obtained after the patient has received the applicable services (i.e., only discussion of treatment costs must occur before consent to payment is obtained). The proposed revisions also would clarify that the restriction is applicable only to non-emergency healthcare services.

    Because the proposed revisions address only the timing of the consent, however, other significant ambiguities and stakeholder questions regarding PHL § 18-c remain. These include:

    • To whom does the statute apply? PHL § 18-c refers only to “patients” (i.e., “[c]onsent to pay for any health care services by a patient shall not be given prior to the patient receiving such services . . . .”) and not to any category of healthcare providers.
    • Must a patient provide a new consent each time a different service is offered? Are multiple consents necessary for a course of treatment? Does a change in treatment plan require a new consent?
    • How do PHL § 18-c’s requirements affect other requirements imposed on providers, such as those under the federal No Surprises Act, other New York state laws, and payor contracts? These require upfront disclosure of costs to patients and may conflict with certain provisions of PHL § 18-c.

    As currently drafted, the proposed revisions do not provide further guidance on these open questions.

    Requirements for Credit Card Payments for Healthcare Services

    The FY 2026 Executive Budget did not propose any amendments to NY General Business Law (GBL) § 519-a, which was adopted along with PHL § 18-c in the 2024 executive budget. GBL § 519-a imposes requirements for credit card payments for healthcare services. For a detailed discussion of GBL § 519-a’s requirements, please see our previous On the Subject.

    Next Steps

    Providers who render services to patients in New York should closely monitor developments related to PHL § 18-c. The Executive Budget will be reviewed, negotiated, and modified by the state legislature prior to its final approval, and further changes to PHL§ 18-c remain possible before the budget is finalized. While the budget is required to be finalized by April 1, 2025, in recent years the state’s budget has not been finalized by the deadline.

    Providers should also continue to monitor for guidance from DOH and be prepared for the possibility that DOH will begin enforcing the law if the revisions are enacted. Providers should assess their current consent and billing processes and determine how they may need to change to comply with PHL § 18-c.

    Please contact the authors of this article or your regular McDermott lawyer with any questions related to New York’s patient consent to payment requirements.

    Authors

    Gregory R. Mitchell

    Partner

    New York – One Vanderbilt Avenue

    Amanda Enyeart

    Partner

    Chicago

    Grayson I. Dimick

    Associate

    Washington, DC

    More insights

  • SEC Launches New Crypto Task Force

    SEC Launches New Crypto Task Force

    ARTICLE / CLIENT ALERT

    SEC Launches New Crypto Task Force

    January 29, 2025

    Read time: 5 min

    Key takeaways
    Overview

    On January 21, 2025, US Securities and Exchange Commission (SEC) Acting Chairman Mark T. Uyeda announced the formation of a new crypto task force.[1] This initiative aims to develop a comprehensive and clear regulatory framework for crypto assets. Led by Commissioner Hester Peirce, the task force signifies a shift toward greater regulatory engagement with the crypto industry under the new SEC leadership.

    In depth

    The crypto task force will collaborate with SEC staff and the public to establish clear regulatory guidelines, provide realistic paths to registration, create sensible disclosure frameworks, and judiciously deploy enforcement resources.[2] The goal of the task force is to set the SEC on a regulatory path that respects the bounds of the law.

    This approach marks a departure from the SEC’s previous strategy of regulating the crypto industry primarily through enforcement actions, which has led to confusion about legality and created an environment hostile to innovation and conducive to fraud.[3] The new task force will align with Commissioner Peirce’s long-standing position on the crypto industry. She has historically criticized the SEC for deploying enforcement actions without issuing appropriate guidance and has advocated for input from market and industry participants when crafting crypto policy. Commissioner Peirce’s leadership of the task force confirms the SEC’s commitment to a new regulatory approach.

    The SEC’s announcement emphasizes that the crypto task force’s success will depend on input from investors, industry participants, academics, and other interested parties via roundtables and other mediums, including the SEC’s new crypto email address, crypto@sec.gov.

    This announcement marks the beginning of a new era for the crypto industry. On January 23, 2025, US President Donald Trump issued an executive order directing regulators to establish a federal framework to oversee digital assets and prohibiting the creation of a central bank digital currency.[4] That same day, the SEC issued Staff Accounting Bulletin (SAB) 122, which rescinded the guidance in SAB 121. The previous guidance had suggested that financial institutions must reflect client crypto assets they hold as balance sheet liabilities.[5]

    Under SAB 122, entities that safeguard crypto assets for others must determine whether to recognize a liability related to the risk of loss under such obligations, applying recognition and, if so, the measurement of such liability, applying recognition and measurement requirements for liabilities under the Financial Accounting Standards Board Accounting Standards Codification (FASB ASC) (Subtopic 450-20, Loss Contingencies) and International Accounting Standards (IAS) 37, Provisions, Contingent Liabilities and Contingent Assets.

    It is well known that Commissioner Pierce is supportive of the crypto industry. We anticipate increased dialogue and collaboration with the industry, which will be a huge shift from the notoriously empty “come in and register” retort from former Commissioner Gary Gensler’s SEC.

    We are seeing a race to market new crypto and blockchain products in the United States. Crypto-related acquisitions are on the rise with many foreign market participants having their eyes set on the US market, some of whom are opting to buy instead of build. We fully anticipate this new task force will stimulate – and not stifle – responsible offerings in the US.

    We will continue to monitor crypto-related developments and provide updates. Please reach out to the authors of this article to discuss new crypto product offerings or acquisitions in the US.

    ***

    Leading the Way in Capital Markets Innovation

    McDermott’s capital markets and public companies lawyers have extensive experience advising clients with raising capital in the public markets. We also provide counsel on the rules and regulations that accompany operating as a public company. We pride ourselves on staying abreast of market trends, delivering pragmatic solutions proactively in support of capital needs and governance requirements, providing sage counsel to quickly resolve compliance issues without disruption to business operations.

    Excellence and Empowering the Future of Finance with Cutting-Edge Crypto Solutions

    Our full-time crypto-exclusive team has been ahead of the curve since Day One. Led by Partner Joe Evans, who has been a crypto lawyer since 2013 and was recognized by The American Lawyer as a “Trailblazer” for his work in crypto law, McDermott is one of the few law firms ranked Band 1 by Chambers USA in crypto-asset disputes. We are the largest crypto-exclusive team in the industry, and we spend 100% of our time on crypto clients.

    Authors

    Oliver Cheng

    Associate

    San Francisco

    Diana Douglas

    Partner

    Silicon Valley

    Thomas P. Conaghan

    Partner

    Washington, DC, New York – One Vanderbilt Avenue

    Eric Orsic

    Partner

    Chicago

    Daniel L. Woodard

    Partner

    New York – One Vanderbilt Avenue

    Joseph B. Evans

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • Global Equity Plan Reporting Obligations for Calendar-Year 2025: Part One

    Global Equity Plan Reporting Obligations for Calendar-Year 2025: Part One

    ARTICLE / CLIENT ALERT

    Global Equity Plan Reporting Obligations for Calendar-Year 2025: Part One

    January 28, 2025

    Read time: 4 min

    Key takeaways
    Overview

    Global equity plans are complex, and administration requires collaboration between various departments, including legal, human resources, payroll, and tax. Plan administrators (and their teams) should be aware of their reporting obligations with respect to international equity awards. Many reports can be submitted by the local entity’s payroll team; however, certain countries require separate standalone submissions.

    In depth

    The following reference chart summarizes selected reporting requirements for equity plans with international grantees. This reference – part one of two – highlights year-end reports (i.e., reporting obligations for prior calendar-year 2024 activity) with deadlines through June 30, 2025. It also includes certain quarterly filings. This resource does not include initial registration/exemption applications, reports due upon equity grants, or other standard payroll/tax reports. Additionally, reporting obligations may differ if certain exemptions apply, if the company implements a recharge agreement, or if the local entity is involved with administration of the plan.

    Please contact a member of your McDermott team or one of the authors listed below for more information about the listed reporting obligations or for assistance with evaluating which reports may apply to your company based on its current grantee population and plan administration. The team expects to publish part two of this reference chart in April 2025, summarizing applicable reports with deadlines from July through December 2025.

    Country Report Type Award Types Report Description Frequency Due Date
    Philippines Securities
    • All Equity Awards
    Applies only to plans that have obtained a registration exemption from the Philippines Securities and Exchange Commission Annually January 10, 2025, for prior calendar year activity
    Thailand Securities
    • Options
    Report option grants and exercises to the Thailand Securities and Exchange Commission Annually January 15, 2025, for prior calendar-year activity
    China Exchange Control
    • All Equity Awards
    For State Administration of Foreign Exchange (SAFE)-registered plans, report plan activity via statutory form to the applicable SAFE office Quarterly1 January 6, 2025, for prior calendar-quarter activity
    Vietnam Exchange Control
    • All Equity Awards
    Report aggregate share value to the State Bank of Vietnam Monthly2 January 12, 2025, for prior month activity
    Saudi Arabia Securities
    • All Equity Awards
    Report plan activity via online portal or email inbox to Capital Markets Authority Quarterly As soon as administratively feasible following the end of Q4 2024 data
    Malaysia Tax
    • All Equity Awards
    For each entity in Malaysia, report option exercises/RSU vesting via Form BT (Appendix C) to the Inland Revenue Board Annually February 28, 2025, for prior calendar-year activity
    France Tax
    • Tax-Qualified Options
    • Tax-Qualified Restricted Stock Units
    For tax-qualified options that are exercised or restricted stock units that vest, distribute statement describing grant activity to employees. A copy must also be provided to the applicable tax office. Annually March 1, 2025, for prior calendar-year activity
    Singapore Tax
    • All Equity Awards
    Distribute statement describing tax gains activity to employees via Form IR8A (Appendix A) Annually March 1, 2025, for prior calendar-year activity
    Ireland Tax
    • Option Awards
    Report option-related activity via Form RSS1 Annually March 31, 2025, for prior calendar-year activity
    Tax
    • All Equity Awards, Excluding Options
    Report all other equity-related activity via Form ESA Annually
    Japan Tax
    • All Equity Awards
    For Japanese affiliates that are 50%+ owned by a non-Japanese company or a Japanese branch of a non-Japanese company, report plan activity Annually March 31, 2025, for prior calendar-year activity
    China Exchange Control
    • All Equity Awards
    For SAFE-registered plans, report plan activity via statutory form Quarterly April 3, 2025, for prior calendar-quarter activity
    Singapore Tax
    • All Equity Awards Eligible for Qualified Employee Equity-Based Remuneration Scheme
    Submit application form for tax deferral eligibility to Comptroller of Income Tax Annually April 15, 2025, for prior calendar-year activity
    Israel Tax
    • All Equity Awards
    Report plan activity via Israel Tax Authority online platform Annually3 April 30, 2025, for prior calendar-year activity
    Authors

    Rob Marshall

    Partner

    London – 22 Bishopsgate

    More insights

  • DOJ Announces Largest Employee Retention Credit Fraud Indictment

    DOJ Announces Largest Employee Retention Credit Fraud Indictment

    ARTICLE / CLIENT ALERT

    DOJ Announces Largest Employee Retention Credit Fraud Indictment

    January 28, 2025

    Read time: 4 min

    Key takeaways
    Overview

    On January 22, 2025, the US Department of Justice (DOJ) announced the indictment of seven individuals in the largest Employee Retention Credit (ERC) fraud scheme to date. According to the indictment, the defendants filed more than 8,000 refund claims for ERCs and Sick and Family Leave Credits (SFLCs), totaling more than $600 million.

    In depth

    The ERC and SFLC programs were designed to help businesses retain employees on the payroll during the COVID-19 pandemic. Prosecutors allege that the defendants exploited these programs by submitting fraudulent claims on behalf of ineligible businesses, inflating employee numbers, and misrepresenting wages. DOJ asserted that the defendants concealed their involvement by not identifying themselves as preparers on the returns, using virtual private networks and through other means.

    ERC fraud has been a top priority of DOJ and the Internal Revenue Service (IRS), and this indictment can be added to a growing list of ERC-related enforcement actions. As of October 2024, the IRS Criminal Investigation division initiated 504 criminal investigations involving more than $5.5 billion in ERC claims. There have been more than 45 cases resulting in federal charges, with 27 resulting in convictions. A specialized unit within DOJ, called the “Fraud Strike Force,” has also been initiating investigations into potential ERC fraud, stating that such enforcement will “occupy a substantial portion of DOJ attention for years to come.”

    On the civil enforcement front, the IRS has strengthened its efforts to examine and disallow improper ERC claims. The IRS announced in mid-2024 that it had issued approximately 28,000 disallowance notices on claims aggregating $5 billion. According to the IRS, these claims “showed a high risk of being incorrect.” The IRS described these disallowances as the “first significant wave,” and with at least 1 million claims still outstanding, practitioners expect more disallowances. The IRS has also announced that it will be sending 30,000 “clawback” letters seeking to reclaim ERC funds that have already been paid.

    We have seen an aggressive examination campaign from the IRS targeting ERC claims. These exams, numbering into the thousands, have often involved more typical questions of taxpayer eligibility (e.g., number of employees and wages amount) but have also inquired about whether there has been “double dipping” with respect to other COVID-19-era stimuli, such as the Paycheck Protection Program. The IRS is also focused on governmental orders and the effects these orders had on taxpayers’ business operations.

    Besides taxpayers, accountants and other tax professionals have also been a target of IRS enforcement activity. The IRS Office of Promoter Investigations “has received hundreds of referrals from internal and external sources” concerning individuals and businesses that it deems as potentially having facilitated fraudulent ERC claims. The IRS has the authority to impose civil penalties on alleged promoters under Internal Revenue Code Section 6700. DOJ may pursue criminal cases against individuals and entities it believes are promoting false ERC claims. This enforcement activity may even target individuals or principals of a firm after it has long ceased operations.

    Practice Point: DOJ’s announcement makes clear that ERC fraud remains an enforcement priority for 2025. Taxpayers and tax professionals should prepare now to defend their ERC claims, including by compiling and maintaining substantiation to support each claim, and be ready to take immediate steps should they receive an IRS audit notice, a request for documentation or information, or are otherwise contacted by the government.

    Authors

    Michael J. Scarduzio

    Partner

    New York – One Vanderbilt Avenue

    Samuel F. Hamer

    Associate

    Washington, DC

    Edward L. Froelich

    Counsel

    Washington, DC

    Shawn O'Brien

    Partner

    Houston

    More insights

  • UK LLPs – Salaried Member Rules: Court of Appeal Decision in HMRC v BlueCrest Capital Management (UK) LLP

    UK LLPs – Salaried Member Rules: Court of Appeal Decision in HMRC v BlueCrest Capital Management (UK) LLP

    ARTICLE / CLIENT ALERT

    UK LLPs – Salaried Member Rules: Court of Appeal Decision in HMRC v BlueCrest Capital Management (UK) LLP

    January 28, 2025

    Read time: 13 min

    Key takeaways
    Overview

    The recent (and somewhat surprising) decision of the Court of Appeal (“CA”) in HMRC v BlueCrest Capital Management (UK) LLP means that the helpful guidance previously provided by the Upper Tribunal (“UT”) on the meaning of the ‘significant influence’ condition (Condition B) can no longer be relied upon. The case seems inevitably bound for the Supreme Court, which we can only hope will provide sensible and reliable guidance.

    The Salaried Member Rules and why they matter

    UK LLPs are widely used as a vehicle of choice for investment management firms in the private capital sector. For tax purposes, a UK LLP is generally treated as a (tax-transparent) partnership and, subject to the salaried member rules, its members are generally treated as self-employed partners.

    However, the salaried member rules treat an individual member of an LLP as a ‘salaried member’, and thus as an employee for tax purposes (subject to PAYE and employer/employee NIC), if each of the three following conditions is met. In brief, these are:

    • Condition A (‘disguised salary’) – at least 80% of the member’s reward is fixed or, if not fixed but variable, varies without reference to the overall profits/losses of the LLP.
    • Condition B (‘significant influence’) – the member does not have ‘significant influence’ over the affairs of the LLP.
    • Condition C[1] – the member’s capital contribution to the LLP is less than 25% of the member’s ‘disguised salary’.

    If any one of the conditions is not met, then the individual is not a salaried member. Most investment management firms look to structure their affairs so that one or both of conditions A and B are not met.

    FTT[2] and UT Decisions

    In upholding the FTT decision, the UT held that in relation to:

    • Condition A, there needs to be a “meaningful link” between at least 20% of an individual’s remuneration and the overall profits and losses of the LLP; the link cannot simply be that if there is less profit available for distribution, the individual member will receive a smaller amount.
    • Condition B, ‘significant influence’ need not be over the entirety of the affairs of the LLP, or necessarily of a managerial nature; operational, financial or managerial responsibility over one or more aspects of the affairs of an LLP may give rise to ‘significant influence’.

    In relation to Condition B, the UT rejected the ‘misconceived’ and ‘highly unrealistic’ way in which HMRC sought to apply the rules, noting that its approach effectively sought ‘to write additional words into Condition B’.

    Court of Appeal (“CA”) Decision

    Allowing HMRC’s appeal, the CA held that:

    • both the FTT and the UT had erred in law and that the ‘influence’ required by Condition B must be ‘conferred by the statutory and contractual framework which governs the operation of the partnership’.  Influence over the affairs of the LLP which lacks any identifiable contractual or statutory source in the specified rights and duties is excluded from being the kind of influence which counts for the purposes of Condition B. On the facts of the case, the main focus in this respect had therefore to be solely on the rights and duties conferred on the members by BlueCrest’s LLP Agreement (which effectively constituted the contractual framework governing the operation of the BlueCrest LLP); and
    • ‘influence’ has to be ‘over affairs of partnership’ which, in the context of Condition B, ‘connotes the affairs of the partnership generally, viewed as a whole’, and that ‘[t]he affairs of the LLP are broader than, although they include, the business of the LLP.’

    The CA decision makes clear that (i) ‘significant influence’ cannot be established by reference to actual (de facto) influence which does not derive (in effect) from the LLP Agreement (so-called ‘non-qualifying influence’); but also that (ii) such ‘non-qualifying influence’ may remain ‘highly material’ in deciding whether the influence that does qualify (so-called ‘qualifying influence’) is ‘significant’ when assessed in the light of any ‘non-qualifying influence’ which may be found to exist on the facts of any given case.

    The CA decision also makes clear that a focus on ‘decision-making at a strategic level’ rather than ‘how individual members perform their duties in conducting the business’ accords better with the basic purpose of Condition B.

    The CA thus explicitly rejected the conclusion reached by the FTT (and endorsed by the UT) that a portfolio manager with responsibility for managing their own substantial allocation of capital could, by that very fact, be regarded as having significant influence for purposes of Condition B (i.e., could have significant influence notwithstanding that they were not on the management/executive committee of the LLP constituted by the LLP Agreement and did not have any involvement in running the wider affairs of the LLP).

    The decision of the UT has been set aside and the case has been remitted to the FTT for it to reconsider the evidence in light of the correct test.

    For the sake of completeness we note that the CA also briefly considered Condition A (disguised salary) and upheld the decisions of both the FTT and UT (in HMRC’s favour) that where the overall amount of profits merely functions as a cap on remuneration which is variable without reference to overall profits, such remuneration is ‘disguised salary’.

    Conclusion

    So where does this leave us? In some respects, the position of an LLP member seeking to rely on Condition B is now worse than HMRC’s own guidance would suggest. Example 2 below (from HMRC’s Partnership Manual PM256200) clearly recognises a founder’s de facto ‘significant influence’.  Not so the Court of Appeal.

     

    Example 2

    This example illustrates an influential individual who is not a manager of the business.

    T was the founder of the firm. Officially she is semi-retired and plays no role in either the management or the strategy of the business. In reality, if T indicates her views on the strategy of the business, and the strategy board will almost invariably follow her guidance. T is still associated with the firm and if she was to disassociate herself from the firm, it would be catastrophic for business.

    Although T officially has no role, she continues to set the direction and strategy of the firm. T continues to hold significant influence and fails Condition B.

     

    It would also seem, if we follow the CA’s reasoning, that a member who does not have any involvement in decisions related to the general affairs of the LLP – for example through membership of a management/executive committee – cannot have significant influence, notwithstanding that that member may be crucial to the success of the business.

    While we consider it likely that this saga is bound for the Supreme Court, for now there is greater pressure on ensuring that members who are intended not to be salaried members on the grounds of significant influence (Condition B) can be seen to derive their influence over the affairs of the LLP from the rights and duties expressly conferred upon them by LLP Agreement and, furthermore, to ensure that such influence is over ‘the affairs of the partnership generally, viewed as a whole’.

    Authored by Nick Fagge (+44 (0) 20 7081 8009) and Dan Roman (+44 (0) 20 7081 8033).

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors. On 30 January 2025, the firm will be hosting a 30-minute discussion and Q&A for our clients and contacts to discuss the judgment and practical next steps.


    [1] Condition C is included here for the sake of completeness and not discussed further, although it is at present plagued by its own controversies.

    [2] First Tier Tribunal


    This communication is issued by Schulte Roth & Zabel International LLP for informational purposes only and does not constitute legal advice or establish an attorney-client relationship. In some jurisdictions, this publication may be considered attorney advertising. © 2025 Schulte Roth & Zabel International LLP. All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.

    In depth
    Authors

    Nick Fagge

    Partner

    London – One Eagle Place

    More insights

  • Data Privacy and Cybersecurity in 2025: PCI DSS 4.0

    Data Privacy and Cybersecurity in 2025: PCI DSS 4.0

    ARTICLE

    Data Privacy and Cybersecurity in 2025: PCI DSS 4.0

    January 24, 2025

    Read time: 4 min

    Key takeaways
    Overview

    Following our recent client alert, learn more about PCI DSS 4.0 coming into effect and its impact on organizations in 2025. Mark Schreiber and Brian Long share further insights from working with clients on these issues.

    In depth

    What is PCI DSS and to whom does it apply?

    Payment Card Industry Data Security Standard (PCI DSS) is a comprehensive set of security requirements that apply to the processing of credit and debit cards. It applies to all merchants and third-party service providers (TPSPs) who use e-commerce for online credit or debit card payments, call centers taking card payments, in-store payments with swipe machines, or any other form of card processing. Even TPSPs that can merely affect the security of card processing are required to comply with PCI DSS.

    What are the new PCI DSS 4.0 obligations that are effective March 31, 2025?

    The deadline for full implementation of the heightened compliance obligations under PCI DSS 4.0 is March 31, 2025. The transition to the new PCI DSS 4.0 controls requires new policies, processes, and technology solutions for card transactions.

    PCI DSS 4.0 introduces significant changes, including longer and more detailed self-assessment questionnaire (SAQ) forms. One major difference is the increased focus on targeted risk analysis and organizational maturity. Additionally, the new version introduces a customized approach to PCI assessments, allowing businesses to implement alternative technical and administrative controls that address the customized approach.

    To prepare for the transition, companies should conduct a thorough gap analysis to identify areas where their current practices diverge from the new 4.0 requirements to avoid fines, penalties, and assessments. They will also need to update their security policies, implement necessary technical changes to meet the enhanced security standards, and train staff on new procedures. Certain PCI DSS 4.0 requirements that were considered “best practices” become mandatory after March 31, 2025. Some companies may wish to complete their 2025 SAQ prior to this date.

    What are common misconceptions about PCI DSS 4.0 compliance?

    Some merchants mistakenly believe that if they outsource card functions to a third-party payment platform and don’t store card numbers, they are exempt from PCI DSS obligations. This is incorrect. These merchants must still complete an annual PCI SAQ and document an Attestation of Compliance (AOC).

    Another common misconception is that PCI DSS 4.0 is solely a technology standard or should only be handled by the information technology (IT) department. This is not true. It addresses a variety of risks associated with people, processes, and technology. PCI DSS 4.0 often requires a team approach involving several departments to address different aspects, including legal, compliance, procurement, vendor management, and IT or IT security.

    What are examples of key changes in PCI DSS 4.0?

    The following are examples of new PCI DSS 4.0 requirements that are mandatory by March 31, 2025:

    1. Defining PCI DSS Scope: This must be done annually for merchants (or every six months for TPSPs) and involves documenting roles and responsibilities across multiple controls.
    2. Payment Page Scripts: Implement controls for all payment page scripts executed in consumers’ browsers.
    3. Automated Technical Solutions: Required for public-facing web applications to continually detect and prevent web-based attacks.
    4. Monitoring and Response: Enhanced obligations for monitoring and obtaining documents from TPSPs.
    5. Targeted Risk Analyses: Required for several controls, necessitating granular risk assessments.
    6. Enhanced Encryption Requirements: Necessary when using whole-disk encryption to protect card numbers.

    What impact does PCI DSS 4.0 have on third-party vendors and service providers?

    As the March 31, 2025, deadline for PCI DSS 4.0 compliance approaches, there is greater emphasis on the security of third-party vendors and service providers. Companies must ensure and monitor that their partners comply with the new standards. This includes conducting thorough due diligence, requiring contractual agreements for compliance, obtaining third-party AOCs, and regularly assessing third-party security practices. To ensure compliance, companies should establish or obtain a responsibility matrix of services from each vendor that identifies what the vendor and the merchant are each responsible for in the covered services.

    Authors

    Mark E. Schreiber

    Counsel

    Boston

    Brian Long

    Associate

    Dallas

    More insights

  • Data Privacy and Cybersecurity in 2025: Website Tracking

    Data Privacy and Cybersecurity in 2025: Website Tracking

    ARTICLE

    Data Privacy and Cybersecurity in 2025: Website Tracking

    January 24, 2025

    Read time: 4 min

    Key takeaways
    Overview

    Following our recent client alert, learn more about enforcement targeting website tracking technologies and the impact on organizations in 2025. Elliot Golding and David Saunders share further insights from working with clients on these issues.

    In depth

    How has the recent trend in enforcement and litigation, particularly under laws like the California Invasion of Privacy Act, impacted companies’ approach to marketing and data analytics?

    Now, more than ever, US and European regulators are targeting cookies and other online tracking technologies (cookies) through extensive investigations and large fines. US litigation, arbitration, and pre-dispute demand letters have increased exponentially. In short, the risk associated with cookies – commonly used for online marketing, analytics, and many other purposes – is greater now than at any other point.

    Few companies are disabling marketing or analytics cookies entirely. Although a growing number of companies are switching to an EU-style “opt-in” cookie banner (at least in high-risk jurisdictions like California), implied consent remains the dominant “market” practice – i.e., providing notice but not seeking opt-in consent. However, most companies are taking at least some steps to reduce risk, such as conducting cookie audits, disabling legacy or unused cookies, improving transparency, and other measures described below.

    What are some of the steps companies should take to audit their current website tracking practices and ensure they are compliant with the latest regulations?

    Companies can take many steps now to reduce cookie risks, including:

    1. Auditing current cookie practices and compliance status, including checking configuration settings and creating a categorized inventory of cookie, server-to-server, and other tracking technologies.
    2. Making key risk and compliance decisions, such as whether and how to use a cookie banner, how to address consumer rights, whether to enable geofencing, and whether to implement heightened controls when processing sensitive information.
    3. Implementing risk decisions by configuring consent tools and web/mobile integrations and updating privacy and cookie notices.
    4. Implementing appropriate vendor management controls, including executing appropriate contracts and configuring cookie account settings to limit third-party data processing.
    5. Testing implementation periodically and checking for common pitfalls.
    6. Documenting key governance procedures, such as technical- and business-facing “standard operating procedures,” cookie change request processes, privacy impact assessments, and testing processes.

    What are the common mistakes companies make when implementing cookie management practices?

    The most common mistakes companies make involve misclassifying cookies and misconfiguring cookie consent tools. Common examples include:

    1. Loading the cookie banner in the wrong order.
    2. Failing to honor choice (such as promising “opt-in” consent even where cookies fire before there is an opportunity to consent) or failing to disable cookies when a user “opts out” (commonly the result of misclassifying cookies, i.e., labeling analytics cookies as “necessary” and therefore not subject to opt-out/reject buttons).
    3. Not providing consumers with “equivalent” choice in their banner (i.e., only having an “accept” button).
    4. Not accurately describing the cookies in use and what information they are collecting.
    5. Not adding disclaimers when third-party tools (e.g., chat bots, search) are in use on the website.

    What are some concerns that your clients have regarding website tracking technologies, and how do you address them?

    Most clients are frustrated by threats of large statutory damages for what seem like “hypertechnical” violations of archaic laws and the lack of clear direction about what to do. Given the unsettled nature of the ongoing civil litigation on the critical question of whether state wiretapping laws require express or implied consent, the biggest concern from clients is how to accurately scope their risk.

    We help our clients assess levels of risk that they may face by first understanding what types of technologies are in use on a particular website along with a client’s risk tolerances for litigation and regulatory risk given the business benefits of those technologies. With those two inputs, we then work with clients to design and implement risk mitigation strategies that are right for them.

    Want to know more? Watch the recording of our webinar that covers how to leverage cookies to maximize value while minimizing risk.

    Authors

    Elliot R. Golding

    Partner

    Washington, DC

    David P. Saunders

    Partner

    Chicago

    More insights