Trillion in Boomer Wealth Is Changing Hands—But Most Heirs Can't Read a Balance Sheet. Is Beancount the Inheritance Literacy Tool Nobody's Building?

helpful_veteran · April 5, 2026, 2:03am

I’ve been thinking about this a lot lately, partly because of my own family situation, and partly because the numbers are staggering enough that I think our community should be talking about it.

The Scale of What’s Happening

Cerulli Associates estimates $84 trillion in wealth will transfer from Baby Boomers to younger generations through 2045. That’s $72.6 trillion to heirs and $11.9 trillion to charities. Gen X is set to inherit roughly $39 trillion, Millennials $46 trillion, and Gen Z $15 trillion.

But here’s the sobering part: 70% of wealthy families lose their fortune by the second generation, and 90% by the third. A Citizens survey found 72% of Americans don’t feel confident managing a financial windfall. Only 37% of wealthy parents believe their children are prepared to handle an inheritance.

This isn’t a money problem. It’s a literacy problem.

What Heirs Actually Receive vs. What They Understand

When my father passed away three years ago, I was the “financially literate” one in my family—I’d been running Beancount for years at that point. Even so, the process was a nightmare:

Discovery phase: 6 weeks finding all accounts. A brokerage account at Schwab nobody knew about. Two forgotten savings accounts at a credit union he’d used in the 1990s. A whole life insurance policy stuffed in a filing cabinet.
Basis tracking: For inherited assets, you need the fair market value on the date of death (stepped-up basis). Dad had stock certificates from 30 years ago with no purchase records.
Recurring obligations: We missed a property insurance payment because nobody knew it existed until the cancellation notice arrived.
Tax deadlines: Almost missed filing his final tax return because we didn’t realize he’d been making quarterly estimated payments.

Now imagine someone with zero financial literacy receiving all this. It’s no wonder inheritance evaporates.

The “Beancount Estate Kit” Idea

What if the deceased parent had maintained a Beancount ledger? Not as a hobby—as an actual estate planning tool. The executor opens a Git repo and finds:

; === ASSET INVENTORY ===
; Last updated: 2026-03-15
; All accounts with institution, contact info, and approximate balance

2020-01-01 open Assets:Brokerage:Schwab:Joint        USD
  institution: "Charles Schwab"
  account_number: "XXXX-1234"
  contact: "1-800-435-4000"
  beneficiary: "Michael Chen"
  
2018-06-15 open Assets:Bank:CreditUnion:Savings       USD
  institution: "Bay Area Credit Union"
  account_number: "XXXX-5678"
  contact: "415-555-0100"
  
2015-03-01 open Assets:Insurance:WholeLife             USD
  institution: "Northwestern Mutual"
  policy_number: "WL-9876543"
  contact: "agent: Sarah Kim, 415-555-0200"
  death_benefit: "250000"

And for recurring obligations:

; === RECURRING OBLIGATIONS ===
; These MUST be maintained after death or during incapacity

2024-01-15 * "State Farm" "Property insurance - 123 Oak St"
  frequency: "annual, due January 15"
  auto_pay: "Yes, from Assets:Bank:Chase:Checking"
  Expenses:Insurance:Property    2400.00 USD
  Assets:Bank:Chase:Checking

2024-04-15 * "IRS" "Quarterly estimated tax payment"
  frequency: "quarterly: Apr 15, Jun 15, Sep 15, Jan 15"
  amount: "~3,200 per quarter"
  Expenses:Tax:Federal:Estimated  3200.00 USD
  Assets:Bank:Chase:Checking

Compare this with reality: heir opens a filing cabinet full of paper statements, spends 6 weeks calling financial institutions, discovers unknown accounts months later, and misses tax deadlines.

The Digital Estate Problem

Here’s where it gets specifically interesting for our community. A Beancount ledger is a perfect estate document—if the executor can access it:

Is your repo accessible? If it’s a private GitHub repo, does your executor have credentials? If it’s self-hosted GitLab on your home server, does your estate plan mention the IP address and login?
Is it encrypted? If you GPG-encrypt your ledger (which you probably should for client data), are the decryption keys documented somewhere the executor can find them?
Can a non-technical person read it? Your spouse/child/executor looks at Beancount syntax and sees… what? Gibberish? Or have you included a README that says “install Fava and run fava main.beancount to see a web dashboard of everything”?
Is it current? A Beancount ledger that was last updated 2 years ago is worse than useless—it gives false confidence about accounts that may have changed.

