The asset with no balance to check
Every other retirement account gives you a number. Log into your 401(k) or IRA and there's a dollar figure sitting on the screen. A traditional pension, a defined benefit plan that promises a fixed monthly payment starting at a future date, doesn't work that way. There's no balance, no daily statement, just a formula and a promise: a monthly amount, starting at a certain age, for as long as you live.
That structure makes pensions the hardest common asset to place in a net worth calculation. Leaving it out entirely understates your financial position, sometimes dramatically for someone who spent a career at an employer that still offers one. Guessing at a number without a method produces something worse than no number at all: false precision. This post covers the three legitimate approaches, in order of how commonly you'll actually be able to use them.
Method 1: Use the lump-sum value your plan already reports
Many defined benefit plans, particularly since a 2015 regulatory shift made it easier for employers to offer this option, will report a lump-sum equivalent value: the amount the plan would pay you today, once, in exchange for giving up the future monthly payments entirely. If your plan reports this figure, either in your benefits statement or on request from the plan administrator, it's the cleanest number to use. The actuaries who calculate it have already done the discounting work for you, using assumptions the plan is contractually required to disclose.
This number typically appears on annual pension statements for plans that offer a lump-sum option, or can be requested directly from HR or the plan administrator even if you have no intention of ever taking the lump sum instead of the monthly annuity. Using it for tracking purposes doesn't commit you to actually taking the lump sum at retirement; it's simply the most defensible number available for your net worth today.
If your plan reports a lump-sum value, use it. Skip the rest of this section and move to how the number evolves over time, further down.
Method 2: Estimate the present value yourself
If no lump-sum figure is available, which is common for older, more traditional pension plans that never added a lump-sum option, you can estimate present value using the same underlying logic actuaries use, simplified for a personal estimate rather than a regulatory filing.
The concept: a future stream of monthly payments is worth less today than the sum of those payments would suggest, because money received later is worth less than money received now, both due to the time value of money and the uncertainty of whether you'll live to collect every payment.
A simplified formula:
Present value ≈ (Annual pension payment × Life expectancy factor) ÷ (1 + discount rate)^years until payments start
Three inputs you need:
- Annual pension payment. Your plan's benefits statement should show your projected monthly benefit at a stated retirement age. Multiply by 12.
- Life expectancy factor. A rough proxy for how many years of payments to expect, often approximated using an annuity factor. For a simplified personal estimate, a factor between 12 and 18 is common depending on your age at the start of payments and how conservative you want to be; pension actuaries use full mortality tables, but a personal estimate doesn't need that precision to be directionally useful.
- Discount rate and years until payments start. The discount rate reflects the time value of money; a common simplified choice is a rate close to current long-term bond yields, since a pension payment is a relatively low-risk, bond-like promise. The years-until-start figure comes from your plan's stated retirement age minus your current age.
A worked example
Tom is 45 and has a traditional pension from a public-sector job. His benefits statement shows a projected monthly payment of $2,400 starting at age 62, with no lump-sum option offered by the plan.
Step 1: Annual payment. $2,400 × 12 = $28,800 per year.
Step 2: Apply a life expectancy factor. Using a factor of 15 (a moderate assumption for payments starting at 62): $28,800 × 15 = $432,000. This represents a rough estimate of the total value of the payment stream at the point payments begin, already accounting for mortality risk in a simplified way.
Step 3: Discount back to today. Payments start in 17 years (62 − 45). Using a 4% discount rate:
$432,000 ÷ 1.04^17 = $432,000 ÷ 1.947 = $221,880
Tom's estimated present-value pension asset today is roughly $222,000. That's the figure he'd add to his net worth, alongside his 401(k), brokerage account, and other holdings.
Change any one input and the number moves substantially. A 3% discount rate instead of 4% raises the estimate to roughly $263,000. A life expectancy factor of 13 instead of 15 lowers it to about $192,000. This method produces a reasonable estimate, not a precise one, which is exactly why it should be labeled clearly as an estimate wherever you record it.
Method 3: Leave it off the balance sheet and adjust retirement spending instead
Some people, particularly those uncomfortable with the estimation involved in Method 2, choose a third approach: don't put a dollar value on the pension at all. Instead, treat it as reducing how much other retirement savings you need, the same way Social Security income reduces the portfolio required to fund a given retirement spending level.
Under this approach, if Tom's pension will cover $28,800 a year of his retirement spending starting at 62, he can reduce his target Coast FIRE or full retirement portfolio calculation by roughly $28,800 × 25, or about $720,000, using the standard 25x spending guideline, rather than adding a present-value estimate to his current asset total. This produces a similar directional effect to Method 2 but expresses it as reduced future need rather than current net worth.
There's no wrong answer between Methods 2 and 3. Both account for the pension's real value; they just place it in different parts of the plan. The mistake to avoid is doing neither, and planning as if the pension doesn't exist at all.
Public-sector pensions and survivor benefit choices
Public-sector pensions (teachers, government employees, some public safety roles) often come with an additional wrinkle: a choice at retirement between a higher "single life" monthly payment or a reduced monthly payment that continues to a surviving spouse after death. If you're married and expect to elect a survivor benefit, use the reduced monthly figure in your calculations, since that's the amount you'll actually receive, or model both scenarios if the decision hasn't been made yet.
Public pensions also sometimes carry a different funding risk than private ones: private pensions are typically insured up to certain limits by the Pension Benefit Guaranty Corporation if the plan becomes underfunded, while public pension funding depends on the specific state or municipality's fiscal health, which varies widely and is worth understanding if a large share of your retirement plan depends on one.
How the number should evolve over time
Whichever method you use, the estimate isn't static. Recalculate it periodically, at minimum whenever your plan issues an updated benefits statement, since your projected monthly payment typically grows each year with additional service credit. If you're using Method 2's present-value estimate, the number will also naturally rise each year simply because you're closer to the payment start date, even with no change to the projected monthly benefit itself, purely from discounting fewer years.
Whatever method you settle on, apply it consistently rather than switching approaches year to year, for the same reason changing a 401(k) tax-haircut method year to year distorts your trend line rather than reflecting real changes in what your account is worth.
Tracking a pension alongside accounts that do have balances
A pension doesn't update monthly the way a 401(k) balance does, so it doesn't need a monthly re-estimate. Most people update their pension figure once a year, when the annual statement arrives, and leave it untouched between updates. A net worth tracker that lets you log an account with an infrequent update cadence, sitting quietly alongside accounts you touch every month, keeps a pension from either being forgotten entirely or forcing an unnecessary monthly guess.
Frequently asked questions
Should I count my spouse's pension in our household net worth?
Yes, using the same method you'd apply to your own: the lump-sum value if the plan reports one, or a present-value estimate if it doesn't. If you're calculating a combined household net worth, both pensions belong in the total, the same as both partners' 401(k) balances.
What if I'm not vested in my pension yet?
Vesting rules for pensions vary by plan; many public-sector and traditional private pensions require five to ten years of service before any benefit is guaranteed. If you haven't met your plan's vesting requirement, treat the pension as $0 for net worth purposes, the same logic used for unvested employer 401(k) contributions, since you'd receive nothing if you left today.
Does a pension count as a liquid asset?
No. A pension is one of the least liquid assets on a typical balance sheet; you generally can't access any of its value before your plan's stated retirement age, and even then only as the monthly payment stream (or a lump sum, if your plan offers one). If you track a liquid net worth figure alongside your total, exclude the pension from it entirely.
How is a pension different from an annuity I purchased myself?
Mechanically similar (both promise a future income stream), but a pension is earned through employment and typically requires no upfront purchase from you, while a purchased annuity is bought with a lump sum from your own savings. If you've purchased an annuity, its value for net worth purposes is usually the current cash surrender value your insurer reports, not a present-value estimate, since insurers generally provide that figure directly.
Ready to see your full financial picture?
Try Pro free for 30 days. No bank login required. No credit card.
Create your free dashboard