Skip Page Banner  
About This Blog

Bloomberg BNA's Pension & Benefits Blog is a special resource offered by Bloomberg BNA to provide commentary and insight on news and trends reported in our publications: Pension & Benefits Daily, Pension & Benefits Reporter, and the Benefits Practice Resource Center. The authors of the blog are members of our Benefits Practice Resource Advisory Board and members of staff (who contribute summaries of some of their recent stories). 

The ideas presented here are those of individuals, and Bloomberg BNA bears no responsibility for the appropriateness or accuracy of the communications between group members. We reserve the right not to post comments that are abusive or otherwise objectionable.

Communications regarding the Pension & Benefits Blog may be directed to Dana Domone via e-mail to

Pension & Benefits

Thursday, November 29, 2012

PBGC Provides Some Relief for Plan Sponsors in its Enforcement of ERISA Section 4062(e)


Since ERISA was first enacted in 1974, it has included a provision, Section 4062(e), that generally applies when the cessation of operations at a facility results in separation from employment of more than 20 percent of active employees covered by a pension plan.  When a 4062(e) event occurs, the plan administrator is required to notify the Pension Benefit Guaranty Corporation, and the employer is required to provide a bond or escrow for a five-year period following the cessation of operations.  If the plan does not terminate within that period, the escrowed amount is returned without interest or the bond is canceled.  In practice, PBGC has typically used Section 4062(e) to extract additional cash contributions or other value for the plan instead of a bond or escrow.
From time to time in the past, PBGC has been aggressive in interpreting and enforcing Section 4062(e).  PBGC recently announced, however, a new “4062(e) enforcement pilot program” that should provide some relief to plan sponsors.  Under the pilot program, PBGC would no longer seek to enforce 4062(e) against plan sponsors that are financially sound or whose pension plans cover not more than 100 participants.  PBGC estimates that, as a result of this new policy, 92 percent of plan sponsors will not face 4062(e) enforcement efforts.  This represents a significant departure from the agency’s enforcement efforts following the release of its proposed 4062(e) regulation in 2010.

Under the announced enforcement policy, PBGC will use established business standards to determine a company's creditworthiness and financial strength.  These standards include credit ratings, credit scores, indebtedness, liquidity, and profitability.  Where there are no indicators of financial weakness or other risks, PBGC says, it will take no enforcement action.

PBGC notes, however, that sponsors must still report all events triggering 4062(e) (using a 2010 proposed PBGC regulation to determine whether an event has occurred).  After notice is given, PBGC will then assess whether the reported case is exempt from enforcement because the plan has no more than 100 participants or the sponsor is financially sound.  

I understand that sponsors that have entered into 4062(e) agreements with PBGC prior to this announcement may petition the agency to amend or modify these agreements based on the pilot program, and that PBGC also will be contacting sponsors that appear to qualify for a suspension of their obligations under a 4062(e) agreement.  If these companies are judged financially sound, PBGC will offer to suspend their agreements.  If any company ceases to be financially sound during the statutory period, however, PBGC will again seek to enforce Section 4062(e).  I understand that PBGC is rescinding prior 4062(e) agreements where the affected plan had no more than 100 participants.  

PBGC notes that the proposed regulation and the pilot program itself are subject to change based on the agency's experience.  PBGC's news release is at  PBGC's Q&A is at

View our selection of Pension & Benefits products.

You must Sign In or Register to post a comment.

Comments (0)