The 401(k) is the most-asked-about asset in elder-law consultations, and for reasonable cause. It is typically the second-largest asset a couple owns, after the home. It is frequently in the community spouse's name. And its Medicaid treatment varies so dramatically from state to state that the same couple with identical balance sheets can face an $80,000 spend-down in one state and a $300,000 spend-down in another.
The default: counted in full
In most states, the community spouse's 401(k), IRA, 403(b), and other qualified retirement accounts are counted as non-exempt assets on the Snapshot Date. That means the full account balance gets added to checking, savings, investments, and any other countable assets — and the combined total is then measured against the Community Spouse Resource Allowance.
For couples with meaningful retirement balances, this default posture has a predictable consequence: the CSRA ceiling of $157,920 (2026) is hit almost immediately. A community spouse with $300,000 in a 401(k) and $50,000 in a joint savings account is already over the ceiling before any of the spend-down conversation begins. The applicant cannot qualify for Medicaid until the combined non-exempt assets are reduced — through spend-down on legitimate expenses, on the community spouse's care, on home repairs, on converting non-exempt assets to exempt ones — to the CSRA plus the applicant's $2,000 asset cap.
The narrow exception: payout-status states
A handful of states — the number and specifics shift as administrative posture evolves — exempt the community spouse's retirement account when it is in payout status. "Payout status" means the account is actively distributing to the community spouse, typically at or above the IRS-required minimum distribution.
In those states, a $400,000 IRA in the community spouse's name that is paying RMDs does not count against the CSRA ceiling. The account is still the community spouse's asset; the RMDs are still income; but the account balance is not in the Snapshot Date total. The planning implications are enormous. A couple in a payout-exempt state can protect a 401(k) of any size that the community spouse was not relying on for daily living.
The tradeoff: payout-status exemption converts sheltered retirement assets into monthly income. That income then gets tested against the MMMNA ceiling. If the community spouse's combined income (including RMDs) exceeds the state's MMMNA, the excess must be contributed toward the applicant spouse's cost of care. In practice, most community-spouse retirement-account RMDs are small enough that the MMMNA trade is favorable, but the arithmetic is real and worth checking.
What about the applicant spouse's 401(k)?
The applicant spouse's own retirement account is rarely sheltered. In most states, the applicant must spend down the account — or liquidate it and apply the proceeds — before qualifying for Medicaid. The applicant's $2,000 asset cap does not bend for qualified-plan assets.
That is why spousal transfers matter. Moving funds from the applicant's 401(k) to the community spouse's name before the Snapshot Date is allowed under the inter-spousal transfer safe harbor of the 5-year lookback. But retitling alone doesn't help if the state counts both spouses' retirement accounts equally — the asset lands in the same combined-asset bucket.
Where this gets tricky
RMD age, contribution history, plan-specific loan provisions, and the timing of the first institutional stay can all complicate the analysis. A community spouse who turns 73 two months after the Snapshot Date will be required to begin RMDs by year-end under current IRS rules — but the Medicaid application may have already been filed against a balance that didn't yet reflect those distributions.
State administrative posture can also shift. A state that exempted retirement accounts in payout status five years ago may have changed its position without legislative action, through guidance memos or caseworker training updates. Any plan relying on the exemption needs current confirmation — not guidance from a blog post, not a conversation with a benefits planner from a different state, and not an assumption that what worked for a neighbor two years ago still works now.