Brief Case
Pension Resource

29 C.F.R. § 4041.49

Verification of plan sufficiency prior to closeout.
eCFR editorial change effective 2017-01-01 · superseded Jun 6, 2024
PrintCompare datesAsk AI about this sectionOfficial source ↗
Back to current
Historical text in effect Jul 1, 1998 through Jun 5, 2024. View current · Compare with current
(a) General rule. Before distributing plan assets pursuant to a closeout under § 4041.50, the plan administrator must verify whether the plan's assets are still sufficient to provide for benefits at the level determined by the PBGC, i.e., guaranteed benefits or benefit liabilities. If the plan administrator finds that the plan is no longer able to provide for benefits at the level determined by the PBGC, then paragraph (b) or (c) of this section, as appropriate, will apply.
(b) Subsequent insufficiency for guaranteed benefits. When a plan administrator finds that a plan is no longer sufficient for guaranteed benefits, the plan administrator must promptly notify the PBGC in writing of that fact and may take no further action to implement the plan termination, pending the PBGC's determination and notice pursuant to paragraph (b)(1) or (b)(2) of this section.
(1) PBGC concurrence with finding. If the PBGC concurs with the plan administrator's finding, the distribution notice will be void, and the PBGC will—
(i) Issue the plan administrator a notice of inability to determine sufficiency in accordance with § 4041.47(b); and
(ii) Require the plan administrator to submit a new valuation, certified to by an enrolled actuary, of the benefit liabilities and guaranteed benefits under the plan, valued in accordance with §§ 4044.41 through 4044.57 of this chapter as of the date of the plan administrator's notice to the PBGC.
(2) PBGC non-concurrence with finding. If the PBGC does not concur with the plan administrator's finding, it will so notify the plan administrator in writing, and the distribution notice will remain in effect.
(c) Subsequent insufficiency for benefit liabilities. When a plan administrator finds that a plan is sufficient for guaranteed benefits but is no longer sufficient for benefit liabilities, the plan administrator must immediately notify the PBGC in writing of this fact, but must continue with the distribution of assets in accordance with § 4041.50.
(d) Finding by PBGC of subsequent insufficiency. In any case in which the PBGC finds on its own initiative that a subsequent insufficiency for guaranteed benefits has occurred, paragraph (b)(1) of this section will apply, except that the guaranteed benefits must be revalued as of the date of the PBGC's finding.
(e) Restrictions upon finding of subsequent insufficiency. When the plan administrator makes the finding described in paragraph (b) of this section or receives notice that the PBGC has made the finding described in paragraph (d) of this section, the plan administrator is (except to the extent the PBGC otherwise directs) subject to the prohibitions in § 4041.42.
29 C.F.R. § 4041.49 — Verification of plan sufficiency prior to closeout. · eCFR editorial change effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4041.49&asof=2009-01-05 · printed Oct 16, 2026
On this page
  • (a) General rule.
  • (b) Subsequent insufficiency for guaranteed benefits.
  • (c) Subsequent insufficiency for benefit liabilities.
  • (d) Finding by PBGC of subsequent insufficiency.
  • (e) Restrictions upon finding of subsequent insufficiency.
Implements
ERISA § 4041 (29 U.S.C. § 1341) Termination of single-employer plans
Cited by (code & regs)
Guidance addressing this section

No documents are primarily about this section.

Also cited in 1 other documents
PBGC
Final Rules
  • 89 FR 48291 Jun 6, 2024 — Valuation Assumptions and Methods

No court rulings in the library cite this provision yet.

No private letter rulings in the library cite this provision yet.

Each row is a version of the text as published by the official source. Code dates are the edition/release point that first reflected the change; regulation dates are eCFR effective dates. The library checks the official sources automatically, so new versions appear here on their own; “run” opens the sync that recorded a version.

EffectiveThroughSourceAmended by
Jul 1, 1998Jun 5, 2024eCFR editorial change effective 2017-01-01 run 26View
Jun 6, 2024Jul 7, 2024eCFR amendment effective 2024-06-06 run 26View · Redline (sign in)
Jul 8, 2024currenteCFR amendment effective 2024-07-08 run 289 FR 48299, June 6, 2024View · Redline (sign in)
Provision-level history (blame)