Enforcement Actions Continue to Spotlight Crypto Risks for Plan Fiduciaries

The Treasury Department issued a record-breaking multi-billion dollar fine against crypto exchange Binance as part of a broad settlement with federal officials.

Enforcement action, including a $4.3 billion Treasury Department fine against Binance just a day after charges were filed against another crypto exchange, should factor into any plan fiduciary’s due diligence, if considering cryptocurrency investments for a retirement plan, ERISA lawyers said.

Wagner Law Group, an ERISA law firm, has previously cautioned retirement plan fiduciaries on the risks of using cryptocurrency investments in their plans, in large part because of the industry’s frequent compliance issues.

On November 20, the Securities and Exchange Commission charged Kraken, a crypto exchange, for operating as an unregistered securities exchange. This prompted Wagner Law Group partner Kimberly Shaw Elliott to caution fiduciaries of the risks of crypto assets, given their compliance issues:

“The SEC’s new enforcement activity should be a clear warning to not only unregistered crypto providers and the advisers who recommend crypto investments, but also to retirement plan fiduciaries who approve those investments,” she wrote. “Is it prudent to place faith in the seller or holder of crypto who does not go through the rigors of registration?”

The Department of the Treasury’s record-breaking fine of Binance further compounds the fiduciary risks of crypto assets.

Get more!  Sign up for PLANSPONSOR newsletters.

The fines and other penalties were levied against Binance Holdings Ltd., a crypto exchange. The SEC had, in June, charged Binance with operating as an unregistered securities exchange, and those allegations have not yet been resolved.

Of the Binance fine, Marcia Wagner, the founder and managing partner of Wagner Law Group, says, “I do not believe that the amount of the fine, per se, will have an effect upon a plan fiduciary’s decision whether to include or possibly remove or reduce the level of crypto assets in some form on its investment platform, but the fact of the SEC action against Binance, as well as other recent events such as the fraudulent activities of FTX, would clearly be a factor a plan fiduciary would need to take into account as part of its due diligence in determining the prudence of such an investment.”

She added that, “since the Department of Labor guidance regarding cryptocurrency, in my experience, clients have not shown an interest in including crypto assets on their investment platform, if for no other reason than the litigation risk if a crypto asset fund on a plan’s investment platform went sideways. That litigation risk is now obviously heightened.”

According to the Department of Justice, Binance pleaded guilty to a wide range of money laundering, violating sanctions and unlicensed money transmitting as part of its settlement.

The fines break down into two parts: one for about $3.4 billion, issued by the U.S. Financial Crimes Enforcement Network for money-laundering violations, and another for $969 million, issued by the Office of Foreign Asset Control, for more than 1.5 million individual violations of U.S. sanctions policy.

According to the settlement reached with the OFAC, though Binance was fined $968 million, the maximum statutory penalty for its alleged sanctions-related offenses was actually $592 billion. OFAC found that Binance’s violations “were egregious and were not voluntarily self-disclosed.” These violations took place from August 2017 through October 2022.

Most of the trading volume, or about $600 million, involved transactions with Iranian persons. The rest of the volume included people in Syria, North Korea, Cuba and Russian-occupied territories of Ukraine, including Crimea, according to the OFAC.

The OFAC found that Binance encouraged U.S. users to use virtual private networks or to provide foreign passports, if they were multinationals, as a way to maintain the appearance of compliance with U.S. law. This practice, according to the OFAC, was endorsed and pushed by Binance’s then-chief compliance officer.

According to FinCEN’s order, the CCO wrote once to another employee at Binance, “We try to ask our US users to use VPN / or ask them to provide (if [they] are an entity) non-US documents / On the surface we cannot be seen to have US users but in reality, we should get them through other creative means.”

Binance consented to the appointment of an independent compliance monitor from the OFAC for five years. The Treasury Department also imposed a $150 million suspended fine against Binance that will be levied if Binance does not comply with the Treasury Department’s compliance program.

A Treasury Department release stated that “Binance was required to report suspicious transactions to FinCEN through suspicious activity reports (SARs). FinCEN’s investigation revealed that Binance’s former Chief Compliance Officer told personnel that the CEO’s policy was to not report such activity, and Binance never filed a single SAR with FinCEN.”

The statement continued, “Binance willfully failed to report well over 100,000 suspicious transactions that it processed as a result of its deficient controls, including transactions involving terrorist organizations, ransomware, child sexual exploitation material, frauds, and scams.”

The OFAC noted in its order that one employee of Binance noted in business communications that effectively blocking IPs for high-risk jurisdictions would be necessary to work with institutional and other large investors.

IRS Proposes Part-Time Eligibility Rules per SECURE Legislation

Plan sponsors now have IRS guidance on what part-time workers are eligible for plans, though a comment period and finalization are still ahead.

The Internal Revenue Service published a rule proposal on November 24 that would clarify the part-time eligibility requirements in the Setting Every Community Up for Retirement Enhancement Act of 2019 and the SECURE 2.0 Act of 2022.

The first SECURE Act legislated that part-time employees cannot be excluded from 401(k) plans if they worked for at least 500 hours in three consecutive 12-month periods.

Never miss a story — sign up for PLANSPONSOR newsletters to keep up on the latest retirement plan benefits news.

David Ashner, an ERISA and tax attorney with the Groom Law Group, says that per the text of the SECURE Act, this provision came into effect on January 1, 2021, which means that as of January 1, 2024, employees who have served 500 or more hours each year in the meantime must be enrolled in plans unless they are disqualified for another reason.

SECURE 2.0, on the other hand, reduced the 500-hour requirement to two consecutive 12-month periods, rather than three, and took effect on January 1, 2023. This means that employees can become eligible under SECURE 2.0 starting on January 1, 2025. SECURE 2.0 also applies to 403(b) as well as 401(k) plans.

Vesting

According to the rules, employees can also earn vesting credits for employer contributions using the same logic. In other words, if a part-timer works at least 500 hours for a year and then becomes full-time for a year, or vice versa, an employer with a two-year vesting schedule must credit the worker for both years.

As Ashner explains, if the employer does offer contributions “and there’s a vesting schedule, an LTPT employee gets a year of vesting if they work 500 hours in a 12-month period. They can’t be required to work 1,000 for vesting purposes.”

Exemptions Still Good

Ashner explains that DC plan eligibility conditions based on employer classifications are still valid under the proposal, provided they are not merely a proxy to exclude participants based on age or service. For example, a class exemption for intern employees or for a branch of a business based in a college town—which effectively removes part-time or young adult participants by proxy—may be challenged by the IRS.

An eligibility condition may not have “the effect of imposing an age or service requirement,” says Ashner.

The comment period for the proposal runs until January 26, and there will be a public hearing on March 15. The proposal will be finalized some time after.

Ashner says the statutory requirement under the first SECURE Act is effective on January 1, 2024. He adds that “the proposed regulation is not technically effective; the regulation will need to be finalized after notice and comment before it can be made effective. But the proposed regulation reflects how the IRS is likely to interpret the statute (subject to any changes in the final rule), so plans should pay attention to the guidance.”

«