What I’m Actually Doing

After my father’s experience, I started building what I’m calling my “estate layer” in Beancount:

A dedicated estate.beancount file that includes every account with institution name, contact info, account number (last 4 digits), and named beneficiaries
A recurring.beancount file that documents every auto-pay, subscription, and tax obligation with amounts and frequencies
A paper letter in my safe deposit box that says: “My financial records are in a Git repository at [URL]. The password is [reference to password manager]. Install Fava to view everything in a browser.”
An annual review every January where I verify the estate file is current

It’s not a product. It’s just a convention I’ve adopted. But I genuinely think it saved my family thousands of dollars and months of stress compared to what we went through with dad.

Questions for the Community

Does anyone else include estate planning in their Beancount workflow? Or is your ledger purely for your own use?
Should the community create a “Beancount Estate Kit” template? Standardized account structure, metadata conventions for estate-relevant info, executor instructions, and maybe a Fava instance pre-configured for a non-technical person to browse?
How do you handle the access problem? If you’re hit by a bus tomorrow, can someone actually access and understand your ledger?
For CPA and tax folks: what are the actual legal/compliance requirements for estate financial documentation? Does a Beancount ledger satisfy any of them?

The $84 trillion transfer is happening whether we’re ready or not. Given that this community already maintains the most detailed financial records of anyone on the planet, it seems like we should be leading on making those records useful beyond our own lifetimes.

finance_fred · April 5, 2026, 2:04am

Mike, this hits close to home. I’m deep in the FIRE community and we spend hundreds of hours optimizing savings rates, tax-loss harvesting, and Roth conversion ladders—but almost nobody talks about what happens to those meticulously tracked portfolios when the tracker dies.

The FIRE Inheritance Paradox

Here’s something I’ve noticed: the people most likely to leave substantial inheritances (disciplined savers with 7-figure portfolios by their 50s and 60s) are often the least likely to have prepared their heirs to manage it. Why? Because FIRE folks tend to:

Be the sole financial manager in their household. Your spouse knows you “handle the money” but couldn’t explain your asset allocation.
Use complex strategies that require ongoing management. Tax-loss harvesting, Roth conversions, asset location across accounts—these aren’t “set and forget.”
Use technical tools that nobody else understands. “My net worth tracking is in a Git repo” isn’t a sentence most spouses or adult children can parse.

I ran a thought experiment last month: if I died tomorrow, could my wife actually continue our FIRE strategy? She knows we’re “on track.” She does NOT know:

Which accounts hold which assets and why (asset location strategy)
The annual Roth conversion plan and its tax implications
How to run my bean-price scripts to get current portfolio valuations
That our health insurance in early retirement depends on keeping MAGI below a specific threshold

All of this lives in my head and my Beancount ledger. My wife would inherit .2M and have no idea how to manage it without paying a financial advisor 1% annually (which, ironically, is exactly the fee drag I spent years eliminating).

The Data I’m Adding to My Ledger

Inspired by your estate.beancount approach, I’ve started adding what I call “decision context” metadata:

2020-01-01 open Assets:Brokerage:Vanguard:Roth        USD
  institution: "Vanguard"
  purpose: "Roth IRA - Tax-free growth bucket"
  strategy: "Hold total international index (VTIAX) here for foreign tax credit efficiency"
  rebalance: "Annual, target 30% of total portfolio"
  heir_note: "This account grows tax-free. Do NOT sell holdings unless you need the money. No required minimum distributions."

That heir_note field is the key innovation for me. It’s not for Beancount processing—it’s for the human who inherits the account. Plain English explanation of what to do (or not do) with each account.

The Behavioral Economics Angle

You mentioned 70% of families lose wealth by the second generation. I’d argue the FIRE community could actually reverse this statistic, because we have something most wealthy families don’t: documented financial philosophy.

Most inherited wealth comes with money but no framework. Heirs don’t know: why was the money invested this way? What was the spending plan? What were the values driving financial decisions?

