Brief Case
Pension Resource

29 C.F.R. § 4043.67

Loan default.
CFR 2015 annual edition (revised as of 2015-07-01) · superseded Jul 1, 2016
PrintCompare datesAsk AI about this sectionOfficial source ↗
Back to current
Historical text in effect Jul 1, 1997 through Jun 30, 2016. View current · Compare with current
(a) Reportable event and information required. Advance notice is required for a loan default, as described in § 4043.34(a) (or that would be so described if “10 days” were substituted for “30 days” in § 4043.34(a)(1)). The notice shall include the information described in § 4043.34(b).
(b) Waivers. Notice is waived if the reportable default is cured, or the lender waives the default, within 10 days or, if later, by the end of any cure period.
(c) Extensions. The notice date is extended to the later of—
(1) 10 days after default. 10 days after the default occurs (without regard to the time of any other conditions required for the default to be reportable); and
(2) One day after subsequent event. One day after—
(i) The applicable cure period provided in the loan agreement (in the case of a default described in § 4043.34(a)(1));
(ii) The date the loan is accelerated (in the case of a default described in § 4043.34(a)(2)); and
(iii) The date the debtor receives written notice of the default (in the case of a default described in § 4043.34(a)(3)).
29 C.F.R. § 4043.67 — Loan default. · CFR 2015 annual edition (revised as of 2015-07-01) · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4043.67&asof=1997-07-01 · printed Oct 16, 2026
On this page
  • (a) Reportable event and information required.
  • (b) Waivers.
  • (c) Extensions.
Implements
ERISA § 4043 (29 U.S.C. § 1343) Reportable events
Guidance addressing this section

No documents are primarily about this section.

Also cited in 2 other documents
PBGC
Final Rules
  • 80 FR 54980 Sep 11, 2015 — Reportable Events and Certain Other Notification Requirements
Proposed Rules
  • 78 FR 20039Proposed Apr 3, 2013 — Reportable Events and Certain Other Notification Requirements Comments due Jun 3, 2013

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, 2016CFR 2015 annual edition (revised as of 2015-07-01) run 127View
Jul 1, 2016currenteCFR amendment effective 2017-01-01 run 2View · Redline (sign in)
Provision-level history (blame)