Brief Case

29 C.F.R. § 4211.31

Allocation of unfunded vested benefits following the merger of plans.
eCFR amendment effective 2023-11-07 · superseded Dec 7, 2023 · last amended by 86 FR 1275, Jan. 8, 2021
Back to current
Historical text in effect Nov 7, 2023 through Dec 6, 2023. View current · Compare with current
Link to an amendment published at 88 FR 76664, Nov. 7, 2023.
(a) General rule. Except as provided in paragraphs (b) through (d) of this section, when two or more multiemployer plans merge, the merged plan shall adopt one of the statutory allocation methods, in accordance with subpart B of this part, or one of the allocation methods prescribed in §§ 4211.32 through 4211.35, and the method adopted shall apply to all employer withdrawals occurring after the initial plan year. Alternatively, a merged plan may adopt its own allocation method in accordance with subpart C of this part. If a merged plan fails to adopt an allocation method pursuant to this subpart or subpart B or C, it shall use the presumptive allocation method prescribed in § 4211.32. In addition, a merged plan may adopt any of the modifications prescribed in § 4211.36 or in subpart B of this part.
(b) Construction plans. Except as provided in the next sentence, a merged plan that primarily covers employees in the building and construction industry shall use the presumptive allocation method prescribed in § 4211.32. However, the plan may, with respect to employers that are not construction industry employers within the meaning of section 4203(b)(1)(A) of ERISA, adopt, by amendment, one of the alternative methods prescribed in §§ 4211.33 through 4211.35 or any other allocation method. Any such amendment shall be adopted in accordance with subpart C of this part. A construction plan may, without the PBGC's approval, adopt by amendment any of the modifications set forth in § 4211.36 or any of the modifications to the statutory presumptive method subpart B of this part.
(c) Section 404(c) plans. A merged plan that is a continuation of a plan described in section 404(c) of the Code shall use the rolling-5 allocation method prescribed in § 4211.34, unless the plan, by amendment, adopts an alternative method. The plan may adopt one of the statutory allocation methods or one of the allocation methods set forth in §§ 4211.32 through 4211.35 without PBGC approval; adoption of any other allocation method is subject to PBGC approval under subpart B of this plan. The plan may, without the PBGC's approval, adopt by amendment any of the modifications set forth in § 4211.36 or in subpart B of this part.
(d) Withdrawals before the end of the initial plan year. For employer withdrawals after the effective date of a merger and prior to the end of the initial plan year, the amount of unfunded vested benefits allocable to a withdrawing employer shall be determined in accordance with § 4211.37.
Source credit, amendments & notes

[61 FR 34097, July 1, 1996, as amended at 86 FR 1275, Jan. 8, 2021]

29 C.F.R. § 4211.31 — Allocation of unfunded vested benefits following the merger of plans. · eCFR amendment effective 2023-11-07 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4211.31&asof=2023-11-07 · printed Oct 16, 2026
On this page
  • (a) General rule.
  • (b) Construction plans.
  • (c) Section 404(c) plans.
  • (d) Withdrawals before the end of the initial plan year.
Implements
ERISA § 4211 (29 U.S.C. § 1391) Methods for computing withdrawal liability
Guidance addressing this section

No documents are primarily about this section.

Also cited in 3 other documents
PBGC
Final Rules
  • 88 FR 76660 Nov 7, 2023 — Technical Amendments: Special Financial Assistance Withdrawal Liability Condition; SECURE 2.0 Act; and Other Updates (b)
  • 86 FR 1256 Jan 8, 2021 — Methods for Computing Withdrawal Liability, Multiemployer Pension Reform Act of 2014
Proposed Rules
  • 84 FR 2075Proposed Feb 6, 2019 — Methods for Computing Withdrawal Liability, Multiemployer Pension Reform Act of 2014 Comments due Apr 8, 2019

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, 1997Jan 7, 2021eCFR amendment effective 2017-01-01 run 26View
Jan 8, 2021Feb 7, 2021eCFR amendment effective 2021-01-08 run 26View · Redline (sign in)
Feb 8, 2021Nov 6, 2023eCFR amendment effective 2021-02-08 run 2686 FR 1275, Jan. 8, 2021View · Redline (sign in)
Nov 7, 2023Dec 6, 2023eCFR amendment effective 2023-11-07 run 2686 FR 1275, Jan. 8, 2021View · Redline (sign in)
Dec 7, 2023currenteCFR amendment effective 2023-12-07 run 288 FR 76664, Nov. 7, 2023View · Redline (sign in)
Provision-level history (blame)