Brief Case

29 C.F.R. § 4211.22

Requests for PBGC approval.
CFR 2003 annual edition (revised as of 2003-07-01) · superseded Jul 1, 2004
Back to current
Historical text in effect Jul 1, 1997 through Jun 30, 2004. View current · Compare with current
(a) General. A plan shall submit a request for approval of an alternative allocation method or modification to an allocation method to the PBGC in accordance with the requirements of this section as soon as practicable after the adoption of the amendment.
(b) Who shall submit. The plan sponsor, or a duly authorized representative acting on behalf of the plan sponsor, shall sign the request.
(c) Where to submit. The plan shall submit the request by first class mail or courier service to Reports Processing, Insurance Operations Department, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005-4026, or by hand to the above address.
(d) Content. Each request shall contain the following information:
(1) The name, address and telephone number of the plan sponsor, and of the duly authorized representative, if any, of the plan sponsor.
(2) The name of the plan.
(3) The nine-digit Employer Identification Number (EIN) that the Internal Revenue Service assigned to the plan sponsor and the three-digit Plan Identification Number (PIN) that the plan sponsor assigned to the plan, and, if different, also the EIN-PIN that the plan last filed with the PBGC. If the plan has no EIN-PIN, the request shall so indicate.
(4) The date the amendment was adopted.
(5) A copy of the amendment, setting forth the full text of the alternative allocation method or modification.
(6) The allocation method that the plan currently uses and a copy of the plan amendment (if any) that adopted the method.
(7) A statement certifying that notice of the adoption of the amendment has been given to all employers that have an obligation to contribute under the plan and to all employee organizations that represent employees covered by the plan.
(e) Additional information. In addition to the information listed in paragraph (d) of this section, the PBGC may require the plan sponsor to submit any other information that the PBGC determines is necessary for the review of an alternative allocation method or modification to an allocation method.
Source credit, amendments & notes

(Approved by the Office of Management and Budget under control number 1212-0035)

29 C.F.R. § 4211.22 — Requests for PBGC approval. · CFR 2003 annual edition (revised as of 2003-07-01) · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4211.22&asof=1997-07-01 · printed Oct 16, 2026
On this page
  • (a) General.
  • (b) Who shall submit.
  • (c) Where to submit.
  • (d) Content.
  • (e) (e) Additional information. In addition to the information …
Implements
ERISA § 4211 (29 U.S.C. § 1391) Methods for computing withdrawal liability
Guidance addressing this section

No documents are primarily about this section.

Also cited in 2 other documents
PBGC
Final Rules
  • 90 FR 39320 Aug 15, 2025 — Miscellaneous Corrections, Clarifications, and Improvements
Proposed Rules
  • 90 FR 6894Proposed Jan 21, 2025 — Miscellaneous Corrections, Clarifications, and Improvements Comments due Mar 24, 2025

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, 2004CFR 2003 annual edition (revised as of 2003-07-01) run 127View
Jul 1, 2004Aug 14, 2025eCFR amendment effective 2025-09-15 run 290 FR 39328, Aug. 15, 2025View · Redline (sign in)
Aug 15, 2025Sep 14, 2025eCFR amendment effective 2025-08-15 run 2668 FR 61355, Oct. 28, 2003View · Redline (sign in)
Sep 15, 2025currenteCFR amendment effective 2025-09-15 run 2690 FR 39328, Aug. 15, 2025View · Redline (sign in)
Provision-level history (blame)