SECURE 2.0 Auto-Portability and the December 31, 2026 401(k) Plan Amendment Deadline: What Small Business Sponsors Must Do Now

Somewhere in a recordkeeper's system, there is probably a 401(k) account with your former employee's name on it — maybe several. Roughly 22% of active retirement plan participants change jobs every year, and about a third of them cash out their balance within twelve months of leaving. Two-thirds of those cash-outs come from accounts under $5,000. The Employee Benefit Research Institute estimates that plugging this "leakage" could keep as much as $2 trillion inside the U.S. retirement system over 40 years — and three-quarters of that figure comes from the smallest accounts, the ones your plan probably forces out today.

Congress noticed. Section 120 of the SECURE 2.0 Act created a legal framework called auto-portability that automatically moves a departing employee's small 401(k) balance into their next employer's plan instead of stranding it in a forgotten IRA. And if you sponsor a calendar-year 401(k) plan, there is a hard date attached to the broader law it rides in on: December 31, 2026 — the deadline the IRS set in Notice 2024-2 for formally amending your plan document to reflect SECURE 2.0 (along with the original SECURE Act and CARES Act changes you have been operating under for years).

This guide explains what auto-portability actually does, how it interacts with the force-out rules you already have, what the amendment deadline covers, and the concrete steps a small business owner should take before year-end 2026.

A Quick Refresher: What Happens to Small Balances When Someone Quits​

When an employee leaves and their vested 401(k) balance is small, most plan documents let you push the money out without their consent. The mechanics come in three tiers:

• Under $1,000: The plan can simply cut a check (a "cash-out distribution"). If the participant doesn't roll it over within 60 days, it becomes taxable income, usually with a 10% early-withdrawal penalty on top.
• $1,000 up to $7,000: The plan cannot just mail a check. If the participant doesn't respond to notices, the balance must be rolled into a safe harbor IRA established in their name — typically a conservative, low-yield account with its own fees.
• Over $7,000: The participant's money stays in your plan until they affirmatively move it.

That $7,000 ceiling is itself a SECURE 2.0 change — it rose from $5,000 for distributions made after December 31, 2023. Many small plans adopted the higher limit operationally the moment their recordkeeper supported it, which matters for the amendment deadline discussed below.

Force-outs exist for good reasons. Terminated participants with tiny balances still count toward your participant tally (which can trigger the audit requirement for larger plans), still generate statements and notices, and still show up in your ERISA bond and fiduciary responsibilities. Sweeping them out keeps the plan clean.

The problem is what happens on the other end. Safe harbor IRAs are where small balances go to die: parked in money-market-style investments, nibbled by maintenance fees, and frequently forgotten entirely. A departing employee who gets cashed out at $900 usually spends it. One who gets swept to a safe harbor IRA at $4,000 often loses track of it. Either way, the retirement system leaks — an estimated $92 billion a year by one widely cited EBRI figure.

What Auto-Portability Actually Does​

Auto-portability closes the loop. Instead of the story ending in a safe harbor IRA, the system keeps watching. When the former employee shows up as a participant in a new employer's 401(k), the mechanism automatically rolls their safe harbor IRA balance into that new plan — unless they opt out. The money follows the worker.

Section 120 of SECURE 2.0 made this commercially viable by adding a statutory prohibited-transaction exemption (Internal Revenue Code section 4975(d)(25)) that lets an "automatic portability provider" collect a fee for executing these transfers, subject to conditions on disclosure, fee reasonableness, and participant rights. The exemption took effect for transactions occurring on or after December 29, 2023, and the Department of Labor issued proposed regulations in January 2024 spelling out the operational guardrails: advance notices to participants, the right to opt out at any time, fee disclosures, and data-security obligations for providers.

The Portability Services Network​

In practice, auto-portability runs through an industry utility called the Portability Services Network (PSN), built on Retirement Clearinghouse's clearing technology and owned by a consortium of the largest recordkeepers: Alight, Empower, Fidelity, Principal, TIAA, and Vanguard. Together, PSN's member recordkeepers serve an estimated 63% of all defined contribution participants in the country. PSN reported that in roughly its first year of operations, more than 15,000 plan sponsors covering over 4 million active participants had adopted auto-portability.

Here is the participant-level flow once your plan opts in:

1. An employee leaves your company with a vested balance between $1,000 and $7,000.
2. After the required notices, the balance is rolled to a safe harbor IRA (same as today).
3. The network then periodically matches that IRA owner against participant records at member recordkeepers.
4. When a match is found — the person is now active in another employer's plan on the network — the participant is notified of the pending transfer and the fee.
5. If they don't opt out, the IRA balance rolls automatically into their new plan's account.