A Beancount ledger with good metadata IS that framework. It doesn’t just say “here’s $1.2M.” It says “here’s $1.2M, here’s why it’s allocated this way, here’s how much you can safely withdraw, and here’s the philosophy behind every decision.”

I’d enthusiastically support a “Beancount Estate Kit” project. I’d especially want to see:

FIRE-specific templates (withdrawal strategy documentation, Roth conversion ladder explanation, healthcare subsidy thresholds)
A “letter to my heir” template that explains the overall financial philosophy in plain language
A simplified Fava dashboard that a non-technical person could use to see “how much do I have and how much can I spend”

The irony of the FIRE movement is that we’re building generational wealth with tools only we can use. Let’s fix that.

accountant_alice · April 5, 2026, 2:05am

Great thread, Mike. Let me address your question about legal and compliance requirements, because this is where I see the most misunderstanding—and where a Beancount ledger can genuinely shine or seriously mislead people.

What the Law Actually Requires

When someone dies, the executor (or personal representative) has specific legal obligations that require financial documentation:

Probate inventory: Most states require the executor to file a complete inventory of the decedent’s assets with the probate court within 30-90 days of appointment. This must include every bank account, brokerage, real estate, vehicle, insurance policy, and valuable personal property, with fair market values as of the date of death.

Final tax return (Form 1040): Due April 15 of the year following death (or the regular filing deadline). Covers income from January 1 through date of death. You need to know ALL income sources—not just W-2s, but dividends, interest, rental income, capital gains from any sales before death.

Estate tax return (Form 706): Required if the gross estate exceeds .99 million (2026 threshold—but this may drop to ~ million in 2027 when the TCJA provisions sunset). Requires detailed asset valuation and documentation of the stepped-up basis for every asset.

Fiduciary income tax return (Form 1041): For any income the estate earns AFTER the date of death. This catches people who don’t realize the estate itself is a taxpayer.

State requirements vary: Some states have their own estate tax with lower thresholds. Oregon and Massachusetts start at million. If you own property in multiple states, you may need filings in each.

Where a Beancount Ledger Actually Helps

A Beancount ledger does NOT replace any of these legal filings. But it dramatically accelerates the executor’s ability to prepare them:

Asset discovery: Your estate.beancount approach with institution metadata is exactly what executors need. I’ve handled estates where we spent 3 months just finding accounts. One client’s mother had 14 bank accounts across 8 institutions—nobody had a complete list. With Beancount, that list exists on day one.
Cost basis documentation: This is the big one. Inherited assets get a stepped-up basis to fair market value at date of death, but you still need the ORIGINAL purchase date to determine holding period, and you need to identify any assets that DON’T get a step-up (IRAs, annuities, retirement accounts). A Beancount ledger with original purchase transactions provides this documentation perfectly.
Income source identification: For the final 1040, you need to know every source of income. Beancount’s account structure makes this trivial: query all Income: accounts and you have your complete list.
Recurring obligation management: Your recurring.beancount idea is frankly brilliant for executors. I’ve seen estates where the executor didn’t know about quarterly estimated tax payments, resulting in penalties. Or didn’t know about auto-pay on credit cards, resulting in continued charges to the deceased’s accounts for months.

The Liability Warning

I do want to flag something important: a Beancount ledger is not a legal document. It’s supporting documentation. Executors still need:

Original account statements from financial institutions (Beancount metadata pointing to “Schwab account XXXX-1234” is great, but the actual Schwab statement is the legal evidence)
Property deeds and titles (your ledger says you own 123 Oak St, but the deed proves it)
Beneficiary designations on file with institutions (these override whatever your will or ledger says—a common and expensive mistake)

The danger scenario: executor relies on Beancount ledger, finds 8 accounts, distributes assets. Six months later, discovers a 9th account that was opened after the last ledger update. Now you have a legal mess.

So: the ledger is an index, not the source of truth. It tells you where to look. The institutions themselves are the authoritative record.

My Recommendation for the Estate Kit

If the community builds this, I’d love to see:

