"When ROBS Goes Wrong: The Failure Modes, the IRS Record, and How to Avoid Both"

The ROBS industry does not like talking about failure. This page is going to.

Search for honest information about what happens when a ROBS arrangement goes badly, and you will find two kinds of content: provider marketing that waves at "compliance" in a reassuring tone, and forum threads from founders trying to reconstruct what went wrong after the fact. Almost nothing in between. That gap is bad for founders, and we think it is bad for the structure's reputation, because the actual record is more specific and more avoidable than the vague unease suggests.

Through our Nexus product, we provide ROBS administration. That is the disclosure, and it is also the reason we want this page to exist: every failure described below is something a founder can see coming, and should avoid or correct as soon as possible. Read this before you commit capital, whoever you end up working with.

What the IRS Found

ROBS arrangements have been in use since the 1970s and use a statutory exemption that allows a retirement plan to purchase qualifying employer securities.

In 2009, the IRS's Employee Plans division opened a dedicated compliance project on ROBS arrangements. The findings are public, and they are worth reading in their original form on the IRS's own page. Summarized honestly:

Many of the sampled businesses were failing. In the IRS's words, many ROBS businesses in its sample "either failed or were on the road to failure," with high rates of bankruptcy, liens, and corporate dissolutions. In some cases, savings were depleted before the business ever offered its product or service.

The paperwork had stopped. Many sponsors failed to file the required annual returns for 401(k) plans, including Form 5500. Some ROBS providers had incorrectly told clients that filing exemptions applied to their arrangement when they did not.

The structures had drifted. The project identified plans amended to shut out other employees after receiving favorable determination letters, asset valuation problems, provider fee issues, and rollovers processed without the required Form 1099-R.

And yet the IRS did not ban ROBS. ROBS is a permissible arrangement when properly structured and operated. The IRS drew a line between the structure and the execution. It flagged the way many arrangements were sold, documented, and administered, with too many plans left to drift out of compliance. Many founders had been sold a transaction and left alone with a structure they didn't understand.

That last sentence is the story. Read the findings again and notice that it was often the administration that failed. It doesn't have to.

The Three Failure Modes

"ROBS went wrong" blurs together three different events with three different causes and three different consequences.

1. The Business Fails

This is the failure mode no provider can underwrite away, as start-ups are typically risky and subject to a high failure rate. ROBS converts a diversified retirement balance into a concentrated position in one private company. If the company fails, the 401(k) plan's shares lose most or all their value.

Two things are worth knowing about this mode.

First, it is not a compliance event. A properly administered ROBS structure whose business fails unwinds in an orderly way: the corporation dissolves properly, the 401(k) plan files its final Form 5500, and any remaining plan assets are rolled over or distributed according to plan terms and tax rules. Failure hurts. It does not, by itself, trigger taxes or penalties.

Second, the IRS's grim sample says something about that era's selling practices as much as about the risks inherent to starting up a business. The compliance project examined arrangements from a period when ROBS was heavily promoted as a transaction, often to first-time business owners buying into ventures with thin economics, with little screening and less follow-through. The structure cannot fix a bad business. Nothing can. Which is why the right eligibility question is not only "do you have $50,000 in a 401(k)" but "should this business exist in the current economy, and are you the right person to run it."

2. The Administration Stops

This is the failure mode the IRS findings are mostly about, and it is the one that turns a struggling business into a tax catastrophe.

A ROBS structure carries recurring obligations for as long as the plan owns stock: the Form 5500 filing, required testing, the ERISA fidelity bond, an annual valuation of the 401(k) plan's shares, corporate good standing, 401(k) plan documents kept current with required amendments. They recur, every year, regardless.

When they stop happening, the plan drifts out of tax qualification. And a tax disqualified plan is the catastrophe scenario: the original rollover can be retroactively treated as a taxable distribution, with income tax and early-withdrawal penalties assessed on money that was spent on the business years ago. The founder ends up owing tax on capital they no longer have.

Notice the pattern in the IRS findings: returns not filed, valuations not performed, amendments not adopted. It often happens by omission, one skipped year at a time, usually starting the moment the setup provider's engagement ends and the founder discovers that "ongoing administration" was not actually in the package. This failure mode is avoidable.

3. The Founder Self-Deals

The third mode is behavioral. The plan and the people who run the company are disqualified persons with respect to each other, and the law strictly limits dealings between and among them.

The recurring patterns are consistent: corporate funds used for personal expenses, unreasonable or undocumented compensation to employees, company money lent to the founder, and non-arm’s-length asset transfers between the founder and the company. Each of these is a prohibited transaction, and prohibited transactions carry their own excise taxes and, in serious cases, threaten the 401(k) plan's tax qualification. The map is in our prohibited transactions guide.

Administration isn't Optional

One structural feature shows up in many bad outcomes: nobody owned and properly administered the structure after funding.

The transaction-shaped version of ROBS, sold hard in the 2000s, often ended at the wire transfer; setup fee collected, corporation formed, and rollover executed, and after that, good luck. Every recurring obligation then defaulted to a founder who was busy running a new business and had likely never heard of an ERISA fidelity bond or other requirements related to a 401(k) plan. The IRS findings read exactly like what that arrangement would predict.

The durable version of ROBS treats funding as the midpoint, not the end. Someone, with their name on it, is responsible for the 5500 every year. Someone commits to doing the stock valuation. Someone is assigned the ERISA bond renewal, naming the registered agent and running the nondiscrimination testing. Know whether that someone is your provider or yourself.

Nexus 401(k) was built administration-first: the recurring obligations sit inside the ongoing services agreement, and the scope is published on our pricing page so you can verify the claims. Different providers structure administration differently, and some founders decide to self-administer. Ask the right questions. The stakes are too high not to.

This information is presented for educational purposes only and should not be construed as tax, legal, or investment advice. These rules are highly fact-specific. Tax rules and IRS guidance may change, and tax treatment depends on individual circumstances. Whenever making an investment decision, please consult with independent legal, tax, and accounting professionals.