Skip to main content

Overview

Each ESOPLoan object represents a debt obligation of the ESOP, with shares held in a dedicated suspense account as collateral. This self-contained design ensures accurate loan-by-loan accounting for leveraged ESOPs.
Critical Concept: Each loan directly owns its suspense shares. When Loan A is paid down, only Loan A’s shares are released—never shares from Loan B.

Model Structure

Why Loan-Specific Suspense Matters

Single Suspense Pool (Incorrect)
Why It Fails:
  • Can’t determine which shares collateralize which loan
  • Violates ERISA’s specific collateral requirements
  • Creates audit and compliance risk

Share Release Mechanics

When a loan payment is made, shares are released proportionally to the principal paid:
ERISA Requirement: Shares must be released proportionally as the loan is repaid. This prevents “back-loading” where all shares are released at the end.

Loan Types & Payment Schedules

Equal principal + interest payments each year.

Methods & Operations

Multi-Loan Example

Here’s a complete example with two loans:

Integration with ESOPTrust

The ESOPTrust aggregates all loans:

Best Practices

Track Original Values

Always store original_principal and original_suspense_shares for accurate release calculations

Validate Releases

Ensure released shares never exceed suspense shares

Document Purpose

Record why each loan was taken (purchase, refinancing, expansion)

Monitor Ratios

Track debt-to-equity and ensure sustainable debt levels

Common Issues

Problem: Accidentally releasing shares from Loan B when paying Loan A.Solution: Each loan owns its shares. Never aggregate suspense shares.
Problem: Share releases don’t add up due to rounding.Solution: Use high-precision decimals and track cumulative releases.
Problem: Large balloon payment creates cash crisis.Solution: Model balloon loans carefully and plan cash reserves.

Next Steps

Share Pool Calculation

See how loan share releases feed into allocation

ESOPTrust

How loans fit into the trust structure