Brief Case

29 C.F.R. § 4231.5

Valuation requirement.
CFR 1997 annual edition (revised as of 1997-07-01) · superseded Jul 1, 1998
Back to current
Historical text in effect Jul 1, 1997 through Jun 30, 1998. View current · Compare with current
(a) Mergers and non-significant transfers. A merger or a transfer that is not significant (“non-significant transfer”) satisfies section 4231(b)(4) of ERISA and § 4231.3(a)(2) (requiring an actuarial valuation) if an actuarial valuation has been performed for each plan involved in the merger or transfer, based on the assets and liabilities of the plan as of a date not more than three years before the date on which the notice of the merger or transfer is filed.
(b) Significant transfers. A significant transfer satisfies section 4231(b)(4) of ERISA and § 4231.3(a)(2) if an actuarial valuation has been performed for each plan involved in the transfer, based on the assets and liabilities of the plan as of a date not earlier than the first day of the last plan year ending before the proposed effective date of the transfer. The valuation shall separately identify assets, contributions and liabilities being transferred, and shall be based on the actuarial assumptions and methods that are expected to be used for the first plan year beginning after the transfer.
29 C.F.R. § 4231.5 — Valuation requirement. · CFR 1997 annual edition (revised as of 1997-07-01) · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4231.5&asof=1997-07-01 · printed Oct 16, 2026
On this page
  • (a) Mergers and non-significant transfers.
  • (b) Significant transfers.
Implements
ERISA § 4231 (29 U.S.C. § 1411) Mergers and transfers between multiemployer plans
Cited by (code & regs)
Guidance addressing this section

No documents are primarily about this section.

Also cited in 2 other documents
PBGC
Final Rules
  • 83 FR 46642 Sep 14, 2018 — Mergers and Transfers Between Multiemployer Plans (a)(b)
Proposed Rules
  • 81 FR 36229Proposed Jun 6, 2016 — Mergers and Transfers Between Multiemployer Plans Comments due Aug 5, 2016

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, 1997Jun 30, 1998CFR 1997 annual edition (revised as of 1997-07-01) run 127View
Jul 1, 1998Oct 14, 2018eCFR amendment effective 2017-01-01 run 26View · Redline (sign in)
Oct 15, 2018currenteCFR amendment effective 2018-10-15 run 2View · Redline (sign in)
Provision-level history (blame)