Brief Case

29 C.F.R. § 4041.3

Computation of time; filing and issuance rules.
eCFR editorial change effective 2017-01-01 · current · last amended by 68 FR 61353, Oct. 28, 2003
Amended effective Jul 1, 2004 by 68 FR 61353, Oct. 28, 2003. See what changed
(a) Computation of time. The PBGC applies the rules in subpart D of part 4000 of this chapter to compute any time period under this part. A proposed termination date may be any day, including a weekend or Federal holiday.
(b) Filing with the PBGC
(1) Method and date of filing. The PBGC applies the rules in subpart A of part 4000 of this chapter to determine permissible methods of filing with the PBGC under this part. The PBGC applies the rules in subpart C of part 4000 of this chapter to determine the date that a submission under this part was filed with the PBGC.
(2) Where to file. See § 4000.4 of this chapter for information on where to file.
(c) Issuance to third parties. The following rules apply to affected parties (other than the PBGC). For purposes of this paragraph (c), a person entitled to notice under the spin-off/termination transaction rules of § 4041.23(c) or § 4041.24(f) is treated as an affected party.
(1) Method and date of issuance. The PBGC applies the rules in subpart B of part 4000 of this chapter to determine permissible methods of issuance under this part. The PBGC applies the rules in subpart C of part 4000 of this chapter to determine the date that an issuance under this part was provided.
(2) Omission of affected parties. The failure to issue any notice to an affected party (other than any employee organization) within the specified time period will not cause the notice to be untimely if—
(i) After-discovered affected parties. The plan administrator could not reasonably have been expected to know of the affected party, and issues the notice promptly after discovering the affected party; or
(ii) Unlocated participants. The plan administrator could not locate the affected party after making reasonable efforts, and issues the notice promptly in the event the affected party is located.
(3) Deceased participants. In the case of a deceased participant, the plan administrator need not issue a notice to the participant's estate if the estate is not entitled to a distribution.
(4) Form of notices to affected parties. All notices to affected parties must be readable and written in a manner calculated to be understood by the average plan participant. The plan administrator may provide additional information with a notice only if the information is not misleading.
(5) Foreign languages. The plan administrator of a plan that (as of the proposed termination date) covers the numbers or percentages in § 2520.104b-10(e) of this title of participants literate only in the same non-English language must, for any notice to affected parties—
(i) Include a prominent legend in that common non-English language advising them how to obtain assistance in understanding the notice; or
(ii) Provide the notice in that common non-English language to those affected parties literate only in that language.
Source credit, amendments & notes

[62 FR 60428, Nov. 7, 1997, as amended at 68 FR 61353, Oct. 28, 2003]

29 C.F.R. § 4041.3 — Computation of time; filing and issuance rules. · eCFR editorial change effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4041.3 · printed Oct 16, 2026
On this page
  • (a) Computation of time.
  • (b) Filing with the PBGC
  • (c) Issuance to third parties.
Implements
ERISA § 4041 (29 U.S.C. § 1341) Termination of single-employer plans
Guidance addressing this section

No documents are primarily about this section.

Also cited in 1 other documents
IRS / Treasury
Proposed Rules
  • 89 FR 4215Proposed Jan 23, 2024 — Request for Information-SECURE 2.0 Section 319-Effectiveness of Reporting and Disclosure Requirements Comments due Apr 22, 2024 (c)(4)(c)(5)

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, 1998Jun 30, 2004CFR 2003 annual edition (revised as of 2003-07-01) run 127View · Redline (sign in)
Jul 1, 2004currenteCFR editorial change effective 2017-01-01 run 268 FR 61353, Oct. 28, 2003View · Redline (sign in)
Provision-level history (blame)