The Social Security Administration made it official in October: the 2027 Social Security wage base is $192,300. The OASDI tax rate itself isn’t changing — it stays at 6.2% for both the employee and the employer — but the ceiling on wages subject to that tax is moving up, and that single number quietly rewrites part of your payroll math starting with the first check of January.
If your workforce is entirely below the wage base, this announcement is background noise. But if you have executives, senior salespeople, physicians, engineers, or anyone else whose earnings crossed the old base in 2026, the change touches real money: theirs, through a longer stretch of the year with Social Security withholding, and yours, through the matching employer tax on every one of those additional dollars.
The good news for ADP Workforce Now clients, is that statutory limits like this one are generally maintained by ADP and applied automatically? The honest follow-up is that “generally applied automatically” and “verified correct for your specific setup” are two different standards, and year-end is exactly the moment to close that gap. Here’s who this change affects, what should happen on its own, what deserves a human set of eyes, and what it means for your 2027 budget. The verification steps live alongside everything else in the free Ignite HCM Year-End Checklist (ignitehcm.com/yearend-guide).
A quick grounding, because this limit behaves differently from most payroll numbers. Social Security tax applies to an employee’s wages from the first dollar of the year up to the wage base, and then stops. An employee who crosses the base mid-year sees Social Security withholding disappear from their check for the rest of the year, then restart with the first payroll of January. Medicare, by contrast, has no wage base at all and keeps going.
Two practical consequences follow. First, high earners are used to a visible bump in net pay partway through the year, and the timing of that bump will shift later in 2027 because the base is higher. Expect questions; the answer is a one-line explanation, not an error. Second, the limit is tracked per employer, which is why employees who changed jobs mid-year or who work for related companies create edge cases worth understanding. Those edge cases are where “automatic” can use some supervision.
The population affected is simple to identify: anyone whose 2027 Social Security wages will exceed the old base. For each of those people, more of their pay is taxed before the ceiling kicks in, at 6.2% on the employee side, matched at 6.2% by you.
That makes the impact easy to estimate at the top end. An employee who earns at or above $192,300 in 2027 will have Social Security tax applied to the full amount, and so will you as the employer. Multiply your count of employees above the base by the incremental taxed wages and the 6.2% match, and you have the budget line. For a company with a meaningful executive and senior-professional layer, this is not a rounding error; it’s a real labor-cost increase that belongs in the 2027 budget now, in November, while budgets are still being set, rather than surfacing as an unexplained variance in Q1.
ADP maintains statutory rates and limits across its platform, and the new wage base is exactly the kind of change the system exists to handle. In the normal course, the 2027 limit takes effect with 2027 check dates, withholding calculates against the new ceiling, and nobody has to key anything.
“Normal course” is carrying weight in that sentence. Automatic updates assume the rest of your configuration is standard: earnings codes correctly flagged as Social Security taxable, employees coded in the right company and tax profile, no manual overrides lingering from some long-forgotten fix. Most setups meet that bar. The ones that don’t tend not to know it, because an error in taxability coding doesn’t announce itself — it just quietly computes the wrong tax all year.
This is the part we’d put on your calendar for December and early January. The verification work includes items like:
Those are the headline checks; the complete verification sequence with timing is in the Ignite HCM Year-End Checklist (ignitehcm.com/yearend-guide). None of this is hard. All of it is the kind of thing that’s only easy before the first January payroll runs.
Don’t let the 2027 announcement distract from the nearer deadline: your 2026 Social Security wages are about to be reported on W-2s due February 1, 2027. If anyone’s withholding ran past the 2026 limit or stopped short of it — because of a manual check, a mid-year company transfer, or a taxability coding issue — that error is sitting in your year-to-date totals right now, and it’s fixable with an adjustment before the final payroll of the year.
After W-2s are produced, the same error means a corrected W-2 and potentially an amended employer return, because Social Security tax has an employer half, and the employer half is reconciled on your quarterly filings. A wage-base reconciliation for your high earners belongs on the November list for exactly this reason: it’s the difference between a December adjustment and a February project.
A typical version of this: a company acquires a smaller one mid-year and moves its few dozen employees into its ADP Workforce Now instance under a new company code. Several of the transferred employees are high earners who already crossed the wage base at the old company. Because the setup treats the new code as a fresh employer for tax tracking without addressing the successor situation, Social Security withholding restarts from zero for all of them.
Nobody notices until W-2 season, when a transferred executive asks why his Social Security tax is thousands of dollars higher than his offer letter math suggested. The unwinding touches a dozen or so employees, over-withheld tax and employer match that add up to well into five figures, and corrected forms and a filing cleanup that consume most of a February. A one-hour review of the acquisition’s payroll setup, against exactly this question, would have prevented all of it.
Mostly yes — the limit won’t bind for anyone, and ADP’s automatic update covers you. The one caveat: taxability coding errors on earnings codes hurt companies of every pay level, and the start of a new year is still the cheapest time to check them.
The new base applies to 2027 wages, meaning checks dated January 1, 2027 or later. Verify in two passes: a 2026 wage-base reconciliation for high earners before your final December payroll, and a calculation check on the first one or two payrolls of January.
Over-withholding that has to be refunded to employees, or under-withholding that becomes employer exposure, plus the matching employer tax either way — and if it’s not caught before filings, corrected W-2s and amended returns. The earlier it’s caught, the smaller every one of those numbers gets.
Statutory limit changes are bread and butter for our team of former ADP service professionals — exclusively ADP, which means we know where wage-base tracking goes sideways in ADP Workforce Now and how to check it fast. We run wage-base reconciliations for your high earners, review taxability setup, verify your first 2027 payrolls, and put the budget impact in writing for your finance team. No ticket number, no waiting on hold — one dedicated consultant who’s answered this exact question before. We’ve got you.
Year-end is won in November, not January. Grab the free Ignite HCM Year-End Checklist (ignitehcm.com/yearend-guide) — or REQUEST A CONSULTATION (ignitehcm.com/solutions/compliance) and we’ll run it with you.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not tax or legal advice — confirm specifics with your licensed advisor or ADP representative.
