One Pipe: Why Saver's Match Payments Should Ride the Notice 2026-49 Rollover Rails
From 2027, Treasury will deposit Saver's Match contributions of up to $1,000 a year into retirement accounts. IRS Notice 2026-48 says how the money might be routed; two of its paths to employer plans are rollovers. Why they should use the Notice 2026-49 forms, identifier and data set — and one registration.
TrustRails Team
• Regulatory & Platform EngineeringStarting with the 2027 tax year, Treasury will deposit Saver's Match contributions of up to $1,000 a year into savers' retirement accounts — and the hardest unsolved problem is routing the money to the right account. IRS Notice 2026-48 describes how; Notice 2026-49, issued five days later, proposes standard rollover forms. Because several Saver's Match paths are literally rollovers, the two should be built as one system.
- maximum annual match
- $1,000
- first tax year
- 2027
- employer-plan routing paths under consideration
- 3
- set of rails needed
- 1
Source: IRS Notice 2026-48; SECURE 2.0 Act Section 103.
Adapted from the TrustRails white paper One Pipe, a companion to Rollover Rails. New to Notice 2026-49? Start with our explainer of the new rollover forms.
What is the Saver's Match?
Section 103 of the SECURE 2.0 Act replaces the nonrefundable Saver's Credit with a federal matching contribution. For tax years beginning after 2026, an eligible individual who contributes to a retirement plan or IRA can claim a match of up to 50 percent of the first $2,000 contributed, phased out with income. Unlike the credit it replaces, the match is not a tax reduction — it is money Treasury deposits into the saver's retirement account. Matches under $100 can be taken as a refundable credit instead.
The saver claims the match on a new Form 8880-A with their tax return and designates where it should go. That designation is where the operational difficulty begins.
How will Treasury route Saver's Match payments?
Notice 2026-48 says the payment mechanics are "still under development" and lays out the options Treasury is weighing:
| Destination | Method under consideration |
|---|---|
| Traditional IRA | The saver enters an IRA tracking number on Form 8880-A. Tracking numbers exist only for IRA providers registered with Treasury. Payment goes directly to the IRA. |
| Roth IRA | Same, except Treasury pays a conduit traditional IRA, which immediately transfers to the Roth IRA as a conversion. |
| Employer plan — Registration Path | Plans or recordkeepers register with Treasury. Treasury pays a conduit IRA, which immediately rolls over to the registered plan. |
| Employer plan — Automatic Match Path | Plans supply plan- and participant-level data, similar to SECURE 2.0 Section 120 auto-portability data, and Treasury pays the plan directly. |
| Employer plan — Rollover Path | The IRS gives the saver a Confirmation Number; the saver gives it to the plan; the plan sends identifying information to Treasury; Treasury pays a conduit IRA, which immediately rolls over to the plan. |
Three of the five methods run money through a Treasury conduit IRA, and in two of them it rolls over to a plan — a rollover Notice 2026-48 says "would be treated like any other rollover." Every method must identify a specific individual to a specific institution, move money to it, and rely on a registry of institutions willing to accept it.
Is the Saver's Match Rollover Path a Notice 2026-49 transaction?
Yes. Notice 2026-49 covers direct rollovers where at least one side is an employer plan and no more than one side is an IRA. A conduit IRA rolling into a 401(k) is squarely inside that scope, and the Rollover Path maps onto its five steps without modification:
| Notice 2026-49 step | Rollover Path event | Note |
|---|---|---|
| 1. Participant’s Rollover Request | Saver gives the Confirmation Number to the chosen plan | Form 8880-A plus the Confirmation Number already contain what Form 1 asks for |
| 2. Receiving Plan’s Request | Plan sends identifying information to Treasury | The Confirmation Number should be, or be embedded in, the RIN |
| 3. Distributing Plan’s Certification | Conduit IRA confirms amount, pre-tax character, identity | The distributing side is Treasury; certification can be automatic |
| 4. Receiving Plan’s Acceptance | Plan accepts and selects the transfer method | ACH or electronic platform |
| 5. Transfer | Conduit IRA rolls funds to the plan | Electronic, consistent with Executive Order 14247 |
Building it this way has three consequences:
- One intake. Plans and recordkeepers build one intake for IRA-to-plan rollovers instead of a general one plus a Saver's Match-specific one.
- No parallel data set. Treasury avoids inventing a second way to identify individuals and plans when Notice 2026-49 has just proposed one.
- Inherited protections. No full SSN in plan-facing messages, verification before funds move, and an audit trail generated as a byproduct of structured messaging.
Scale runs one way. The Notice 2026-49 protocol was designed for more than ten million participant-initiated rollovers a year. Saver's Match adds millions of small federal payments to that flow. A protocol built for the larger flow is the natural carrier for the smaller one; the reverse is not true.
One door for rollovers and federal match deposits
TrustRails implements the Notice 2026-49 procedure as structured plan-to-plan messages keyed to a single identifier — the same rails a conduit-IRA rollover would ride.
Why should Saver's Match use one registration, not three?
Notice 2026-48 contemplates IRA providers registering for tracking numbers, plans or recordkeepers registering under the Registration Path, and plans supplying auto-portability-style data under the Automatic Match Path. Notice 2026-49 encourages plans to publish their rollover submission information, and TrustRails has recommended a public registry of plans that adopt the standard procedures.
These are the same record. A plan or provider should register once: an IRA tracking number and a rollover routing entry should be two attributes of one registration. The Automatic Match Path should use the batch form of the Notice 2026-49 messages, with a distinct RIN per individual, so a recordkeeper supplying Saver's Match data uses the same structure it will use for Section 120 automatic portability once the DOL's final rule is issued. The Retirement Savings Lost and Found already collects plan contact data from the same population; a shared plan identifier across all of these would end duplicate reporting.
How can Treasury identify savers without sending their SSN?
Every Saver's Match path requires Treasury to tell a private institution whose money it is. Notice 2026-49 identifies a participant by full name, last four SSN digits and date of birth, then uses the RIN on all later correspondence — the forms never carry a full SSN between institutions. The same composite identifier, plus the Confirmation Number or IRA tracking number, should be used in every message Treasury sends to a plan or provider under section 6433. Treasury already holds the full SSN; every outward transmission is a harvesting opportunity for synthetic identity fraud.
The same structure answers a question Notice 2026-48 asked directly: what happens when a match is paid to an unintended account? A message chain keyed to a Confirmation Number gives Treasury and the plan an unambiguous record of what was requested, what was certified, and where the money went — exactly what is needed to find and reverse a misdirected payment.
Why does the timing matter?
Saver's Match applies to 2027 contributions, claimed on returns filed in 2028. Plans that build intake in 2027 on an interim data set will be reluctant to rebuild it in 2028. The Notice 2026-49 procedures, and any companion machine-readable schema, should be settled before the first payments are made — so the rollover rails are in place when the federal money starts to flow.
What should IRA providers, recordkeepers, and plan sponsors do now?
IRA providers
- •Decide whether you will accept Saver's Match contributions and register. Treasury has said more information for providers will come later in 2026.
- •Build intake so a Saver's Match deposit and a Notice 2026-49 rollover arrive through the same door, keyed to the same composite identifier.
Recordkeepers
- •Evaluate the Registration and Automatic Match Paths against the data you already hold for auto-portability. If you can supply Section 120 data, you can supply Saver's Match data in the same structure.
- •Prepare for Form 5500-series reporting of aggregate Saver's Match receipts and separate accounting of match dollars for hardship-distribution purposes.
Plan sponsors
- •Accepting the match directly requires a plan amendment (a discretionary amendment, with model language to come). Accepting a conduit-IRA rollover generally does not, if your plan already accepts rollovers.
- •Consider adding the model Saver's Match language from Notice 2026-48 to your 2027 annual notice. If your plan accepts the match directly, your SPD must describe it.
Frequently asked questions
What is the Saver's Match?
A federal matching contribution created by SECURE 2.0 Section 103 that replaces the nonrefundable Saver's Credit. For tax years beginning after 2026, eligible low- and moderate-income savers can receive a match of up to 50% of the first $2,000 they contribute — up to $1,000 a year — deposited by Treasury into their retirement plan or IRA.
When does the Saver's Match start?
It applies to contributions made in the 2027 tax year, claimed on returns filed in 2028. Savers claim it on the new Form 8880-A and designate where it should be deposited. Matches under $100 can be taken as a refundable credit instead.
How will Saver's Match payments reach a 401(k) plan?
Notice 2026-48 describes three paths under consideration for employer plans: a Registration Path, an Automatic Match Path, and a Rollover Path. Two of them — Registration and Rollover — have Treasury pay a conduit IRA that immediately rolls the money over to the plan. Treasury says the payment mechanics are still under development.
Is a Saver's Match rollover from a conduit IRA a normal rollover?
Yes. Notice 2026-48 states that a rollover from the Treasury-established conduit IRA to a plan would be treated like any other rollover. That places it inside the scope of Notice 2026-49, which covers direct rollovers where at least one side is an employer plan and no more than one side is an IRA.
Does a plan need an amendment to accept the Saver's Match?
Accepting the match directly requires a discretionary plan amendment, for which Treasury has said model language will follow. Accepting a rollover from a conduit IRA generally does not, if the plan already accepts rollovers.
Will Saver's Match messages include a full Social Security number?
They should not need to. TrustRails recommends that every message Treasury sends to a plan or provider use the Notice 2026-49 composite identifier — full name, last four SSN digits and date of birth — plus the Confirmation Number or IRA tracking number. Treasury already holds the full SSN; it has no reason to travel outward.
TrustRails builds infrastructure for direct trustee-to-trustee retirement plan rollovers and has implemented the Notice 2026-49 forms and five-step procedure as structured electronic messages. Our formal comment letters on Notices 2026-48 and 2026-49 and the full white paper are available on request — talk to us.
For general information only; not legal, tax, or investment advice. Notices 2026-48 and 2026-49 are proposed or developing guidance and do not describe the final position of Treasury, the IRS, or the Department of Labor.