Roth catch-up contributions 2027: fix this before December
The SECURE 2.0 good-faith transition period closes with plan years after Dec. 31, 2026, which makes this the last quarter to align payroll, plan documents, and high-earner messaging.
Roth catch-up contributions 2027 will not arrive as a legal notice. They will arrive as a slightly smaller January net paycheck for your senior individual contributors, executives, and pre-retirees. SECURE 2.0's mandatory Roth catch-up rule has been operating under an IRS good-faith transition period, and that period closes for plan years beginning after Dec. 31, 2026. Whatever is not configured, reconciled, and explained by the end of this year becomes a rewards credibility problem rather than a compliance footnote.
What Section 603 actually requires
Under Section 603 of SECURE 2.0, catch-up contributions must be made on a Roth basis for any participant whose prior-year Social Security wages from that employer exceeded an indexed threshold, originally set at $145,000. The IRS issued final regulations in September 2025 and allowed a good-faith transition window that ends with plan years beginning after Dec. 31, 2026. Practically, that means 2026 wages determine 2027 treatment, and the indexed figure in effect should be confirmed against the current IRS notice before any communication goes out.
Two design details matter more than the headline. First, the test is employer-by-employer on prior-year Social Security wages, not household income and not total compensation across a career. Second, higher 2026 contribution limits mean the rule touches more dollars, not just more people. Even a stable affected headcount can see a materially larger share of deferrals shift from pre-tax to Roth.
If your highest earners learn about this from a smaller January paycheck instead of from HR, a neutral tax rule becomes a perceived pay cut.
Where the identification gaps show up
The eligibility test sounds mechanical until you run it across a real payroll estate. Mid-year hires have no prior-year wages with the current employer, which can exempt a very highly paid new executive while a longer-tenured colleague earning less is captured. Multi-entity payrolls raise the question of which employer's wages count. Acquisitions and payroll platform migrations frequently break the wage history the test depends on.
This is where HR, payroll, and the recordkeeper need to agree in writing. A single eligibility list that all three parties have reconciled is the only defensible artifact. If payroll flags one population and the recordkeeper flags another, the mismatch surfaces in January as rejected contributions, corrective distributions, or deferrals that silently stop. None of those outcomes are easy to explain to a 58-year-old vice president trying to maximize retirement savings.
Why the perceived value problem makes this riskier
WTW reported in December 2025 that employee understanding of benefits reached roughly 80% while satisfaction fell to a new low, findings picked up by BenefitsPro and SHRM. Read those two numbers together and the implication is uncomfortable. Comprehension is no longer the constraint. Perceived value is. Employees know what they have and think less of it.
Timing compounds the exposure. Mercer data reported by WorldatWork in May 2026 found actual 2026 pay increases trailed projected budgets. So the same senior population absorbing a tax-timing change in January is doing so in a year when the raise already underdelivered. A neutral rule landing on an irritated population reads as a pay cut unless someone gets ahead of it.
Three deliverables to close before December
First, produce the reconciled eligibility list. Pull 2026 Social Security wages by employer entity, apply the indexed threshold, and have payroll and the recordkeeper sign off on the same file. Document the treatment of mid-year hires, transfers between entities, and anyone acquired during the year.
Second, enable and test a Roth source in payroll, and confirm the plan document and any required amendment support it. Testing means running a live paycheck calculation for a sample affected employee, not confirming that a checkbox exists. Also decide in advance how the system behaves if an eligible employee has elected pre-tax catch-up: does it convert automatically, or does the contribution fail?
Third, write a targeted communication, not an all-staff email. The affected group is small, senior, and financially literate, and it deserves a message that names the change as a shift in tax timing rather than a reduction in pay. Show the net paycheck impact with real numbers, explain that Roth contributions grow tax-free, and give people a named contact. Advisory explainers from Fidelity, Schwab, and others can support the message, but the source employees trust on their own paycheck is HR.
Treat it as rewards delivery, not filing
The compliance obligation here is narrow and well documented. The rewards obligation is broader. Total Rewards owns the moment an employee looks at a paycheck and forms a judgment about whether the company is on their side. A change that was legislated in 2022 and finalized in 2025 should not be discovered by a plan participant in a payroll portal in January 2027.
Build the December checkpoint into the same cadence you use for open enrollment confirmations and merit letters. The affected population is your most retention-sensitive segment, and the cost of a five-minute conversation now is far lower than the cost of a defensive one later.
