ARTICLE / CLIENT ALERT
New French Decree, Ministerial Order Clarify Foreign Investment Authorisation Rules
January 14, 2020
Read time: 4 min
Dated 31 December 2019, the legislation updates and elucidates the process for obtaining foreign investment authorisations in France. The new provisions go into effect on 1 April 2020.
Under French law, investments made by foreign entities in French companies that conduct activities considered “sensitive” or strategic to French national interests may require prior authorisation by the French Minister of the Economy. A newly published decree and ministerial order, both dated 31 December 2019, modify and clarify the rules and procedures governing foreign investment authorisations in France. The provisions of this legislation become effective on 1 April 2020.
The new Decree No. 2019-1590 provides for additional sectors of activities that fall under the foreign investment regulations, including print and digital media, food safety and critical technologies (i.e., cybersecurity, AI, robotics, additive manufacturing, semiconductors, quantum technologies and energy storage).
The decree also modifies the definition of investments subject to prior authorisation. As of 1 April 2020, shares exceeding 25% of voting rights in an entity governed by French law will trigger control of investments for non-EU investors. This threshold previously was 33.33%.
In terms of procedure, the new decree provides that investors must submit an application for authorisation. The Minister of the Economy has 30 business days from the date of receipt of the application to notify the investor that the investment (i) is not subject to the prior authorisation requirement, (ii) is subject to it and is authorised without conditions, or (iii) requires further examination. In the latter case, the Minister has an additional 45 business days to conduct the examination. In the absence of a response from the Minister within the stated time limit, the application is deemed to be rejected.
The decree also allows both the target company and the investor to file a written preliminary request to the Minister to confirm whether the contemplated investment is subject to the prior authorisation requirement. The 31 December 2019 Ministerial Order specifies the information that the investor must provide when filing an authorisation application or a preliminary request.
Finally, the new decree provides further details on the Minister’s powers to impose sanctions in the event of non-compliance with the foreign investment regulations.
Pursuant to Article L. 151-3-1 of the French Financial and Monetary Code, failure to comply with the obligation to obtain prior authorisation exposes the investor to administrative sanctions, among other things. In particular, the Minister may order the investor to:
- Apply for authorisation to regularise the transaction
- Amend the transaction
- Return to the status quo ante at the investor’s expense.
The Minister’s decision may be accompanied by a per diem penalty and precautionary measures, such as suspending the investor’s voting rights and preventing the investor from disposing of assets or receiving dividends.
Under the new decree, the Minister may impose sanctions in cases of emergency, exceptional circumstances or imminent threat to the public order. In such cases, the investor must be provided with formal notice and will have a minimum of five business days to submit its observations.
The new decree sets at EUR 50,000 the amount of the per diem penalty that the Minister may impose on the investor in addition to other injunctions.
2020 Starts Off with Two Government Publications Critical of 340B Program Oversight
ARTICLE / CLIENT ALERT
2020 Starts Off with Two Government Publications Critical of 340B Program Oversight
January 13, 2020
Read time: 11 min
Less than two weeks into the new year, the federal government has released two new publications addressing concerns related to 340B Program oversight by both state and federal agencies. After a relatively quiet 2019, 340B Covered Entities should be prepared for increased scrutiny, oversight and the potential for additional 340B Program compliance requirements in 2020.
After a comparatively quiet 2019, 340B Covered Entities should be prepared for increased scrutiny, oversight and the potential for additional 340B Program compliance requirements in 2020. Less than two weeks into the new year, the federal government has released two new publications addressing concerns related to 340B Program oversight by both state and federal agencies.
On January 8, 2020, the Centers for Medicare and Medicaid Services (CMS) issued an “Informational Bulletin” to state Medicaid programs on Best Practices for Avoiding 340B Duplicate Discounts in Medicaid. This publication was followed on January 10, 2020, by the release of a long-awaited Government Accountability Office report on oversight of non-governmental hospitals participating in the 340B Program by the Health Resources and Services Administration (HRSA).
Based on the information provided in these two publications, we expect to see additional obligations being imposed on 340B Covered Entities by both state Medicaid agencies and HRSA in the coming months, particularly as they relate to limitations on dispensing of 340B drugs to Medicaid Managed Care plan enrollees and 340B nongovernmental hospitals’ contracts with state and location governments. In anticipation of such additional obligations and oversight relating to duplicate discount prevention all Covered Entities should consider reviewing the effectiveness of their duplicate discount prevention policies, procedures, and operations and nongovernmental hospitals should also evaluate contracts with state and local governments supporting 340B Program eligibility for consistency with 340B statutory requirements.
CMS Informational Bulletin on Best Practices for Avoiding 340B Duplicate Discounts
State Medicaid agencies are prohibited from billing manufacturers for Medicaid rebates for drugs dispensed to Medicaid patients that have already been discounted under the 340B Program. If a manufacturer erroneously provides both a discount and a rebate on a drug, it is considered a “duplicate discount” and the 340B Covered Entity that dispensed and billed Medicaid for the drug may be subject to repayment of the 340B discount to the manufacturer.
Identification of 340B drugs dispensed to Medicaid beneficiaries for purposes of preventing duplicate discounts has been challenging for state Medicaid agencies, 340B Covered Entities, and drug manufacturers. States have experimented with a variety of methods to attempt to identify 340B drugs dispensed to Medicaid beneficiaries, but neither CMS nor HRSA have issued regulations requiring specific duplicate discount prevention processes by 340B Covered Entities or state Medicaid agencies. The identification and prevention of duplicate discounts is further complicated when 340B drugs are dispensed through contract pharmacy arrangements or paid by Medicaid Managed Care plans, as such arrangements create additional barriers to and parties involved with transmission of 340B purchasing information from Covered Entities to the State.
Recognizing the challenges that states have in identifying Medicaid claims for 340B drugs, but stopping short of requiring any specific methodology for states to identify the claims, CMS released an Informational Bulletin to state Medicaid programs that lists and explains seven different approaches, which CMS describes as “best practices”, that states could adopt to avoid duplicate discounts. The seven approaches are summarized below in Table 1.
Table 1
CMS Best Practice to Avoid Duplicate DiscountsAnalysis
| Use the 340B Medicaid Exclusion File (MEF) to identify 340B Covered Entities that dispense 340B drugs to Medicaid beneficiaries. | CMS notes that the MEF does not apply to arrangements between Covered Entities and Medicaid Managed Care plans and, therefore, can be used only to identify Medicaid Fee-For-Service (FFS) claims. |
| Develop strategies with Contract Pharmacies. | CMS notes that 340B Covered Entities are not permitted to dispense 340B drugs to Medicaid FFS beneficiaries through contract pharmacy arrangements unless they have received approval from HRSA and provide a link to the website where states can view a list of Covered Entities that have received such approval. |
| Limit Medicaid reimbursement for 340B Drugs purchased by Covered Entities. | CMS notes that states can utilize the State Plan Amendment (SPA) process to receive approval to place parameters around the ability of Covered Entities and contract pharmacies to dispense 340B drugs to Medicaid FFS beneficiaries, as well as to require Covered Entities to notify the state of 340B dispensing to Medicaid beneficiaries. As an example, CMS includes use of SPAs to limit the ability of Covered Entities to dispense 340B drugs to Medicaid beneficiaries and require Covered Entities to use non-340B drugs for Medicaid beneficiaries. The Informational Bulletin does not address the impact that such Medicaid dispensing restrictions may have on Covered Entities subject to the 340B GPO Prohibition and could incur significantly higher drug costs if restrictions are placed on dispensing 340B drugs to Medicaid beneficiaries. |
| Use 340B claims identifier options. | CMS identifies and provides descriptions of five separate codes that can be placed on claims for 340B drugs, including pharmacy claim identifiers “20” and “08”, as well as hospital claim identifiers “UB,” “JG,” and “TB.” Of particular interest to 340B Covered Entities, CMS indicates that code “20” is expected to be discontinued in the future and suggests to state Medicaid agencies that they use the “JG” and “TB” modifiers to identify (and exclude from rebate requests) 340B claims, including through instructions to Medicaid Managed Care plans to use these modifiers to identify claims to exclude from utilization data submitted to the state. |
| Include 340B duplicate discount provisions in Medicaid managed care contracts. | CMS uses the Informational Bulletin to remind states that they are required to comply with the provisions of 42 CFR § 438.3(s)(3), which obligate states to include provisions in Medicaid managed care contracts that instruct the Medicaid managed care plans to exclude utilization data for drugs subject to 340B discounts, unless the state requires submission of Medicaid managed care drug claims data directly from the Covered Entities. |
| Provide claims-level data to manufacturers. | CMS suggests that states could provide Medicaid drug claim data directly to manufacturers to assist in identifying duplicate discounts, although CMS recognizes that providing such data is not required. CMS notes, however, that it believes that providing such data could reduce administrative burdens and costs to the states in identifying and validating duplicate discount data. |
| Use specific Medicaid BIN/PCN on Medicaid managed care plan identification cards. | Recognizing that contract pharmacy claims create particular problems for duplicate discount prevention, CMS recommends that states require Medicaid managed care plans and their Pharmacy Benefit Managers to use Medicaid-specific BIN/PCN numbers. Currently, some plans use the same BIN/PCN for Medicaid and non-Medicaid enrollees, making it difficult to identify Medicaid pharmacy claims. If claims cannot be identified as Medicaid claims, it complicates management of duplicate discount prevention approaches. CMS acknowledges that once a claim is identified as a Medicaid claim, additional data is required to determine if the claim relates to a 340B-purchased drug. |
The release of the Informational Bulletin suggests that CMS is continuing to monitor state efforts to reduce duplicate discounts and could begin to take enforcement action against states that do not comply with regulatory requirements related to duplicate discount prevention, including those related to Medicaid managed care plan contracts. 340B Covered Entities should be prepared for increased state regulation of 340B Medicaid claims and dispensing, as well as increased restrictions on use of 340B drugs under Medicaid managed care plan arrangements.
GAO Report on HRSA Oversight of Nongovernmental Hospital Eligibility Requirements
Hospitals participating in the 340B Program must be either governmental hospitals or nonprofit hospitals. Nonprofit hospitals that participate in the 340B Program are required to contract with state or local governments to provide healthcare services to low-income individuals not eligible for Medicare or Medicaid. In response to a request from the Republican leadership of the Senate Committee on Health, Education, Labor and Pensions and the House Committee on Energy and Commerce arising out of concerns about growth in nongovernmental hospital participation in the 340B Program, the Government Accountability Office (GAO) recently conducted a review of HRSA’s oversight of compliance of nongovernmental hospitals with the nonprofit status and government contract requirements.
GAO concluded in a report released publicly on January 10, 2020, that HRSA’s oversight of both the nonprofit status requirements and government contract requirement is lacking, primarily due to HRSA’s reliance on self-attestations of compliance, as well as limited and inconsistent review of verifiable primary-source documentation. GAO recommended six specific actions for HRSA to take to increase its oversight of nongovernmental hospital eligibility requirements. The Department of Health and Human Services (HHS) concurred with GAO on all but one of the recommendations, although HHS also noted that HRSA would be most effectively able to oversee the 340B Program if it were granted regulatory authority to do so by Congress, consistent with the request in the FY 2020 President’s Budget. A list of the recommendations is provided below in Table 2.
Table 2
GAO RecommendationAnalysis
| HRSA should ensure that information used to verify nonprofit status is reliable. | GAO found that HRSA relies primarily on CMS Medicare Cost Report data to verify hospitals’ government or nonprofit status, but that HRSA did not validate that the CMS data is accurate or consistent with 340B Program nonprofit requirements. HRSA indicated that it may request submission of supporting documentation (e.g., IRS form 990, IRS letter, state letter) and that such documentation must be a part of a nongovernmental hospital’s auditable records and available on request at any time. |
| HRSA should implement a process to verify that every nongovernmental hospital that participates in the 340B Program has a contract with state or local government. | GAO found that HRSA does not adequately verify the existence of a contract with state or local government for all nongovernmental hospitals and instead relies on hospitals’ self-certification that such contracts exist. Notably, HHS did not agree that HRSA should implement a process to verify the existence of a contract for every nongovernmental hospital because HHS does not believe HRSA has the resources to do so and that such a process would create significant burdens for hospitals. |
| HRSA should amend its contract integrity check procedures to review whether government contracts require the provision of healthcare services to low-income individuals not eligible for Medicare or Medicaid. | GAO found that certain contracts it reviewed in the course of its review did not include requirements for the contracting hospital to provide healthcare services to low income individuals not eligible for Medicare or Medicaid, or did not state how such compliance would be determined or evaluated. HHS is concerned with this recommendation and noted that HRSA is evaluating the feasibility of incorporating additional review of contracts into its internal procedures, although HRSA indicted that such reviews have not previously occurred due to resource constraints. HRSA noted that the 340B statute does not specify what types of services are required to be provided. |
| HRSA should provide guidance to audit staff on how to review government contracts for compliance with 340B statutory requirements. | GAO found that HRSA had not provided adequate or consistent instruction to auditors on how to determine whether contracts included requirements to provide healthcare services to low-income individuals not eligible for Medicare or Medicaid. HHS concurred with this recommendation and indicated that HRSA had already updated its standard operating procedures for auditors to include instructions to notify HRSA if an auditor has any concerns with a contract or the required elements are not easily identifiable in the contract. |
| HRSA should revise audit procedures to require auditors to document review and assessment of whether government contracts are appropriately signed, cover the period under review, and require provision of healthcare services to low-income individuals not eligible for Medicare and Medicaid. | GAO found that HRSA auditors did not routinely document their affirmative review and assessment of the required government contract elements. HHS agreed with this recommendation and indicated that HRSA had already updated its audit procedures to comply with this recommendation. |
| HRSA should require nongovernment hospitals to demonstrate that they have government contracts in place prior to the beginning of the auditor’s review period and should apply consistent and appropriate consequences for hospitals that are unable to do so. | GAO found that HRSA auditors were permitting hospitals to retroactively enter into government contracts if the hospitals were unable to produce valid contracts during an audit. HHS concurred with GAO’s recommendation and noted that HRSA included additional requests for contract information in the Information Collection Request that it submitted to the Office of Management and Budget and for public comment in fall 2019. HHS further noted, however, that the 340B Statute does not provide HRSA with the authority over the specific contract details, resulting in enforcement actions being evaluated on a case-by-case basis. |
In light of HHS’ agreement with GAO’s recommendations, we expect nongovernmental 340B hospitals to see significantly increased scrutiny and oversight of their compliance with nonprofit status and government contract requirements in the coming year. We have already seen some evidence of additional scrutiny in requests from HRSA for government contract information from currently enrolled nongovernmental hospitals.
Nongovernmental hospitals participating in the 340B Program should review their existing contracts used for 340B eligibility purposes to ensure they meet state law contract requirements and comply with 340B Program statutory requirements.