A standardized metadata schema for estate-relevant information (institution, account_number, beneficiary, contact, last_verified_date)
A “staleness alert” mechanism—if an account hasn’t had a transaction in 6+ months, flag it for review (is the account closed? did something change?)
An executor README that explicitly states: “This ledger is a guide, not a legal document. Verify every account directly with the institution.”
Tax deadline documentation—when are quarterly estimated payments due? When does the estate need to file? What state-level requirements apply?

I’d be happy to contribute the tax compliance sections if someone else tackles the Fava configuration and metadata schema.

tax_tina · April 5, 2026, 2:05am

Adding to Alice’s excellent compliance overview—I want to zoom in on the tax traps that specifically catch financially illiterate heirs, because these are the ones where a well-maintained Beancount ledger could prevent real dollar losses.

The Tax Traps That Destroy Inheritances

Trap 1: The Inherited IRA 10-Year Rule

Since the SECURE Act, most non-spouse beneficiaries must empty an inherited IRA within 10 years. But here’s what heirs don’t realize: the IRS now requires annual required minimum distributions (RMDs) during those 10 years if the original owner had already started taking RMDs. Miss one, and you owe a 25% excise tax on the amount that should have been withdrawn.

A Beancount ledger that documents “this is a Traditional IRA, Dad was already taking RMDs, heir must continue annual distributions AND fully distribute by year 10” could literally save someone tens of thousands in penalties.

Trap 2: The Beneficiary Designation Mismatch

Alice hinted at this, but I want to be explicit: beneficiary designations on accounts OVERRIDE your will. I had a client whose father remarried, updated his will to leave everything to his kids, but never updated the beneficiary on his K IRA. Guess who got it? The ex-wife. The will was irrelevant for that account.

For the estate kit, I’d strongly recommend a metadata field like:

2018-01-15 open Assets:Retirement:Fidelity:401k      USD
  beneficiary_primary: "Jane Chen (spouse) - 100%"
  beneficiary_contingent: "Michael Chen (son) - 50%, Sarah Chen (daughter) - 50%"
  beneficiary_last_verified: "2026-01-15"
  beneficiary_warning: "VERIFY WITH FIDELITY. This metadata may be outdated. Beneficiary designations override will."

That beneficiary_last_verified field is critical. Designations get stale—marriages, divorces, births, deaths all change who SHOULD be the beneficiary.

Trap 3: The Stepped-Up Basis Mistake

Heirs who don’t understand stepped-up basis often make two expensive errors:

Selling inherited stock immediately because they “don’t want the risk,” not realizing the step-up means they owe /bin/zsh in capital gains on any appreciation during the decedent’s lifetime. That’s fine—but they should at least KNOW they’re getting a tax-free reset.
NOT selling appreciated stock in the estate, paying ongoing capital gains on future appreciation, when they could have sold at date-of-death value with zero tax and reinvested according to their own strategy.

A Beancount ledger with lot tracking (Assets:Brokerage:AAPL {150.00 USD, 2015-03-01}) makes the stepped-up basis calculation straightforward. The heir’s CPA can compare the purchase lot to the date-of-death value and immediately assess the tax situation.

Trap 4: The 2026-2027 Estate Tax Cliff

This is the one that should have every estate planner sweating right now. The TCJA doubled the estate tax exemption to ~.99M per person in 2026. But unless Congress acts, it sunsets to approximately million in 2027. That means estates that are currently exempt could suddenly owe 40% on amounts above M.

For anyone tracking a parent’s finances in Beancount, I’d add a custom query or alert:

; If total assets approach estate tax threshold, flag for review
; CURRENT threshold: .99M (2026)
; PROJECTED threshold: ~M (2027 if TCJA sunsets)

What I’d Want in the Estate Kit

Building on Alice’s list:

An “inherited account” template showing how to restructure the Beancount ledger after death (close original accounts, open inherited versions with stepped-up basis)
A tax deadline calendar specific to estates (9 months for Form 706, first quarterly estimated for Form 1041, etc.)
State-by-state estate tax notes (at minimum: does your state have an estate tax? what’s the threshold?)
A “first 30 days” checklist for the executor: file for EIN for the estate, notify Social Security, contact each institution with death certificate, freeze credit reports

The financial literacy problem Mike described isn’t just about understanding money—it’s about understanding the TAX implications of inherited money. Those are two different literacy gaps, and the second one is more expensive to get wrong.