Bay Area Laundry
Does the statute of limitations for a multiemployer pension plan to bring suit to collect withdrawal liability under ERISA begin to run when the employer withdraws from the plan, or when the plan assesses the withdrawal liability and demands payment?
The Decision
9-0 decision · Opinion by Clarence Thomas
Majority Opinion— Clarence Thomasconcurring ↓
The Supreme Court reversed the Ninth Circuit and ruled in favor of the pension trust fund. In a unanimous decision authored by Justice Clarence Thomas, the Court held that the statute of limitations for a plan's action to collect withdrawal liability begins to run when the plan completes its assessment and demands payment — not when the employer withdraws from the plan.
The Court's reasoning focused closely on the statutory framework established by the MPPAA. Under that framework, when an employer withdraws from a multiemployer pension plan, the plan must determine the amount of withdrawal liability, notify the employer, and demand payment according to a schedule. Until the plan takes these steps, the employer has no obligation to make any specific payments. Because the employer's concrete payment obligation arises only upon assessment and demand, the Court concluded that the plan's cause of action to collect those payments likewise arises only at that point. Under traditional principles governing statutes of limitations, the clock starts when the cause of action is complete — and here, it is not complete until the plan acts.
The Court acknowledged the concern raised by Ferbar and others that tying the limitations period to the plan's own assessment could, in theory, allow a plan to delay indefinitely. However, the Court found this concern largely theoretical. The statutory framework gives plans powerful financial incentives to assess withdrawal liability promptly: a plan cannot begin collecting any payments until it completes the assessment process. Every day of delay in assessment is a day of lost revenue for the plan, which must continue to fund its obligations to retirees from other sources. This built-in incentive, the Court concluded, serves as a natural practical check against abusive delay, even without starting the limitations clock at the moment of withdrawal.
The Court also noted that reading the statute to start the limitations period at withdrawal would create serious practical problems. Plans often need considerable time to gather financial data and perform the complex actuarial calculations required to determine withdrawal liability. Starting the clock at withdrawal could force plans into premature litigation or risk losing their claims entirely before they even know how much is owed.
Concurring Opinions
The decision was unanimous with no separately filed concurring or dissenting opinions, reflecting broad agreement among the Justices on how the MPPAA's statutory framework governs the timing of withdrawal liability claims.
Background & Facts
This case arose from the complex world of multiemployer pension plans — retirement funds jointly maintained by multiple employers, often in the same industry, under collective bargaining agreements. When an employer stops participating in such a plan (known as 'withdrawal'), federal law — specifically the Multiemployer Pension Plan Amendments Act of 1980 (MPPAA), which amended ERISA — imposes 'withdrawal liability' on that employer. This liability represents the employer's share of the plan's unfunded obligations to workers and retirees. The plan must calculate the amount owed, notify the employer, and set up a payment schedule.
Bay Area Laundry and Dry Cleaning Pension Trust Fund was a multiemployer pension plan that covered workers in the laundry and dry cleaning industry in the San Francisco Bay Area. Ferbar Corporation of California was an employer that had participated in the plan but later withdrew. After Ferbar's withdrawal, the pension trust fund assessed withdrawal liability against the company and demanded payment. The dispute centered on timing: by the time the plan brought a lawsuit to collect the assessed withdrawal liability, the employer argued that the six-year statute of limitations under ERISA Section 4301(f) had already expired — because, in the employer's view, the clock started ticking the moment Ferbar withdrew from the plan.
The pension fund countered that the statute of limitations should not begin to run until the plan actually assesses the liability and demands payment, because no enforceable obligation to pay specific amounts exists until that point. The lower courts grappled with this timing question, and the Ninth Circuit Court of Appeals sided with the employer, holding that the limitations clock began at the time of withdrawal. This meant the plan's lawsuit was too late.
The Supreme Court agreed to hear the case because the question of when the limitations period begins was critically important to the administration of multiemployer pension plans across the country, and different courts had reached different conclusions on the issue.
The Arguments
The pension trust fund argued that the statute of limitations for collecting withdrawal liability should not begin to run until the plan completes its assessment and demands payment from the withdrawing employer. Until that assessment occurs, the plan has no specific, quantified claim to enforce in court.
- Under the MPPAA statutory framework, an employer's obligation to make specific withdrawal liability payments does not crystallize until the plan calculates the amount owed, notifies the employer, and establishes a payment schedule.
- A cause of action to collect payments cannot exist before the plan demands payment, because there is nothing concrete to collect until assessment is complete.
- The standard rule in federal law is that a statute of limitations begins to run when the plaintiff has a complete and present cause of action — which, in this context, requires assessment and demand.
Ferbar argued that the statute of limitations begins running at the time of the employer's withdrawal from the pension plan, not at the later point when the plan gets around to assessing liability. Starting the clock at assessment would give plans unchecked power to delay indefinitely and revive otherwise stale claims.
- The withdrawal itself is the triggering event that creates the underlying liability, so the limitations period should logically begin at that point.
- Allowing the plan to control when the clock starts by choosing when to assess liability creates an unfair situation where employers face open-ended exposure with no time limit.
- However, even under the plan's interpretation, plans have strong built-in incentives to assess withdrawal liability quickly so they can begin collecting payments, which provides a natural practical limit on delay.