Content Type: Article

  • The SEC Takes Aim at Another Initial Coin Offering

    The SEC Takes Aim at Another Initial Coin Offering

    ARTICLE / CLIENT ALERT

    The SEC Takes Aim at Another Initial Coin Offering

    June 12, 2019

    Read time: 12 min

    Key takeaways
    Overview

    A recent complaint concerning KIK Interactive Inc. filed in the US District Court of the Southern District of New York reveals some SEC priorities for cryptocurrency enforcement actions. The complaint indicates that the SEC believes that even if a “simple agreement for future tokens” (SAFT) is itself exempt from securities registration, an analysis of any digital asset offered or sold using the SAFT must be assessed separately under US Securities laws.

    In depth

    The SEC is pursuing another company for its initial coin offering (ICO), alleging in a complaint filed in the United States District Court for the Southern District of New York (SDNY) on June 4, 2019 (the Complaint), that KIK Interactive Inc. (Kik)’s ICO constituted an unregistered sale of securities. Interestingly, the SEC has taken aim at a company that utilized the once popular “Simple Agreements for Future Tokens” (more commonly referred to as a “SAFT”) to sell its virtual currency. The Complaint indicates that the SEC believes that even if a SAFT is itself exempt from securities registration, an analysis of any digital asset offered or sold using the SAFT must be assessed separately under the US Securities laws. When considering whether a sale of virtual currency is a security, the question is whether the sale constitutes an “investment contract” under the Securities Exchange Act of 1934 and SEC v. Howey, 328 U.S. 293 (1946) and its progeny. Whether an investment constitutes an “investment contract” is referred to as the “Howey test.” Under Howey, an offering is an investment contract, and therefore a security, where there is an (1) investment of money; (2) in a common enterprise; (3) with the expectation of profits to be derived solely from the efforts of others. Further analysis on this topic is available in the following articles: Blockchain Tokens: the SEC Staff Issues Its Framework for Determining Whether an ICO Is an Issuance of Securities, Digital Token Offerings and Sales Under Regulation S, SEC Director Makes Groundbreaking Speech About Blockchain Token Sales, and Compliant Structures for Securities Offerings of Blockchain Tokens.

    As in the SEC’s actions against Paragon and Airfox, the SEC referenced, and took into account, Kik’s white paper, marketing materials and statements on social media in the making of its determination, and decided that the ICO constituted an unregistered offering of securities.

    The Complaint serves as another reminder that the SEC is focused on sales and distributions of digital assets, including ICOs, and how ICOs are marketed. The SEC continues to examine ICOs that took place years ago, before certain of the more recent SEC guidance on digital assets was issued. Companies in the industry must exercise extreme caution in structuring, marketing and offering digital assets, whether structured as an ICO or otherwise.

    Summary

    Kik, a messaging application company through the sale of Kin tokens, raised more than (the equivalent of) $100 million USD, and $55 million USD of that total came from US investors. At the time the Complaint was filed, Kin tokens were trading at about half the price investors had paid for Kin tokens in connection with the ICO. The price of Kin tokens has been dropping precipitously ever since the filing of the Complaint. According to the SEC, “Kik told investors they could expect profits from its effort to create a digital ecosystem . . . future profits based on the efforts of others is a hallmark of a securities offering that must comply with the federal securities laws.” Ultimately, the SEC alleged that, notwithstanding the SAFT structure, the Kik ICO constituted an unregistered sale of securities.

    Kik’s Marketing

    Like many companies engaging in ICOs, Kik issued a “white paper” prior to the ICO, which came back to haunt Kik. The SEC cited repeatedly to the white paper throughout the Complaint. The SEC also pointed to press releases, speeches by Kik’s chief executive officer, presentations to potential investors, YouTube postings, various social media postings and television appearances. The SEC’s main focus was the fact that Kik had promised investors that Kik’s efforts would result in profits for the investors. The SEC referenced the fact that Kik “promised” investors that Kik would spur demand for Kin tokens by 1) redesigning the “Kik Messenger” (Kik’s messaging application) to incorporate Kin tokens; 2) by creating a “rewards engine” to compensate companies that fostered Kin token transactions; and 3) by implementing new “transaction services” that would address flaws in existing blockchain technology. According to the SEC, these promises and statements indicated that Kin tokens satisfied the third prong of the Howey test because they indicate an “expectation of profits to be derived from the efforts of others.”

    The SEC also cited to the fact that Kik highlighted in its marketing materials that contain members of Kik management that would profit alongside other investors because they would also be holding Kin tokens. According to the SEC, Kik assured buyers that after the ICO, Kin tokens would be sold on secondary virtual currency exchanges. According to the SEC, these allegations further indicate that investors in Kin tokens were expecting profits to be derived from the efforts of others under Howey.

    The Kik Complaint is another reminder that companies that have launched ICOs need to be particularly careful with their marketing materials and statements on social media. For example, Kik apparently wrote in a tweet the following, seemingly equivocal statement about Kin tokens being adopted by virtual currency exchanges: “We have been given indication from multiple exchanges that they plan to list the token, no specifics available yet though. :)” At first glance, this tweet might appear to be mere puffery or standard marketing, but the SEC cited it and provided a screenshot in the Complaint as a reason why the Kik ICO constituted the unregistered sale of securities. When considering the Howey test, and whether an ICO satisfies the “expectation of profits derived from the efforts of others” prong, the SEC appears to be acutely focused on statements made in marketing materials and social media.

    Kik’s SAFTs

    Kik offered pre-sales of Kin tokens by using “Simple Agreements for Future Tokens” or “SAFTS.” While the Kik SAFT asserted that the SAFT itself was exempt from registration under Section 4(a)(2) of the Securities Act and Regulation D, Kik did not claim a separate exemption for the offer and sale of the Kin tokens themselves. The SEC claims that Kik’s failure to have a separate exemption for the underlying Kin tokens rendered the ICO an unregistered sale of securities. More specifically, the SEC alleges the following:

    Although Kik’s SAFT specifically stated that the SAFT was itself a security, it failed to state that the Kin to be delivered under the SAFT were securities sold pursuant to the SAFTs. And although Kik’s PPM claimed that the offer and sale of the SAFTs were subject to an exemption from registration under Section 4(a)(2) of the Securities Act and Regulation D promulgated thereunder, among other United States laws, Kik did not claim any exemption for the offer and sale of Kin through the SAFT. As such, Kik’s offer and sale of the SAFTs and Kik’s offer and sale of the Kin purchased under the SAFTs were not registered.

    While SAFTS have been popular mechanisms to pre-sell tokens in anticipation of an ICO, the SEC appears to have taken a dim view as to their legality if it is determined that the underlying virtual currency is a security.

    Kik also raised money from venture capital investments and the general public. But it pooled all the proceeds from the sales of Kin into two Kik bank accounts and an Ethereum wallet.

    Information Available to Kik at the Time of the ICO

    The SEC noted that the DAO Report was issued seven weeks before the ICO, and alleged that the report should have provided sufficient warning to Kik that its planned ICO would violate federal securities laws. See Report of Investigation Pursuant to Section 21(a) of the Securities Exchange Act of 1934: The DAO, Release No. 81207 (July 25, 2017). The SEC also cited communications between Kik and its “New York-based consultant” to support the SEC’s allegation that Kik was advised that its ICO would constitute a securities offering.

    In addition, the SEC pointed out that Kik has spoken with the Ontario Securities Commission, which indicated that the contemplated ICO constituted an offering of securities. Kik subsequently barred Canadians from the ICO, but launched the offering in the United States without first contacting the SEC.

    It is important to note that Kik’s sales concluded in September of 2017. Since September of 2017, the SEC and other regulators have issued significant relevant guidance, including the most recent Framework for ‘Investment Contract’ Analysis of Digital Assets. See also Blockchain Tokens: the SEC Staff Issues Its Framework for Determining Whether an ICO Is an Issuance of Securities.

    Emails Undermining the “Utility” Aspect of the Kik Offering

    Apparently Kik gave investors “crypto stickers,” which were images that users can send to one another on the Kik messaging application. This, according to the SEC, was a ruse to “create a hypothetical ‘use’ for the tokens, which Kik believed was relevant to whether Kik’s sales of Kin were securities transactions under the securities laws.” Presumably, this was Kik’s effort to provide a “utility” aspect to its offering in the hope that Kin tokens would be considered “utility tokens” in then-current parlance, and, therefore, not securities. But emails sent by Kik executives undermined this argument. For example, one Kik executive sent an email stating the following: “Basically it doesn’t really matter. The whole point is to make our legal department happy, not the users (who are actually investors and probably could care less that they got a sticker pack for their $10K investment into KIN).”

    Background of the Kik Investigation and Significance to the Industry

    Kik received its first inquiry from the SEC on September 15, 2017. The SEC issued a series of subpoenas and took testimony from at least 10 witnesses in 2018.

    When companies are under investigation by the SEC, they are given a “Wells” notice when the SEC staff comes to a preliminary conclusion that an enforcement action is necessary. The company is then given an opportunity to submit a memorandum spelling out why the SEC should not proceed with an enforcement action. These are called “Wells” submissions. Wells submissions are routinely filed with the SEC and are usually not released to the general public.

    Kik received a Wells notice from the SEC on November 16, 2018. Kik responded with a detailed memorandum on December 10, 2018. However, Kik took the highly unusual step of publishing its Wells submission publicly on its website. The public filing of Kik’s Wells submission received substantial attention and garnered support from significant members of the virtual currency industry. Kik maintained its offensive with press releases, describing, in Kik’s view, “what has been going on behind the scenes with the SEC.” Prominent players in the virtual currency industry then marshalled their resources to hire law firms to help defend the investigation into Kik. Indeed, Kik launched a legal defense fund called “Defend Crypto” which, at the time of the writing of this article, had received the equivalent of $4,405,133 USD in various virtual currency (primarily Bitcoin and Ethereum). The Defend Crypto website calls for donations stating “if you too are fed up with this innovation tax, we encourage you to contribute also as we take on the SEC on behalf of the future of crypto in the US.” Following the filing of the SEC Complaint, Kik CEO Ted Livingston stated, “We have been expecting this for quite some time, and we welcome the opportunity to fight for the future of crypto in the United States.”

    There is no question that Kik has taken an aggressive approach with the SEC. Both Kik and the SEC have become emboldened during the course of this investigation, and we anticipate a    hard-fought legal battle that could significantly alter virtual currency law. We anticipate that Kik will be filing a motion to dismiss. If the Court were to dismiss the Complaint, it would be a significant blow to the SEC’s ability to enforce upon virtual currency companies. If the Court rejects that motion to dismiss, the SEC will likely continue to aggressively pursue similar causes of action against other virtual currency companies that previously launched ICOs. This is perhaps most significant to the many virtual currency companies that launched ICOs in 2017 using the same or similar structures as Kik.

    Conclusion

    This is another aggressive action by the SEC indicating that the SEC will continue to actively investigate virtual currency companies. In particular, the SEC remains focused on ICOs and other sales and distributions of digital assets launched in 2017, long before additional clarifying guidance was issued. Companies that have launched ICOs need to be very careful with their external and internal communications and marketing materials. A tweet, reddit post or email that appears funny, innocuous or like mere puffery at the time could wind up in an SEC complaint. This action also impacts, perhaps even more significantly, companies that have already launched ICOs with the same or similar structures as Kik. The SEC is aggressively policing ICOs, and companies that have launched ICOs in the past would be well served to analyze their past ICOs and determine what can be done to limit potential exposure to SEC enforcement actions. While the SEC has taken aim at a company that used SAFTs to pre-sell its ICO, this enforcement action is not necessarily the death-knell for SAFTs. Kik will have the opportunity to fight these allegations, and the industry will be watching with great interest, since the case will likely lead to court decisions that could significantly shape how ICOs are launched—and regulated—in the future.

    Authors

    Todd Harrison

    Partner

    New York – One Vanderbilt Avenue

    David L. Taub

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • Eagle Eye on Attorneys’ Fee Award: Courts Must Apportion Award Based on Successful Claims

    Eagle Eye on Attorneys’ Fee Award: Courts Must Apportion Award Based on Successful Claims

    ARTICLE

    Eagle Eye on Attorneys’ Fee Award: Courts Must Apportion Award Based on Successful Claims

    June 12, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Sarah Hogarth authored this bylined article summarizing the US Court of Appeals for the Fifth Circuit’s decision to affirm the district court’s finding that the case, Alliance for Good Government v Coalition for Better Government was “exceptional” but required it to recalculate the fee award.

    In depth
    Authors

    Sarah P. Hogarth

    Partner

    Washington, DC

    More insights

  • Taxation of U.S. Shareholders of Foreign Corporations After Tax Reform

    Taxation of U.S. Shareholders of Foreign Corporations After Tax Reform

    ARTICLE

    Taxation of U.S. Shareholders of Foreign Corporations After Tax Reform

    June 10, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Ellen Harrison co-authored this bylined article examining the changes made by the Tax Cuts and Jobs Act to investments in controlled foreign corporations and passive foreign investment companies that estate planners should consider.

    In depth
    Authors

    Ellen K. Harrison

    Counsel

    Washington, DC

    More insights

  • Supreme Court: Rejection of Trademark License in Bankruptcy is Breach of Contract That Does Not Terminate Licensee’s Right to Use Mark

    ARTICLE

    Supreme Court: Rejection of Trademark License in Bankruptcy is Breach of Contract That Does Not Terminate Licensee’s Right to Use Mark

    June 7, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Peg Duncan Nathan Coco authored this bylined article summarizing the US Supreme Court’s decision to hold that, under 11 USC § 365, a debtor’s rejection of an executory contract in bankruptcy has the same effect as a breach outside bankruptcy, therefore reversing the First Circuit’s ruling in Mission Product Holding Inc v Tempnology LLC.

    In depth
    Authors
    More insights

  • Opportunity and Risk: Standard Antitrust Clauses in Share and Asset Purchase Agreements

    ARTICLE

    Opportunity and Risk: Standard Antitrust Clauses in Share and Asset Purchase Agreements

    June 6, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Daniel von Brevern authored this bylined article exploring the consequences and potential risks of standard antitrust clauses in share and asset purchase agreements.

    In depth
    Authors
    More insights

  • Takeaways from the High Court’s Medicare Ruling

    ARTICLE

    Takeaways from the High Court’s Medicare Ruling

    June 6, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Michael Kimberly and Ethan Townsend authored this bylined article summarizing the US Supreme Court’s decision on Azar v. Allina Health Services and how it not only changes the standards for Medicare reimbursements to hospitals for serving low-income patients, but how it may also have far-reaching implications for the government’s ability to change Medicare policy.

    In depth
    Authors

    Ethan H. Townsend

    Partner

    Wilmington

    More insights

  • New Developments for Employers Regarding Employee Reproductive Health Decisions, Marijuana Drug Testing and Wage Reporting Requirements

    New Developments for Employers Regarding Employee Reproductive Health Decisions, Marijuana Drug Testing and Wage Reporting Requirements

    ARTICLE / CLIENT ALERT

    New Developments for Employers Regarding Employee Reproductive Health Decisions, Marijuana Drug Testing and Wage Reporting Requirements

    June 6, 2019

    Read time: 5 min

    Key takeaways
    Overview

    Employers should be aware of recent developments in the area of employment law: (1) an amendment to the New York City Human Rights Law (“NYCHRL”) to include sexual and reproductive health decisions as a protected category; (2) New York City’s prohibition of pre-employment drug testing for marijuana usage; and (3) new wage and hour reporting requirements from the Equal Employment Opportunity Commission (“EEOC”).

    “Sexual and Reproductive Health Decisions” as a Protected Category

    Effective May 20, 2019, New York City amended the NYCHRL to include “sexual and reproductive health decisions” as a protected category for employment purposes. The NYCHRL defines sexual and reproductive health decisions as “any decision by an individual to receive services, which are arranged for or offered or provided to individuals relating to sexual and reproductive health, including the reproductive system and its functions.” Under the amended NYCHRL, protected sexual and reproductive health decisions include, but are not limited to, fertility-related medical procedures; sexually transmitted disease prevention, testing and treatment; and family planning services and counseling, such as birth control drugs and supplies, emergency contraception, sterilization procedures, pregnancy testing and abortion.

    Prohibition on Pre-Employment Drug Testing for Marijuana Use

    Effective May 10, 2020, New York City will prohibit pre-employment drug testing for marijuana usage. The new NYCHRL amendment prohibits employers, labor organizations, employment agencies or their agents from requiring prospective employees to submit to drug testing for marijuana or any tetrahydrocannabinols (“THC”) as a condition of employment.

    The amendment does not apply to persons applying to work in positions (i) involving the supervision of children, medical patients or vulnerable persons; (ii) in law enforcement; (iii) that require compliance with certain provisions of the state labor law and city building code relating to construction and public work sites; (iv) impacting the health and safety of employees or the public; or (v) that require a commercial driver’s license.

    Additionally, the amendment does not apply to drug testing that is required pursuant to federal, state or local statute, regulation or order; a federal government contract granting financial assistance to an employer; or a collective bargaining agreement to which the employer is a party.

    The New York City Commission on Human Rights is expected to promulgate rules for the implementation of this amendment prior to the amendment’s effective date on May 10, 2020.

    The amendment is not without controversy. Many employers drug test prospective employees and will be affected by the amendment. Further, since the language of the amendment refers to “prospective employees,” it is unclear how the amendment will affect an employer’s ability to drug test employees after they have been hired. The Commission’s forthcoming regulations will hopefully add clarity.

    New Wage and Hour Reporting Requirements

    On April 25, 2019, in National Women’s Law Center (NWLC) et al. v. Office of Management and Budget (OMB) et al., the U.S. District Court for the District of Columbia reinstated a 2016 rule requiring the U.S. Equal Employment Opportunity Commission (“EEOC”) to collect data on employee compensation and hours sorted by race, ethnicity and gender. The new reporting requirement, referred to as Component 2 of the Employer Information Report EEO-1 (“EEO-1 Report”), is intended to assist the EEOC in identifying discriminatory pay practices.

    Private employers with 100 or more employees and federal contractors with 50 or more employees are required to submit Component 2 data for calendar years 2017 and 2018 by Sept. 30, 2019. These employers must report W-2 wage information and total hours worked — sorted by race, ethnicity and gender — for persons employed during a selected pay period between Oct. 1 and Dec. 31 of 2017 and 2018. All reports are subject to the confidentiality provisions of Section 709(e) of Title VII of the Civil Rights Act of 1964.

    The EEOC has issued a statement that it will provide further information as soon as possible to assist employers in preparing their filings.

    Authored by Mark E. Brossman, Holly H. Weiss, Scott A. Gold and Andrew B. Lowy.


    This communication is issued by Schulte Roth & Zabel 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. ©2019 Schulte Roth & Zabel LLP.

    All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.

    In depth
    Authors

    Mark E. Brossman

    Partner

    New York – 919 Third Avenue

    Holly H. Weiss

    Retired Partner

    New York – 919 Third Avenue

    Andrew B. Lowy

    Partner

    New York – 919 Third Avenue

    More insights

  • Bipartisan Bill Paves the Way for Significant Retirement Plan Reforms

    Bipartisan Bill Paves the Way for Significant Retirement Plan Reforms

    ARTICLE / CLIENT ALERT

    Bipartisan Bill Paves the Way for Significant Retirement Plan Reforms

    June 4, 2019

    Read time: 8 min

    Key takeaways
    Overview

    The House recently passed the most significant piece of proposed retirement plan legislation in more than a decade: the SECURE Act. Although the Senate must also approve the bill before it becomes law, its proposed changes have considerable bipartisan support in Congress. Plan sponsors should start considering how changes included in the SECURE Act could impact their retirement plans. Employers who do not currently offer retirement plans should also review the new retirement plan incentives included in the proposed legislation.

    In depth

    On May 21, 2019, the US House of Representatives passed the Setting Every Community Up for Retirement Enhancement Act of 2019 (SECURE Act) by a vote of 417 to 3. The SECURE Act is one of the most significant pieces of retirement plan legislation in more than a decade and proposes a number of changes to existing retirement plan rules that are designed to make it easier for employees to save for retirement. The legislation aims to help employees achieve retirement security by ensuring that more workers have access to a retirement plan, are able to save enough money to maintain their standard of living in retirement and do not outlive their retirement savings.

    Key Changes Proposed Under the Secure Act

    Provisions Designed to Encourage Employer-Provided Retirement Plans

    The SECURE Act includes provisions to encourage employers to adopt retirement plans for their employees and to expand access to existing plans. In particular, the bill:

    • Broadens eligibility rules for long-term, part-time employees. Currently, an employer may require its employees to complete 1,000 hours of service during a 12-consecutive-month period to begin participating in its retirement plan. This can result in certain long-term, part-time employees being excluded from plan participation. As a result, the bill requires employers to permit long-term, part-time employees who work at least 500 hours in three consecutive 12-month periods to participate in their plans. However, an employer would not be required to make matching or nonelective contributions on behalf of such employees and could continue to impose an age-21 requirement.
    • Allows small, unrelated employers to adopt “open” multiple employer plans. Existing Department of Labor (DOL) rules require employers that band together to create a multiple employer plan (MEP) to share an economic nexus and commonality of interests completely unrelated to providing benefits. Although the DOL issued proposed regulations last fall that would expand the types of employer groups, associations and organizations that could establish MEPs, the proposal still requires some commonality of interest among employers participating in the MEP. The SECURE Act goes further, and would permit small employers with no commonality of interest to adopt “open” MEPs administered by what the bill refers to as “pooled plan providers.” This change is designed, at least in part, to allow small employers to reduce the administrative cost of providing benefits by leveraging the size of a larger group of employers participating in the plan. The bill also eliminates the so-called “one bad apple” rule and includes provisions designed to protect employers participating in a MEP from penalties that result from another member’s violation of certain plan and regulatory rules.
    • Increases the income tax credit for costs paid or incurred by small employers in connection with establishing a retirement plan. The bill increases the annual start-up credit cap for small employers that adopt a new retirement plan from $500 to up to $5,000.
    • Creates a new income tax credit for small employers that add automatic enrollment. The bill also creates a new income tax credit of $500 per year for up to three years for small employers that add automatic enrollment to their plan.

    Provisions Designed to Promote Additional Savings

    The SECURE Act also includes provisions designed to increase retirement-readiness by closing the gap between what employees are and should be saving for retirement. For example, the bill:

    • Increases the percent cap on automatic enrollment contributions to safe harbor plans. Currently, certain special types of safe harbor 401(k) plans may not automatically enroll or escalate employee contributions above 10% of the employee’s eligible compensation. The bill would raise this 10% cap on automatic contributions to 15% after the employee’s first plan year of participation.

    Provisions Designed to Ensure Financial Security to and Through Retirement

    The SECURE Act includes a number of provisions designed to ensure that employees understand the amount of money needed to retire and do not outlive their retirement savings. For example, the bill:

    • Requires lifetime income disclosure statements. The bill requires employers to provide defined contribution plan participants with information illustrating the amount of monthly payments a participant would receive if the participant’s total defined contribution plan account balance was used to provide lifetime income through an annuity.
    • Permits retirees to delay required minimum distribution (RMD) payments until age 72. Under current law, RMD payments must generally start by April 1 of the calendar year following the later of the calendar year in which an employee reaches age 70-1/2 or terminates employment. The bill would increase the age at which RMD payments must begin from age 70-1/2 to age 72.
    • Enhances rules regarding lifetime annuity options under defined contribution plans. The bill includes provisions designed to encourage defined contribution plan sponsors to offer in-plan annuity options that provide lifetime income during retirement by creating a new fiduciary safe harbor for employers that include such investments in their defined contribution plans. The bill also permits participants to roll over lifetime income investments to an IRA or other retirement plan as needed.

    Other Changes Impacting Plan Administration

    Lastly, the SECURE Act includes a number of other changes that would impact retirement plan administration. Specifically, the bill:

    • Simplifies certain safe harbor plan rules and notice requirements. The bill eliminates the safe harbor notice requirement for safe harbor plans that satisfy the safe harbor plan rules by making nonelective contributions to their employees. The bill also provides additional flexibility to add safe harbor nonelective contributions to plans mid-year.
    • Provides nondiscrimination testing relief for certain closed defined benefit pension plans. Many employers have closed their defined benefit plans to new participants, but permit existing participants (or groups of participants) to continue to earn benefits under the plan. Because new employees can no longer enter the plan, closed plans can become discriminatory if the attrition rate of non-highly compensated employees outpaces the attrition rate of highly compensated employees. Therefore, the bill includes testing relief that would make it easier for closed pension plans to satisfy certain nondiscrimination testing requirements.
    • Modifies certain rules regarding RMD payments made following a participant’s death. The bill changes the post-death RMD rules to require that all distributions after death (other than distributions to certain types of beneficiaries) be made by the end of the tenth calendar year following the year of the participant’s death. This rule would apply to defined contribution, but not defined benefit, plans.
    • Prohibits plan loans through credit cards or similar arrangements.
    • Increases penalties for failure to timely file certain plan returns. The bill significantly increases the penalties for failure to timely file (i) a plan’s Form 5500, (ii) the registration statement for deferred vested benefits and (iii) the notification of certain changes in a plan’s registration information. The bill also increases penalties for failing to timely provide a required withholding notice.
    • Permits penalty-free withdrawals for birth or adoption. The bill allows penalty-free withdrawals from defined contribution plans of up to $5,000 within one year of the birth or adoption of a child to help cover related expenses.
    • Modifies rules related to the treatment of 403(b) custodial accounts upon termination. The bill directs the Secretary of Treasury to issue guidance that will provide that, if an employer terminates a 403(b) custodial account, the account can be distributed in-kind to a participant or beneficiary. The individual custodial account will be maintained on a tax-deferred basis as a 403(b) custodial account until paid out.
    • Clarifies that employees of certain church-related organizations may be covered under a 403(b) plan that consists of a retirement income account.

    What’s Next?

    The House’s passage of the SECURE Act is a significant step toward potentially sweeping retirement plan reforms. While the bill must still make its way through the US Senate to become law, the changes proposed by the SECURE Act have considerable bipartisan support in Congress. In fact, the Senate is also considering a separate bill that proposes a number of similar changes (the Retirement Enhancement and Savings Act of 2019). As a result, many expect some version of the SECURE Act (or a similar bill) to successfully move forward through the Senate and be signed into law later this year. Accordingly, plan sponsors should start considering how changes included in the SECURE Act could impact their retirement plans. In addition, employers who do not currently provide retirement plans should review the new retirement plan incentives included in the bill.

    Authors
    More insights

  • Texas Court Declares Licensing Offer Based on End Device Is FRAND, Diverges from California Court in Qualcomm

    Texas Court Declares Licensing Offer Based on End Device Is FRAND, Diverges from California Court in Qualcomm

    ARTICLE / CLIENT ALERT

    Texas Court Declares Licensing Offer Based on End Device Is FRAND, Diverges from California Court in Qualcomm

    June 3, 2019

    Read time: 7 min

    Key takeaways
    Overview

    Standard-essential patent holders and implementers may face uncertainty regarding licensing practices following a May 23 Texas court ruling. In the ruling, a Texas federal judge reached a conclusion different from a recent California court decision—FTC v. Qualcomm—on the question of whether an SEP holder must base its royalty rates on the “smallest salable patent-practicing unit” in order to comply with a fair, reasonable and non-discriminatory royalty commitment.

    In depth

    On May 23, a Texas federal judge entered a declaratory judgment that Ericsson, a standard-essential patent (SEP) holder, did not breach its obligation to offer HTC, an end-device manufacturer, a license to its SEPs on fair, reasonable and non-discriminatory (FRAND) terms. The decision follows a jury verdict finding that Ericsson did not breach its FRAND commitment. The judge rejected HTC’s argument that Ericsson must base the royalty rate for its SEPs on the value of baseband chips within smartphones rather than on the phones themselves. This ruling stands in tension with the recent decision in FTC v. Qualcomm, where a California court concluded that it was unreasonable for Qualcomm to base the royalty rates for its SEPs on the price of an entire phone rather than on the baseband chip. The contrasting rulings, thus, may create uncertainty regarding licensing practices among SEP holders and implementers until further clarification is provided from courts of appeal.

    Ericsson owns patents declared essential to the 2G, 3G and 4G wireless communication standards. Ericsson made a commitment to several standard setting organizations, including the European Telecommunications Standards Institute (ETSI), to license those SEPs on FRAND terms. HTC makes smartphones that implement Ericsson’s SEPs and brought suit against Ericsson in April 2017, alleging that Ericsson overcharges for its SEPs. HTC argued that Ericsson’s royalty rates are unreasonable on a number of grounds, including because they are based on the value of the smartphones HTC produces rather than on the baseband chips that incorporate Ericsson’s SEPs within the phones. In response, Ericsson brought a counterclaim seeking a declaratory judgment that it complied with its FRAND obligation.

    Last year, Ericsson moved for a ruling that its FRAND commitment to ETSI does not require it to base its royalty rates on the “smallest salable patent-practicing unit” (SSPPU)—the baseband chip. The court held earlier this year that, as a matter of French law, ETSI’s Intellectual Property Rights policy neither requires nor precludes SEP holders from using the SSPPU as a royalty base. Instead, what constitutes a FRAND offer depends on the particular facts of the case. The parties then proceeded to trial and the jury found that Ericsson did not breach its FRAND commitment.

    Following the jury verdict, the court entered a declaratory judgment that, based on the facts of the case, Ericsson complied with its FRAND obligation despite not using the SSPPU as its royalty base. The court rejected HTC’s assertion that Ericsson must base its royalty rates on the value of the baseband chip instead of the smartphone itself. Baseband chips enable phones to communicate with each other across cellular networks but serve no other function. HTC argued that basing the royalty rate on the entire phone is unreasonable because modern smartphones have many features unrelated to cellular connectivity that do not utilize Ericsson’s SEPs. Thus, HTC argued that Ericsson’s proposed royalty rate does not reflect the limited value baseband chips add to smartphones.

    The court rejected HTC’s SSPPU argument on several grounds. First, the court cited evidence that customers value cellular connectivity more than HTC suggested. Given that Ericsson was negotiating with the end-device manufacturer and not the component supplier, it was appropriate to consider the overall value Ericsson’s technology added to the end device rather than limit the value to the component only. Second, the court found that the baseband chip is not the SSPPU. Ericsson presented expert testimony that its SEPs also cover additional components, such as antennas and RF switches. Thus, the court determined that Ericsson’s SEPs would not be infringed by a baseband chip alone. Finally, the court noted that HTC was unable to identify even a single example of a license to a smartphone OEM based on the baseband chip.

    The court also found that other comparable licenses provide evidence that Ericsson’s royalty rates are consistent with its FRAND obligation. The court cited evidence that Ericsson’s SEP licenses with other smartphone OEMs all have royalty rates that are similar to the rates Ericsson offered to HTC. Given these other comparable licenses, the court concluded that Ericsson’s offers to HTC were FRAND.

    The court’s declaratory judgment in HTC v. Ericsson stands in contrast with a California court’s decision earlier this month in FTC v. Qualcomm. In that ruling, the court concluded that Qualcomm violated the Federal Trade Commission Act by maintaining its monopoly power as a baseband chip supplier through a number of exclusionary practices. One of the Qualcomm court’s findings was that Qualcomm’s royalty rates for its SEPs, with respect to baseband chips, are unreasonably high.

    In particular, the Qualcomm court found that it is unreasonable for Qualcomm to charge royalty rates to chipset suppliers on the price of an entire phone. The court cited an internal Qualcomm document acknowledging that “user experience,” rather than the baseband chip, drives the modern smartphone’s value. The Qualcomm court also was persuaded by several OEMs’ testimonies that OEMs add significant value to their phones unrelated to the baseband chip and that smartphones “are now essentially computers.” Thus, in the court’s view, Qualcomm’s royalty rates based on the end device are disproportionate to the value of its SEPs and the chips that implement them. The court also cited Federal Circuit precedent holding that a patent royalty should be based on the SSPPU, and then concluded that Qualcomm’s imposition of a royalty based on the entire phone is inconsistent with that precedent.

    The HTC and Qualcomm decisions demonstrate that the law is unsettled as to whether an SEP holder must base its royalty rates on the SSPPU in order to comply with a FRAND commitment. In the smartphone context, some may argue that basing SEP royalty rates on the value of the entire phone exaggerates the value of those SEPs—especially as modern cell phones have become more sophisticated. The Qualcomm court accepted this argument, but the HTC court found that Ericsson’s practice of basing its royalty rates on the entire phone is consistent with industry practice. Going forward, district courts may issue more divided opinions on this issue. In the interim, it is important for SEP holders to look to industry practice, comparable licenses and ordinary course documents when assessing their strategy for SEP licensing negotiations.

    Authors
    More insights

  • New DOJ Guidance on “Cooperation Credit”

    ARTICLE

    New DOJ Guidance on “Cooperation Credit”

    May 31, 2019

    Read time: 2 min

    Key takeaways
    Overview

    Michael Peregrine and Tony Maida co-authored this bylined article discussing the recent DOJ guidance on how it awards Cooperation Credit and its relevance to health systems’ legal and compliance officers and boards.

    In depth
    Authors

    Tony Maida

    Partner

    New York – One Vanderbilt Avenue

    More insights