Brief Case

29 C.F.R. § 2580.412-4

“Funds or other property” of a plan.
eCFR amendment effective 2017-01-01 · current
The affirmative requirement for bonding persons falling within the definition of administrator, officer or employee is applicable only if they handle “funds or other property” of the plan concerned. The term “funds or other property” is intended to encompass all property which is used or may be used as a source for the payment of benefits to plan participants. It does not include permanent assets used in the operation of the plan such as land and buildings, furniture and fixtures or office and delivery equipment used in the operation of the plan. It does include all items in the nature of quick assets, such as cash, checks and other negotiable instruments, government obligations and marketable securities. It also includes all other property or items convertible into cash or having a cash value and held or acquired for the ultimate purpose of distribution to plan participants or beneficiaries. In the case of a plan which has investments, this would include all the investments of the plan even though not in the nature of quick assets, such as land and buildings, mortgages, and securities in closely held corporations. However, in a given case, the question of whether a person was “handling” such “funds or other property” so as to require bonding would depend on whether his relationship to this property was such that there was a risk that he, alone or in connivance with others, could cause a loss of such “funds or other property” through fraud or dishonesty.
29 C.F.R. § 2580.412-4 — “Funds or other property” of a plan. · eCFR amendment effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-2580.412-4 · printed Oct 16, 2026
Implements
Cited by (code & regs)

No guidance in the library cites this section yet.

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 amendment effective 2017-01-01 run 2View
Provision-level history (blame)