Defined Benefit Plan
A Defined Benefit (DB) plan is an employer-sponsored retirement plan that promises a specific benefit at retirement, computed by the plan's benefit formula (typically years-of-service × accrual-rate × final-pay-average). The employer bears the investment risk and funding obligation. Plan benefits are insured by the PBGC for private-sector single-employer plans up to age-specific maximums.
DB plans dominated US retirement provision through the 1980s. Their decline since then — replaced by 401(k) plans across most of the private sector — has been substantial but incomplete. As of 2025, approximately 12 million private-sector workers are active participants in DB plans (PBGC data), heavily concentrated in legacy industries (manufacturing, utilities, large legacy corporates). The public sector retains DB as the dominant model for federal, state, and most municipal employees.
DB plans differ from defined-contribution (401(k)-style) plans in three structural ways. First: the benefit is defined, not the contribution. The participant accrues a benefit (a future income stream) rather than an account balance. Second: the employer bears the investment risk. Underperformance of plan assets relative to the actuarial assumptions creates a funding shortfall the employer has to cover. Third: the actuarial mechanics matter — accrual rates, mortality assumptions, discount rates all interact to produce the participant's economic outcome.
The plan's benefit formula is typically one of three types: final-average pay (most traditional), career-average pay (some newer plans), or cash-balance (modern hybrid that resembles a 401(k) but is technically DB). Each has different accrual mechanics. Final-average plans accrue benefits as a function of the years-of-service and the highest-N-year average pay; the benefit accrual rate compounds across years of service.
Lump-sum offers — increasingly common at separation, plan-termination, or specific window events — convert the future annuity stream to a single payment. The conversion uses §417(e) segment rates as the discount rate for non-cash-balance plans. Lump-sum amounts swing 20-30% across a typical Fed-rate cycle for the same underlying benefit; the rate sensitivity is the major source of variation in the lump-sum-vs-annuity decision.
For wealth-tech platforms, DB pensions are the actuarial-product cohort. The 'value' is not a single number but a function of the discount rate, mortality assumptions, and election (single-life, joint-and-survivor, lump sum). Platforms that display DB pensions as a static balance produce wrong customer experiences when the customer asks for a quote and gets a different number. The [DB pension modeling](/articles/defined-benefit-pension-modeling) article covers the data shapes; the [lump-sum-vs-annuity comparison](/resources/comparisons/lump-sum-vs-annuity-pension) covers the decision framework.
B = AccrualRate × YearsOfService × FinalAvgPay- B
- = annual accrued benefit
- AccrualRate
- = plan-defined rate (typically 1-2% per year)
- YearsOfService
- = credited service years
- FinalAvgPay
- = average compensation over final N years (often 3 or 5)
1.5% × 30 years × $182,600 = $82,170/yr. Monthly: $6,847. The same formula with 1% accrual rate would produce $54,780/yr — the accrual rate is the most-leveraged input and varies meaningfully across plans.DB-pension-aware synthetic data needs the benefit-formula inputs (accrual rate, averaging period, service credit history, compensation history), the joint-and-survivor election factors, the early-retirement reduction schedule, the plan funding status, and the §417(e) segment rates for lump-sum-offer scenarios. The longitudinal data has to track year-over-year benefit accrual; current-state-only data is insufficient.
Common pitfalls
- Treating the accrued benefit as a single 'pension value' — the value depends on rate environment, mortality, and election form.
- Ignoring plan funding status — underfunded plans pose haircut risk above the PBGC cap.
- Forgetting J&S election impact — the actuarial-equivalent factors materially reduce monthly payments for survivor protection.
- Hardcoding mortality assumptions — IRS-mandated tables update periodically; lump-sum calculations have to use current tables.
Examples
Participant: 30 years of service, final-5-year average pay $182,600, accrual rate 1.5%. Annual benefit at NRA: 30 × 0.015 × $182,600 = $82,170. Monthly benefit: $6,847. Lump-sum offer at 3% discount rate: ~$1,580,000. Lump-sum offer at 5% discount rate: ~$1,260,000. Same accrued benefit, 25% smaller offer at the higher rate. The customer's decision depends on life expectancy, expected investment returns, and survivor protection needs.