Supplemental Wage Withholding: Where Payroll Platforms Break

Every November, a quiet test hits payroll platforms. Annual bonuses, spot awards, and holiday commissions all post within a few weeks of each other. Most of them process without incident. A few produce a support ticket that begins, “Why did my bonus get taxed so much?”

That ticket reaches your customer’s payroll admin first, then your support team, then your roadmap. This post is about why the ticket exists, and what it says about how a platform handles tax.

How Supplemental Wage Withholding Works: Federal Flat Rate vs. Aggregate Method

At the federal level, employers may use a flat 22% rate on supplemental wages up to $1 million for the year. Above $1 million, a mandatory 37% rate applies, even if the employee has submitted a Form W-4 claiming exemption from withholding (Treas. Reg. § 31.3402(g)-1; see also IRS Publication 15). The flat rate is optional. The alternative is the aggregate method: combine the supplemental and regular wages for the pay period, withhold as if the total were one regular payment, then subtract the tax already withheld on the regular wages.

So even federally, “22%” is one branch of a decision, with a threshold and a mandatory override attached. It is not a constant.

State Supplemental Wage Withholding Rates and Rules in 2026

The federal rule has two methods, one threshold, and one mandatory rate. State and local rules are where the variety lives. EY’s 2026 survey of state withholding rates (January 12, 2026) is a useful illustration. It shows that “the supplemental rate” is a different question in almost every state:

• Different flat rates. Supplemental rates range from 1.5% in North Dakota to 11.70% in New York. Others include Oregon at 8%, Minnesota at 6.25%, and Nebraska at 3.5%.
• Different rates by payment type. California withholds 10.23% on bonuses and stock options and 6.6% on other compensation such as overtime, commissions, sales awards, and vacation pay. The same dollar amount is withheld differently depending on how the payment is classified.
• Rates that depend on the employee. Wisconsin allows a flat rate that varies by the employee’s annual gross salary, with four tiers from 3.54% to 7.65%. West Virginia directs employers to an annual table. Vermont uses 30% of the federal income tax withheld, and 6% for payments under a nonqualified deferred compensation plan.
• Different rules about how the payment is paid. New York offers the flat 11.70% only when supplemental wages are stated separately and income tax is also withheld from regular wages. If the employer pays supplemental wages with regular wages and does not specify the amount of each, it must withhold as if the total were a single regular payment. Arkansas, similarly, applies its 3.9% treatment when bonuses are paid at the same time as regular wages.
• Local layers. In New York, the supplemental rate is 4.25% for New York City residents, 1.95975% for Yonkers residents, and 0.50% for Yonkers nonresidents. Maryland’s 6.5% is plus the applicable local rate, and the highest local rate is 3.3%.
• Sources that disagree. Ohio’s statute sets the supplemental rate at 3.5%, but the Department of Revenue says on its website that the rate is 2.75%. Iowa’s administrative code says 6%, while the Department of Revenue told EY it will accept the lower statutory 3.8%.
• No supplemental rate at all. Connecticut has none. Many other states have a flat income tax or use their regular formula, so there is nothing to look up and the platform still has to know that.
• Rates that keep moving. EY’s chart flags many 2026 changes. Nebraska’s supplemental rate and North Carolina’s changed for 2026. Ohio’s changed as well.

Then add the situations real payrolls produce:

• Off-cycle runs. Bonuses are often paid in a separate run. The platform has to know whether the payment is stated separately from regular wages, because several states’ rules turn on that.
• Multi-state employees. A bonus for an employee who lives in one state and works in another has to be sourced correctly before any rate applies.
• Year-to-date tracking. The $1 million threshold is a running total for the year. A platform that cannot accumulate supplemental wages per employee cannot apply the 37% rule reliably, which matters most for executive and equity-related pay.
• Gross-up bonuses. When an employer wants a specific net amount, the platform works backward through every applicable tax. That calculation is only as good as the forward calculation underneath it.

None of this is exotic. It is ordinary Q4 payroll.

Bonus Tax Withholding Errors: What Employees and Payroll Admins Experience

Your direct customer is a platform. Their customer is an employer. The person who feels a withholding error is an employee, on the day the largest paycheck of the year arrives.

1. The employee sees a withholding amount that looks wrong and asks HR.
2. HR asks the payroll admin.
3. The payroll admin has to work out whether the platform made a mistake or the rule is working as designed. Often neither the admin nor support can tell.
4. If the platform did make an error, the correction may touch payroll records and year-end forms, and the problem is now bigger than one paycheck.

At each step, trust in your product drops. Payroll admins judge a platform by how it handles the unusual, high-visibility payments, and a bonus is the most visible of them.

What a Payroll Tax Engine Needs to Handle Supplemental Wages Accurately

Platforms that handle this season well share some design choices:

• Rules, not constants. The method, rate, and conditions are looked up by jurisdiction and payment type. “Bonus = 22%” is never hard-coded.
• Payment-type awareness. The platform distinguishes a bonus from a commission, severance, or equity pay, because the treatment can differ, as California’s two rates show.
• Cumulative tracking. Supplemental wages accumulate per employee for the calendar year, so threshold rules apply without manual intervention.
• Explainability. When an employee or admin asks “why this amount?”, the platform can show the method used and its inputs. A figure that cannot be explained produces a ticket even when it is correct.
• Update discipline. Changes arrive through a managed process, not from an engineer reading a state bulletin in December.

Building and maintaining that internally is possible. It is also a standing commitment: dozens of jurisdictions, each changing on its own schedule, each needing tests. It is the kind of work many platforms choose to source from a dedicated tax engine, so their team’s time goes to the features customers choose them for. Symmetry Tax Engine handles supplemental wage methods across jurisdictions, so the platform can ask “what is the correct withholding for this payment?” and get an answer it can show its users. With the Symmetry Tax Engine MCP, those questions can be asked in natural language inside Claude, Cursor, ChatGPT, or your own AI agent, so a developer, a support rep, or an AI assistant can check a bonus calculation against the same tax logic the platform runs on.