IRS Notice 2026-49 Explained: The New Standardized Rollover Process (and Why It Looks Like Payment-System Engineering)
The IRS has proposed optional sample forms and a five-step, plan-to-plan procedure for direct rollovers. Here is what the Notice actually says, what is proposed versus final, and why the procedure is instantly recognizable to anyone who has built payment infrastructure.
TrustRails Team
• Regulatory & Platform EngineeringIRS Notice 2026-49, issued August 12, 2026, proposes optional sample forms and a standardized five-step procedure for direct rollovers between employer retirement plans and IRAs, under Section 324 of the SECURE 2.0 Act. The forms are not mandatory, and no safe harbor currently exists for using them — but the IRS is considering safe harbors, an electronic-transfer requirement, and eliminating rollover checks mailed to participants. Public comments are due October 23, 2026.
That's the summary. Here's what is actually in the Notice, what it means for plans and custodians, and why — to anyone who has built payment infrastructure — the IRS's proposed procedure is instantly recognizable as a classic engineering pattern.
What is IRS Notice 2026-49?
Notice 2026-49 is guidance from the Treasury Department and the IRS implementing Section 324 of the SECURE 2.0 Act of 2022, which required the IRS to develop sample forms and procedures to "simplify, standardize, facilitate, and expedite" rollovers between retirement plans.
The Notice responds to a problem documented for over a decade. A 2013 GAO report found the rollover process inefficient because plans lack uniform procedures. A 2024 GAO follow-up found that nearly one-third of participants still receive paper checks they must forward to the receiving plan themselves — checks that get lost, delayed, and leave retirement savings out of the market in the meantime.
The Notice covers direct rollovers where at least one side is an employer plan — for example, a 401(k) to an IRA, or an IRA into a new employer's plan. It does not cover IRA-to-IRA transfers, which already run through the ACATS electronic system.
How does the proposed five-step rollover process work?
The Notice proposes four sample forms and a five-step sequence:
- 1The participant submits a rollover request to the receiving plan (Form 1), authorizing it to act on their behalf.
- 2The receiving plan assigns a unique Rollover Identification Number (RIN) and sends the request to the distributing plan (Form 2), listing the transfer and communication methods it can accept.
- 3The distributing plan verifies the request — identity, distribution eligibility, spousal consent — then certifies the rollover (Form 3), including a breakdown of the account by contribution type (pre-tax, Roth, after-tax).
- 4The receiving plan accepts (Form 4) and selects the transfer method, providing account details.
- 5Only then does the money move.
Two design choices stand out. First, the participant steps out of the middle: after Form 1, everything is plan-to-plan. Second, the forms carry an explicit instruction — "Do Not Transfer Rollover until Instructed." Funds move only after both institutions have confirmed readiness.
Why engineers recognize this pattern: the two-phase commit
In distributed computing, a two-phase commit is the standard protocol for making sure a transaction between two systems either fully happens or doesn't happen at all — never half-happens. Phase one: both sides confirm they're ready. Phase two: the transaction executes. It's the reason a bank transfer doesn't debit one account without crediting the other.
The IRS's five-step procedure is a two-phase commit expressed as paperwork. Form 3 is the sender's "ready." Form 4 is the receiver's "ready." The transfer is the commit — and it's forbidden until both confirmations exist.
At TrustRails, this is not an abstract observation. We built our rollover settlement platform on exactly this pattern — before the Notice was published:
Dual confirmation, enforced in code. Both custodians must affirmatively agree before a transfer can advance. In our system, "Do Not Transfer until Instructed" isn’t a line on a form a busy operator might miss — it’s a machine-checked gate that rejects any attempt to move funds early.
One identifier on every message. The Notice’s RIN exists so plans can coordinate a rollover without repeatedly transmitting Social Security numbers. Our platform keys every event in a transfer’s lifecycle to a single transfer identifier for the same reason.
A structured contribution-type breakdown. Form 3 transmits the pre-tax/Roth/after-tax composition of the account. We carry that same breakdown as structured data at settlement, with an integrity check that rejects any breakdown whose parts don’t sum to the whole.
Transfer-method matching. The Notice has both plans select and match a method (ACH, electronic platform, or other). We capture ACH, wire, and check details as validated, encrypted settlement instructions inside one coordinated workflow.
A step-by-step audit trail. The Notice expects encryption in transit and at rest, citing Department of Labor cybersecurity best practices. Every state transition in our system is an append-only, timestamped event, with personal data encrypted at rest.
When a federal agency and an engineering team independently converge on the same architecture, that's evidence the architecture matches the problem.
Are the new IRS rollover forms mandatory?
No. The forms are optional. Plans may use them, modify them, build them into their own systems and APIs, or ignore them entirely. The Notice explicitly encourages programming the forms "into an API or for use on a clearinghouse or other electronic platform."
Is there a safe harbor for using the Notice 2026-49 forms?
No — not currently, and the Notice says so directly. However, the IRS is considering future guidance that would create safe harbors: for example, allowing a receiving plan that uses the standardized forms to reasonably conclude, absent contrary evidence, that the distributing plan is tax-qualified and the rollover is valid.
Under existing regulations, receiving plans already make a "reasonable conclusion" determination about incoming rollovers. Standardized, verified, plan-to-plan data of the kind the Notice describes supports that determination today — but no plan or platform can claim a Notice 2026-49 safe harbor, because none exists yet.
Already built for a two-phase rollover
Dual custodian confirmation, a verified contribution-type breakdown, and an auditable record of every step — the pattern the Notice describes, running today.
What bigger changes is the IRS considering?
Section IV of the Notice lists changes under consideration that would go well beyond optional forms:
- •Removing the rule that lets rollover checks be mailed to participants (Treasury Regulation § 1.401(a)(31)-1, Q&A-4)
- •Requiring electronic transfers, or paper checks sent only plan-to-plan
- •Creating safe harbors tied to the standardized forms and procedures
- •Declaring certain practices impermissible, such as requiring Medallion Signature Guarantees — and potentially barring a distributing plan from refusing an electronic transfer when both plans can support one
None of these is final. The IRS has asked for public comment by October 23, 2026 (docket IRS-2026-0100 at regulations.gov), including specifically on how "technology standards, platforms, or automated solutions" could simplify the rollover process — and what implementation timelines the industry would need.
TrustRails intends to file a comment before the deadline. Our core recommendation: any future safe harbor should attach to the standardized data and verification protocol — however implemented, including via API or platform — rather than to the paper forms alone.
What should plans, custodians, and recordkeepers do now?
The forms are optional today, but the direction is unmistakable: coordinated plan-to-plan verification, electronic transfer, minimized PII, and an auditable record of every step. The open question is timing, not destination — and history suggests the destination arrives faster once a standard exists. IRA-to-IRA transfers were once just as fragmented; they became fast and uniform when FINRA made the ACATS protocol mandatory for its members.
Practical steps worth taking now:
Map your current rollover workflow against the five-step procedure. Where does your process rely on the participant as courier? Where would Forms 2–4 data come from in your systems?
Inventory your electronic transfer capability. If guidance requiring electronic transfer arrives, "we can’t" stops being an answer — especially if capability via a third-party platform counts.
Consider filing a comment. Implementation timelines will be shaped by whoever shows up in the docket before October 23.
Watch the safe harbor. If it materializes, early adopters of the standardized protocol will already have their processes, integrations, and operational learning in place while others start from zero.
Frequently asked questions
When was IRS Notice 2026-49 issued?
August 12, 2026.
What law does Notice 2026-49 implement?
Section 324 of the SECURE 2.0 Act of 2022, which directed the IRS to issue sample forms and procedures to simplify and expedite rollovers.
Does Notice 2026-49 apply to IRA-to-IRA transfers?
No. It covers direct rollovers where at least one side is an employer plan. IRA-to-IRA transfers are typically handled through ACATS.
Is there a safe harbor for using the Notice 2026-49 forms?
No. The forms are optional and the IRS states no safe harbor currently exists, though safe harbors are under consideration in future guidance.
What is a Rollover Identification Number (RIN)?
A unique identifier assigned by the receiving plan to a rollover request, included on all communications between plans to coordinate the rollover while minimizing transmission of the participant’s personal information.
Do the forms change the tax rules for rollovers?
No. Eligibility rules, required minimum distributions, and the tax treatment of rollovers are unchanged. The Notice addresses how direct rollovers are processed, not which distributions qualify.
When are comments on Notice 2026-49 due?
October 23, 2026, via regulations.gov docket IRS-2026-0100 or by mail to the IRS.
Can a plan be "compliant with Notice 2026-49"?
Not in any formal sense — the forms are optional proposals, and no safe harbor or requirement exists. A plan can align its processes with the Notice’s procedures, which may position it well if the proposals in Section IV are finalized.
TrustRails builds settlement infrastructure for retirement plan rollovers: both custodians confirm readiness, the contribution-type breakdown is verified, and only then does the money move — with every step recorded in an auditable trail. If you're a custodian, recordkeeper, or plan thinking through what standardized electronic rollovers look like operationally, talk to us.
This post is for general information and is not tax or legal advice. Notice 2026-49 is proposed guidance; consult counsel regarding your plan's obligations.