Brief Case
Pension Resource

29 C.F.R. § 4231.9

Notice of merger or transfer.
CFR 2016 annual edition (revised as of 2016-07-01) · superseded Jan 1, 2017
PrintCompare datesAsk AI about this sectionOfficial source ↗
Back to current
Historical text in effect Jul 1, 1998 through Dec 31, 2016. View current · Compare with current
(a) General. The plan sponsor(s) of one or more plans involved in a merger or transfer, or the duly authorized representative(s) acting on behalf of the plan sponsor(s), may file a request for a determination that the transaction complies with the requirements of section 4231 of ERISA. The request must contain the information described in paragraph (b) or (c) of this section, as applicable.
(1) The place of filing. The request must be delivered to the address set forth in § 4231.8(c).
(2) Single request permitted for all de minimis transactions. Because the plan solvency test for de minimis mergers and transfers is based on the most recent valuation (without adjustment for intervening de minimis transactions), a plan sponsor may submit a single request for a compliance determination covering all de minimis mergers or transfers that occur between one plan valuation and the next. However, the plan sponsor must still notify PBGC of each de minimis merger or transfer separately, in accordance with § 4231.8. The single request for a compliance determination may be filed concurrently with any one of the notices of a de minimis merger or transfer.
(b) Contents of request
(1) General. A request for a compliance determination concerning a merger or transfer that is not de minimis must contain—
(i) A copy of the merger or transfer agreement;
(ii) A summary of the required calculations, including a complete description of assumptions and methods, on which the enrolled actuary based each certification that a plan involved in the merger or transfer satisfied a plan solvency test described in § 4231.6; and
(iii) For each significantly affected plan, other than a plan that is a significantly affected plan only because the merger or transfer involves a plan that has terminated by mass withdrawal under section 4041A(a)(2) of ERISA, copies of all actuarial valuations performed within the 5 years preceding the date of filing the notice required under § 4231.8.
(2) De minimis merger or transfer. A request for a compliance determination concerning a de minimis merger or transfer must contain one of the following statements for each plan that exists after the transaction, certified by an enrolled actuary:
(i) A statement that the plan satisfies one of the plan solvency tests set forth in § 4231.6(a), indicating which test is satisfied.
(ii) A statement of the basis on which the actuary has determined that benefits under the plan are not reasonably expected to be subject to suspension under section 4245 of ERISA, including supporting data or calculations, assumptions and methods.
29 C.F.R. § 4231.9 — Notice of merger or transfer. · CFR 2016 annual edition (revised as of 2016-07-01) · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4231.9&asof=1998-07-01 · printed Oct 16, 2026
On this page
  • (a) General.
  • (b) Contents of request
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 6 other documents
PBGC
Final Rules
Proposed Rules
  • 81 FR 36229Proposed Jun 6, 2016 — Mergers and Transfers Between Multiemployer Plans Comments due Aug 5, 2016 (1)(e)
  • 79 FR 4642Proposed Jan 29, 2014 — Multiemployer Plans; Valuation and Notice Requirements Comments due Mar 31, 2014

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