FDA 2019 Year in Review
ARTICLE / REPORT
FDA 2019 Year in Review
January 2020
Read time: 2 min
2019 was a robust year for the US Food and Drug Administration’s (FDA’s) regulatory agenda. The agency continued to implement initiatives and mandates required by the 21st Century Cures Act (Cures Act), and navigated leadership and staffing changes at many levels. Most notably, Commissioner Scott Gottlieb resigned on April 5. Norman Sharpless and Brett Giroir served as acting interim commissioners following Commissioner Gottlieb’s resignation. On December 17, Congress swore in Commissioner Stephen Hahn, a radiation oncologist and former chief executive of MD Anderson Cancer Center.
This Special Report reviews notable actions that shaped FDA-regulated industries and products last year, and offers insight into the agency’s 2020 priorities and expected actions in a number of areas, including:
- Digital health;
- Streamlined product approvals;
- Evolving evidentiary thresholds for product approvals;
- Strategic enforcement;
- And much more.

AI Implementation Isn’t Just ‘Picking a Technology and Installing It’
ARTICLE
AI Implementation Isn’t Just ‘Picking a Technology and Installing It’
January 13, 2020
Read time: 2 min
As part of the Legalweek 2020 Q&A series, Martha Louks speaks to Legaltech News about AI’s importance to knowledge management, looking out for AI hype, and more.

