IRS Notice 2026-49 proposes standard forms for plan-to-plan rollovers

IRS Notice 2026-49 would give the machinery for moving a 401(k) balance from one employer's plan to another a federal template: four model forms, a five-step process, electronic communication between distributing and receiving plans, less reliance on paperwork that participants carry between them, and common data standards meant to improve efficiency and protect participant information, as Tom Hawkins describes in a 401(k) Specialist column. The notice answers a SECURE 2.0 Act directive that Treasury supply sample forms to simplify, standardize, facilitate, and expedite rollovers to eligible retirement plans and trustee-to-trustee transfers from IRAs, and Hawkins calls it a welcome and constructive development that credits the agencies with taking on what he describes as one of the retirement system's longest-standing operational weaknesses.

That weakness is familiar to anyone who has tried to consolidate an old 401(k): Hawkins calls plan-to-plan roll-ins incredibly difficult and, from the participant's side, the Achilles Heel of the defined contribution system, a process he characterizes as cumbersome, inconsistent and often frustrating at the moment a worker is changing jobs.

Other financial plumbing solved comparable problems long ago: consumers move securities between brokerage accounts through ACATS, banks exchange funds across automated networks, and electronic payment systems clear trillions of dollars daily, while plan-to-plan retirement transfers still depend on manual reviews, institution-specific forms, paper checks, and procedures that vary from one recordkeeper to the next. Hawkins locates the cause in how the work gets scheduled: Washington issues regulations requiring recordkeepers to make substantial IT updates on tight deadlines, client-driven priorities compete for the same capacity, and because much of that work can be completed inside a single firm's own systems, it tends to be tackled first, leaving the shared-interface work as the one project no recordkeeper can finish alone and a durable reason for it to sit at the back of every queue at once.

The population that meets this boundary every year is not small: RCD's own reporting has put the number of participants who face a recordkeeper change or plan termination in a given year at an estimated 6.1 million, and workers who have already left the payroll are the ones most likely to be lost in the handoff. For them, the difference between a proprietary form and a common one is the difference between a completed rollover and a balance that stays where it was.

The choice of instrument matters as much as the content: four model forms and a five-step sequence compel nobody to rebuild a system; they give plan administrators and recordkeepers a shared target to build toward, and the data standards carry the most weight because the friction in this process sits at the seam between two firms' systems rather than inside either one, so a shared vocabulary is what allows that seam to be automated instead of narrated over the phone.

For the recordkeeping business, the interesting question is how far the agencies can push: this publication has argued that the recordkeeping tech stack is now the distribution battleground and whoever owns the workflow owns the plan relationship, and a federal move toward common data standards bends that logic at the margin because institution-specific forms and procedures create friction that favors the incumbent provider while a common template reduces it. That is a structural reading, not a stated position of any firm named in the notice.

What the notice does not settle, at least as the column presents it, is whether the forms would bind plan administrators or function as a safe harbor, how long implementation would take, or when the guidance moves from proposal to rule, and those details decide whether four model forms change behavior or become an optional shortcut that sits alongside the old process.

Treasury and the IRS are not writing on a blank page: SECURE 2.0 gave them the assignment precisely because plan-to-plan movement had resisted a market solution, and the column's account of why is the part worth holding onto, since the firms that would have to build the shared interface are the same firms whose near-term obligations run in the opposite direction and nothing in the notice, as described, changes the deadlines those firms already carry.

That makes the notice a test of whether a standard can take hold without a mandate behind it, and the question the proposal leaves open is whether four forms and a five-step process will do for plan transfers what ACATS did for securities transfers.