Brief Case

ERISA § 4231 (29 U.S.C. § 1411)

Mergers and transfers between multiemployer plans
USC 2013 ed., current through 2014-01-16 · superseded Jan 5, 2015 · last amended by Pub. L. 96-364
Back to current
Historical text in effect Jan 4, 1995 through Jan 4, 2015. View current · Compare with current
(a) Authority of plan sponsor Unless otherwise provided in regulations prescribed by the corporation, a plan sponsor may not cause a multiemployer plan to merge with one or more multiemployer plans, or engage in a transfer of assets and liabilities to or from another multiemployer plan, unless such merger or transfer satisfies the requirements of subsection (b) of this section.
(b) Criteria A merger or transfer satisfies the requirements of this section if—
(1) in accordance with regulations of the corporation, the plan sponsor of a multiemployer plan notifies the corporation of a merger with or transfer of plan assets or liabilities to another multiemployer plan at least 120 days before the effective date of the merger or transfer;
(2) no participant's or beneficiary's accrued benefit will be lower immediately after the effective date of the merger or transfer than the benefit immediately before that date;
(3) the benefits of participants and beneficiaries are not reasonably expected to be subject to suspension under section 1426 of this title; and
(4) an actuarial valuation of the assets and liabilities of each of the affected plans has been performed during the plan year preceding the effective date of the merger or transfer, based upon the most recent data available as of the day before the start of that plan year, or other valuation of such assets and liabilities performed under such standards and procedures as the corporation may prescribe by regulation.
(c) Actions not deemed violation of section 1106(a) or (b)(2) of this title The merger of multiemployer plans or the transfer of assets or liabilities between multiemployer plans, shall be deemed not to constitute a violation of the provisions of section 1106(a) of this title or section 1106(b)(2) of this title if the corporation determines that the merger or transfer otherwise satisfies the requirements of this section.
(d) Nature of plan to which liabilities are transferred A plan to which liabilities are transferred under this section is a successor plan for purposes of section 1322a(b)(2)(B) of this title.
Source credit, amendments & notes

(Pub. L. 93–406, title IV, §4231, as added Pub. L. 96–364, title I, §104(2), Sept. 26, 1980, 94 Stat. 1244.)

Effective Date

Part effective Sept. 26, 1980, except as specifically provided, see section 1461(e) of this title.

ERISA § 4231 (29 U.S.C. § 1411) — Mergers and transfers between multiemployer plans · USC 2013 ed., current through 2014-01-16 · https://pensionresource.website/EAMain?content=EAMain.Law&id=usc29-1411&asof=1995-01-04 · printed Oct 17, 2026
On this page
  • (a) Authority of plan sponsor
  • (b) Criteria
  • (c) Actions not deemed violation of section 1106(a) or (b)(2) o…
  • (d) Nature of plan to which liabilities are transferred
Cited by (code & regs)
PBGC Regulations
Guidance addressing this section
PBGC
Final Rules
Proposed Rules
Also cited in 5 other documents
PBGC
Final Rules
  • 87 FR 40968 Jul 8, 2022 — Special Financial Assistance by PBGC (a)(e)(f)
  • 86 FR 36598 Jul 12, 2021 — Special Financial Assistance by PBGC (a)(e)(f)
  • 80 FR 54980 Sep 11, 2015 — Reportable Events and Certain Other Notification Requirements
  • 80 FR 35220 Jun 19, 2015 — Partitions of Eligible Multiemployer Plans
Proposed Rules
  • 78 FR 20039Proposed Apr 3, 2013 — Reportable Events and Certain Other Notification Requirements Comments due Jun 3, 2013

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
Jan 4, 1995Jan 4, 2015USC 2013 ed., current through 2014-01-16 run 13Pub. L. 96-364View
Jan 5, 2015Jan 5, 2017USC 2014 ed., current through 2015-01-05 run 14Pub. L. 113-235View · Redline (sign in)
Jan 6, 2017currentUSC 2024 ed., current through 2025-01-06 run 1Pub. L. 113-235View · Redline (sign in)
Provision-level history (blame)