Brief Case
Pension Resource

29 C.F.R. § 4044.4

Violations.
eCFR editorial change effective 2017-01-01 · current
PrintCompare datesAsk AI about this sectionOfficial source ↗
Back to current
The earliest stored text of this section is effective Jul 1, 1997. Showing that version.
(a) General. A plan administrator violates ERISA if plan assets are allocated or distributed upon plan termination in a manner other than that prescribed in section 4044 of ERISA and this subpart, except as may be required to prevent disqualification of the plan under the Code and regulations thereunder.
(b) Distributions in anticipation of termination. A distribution, transfer, or allocation of assets to a participant or to an insurance company for the benefit of a participant, made in anticipation of plan termination, is considered to be an allocation of plan assets upon termination, and is covered by paragraph (a) of this section. In determining whether a distribution, transfer, or allocation of assets has been made in anticipation of plan termination PBGC will consider all of the facts and circumstances including—
(1) Any change in funding or operation procedures;
(2) Past practice with regard to employee requests for forms of distribution;
(3) Whether the distribution is consistent with plan provisions; and
(4) Whether an annuity contract that provides for a cutback based on the guarantee limits in subpart B of part 4022 of this chapter could have been purchased from an insurance company.
29 C.F.R. § 4044.4 — Violations. · eCFR editorial change effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4044.4&asof=1995-01-04 · printed Oct 16, 2026
On this page
  • (a) General.
  • (b) Distributions in anticipation of termination.
Implements
ERISA § 4044 (29 U.S.C. § 1344) Allocation of assets
Cited by (code & regs)
Guidance addressing this section

No documents are primarily about this section.

Also cited in 1 other documents
PBGC
Final Rules

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, 1997currenteCFR editorial change effective 2017-01-01 run 2View
Provision-level history (blame)