CFTC Cyber Incident Information Request — Private Fund Manager Responses Required
ARTICLE / CLIENT ALERT
CFTC Cyber Incident Information Request — Private Fund Manager Responses Required
January 9, 2020
Read time: 4 min
On Jan. 3, 2020, the National Futures Association distributed a Cyber Threat Alert from the U.S. Commodity Futures Trading Commission to registered commodity pool operators (i.e., many private fund managers) related to a cyber-intrusion affecting a number of cloud service providers, which was the focus of a Dec. 30, 2019 Wall Street Journal article.[1] The CFTC clarified the scope of its requests in a supplement sent on Jan. 9, 2020.
All registered private fund managers will have to take the following actions in response to the Cyber Threat Alert.
- Directly Affected Managers. CFTC-registered managers that engage cloud service providers impacted by the intrusion need to notify the CFTC’s Division of Swap Dealer and Intermediary Oversight by Jan. 10, 2020, by emailing DSIOAlerts@CFTC.gov. Affected managers will need to include in their reply: (i) information regarding whether and when any provider informed them about the attack, (ii) a summary of any steps they have taken to protect their systems and data in response this attack and (iii) plans to notify market participants whose data may have been affected. Managers not affected by the attack need not reply to this request.
- All CFTC-Registered Managers. The Cyber Threat Alert asks that managers promptly notify the CFTC if their assessment of the impact of the intrusion changes.
- All CFTC-Registered Managers. The CFTC asked all managers “to consider, in light of this reporting, your organization’s systems and data vulnerability.” Managers therefore should address this CFTC request in their annual compliance reviews or, if that process is not imminent, in a separate review.
- All Managers. All Managers should consider what level of response to this situation is necessary or appropriate under their fiduciary obligations (understanding that regulators and investors may ask questions on this topic in the future).
The Cyber Threat Alert is a reminder that, to the extent managers experience any cyber intrusion, they should promptly review their disclosure obligations under their offering documents, regulatory filings, and investor agreements (including side letters), and consider any notification requirements under the rules of the NFA or any other applicable self-regulatory organization (the NFA has separate data breach notification requirements) and under state laws. These disclosures and responses will likely require the guidance of specialized privacy counsel.
Authored by Brian T. Daly, Edward H. Sadtler, Kelly Koscuiszka and Joshua B. Wright.
If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.
[1] The article reports that approximately a dozen cloud service providers have been hacked, and indicates that the attackers may have gained access to the providers’ networks, compromising their clients’ data in turn. See Rob Barry and Dustin Volz, “Ghosts in the Clouds: Inside China’s Major Corporate Hack,” The Wall Street Journal, Dec. 30, 2019, available here.
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. ©2020 Schulte Roth & Zabel LLP.
All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.
Corporate Practice of Medicine: A 50 State Survey
ARTICLE
Corporate Practice of Medicine: A 50 State Survey
Second Edition
Read time: 2 min
McDermott health lawyers contributed to the second edition of AHLA’s Corporate Practice of Medicine: A 50 State Survey. Expanded to cover a broader range of healthcare professionals, this edition contains the latest information on practice restrictions by state as they relate to behavioral health providers, dentists, chiropractors, optometrists, and more.
Editor: Joel C. Rush
Authors: Carole M. Becker, Stacey L. Callaghan, Dana Dombey, M. Brian Hall IV, Dawn R. Helak, Marshall Jackson Jr., Amanda Jester, Chelsea Rogers and Li Wang.
Subpart F Sales Income: The ‘Whirlpool’ Case
ARTICLE
Subpart F Sales Income: The ‘Whirlpool’ Case
1/8/2020
Read time: 1 min
Cookie Crumbles Against Injunction Granted to Terminated Trademark Licensee
ARTICLE
Cookie Crumbles Against Injunction Granted to Terminated Trademark Licensee
January 8, 2020
Read time: 1 min

