A business owner calls their financial advisor and says, "I read that there's a plan that combines my 401(k) and a pension into one document — can we set that up?" The advisor's answer, almost every time, is some version of "technically yes, but you don't want that."
The plan the owner is describing is real. It's called the DB(k) plan — formally an "Eligible Combined Plan" under Section 414(x) of the tax code — and Congress created it nearly two decades ago specifically to make life easier for small employers who wanted both a 401(k) and a defined benefit pension. It was supposed to cut paperwork, cut cost, and get more small businesses offering real retirement security instead of just a bare-bones 401(k).
It didn't work out that way. Almost no one uses a DB(k) today. But the reason it failed is instructive, because the thing small business owners actually do use to get the tax benefit they were chasing — a "DB/DC combo" of two separate plans — is one of the most powerful retirement and tax-deferral tools available to a profitable, older business owner. Understanding why the combined version flopped tells you exactly what to ask for instead.
What a DB(k) Plan Was Supposed to Do
The DB(k) came out of the Pension Protection Act of 2006, aimed at "small employers" — defined as having at least 2 but fewer than 500 employees. The pitch was straightforward: instead of maintaining two entirely separate retirement plans with two sets of documents, two sets of testing, and two Form 5500 filings, a small employer could adopt one combined plan that bundled:
- A defined benefit (DB) component — a traditional pension formula that had to credit employees with at least 1% of pay for every year of service, up to 20 years, with full vesting required after just 3 years of service (much faster than a typical pension's vesting schedule).
- A defined contribution (DC) component — a 401(k) with automatic enrollment at a 4% deferral rate (employees could opt down or out), plus a required employer match of 50% of employee deferrals up to 4% of pay, immediately vested.
In exchange for meeting those minimum benefit levels for rank-and-file employees, the whole thing was supposed to be treated as a single plan for annual reporting purposes — one Form 5500 instead of two, simpler nondiscrimination testing, and lower administrative overhead. On paper, it looked like a genuine win for a small employer who wanted to offer serious retirement benefits without hiring a small army of consultants.
Why It Never Caught On
Three things killed the DB(k) in practice, and they're worth knowing even if you'll never touch this specific plan type — they explain a lot about how retirement plan design actually gets decided.
The IRS never gave it the streamlined treatment it promised. Despite being built around pre-approved plan documents, the IRS ended up treating DB(k) plans as individually designed plans for determination-letter purposes. That meant employers submitting two Form 5300s and paying double the user fees — the exact opposite of the simplification the law was written to deliver.
The administrative burden didn't actually shrink. A single Form 5500 filing sounds like a win, but the DB component still needed its own annual actuarial valuation, and the DC component still needed its own compliance testing and recordkeeping. Combining the wrapper around two plans doesn't combine the actual work of running two plans.
The math usually favored separate plans anyway. For most profitable small businesses — especially ones where the owner is significantly older or higher-earning than staff — running a standalone defined benefit or cash balance plan alongside a standard 401(k) profit-sharing plan produces a larger deductible contribution for the owner than the DB(k)'s built-in formula allows. When the "simpler" combined option also produces a worse financial outcome, there's no reason to choose it.
What Business Owners Actually Set Up Instead
The retirement plan design that actually delivers what owners were hoping the DB(k) would give them is a DB/DC combo plan: two legally separate plans — typically a cash balance plan (a modern, more flexible cousin of the traditional defined benefit plan) and a 401(k) with profit-sharing — administered together but documented and filed independently.
The numbers explain why advisors steer clients here instead. In illustrative examples used by retirement plan actuaries, a younger business owner group might see a standalone defined benefit plan cap out around $250,000 in total deductible owner contributions in a year, while pairing it with a 401(k) profit-sharing component pushes that past $330,000 — an extra $80,000 in pretax savings from the same underlying business. For an older owner closer to retirement age, where defined benefit formulas can front-load much larger contributions, a standalone DB plan might support roughly $385,000 in owner benefits, while the combo structure pushes that above $480,000.
The combo also gives an employer more control over the cost of covering employees. Because the 401(k)/profit-sharing side can be designed with a "new comparability" allocation formula, an employer can often satisfy nondiscrimination testing while directing a much larger share of the total contribution to the owner and a much smaller share to staff — frequently cutting the cost of covering rank-and-file employees relative to what the DB(k)'s built-in 1%-per-year formula and required match would have required.
Who Should Actually Consider This
A DB/DC combo plan isn't for every small business — it's a specific tool for a specific profile:
- Consistent, healthy profitability. Defined benefit and cash balance plans require an actuary to calculate a funding target, and that contribution is largely mandatory once committed — unlike a 401(k) profit-sharing contribution, which can flex down in a bad year.
- An owner who is older than most of the staff, or a business with few employees relative to owner compensation. The bigger the age or income gap, the bigger the advantage tilts toward the owner.
- A multi-year time horizon. These plans work best funded for at least 3–5 years; setting one up and terminating it the following year invites IRS scrutiny.
- Willingness to fund staff accounts. Employees still have to receive a meaningful, IRS-compliant contribution — this is a way to shift more of the tax-advantaged dollars toward the owner, not a way to avoid covering staff.
If that profile doesn't match your business, a SEP-IRA, Solo 401(k), or standard 401(k) profit-sharing plan is usually a better fit with far less administrative overhead.
The Bookkeeping Side Owners Often Underestimate
Whichever structure you land on, a defined benefit or cash balance plan changes what your books need to track. The required employer contribution isn't discretionary the way a 401(k) match often is — it's closer to a debt obligation the business owes to the plan, calculated by an actuary and due on a schedule. That means your ledger should be tracking it as an accrued liability throughout the year, not as a surprise cash outflow discovered at tax time.
This is exactly the kind of obligation that's easy to lose track of in a spreadsheet or a bookkeeping tool that only shows you a checking account balance. Plain-text accounting makes it straightforward to model: a liability account for the accrued plan contribution, funded incrementally as the year progresses, reconciled against the actuary's annual funding notice, and closed out when the contribution is actually deposited — all fully auditable in version control, so your CPA and your actuary are always looking at the same numbers you are.
Keep Your Retirement Plan Contributions in Clear View
Complex retirement structures like a DB/DC combo plan only pay off if the underlying bookkeeping keeps pace with them — tracking accrued plan liabilities, employer contributions, and the cash set aside to fund them shouldn't be guesswork. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data, with a full audit trail your accountant, actuary, and future self can all trust. Get started for free and see why business owners managing sophisticated benefit plans are switching to plain-text accounting.