Brief Case
Pension Resource

29 C.F.R. § 4262.7

Plan information.
eCFR amendment effective 2021-07-12 · superseded Aug 8, 2022
PrintCompare datesAsk AI about this sectionOfficial source ↗
Back to current
Historical text in effect Jul 12, 2021 through Aug 7, 2022. View current · Compare with current
(a) Basic information. An application for special financial assistance must include all of the following information with respect to the plan and amount of special financial assistance requested:
(1) Name of the plan, Employer Identification Number (EIN), and three-digit Plan Number (PN).
(2) Name of the individual filing the application and role of the individual with respect to the plan.
(3) Name, address, email, and telephone number of the plan sponsor and the plan sponsor's authorized representatives, if any.
(4) The total amount of special financial assistance requested.
(b) Eligibility. An application must identify the eligibility requirements in § 4262.3 that the plan satisfies to be eligible for special financial assistance. An application for a plan that is eligible under section 4262(b)(1)(C) of ERISA must include a demonstration to support that the plan meets the eligibility requirements.
(c) Priority group identification. An application must identify any priority group under § 4262.10(d)(2) that the plan is in. An application must include a demonstration to support the plan's inclusion in a priority group, unless the plan is insolvent under section 4245(a) of ERISA, has implemented a suspension of benefits under section 305(e)(9) of ERISA as of March 11, 2021, is in critical and declining status (as defined in section 305(b)(6) of ERISA) and had 350,000 or more participants, or is listed on PBGC's website at www.pbgc.gov as a plan in priority group 6, as defined under § 4262.10(d)(2)(vi).
(d) Plans with a suspension of benefits. If a plan previously suspended benefits under sections 305(e)(9) or 4245(a) of ERISA, its application must include a description of how the plan will reinstate the benefits that were previously suspended and a proposed schedule showing aggregate amount and timing of payments (in accordance with § 4262.15) to participants and beneficiaries under the plan. The proposed schedule should be prepared assuming the effective date for reinstatement is the SFA measurement date and that payments for previously suspended benefits described in § 4262.15(a)(2) are paid or commence on the SFA measurement date. If the plan restored benefits under 26 CFR 1.432(e)(9)-1(e)(3) before the SFA measurement date, the proposed schedule should reflect the amount and timing of payments of restored benefits and the effect of the restoration on the benefits remaining to be reinstated.
(e) Plan documentation. An application must include all of the following plan documentation:
(1) Most recent plan document or restatement of the plan document and all subsequent amendments adopted (if any), including a copy of the executed plan amendment required under § 4262.6(e)(1).
(2) A copy of the proposed plan amendment required under § 4262.6(e)(2) and certification by the plan sponsor that the plan amendment will be timely adopted.
(3) Most recent trust agreement or restatement of the trust agreement and all subsequent adopted amendments (if any).
(4) Most recent IRS determination letter.
(5) Actuarial valuation report completed for the 2018 plan year and each subsequent actuarial valuation report completed before the date the plan's application was filed.
(6) Most recent rehabilitation plan (or funding improvement plan, if applicable), including all subsequent amendments and updates, and the percentage of total contributions received under each schedule of the rehabilitation plan for the most recent plan year available. If the most recent rehabilitation plan does not include historical documentation of rehabilitation plan changes (if any) that occurred in calendar year 2020 and later, these details must be provided in a supplemental document.
(7) Most recent Form 5500 and all schedules and attachments (including the audited financial statement).
(8) Plan actuary's certification of plan status required under section 305(b)(3) of ERISA completed for the 2018 plan year and each subsequent annual certification completed before the date the plan's application was filed, with documentation supporting each certification, which must include the projections and information required in the special financial assistance instructions on PBGC's website at www.pbgc.gov.
(9) Most recent statement for each of the plan's cash and investment accounts.
(10) Most recent plan financial statement (audited, or unaudited if audited is not available).
(11) Bank account and other information necessary for electronic payment of funds.
(12) All written policies and procedures governing withdrawal liability determination, assessment, collection, settlement, and payment.
29 C.F.R. § 4262.7 — Plan information. · eCFR amendment effective 2021-07-12 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4262.7&asof=2021-07-12 · printed Oct 16, 2026
On this page
  • (a) Basic information.
  • (b) Eligibility.
  • (c) Priority group identification.
  • (d) Plans with a suspension of benefits.
  • (e) Plan documentation.
Implements
ERISA § 4262 (29 U.S.C. § 1432) Special financial assistance by the corporation
Cited by (code & regs)
Guidance addressing this section

No documents are primarily about this section.

Also cited in 2 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 12, 2021Aug 7, 2022eCFR amendment effective 2021-07-12 run 26View
Aug 8, 2022currenteCFR amendment effective 2022-08-08 run 2View · Redline (sign in)
Provision-level history (blame)