Finally SECURE: Opportunities in the 2019 SECURE Act for Plan Sponsors
ARTICLE / CLIENT ALERT
Finally SECURE: Opportunities in the 2019 SECURE Act for Plan Sponsors
January 8, 2020
Read time: 10 min
On December 19, 2019, Congress passed the Further Consolidated Appropriations Act of 2020. Tucked into this year-end spending bill is the SECURE Act—the most significant piece of retirement plan legislation in more than a decade—and a number of other provisions impacting health and welfare plans. Plan sponsors should immediately start considering how these changes could impact their retirement and health and welfare plans in 2020 and beyond.
On December 19, 2019, Congress passed the Further Consolidated Appropriations Act of 2020 (the Act), which the President signed into law shortly thereafter. This year-end spending bill included the Setting Every Community Up for Retirement Enhancement Act of 2019 (SECURE Act) and a number of other new rules impacting health and welfare plans.
The SECURE Act is the most significant piece of retirement plan legislation in more than a decade. The SECURE Act includes a number of changes to existing retirement plan rules that are designed to make it easier for employees to save for retirement. The SECURE Act 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. In addition, the Act includes a number of important new rules impacting health and welfare plans.
The following summarizes the most significant changes for plan sponsors:
Provisions Designed to Encourage Employer-Provided Retirement Plans
The SECURE Act includes provisions that encourage employers to adopt retirement plans for their employees and to expand access to existing plans. In particular, the SECURE Act:
- 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 SECURE Act 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 (other than collectively bargained plans). However, an employer will not be required to make matching or nonelective contributions on behalf of such employees and may continue to impose an age-21 requirement.
Timing: This change is effective for plan years beginning after December 31, 2020. However, for purposes of determining the three consecutive 12-month periods, 12-month periods occurring before January 1, 2021, do not need to be taken into account.
- 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 regulations this summer that expand the types of employer groups, associations and organizations that can establish MEPs, the regulations still require some commonality of interest among employers participating in the MEP. The SECURE Act goes further, and permits small employers with no commonality of interest to adopt “open” MEPs administered by what the SECURE Act 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 SECURE Act also eliminates the so-called “one bad apple” rule by including provisions designed to protect employers participating in a MEP from penalties that result from another member’s violation of certain plan and regulatory rules.
Timing: This change is effective for plan years beginning after December 31, 2020.
- Increases the income tax credit for costs paid or incurred by small employers in connection with establishing a retirement plan. The SECURE Act increases the annual start-up credit for small employers that adopt a new retirement plan from $500 to up to $5,000.
Timing: This change is effective for tax years beginning after December 31, 2019.
- Creates a new income tax credit for small employers that add automatic enrollment. The SECURE Act 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.
Timing: This change is effective for tax years beginning after December 31, 2019.
Provisions Designed to Promote Additional Savings and to Ensure Financial Security to and Through Retirement
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, and helping employees understand the amount of money needed to retire. For example, the SECURE Act:
- Increases the percent cap on automatic enrollment contributions to safe harbor plans. Currently, safe harbor 401(k) plans that include a qualified automatic contribution arrangement (QACA) may not automatically enroll or escalate employee contributions above 10% of the employee’s eligible compensation. The SECURE Act raises this 10% cap on automatic contributions to 15% after the employee’s first plan year of participation.
Timing: This change is effective for plan years beginning after December 31, 2019.
- Requires lifetime income disclosure statements. The SECURE Act 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.
Timing: To be determined. This change will become effective for benefit statements furnished more than 12 months after the later of the Department of Labor’s issuance of (1) an interim final rule regarding these disclosures, or (2) model disclosures and assumptions.
- 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 SECURE Act increases the age at which RMD payments must begin from age 70-1/2 to age 72.
Timing: This change is effective for required distributions made after December 31, 2019, with respect to individuals who attain age 70-1/2 after that date. Participants who attained age 70-1/2 during 2019 will still need to receive RMD payments by April 1, 2020.
- Enhances rules regarding lifetime annuity options under defined contribution plans. The SECURE Act 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 options in their defined contribution plans. The SECURE Act also permits participants to roll over lifetime income investments to an IRA or other retirement plan as needed.
Timing: The fiduciary safe harbor became effective upon enactment. The rollover option is effective for plan years beginning after December 31, 2019.
Other Changes Impacting Retirement Plan Administration
The SECURE Act includes a number of other changes that will impact retirement plan administration. Specifically, the SECURE Act:
- Simplifies certain nonelective 401(k) plan safe harbor rules and notice requirements. The SECURE Act 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 SECURE Act also provides additional flexibility to add or amend safe harbor nonelective contributions to plans mid-year.
Timing: This change is effective for plan years beginning after December 31, 2019.
- Provides nondiscrimination testing relief for certain closed or “frozen” 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. The SECURE Act includes testing relief that will make it easier for closed pension plans to satisfy certain nondiscrimination testing requirements.
Timing: This change is generally effective upon enactment.
- Modifies certain rules regarding RMD payments made following a participant’s death. The SECURE Act 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 will apply to defined contribution, but not defined benefit, plans.
Timing: This change is generally effective for distributions with respect to employees who die after December 31, 2019 (or December 31, 2021, for certain collectively bargained plans and governmental plans).
- Prohibits plan loans through credit cards or similar arrangements. This is effective for loans made after the date of enactment.
- Increases penalties for failure to timely file certain plan returns. The SECURE Act significantly increases the penalties for failure to timely file (i) a plan’s Form 5500, (ii) the registration statement for deferred vested benefits (Form 8955-SSA) and (iii) the notification of certain changes in a plan’s registration information. The SECURE Act also increases penalties for failing to timely provide a required withholding notice.
Timing: These changes are generally effective for returns, statements and notices required to be filed or provided beginning after December 31, 2019.
- Permits penalty-free withdrawals for birth or adoption. The SECURE Act 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. Under certain conditions, plans may allow such distributions to be repaid to the plan.
Timing: This change is effective for distributions after December 31, 2019.
- Modifies rules related to the treatment of 403(b) custodial accounts upon termination. The SECURE Act 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.
Timing: Guidance will be retroactively effective for tax years beginning after December 31, 2008.
Clarifies that employees of certain church-related organizations may be covered under a 403(b) plan that consists of a retirement income account.
Timing: This change is effective for all years beginning before, on or after the enactment of the SECURE Act.
Health and Welfare Changes
Lastly, the Act includes a few significant changes affecting health and welfare plans:
- Repeals the Medical Device Tax. The Act eliminates the medical device tax, a 2.3% excise tax on certain devices such as pacemakers, which was part of the Affordable Cart Act (ACA).
Timing: This change is effective for sales after December 31, 2019.
- Repeals the Health Insurance Providers Tax. The Act eliminates the annual health insurance tax (HIT) on insurers of fully insured plans that was part of ACA.
Timing: This change does not take effect until calendar years after December 31, 2020.
- Repeals the Cadillac Tax. The Act eliminates the excise tax on high-cost employer-sponsored health coverage (the “Cadillac tax”) enacted as part of ACA, but continually delayed.
Timing: This change is effective for tax years after December 31, 2019.

Gender Sidelining’ Claims Raise 4 Key Issues
ARTICLE
Gender Sidelining’ Claims Raise 4 Key Issues
January 7, 2020
Read time: 1 min