The participant pays a one-time transaction fee (disclosed in advance and capped by the exemption's reasonableness conditions); the employer generally pays nothing additional for the matching service itself.

Is It Mandatory?​

No. Auto-portability is an optional plan feature. Nothing in SECURE 2.0 forces you to adopt it, and if your recordkeeper isn't part of the network, you may not even have the choice yet. But two things are converging in 2026 that put it on the small-employer agenda anyway:

1. Recordkeepers are switching it on. Several PSN members have been enrolling their plan clients on an opt-out basis — meaning your plan may already be participating unless you affirmatively declined. Check your service agreements and recent recordkeeper notices; do not assume the answer is no.
2. You have to amend your plan document by December 31, 2026 anyway. If your plan's operations have changed — the $7,000 force-out limit, auto-portability participation, or any other SECURE 2.0 feature — the amendment is where the paperwork finally catches up with reality.

The December 31, 2026 Amendment Deadline, Explained​

Since 2020, retirement plans have been operating under a stack of statutory changes — SECURE Act (2019), CARES Act (2020), and SECURE 2.0 (2022) — largely without formal plan document amendments. The IRS deliberately allowed this: in Notice 2024-2, it set a single consolidated amendment deadline of December 31, 2026 for most non-governmental qualified plans (collectively bargained plans ratified before SECURE 2.0's enactment get until December 31, 2028).

Three points that trip up small employers:

Operational compliance came first — the amendment is retroactive documentation​

You were never allowed to wait until 2026 to follow the rules. Required minimum distribution age changes, long-term part-time employee eligibility, mandatory Roth catch-up contributions for high earners — each took effect on its own statutory schedule, and your plan had to operate accordingly. The 2026 amendment memorializes, retroactively, everything you have been doing. The IRS's anti-cutback relief protects that retroactive amendment only if your operations actually matched what the amendment says. If your plan forced out $6,500 balances in 2024 but your document still says $5,000, the amendment fixes it; if your operations were inconsistent — some force-outs at $5,000, some at $7,000, no clear effective date — you have a compliance issue the amendment alone cannot paper over.

Optional features you adopted must be in the amendment too​

The deadline is not only about mandatory provisions. If you turned on any optional SECURE 2.0 feature — the higher force-out limit, auto-portability, self-certified hardship withdrawals, emergency personal expense distributions — the amendment must capture each one, with its actual operational effective date. This is why a records review has to precede the amendment: you need to reconstruct what changed and when in your plan's actual administration.

Pre-approved plan documents don't amend themselves​

Most small business 401(k)s run on a pre-approved document maintained by the recordkeeper or a third-party administrator (TPA). Your provider will typically send you an amendment package to sign. Two cautions: first, the sponsor — you — remains legally responsible for timely adoption, even if the provider is late; calendar the deadline yourself. Second, review the package rather than blind-signing it. The amendment should reflect the elections your plan actually made, and providers process thousands of these at once. A wrong checkbox on the force-out threshold or the auto-portability election becomes your operational-failure problem later.

A Decision Framework: Should You Adopt Auto-Portability?​

For most small employers, the honest answer is: if your recordkeeper offers it, there is little reason to say no. The costs fall on transferring participants (modest, one-time, disclosed), the fiduciary lift is a one-time review, and the benefit lands on exactly the people force-out provisions treat worst — your lowest-balance, often lowest-wage, former employees. Research on cash-out behavior consistently shows minority and lower-income workers cash out at higher rates, so this is also a quiet equity improvement in your benefits program.

Run through these questions:

• Is your recordkeeper a PSN member or connected to the network? If yes, ask whether your plan is already enrolled, on what consent basis, and what the participant transaction fee is.
• Does your plan even have a force-out provision, and at what threshold? Some small plans never adopted one. If you're adding or raising it (to $7,000), that's an amendment item with its own notice requirements.
• What does the fiduciary file look like? Adopting auto-portability is a fiduciary decision. Document that you reviewed the provider's fees, the disclosures participants receive, and the opt-out mechanics. A one-page memo in your plan file is enough for most small plans.
• Are your participant notices updated? Force-out and auto-portability both depend on notices reaching terminated employees. Bad addresses are the failure mode — which is a recordkeeping problem, addressed next.

The Recordkeeping Layer: Where This Actually Gets Done​

Every step of this process runs on records that live — or should live — in your books, not your memory.

Termination data feeds the whole machine. Force-out timing, notice delivery, and auto-portability matching all key off accurate termination dates and last-known addresses. If your payroll system, your plan's census file, and your HR records disagree about when someone left, the plan's administration inherits the mess. Reconcile the annual census file your TPA requests against your payroll ledger, not against memory.

Plan expenses deserve their own accounts. Recordkeeping fees, TPA charges, amendment fees (many providers bill separately for the SECURE 2.0 amendment package), and any per-head charges for terminated participants should be tracked in dedicated expense subaccounts. When your provider quotes a fee for the amendment, you want to see instantly what you already paid them this year and whether force-out sweeps are actually reducing your per-participant charges the way the pitch claimed.

Employer contributions need a clean audit trail. The amendment review is a natural moment to verify that matching and profit-sharing contributions posted to the plan reconcile to what your general ledger shows, period by period. Discrepancies found in 2026 are cheap to fix; the same discrepancies found during a DOL inquiry are not.

Deadlines are ledger events too. December 31, 2026 for the amendment; January 1, 2026 for operational compliance with the Roth catch-up rules for high earners; your plan year-end for the census. Businesses that treat compliance dates as calendar entries miss them; businesses that tie them to their monthly close process don't.

Your Pre-Deadline Checklist​

Between now and December 31, 2026:

1. This month: Email your recordkeeper or TPA. Ask (a) when your SECURE 2.0 amendment package will arrive, (b) whether your plan is enrolled in auto-portability and on what basis, and (c) your current force-out threshold as administered.
2. This quarter: Reconstruct your plan's operational history — which optional provisions you use and their effective dates. Reconcile census data against payroll.
3. Before year-end 2026: Review and sign the amendment. Confirm every election matches operations. File the executed amendment with your plan records, and document the auto-portability fiduciary review if you adopted it.
4. Ongoing: Keep terminated-employee addresses current, and route plan-related invoices through dedicated expense accounts so next year's review takes an hour, not a week.

Keep Your Plan Records as Clean as Your Ledger​

A 401(k) amendment deadline is ultimately a records problem: proving what your plan did, when, and that the paperwork matches. The same discipline applies to every corner of your business finances. Beancount.io brings plain-text accounting to that job — every transaction, fee, and contribution in a transparent, version-controlled ledger you can audit line by line, with no black boxes and no vendor lock-in. Get started for free and give your business the same audit trail you're about to give your retirement plan.