You can cut corners in business. You can play fast and loose with your vendor contracts. You can even get away with sloppy recordkeeping\u2014at least for a while. But when you mess with employee 401(k) contributions, you\u2019re not playing games anymore\u2014you\u2019re playing with fire. And in Micone v. iProcess Online, Inc., the fire finally burned everything down.<\/p>\n
In a brutal but unsurprising decision out of the District of Maryland, the Court ruled in favor of the Department of Labor (DOL), after the employer, not only the plan sponsor but also the plan administrator\u2014ghosted the case completely. No response, no defense, no apology. Just silence. That\u2019s not a strategy; that\u2019s a confession.<\/p>\n
What Went Wrong\u2014And How It All Fell Apart<\/p>\n
According to the DOL, the fiduciaries at iProcess Online failed in the most fundamental way: they didn\u2019t deposit participant contributions into the 401(k) trust. Instead, they commingled those funds, over $175,000 withheld from employee paychecks across seven years\u2014with the company\u2019s general assets. In plain English? They treated employees\u2019 retirement money like a piggy bank for operating expenses.<\/p>\n
That\u2019s not just bad practice, it\u2019s a textbook breach of fiduciary duty under ERISA. Participant contributions become plan assets as soon as they can be \u201creasonably segregated\u201d from employer funds. The law is crystal clear. You don\u2019t borrow against it. You don\u2019t delay. You don\u2019t \u201cfloat\u201d the money for other business needs. You deposit it. Promptly. Period.<\/p>\n
But that\u2019s not all. iProcess also failed to make required employer matching contributions and didn\u2019t process participant distribution requests in a timely manner. The company\u2019s negligence was so egregious that the Court not only ruled in the DOL\u2019s favor\u2014it appointed an independent fiduciary to clean up the mess, to be paid out of the pockets of the very fiduciaries who made it.<\/p>\n
Oh, and did I mention the company officer had already been convicted of embezzlement and was staring down additional lawsuits from plan participants? The whole story reads like a fiduciary horror show.<\/p>\n
Joint and Several Liability: The Final Nail<\/p>\n
The Court didn\u2019t just slap the company on the wrist and walk away. It imposed joint and several liability on the fiduciaries for more than $100,000 in remaining damages\u2014money that must be paid within 60 days. That means each fiduciary is on the hook for the entire amount, not just their \u201cshare.\u201d There\u2019s no safe harbor here. No ducking responsibility. And to ensure the safety of other retirement plans, the Court barred the individuals involved from serving in any ERISA fiduciary capacity going forward.<\/p>\n
That\u2019s not just accountability, it\u2019s professional exile.<\/p>\n
The Message for Plan Sponsors: Pay Attention or Pay the Price<\/p>\n
If you\u2019re a business owner, a CFO, an HR manager, or anyone with fiduciary responsibility over a retirement plan\u2014this case should give you chills. Because the story here isn\u2019t just about one company\u2019s failure. It\u2019s about what happens when fiduciary oversight breaks down entirely.<\/p>\n
The DOL is watching. Participants are empowered. And when things go wrong, the consequences are swift and severe.<\/p>\n
Here\u2019s what this case reminds us:<\/p>\n
1. Participant contributions are sacred. Once that money comes out of an employee\u2019s paycheck, it\u2019s no longer yours. Delay in depositing it into the plan is not a harmless administrative hiccup, it\u2019s a potential fiduciary breach.<\/p>\n
2. Commingling plan assets is never acceptable. This isn\u2019t a gray area. It\u2019s black-letter law. Your business accounts and the plan\u2019s accounts are two different worlds. Don\u2019t cross the streams.<\/p>\n
3. Fiduciary responsibility is personal. You can\u2019t hide behind your company\u2019s logo. If you serve as a fiduciary and the plan suffers because of your breach, you\u2019re on the hook, personally.<\/p>\n
4. Ignoring the problem doesn\u2019t make it go away. iProcess didn\u2019t show up to court. The Court showed up anyway, with a judgment, with penalties, and with a permanent ban from ERISA service.<\/p>\n
Don\u2019t Be a Micone<\/p>\n
I\u2019ve said it before and I\u2019ll say it again: your 401(k) plan isn\u2019t just a perk\u2014it\u2019s a fiduciary minefield. You don\u2019t have to be perfect, but you do have to take your responsibilities seriously. That means timely deposits. Clear documentation. Active oversight. And when in doubt? Ask for help before the DOL shows up with a lawsuit and a court-appointed fiduciary.<\/p>\n
Because once you lose the trust of your employees\u2014and your grip on compliance\u2014it\u2019s not just your retirement plan that\u2019s in trouble. It\u2019s your reputation, your wallet, and in some cases, your freedom.<\/p>\n
Don\u2019t be Micone. Be the fiduciary your employees deserve.<\/p>\n
<\/span><\/p>","protected":false},"excerpt":{"rendered":" You can cut corners in business. You can play fast and loose with your vendor contracts. You can even get away with sloppy recordkeeping\u2014at least for a while. But when you mess with employee 401(k) contributions, you\u2019re not playing games … Continue reading