Employer payroll taxes are not a fixed percentage of wages. They are a cost curve that shifts within the year, across states, and across your wage distribution. Growth-stage companies that budget a flat addition to gross wages routinely hit mid-year cash-flow surprises, and the pattern is preventable.
The flat-percentage assumption is the most expensive mistake in payroll budgeting
Ask a finance leader at a growth-stage company how they budget for employer payroll taxes, and most will describe some version of the same shortcut. Take gross wages, add a flat percentage, and call it the employer tax line. It is fast, it fits neatly into a spreadsheet, and it is wrong in a way that compounds as headcount grows.
The shortcut fails because employer payroll taxes are not proportional to wages. They are capped. The employer Social Security tax is 6.2% of wages, but only on the first $184,500 an employee earns in 2026, per IRS Topic No. 751. Once an employee crosses that threshold, the employer stops owing Social Security tax on that person for the rest of the year. Medicare works differently. The employer Medicare tax is 1.45% with no wage cap at all, applied to every dollar an employee earns, per IRS Topic No. 751. Employers must also withhold an Additional Medicare Tax of 0.9% on an employee's wages above $200,000 in a calendar year, though this additional amount carries no employer-side match, also per IRS Topic No. 751.
Layer in the Federal Unemployment Tax Act. FUTA applies to just the first $7,000 of each employee's wages per year, a wage base that has not changed since 1983, per IRS Topic No. 759. The standard FUTA rate is 6.0%, but employers who pay their state unemployment tax in full and on time in a state without a credit reduction receive a credit of up to 5.4%, bringing the net FUTA rate down to 0.6%, or up to $42 per employee per year, per IRS Topic No. 759. State unemployment tax, or SUTA, adds another layer of variation entirely, with wage bases and rates that differ by state and by employer.
This is why a $60,000-a-year employee and a $160,000-a-year employee do not produce proportional employer tax costs. The lower earner's wages stay below the Social Security wage base all year, so the employer keeps paying 6.2% on every paycheck. The higher earner's wages may still sit below that cap too, depending on the year, but both employees exhaust their FUTA and SUTA wage bases within the first few pay periods of January, after which the employer's obligation for those specific taxes drops to zero for that employee until the calendar resets. A flat percentage applied uniformly across the payroll ignores all of this structure.
In our work with growth-stage payroll teams, the flat-percentage assumption is the starting point for nearly every mid-year budget variance we help diagnose. Finance builds an annual plan assuming employer tax cost holds steady across twelve months, and then wonders why the January and February payroll runs consume more cash than the model predicted while October and November come in under budget. The rates were never mysterious. The problem is that a flat percentage cannot represent a system with three separate caps, each expiring on a different wage threshold, for every employee on the payroll.
The flat-percentage error is compounded by a second variable that most budgeting models treat as a footnote: the within-year timing of wage-base exhaustion.
Wage-base exhaustion creates a within-year cost curve that front-loads employer tax expense
Every wage base referenced above, the $184,500 Social Security limit, the $7,000 FUTA limit, and each state's SUTA limit, resets to zero on January 1. That reset is the mechanical cause of what shows up in practice as a first-quarter cash crunch. Call it the Q1 tax cliff. Because none of an employee's wages have accumulated yet in January, the employer owes the full rate on FUTA, SUTA, and Social Security for every dollar paid, up to each respective cap. By the third and fourth quarters, many employees, particularly higher earners, have already exhausted one or more of those caps, and the employer's per-paycheck tax obligation for that employee drops accordingly.
The practical effect is a cost curve, not a flat line. A company budgeting employer payroll tax as a single annual percentage applied evenly across every pay period will overstate its tax liability in the back half of the year and, more dangerously, understate its cash requirement in the front half. For a company that plans to make headcount investments early in the year, or that runs tight on operating cash in the first quarter for reasons unrelated to payroll, this timing mismatch can create a real liquidity problem even when the annual total was estimated correctly.
The FUTA and SUTA wage bases are small enough, $7,000 federally and typically well under six figures at the state level, that most employees exhaust them within the first one to three pay periods of the year if they are paid biweekly or more frequently. That means the heaviest concentration of FUTA and SUTA expense lands in January and February for nearly the entire workforce, every year, regardless of company size. The Social Security wage base takes longer to exhaust for most employees given its higher 2026 threshold of $184,500, but for higher-earning employees, typically in sales, engineering, or executive roles, that cap can be reached mid-year, after which the employer's Social Security obligation for that individual stops for the remainder of the year.
Companies that hire heavily in the fourth quarter compound the problem. A new employee hired in November starts the following January with a fully reset wage base, meaning the company's Q1 tax cliff the next year is larger than the prior year's Q1, not because rates changed, but because headcount grew right before the reset. A budget built on trailing annual averages will not catch this. A budget built on annual wages multiplied by a flat percentage will not catch it either, because it treats the calendar as irrelevant to the tax calculation.
AsureCentral accounts for wage-base exhaustion at the point of calculation, recalculating per-paycheck employer cost in real time as each employee's cumulative wages cross each cap threshold for Social Security, FUTA, and applicable state unemployment tax. That is a mechanical requirement of accurate payroll processing, not an optional reporting feature, because getting the timing wrong means either under-withholding or over-remitting on taxes that are legally capped.
Wage-base timing is a within-company problem, tied to your own payroll calendar and wage distribution. The next variable, multi-state exposure, introduces between-state variability that multiplies the complexity for any growth-stage company with distributed or remote headcount.
Multi-state payroll exposure turns a single tax estimate into a range, and most budgets use the low end
State unemployment tax is easy to underestimate because it looks, on paper, like a minor line item next to Social Security and Medicare. That assumption breaks down the moment a company adds an employee in a new state. SUTA is not a single national rate. Each state sets its own wage base and its own rate structure, and both vary substantially by jurisdiction, by an employer's experience rating, and by whether the employer is new to that state's unemployment system.
Washington state illustrates the range at the high end. For 2026, Washington's unemployment insurance taxable wage base is $78,200 per employee, up from $72,800 in 2025, the highest state wage base in the country, per the Washington State Employment Security Department. Washington's employer rate structure combines an experience-rating tax capped at 5.4%, a social cost tax capped at 1.22%, and a small Employment Administration Fund assessment of 0.02% to 0.03%, also per the Washington State Employment Security Department. A company headquartered in a state with a $7,000 or $10,000 SUTA wage base that hires its first remote employee in Washington, without updating its per-employee cost model for that state's substantially higher wage base, will materially underestimate the SUTA cost tied to that single hire.
This is the new-employer rate trap. States assign employers a standardized new-employer SUTA rate when they first register in that jurisdiction, rather than basing the rate on the specific employer's claims history from day one. Washington, for example, assigns new employers a rate based on 115% of their industry's average rate, subject to a statutory minimum around 1%, per the Washington State Employment Security Department. That new-employer rate can shift materially once the state has enough claims history to apply the employer's own experience rating, which means a growth-stage company with early turnover in a new state can see its SUTA rate move after the first experience-rating period, independent of anything happening in its home state.
What Asure sees in growth-stage companies expanding to a second or third state is a systematic undercount. The finance model uses the home-state SUTA rate and wage base as a proxy for every new hire, regardless of where that person actually works. A remote hiring strategy makes this worse, not better, because it removes the natural constraint that used to keep most employees in one or two states. A company with a single headquarters and a handful of field employees might reasonably tolerate a simplified SUTA assumption. A company hiring remote employees across eight or ten states cannot, because each state carries its own wage base, its own rate mechanics, and its own registration requirement.
The size of the miscalculation depends on which states are involved, which is exactly the point. There is no single national SUTA rate to plug into a spreadsheet, which means any budget that uses one number for state unemployment tax across a distributed workforce is, by construction, wrong for most of that workforce. The gap between the assumption and the actual liability grows every time the company adds a state, which is precisely when growth-stage companies are least likely to revisit the budgeting model, because hiring is already consuming the finance team's attention.
Once the three structural variables, the flat-percentage assumption, wage-base timing, and multi-state rate variance, are understood individually, the practical question becomes how to build a budget model that accounts for all three without requiring a tax attorney for every headcount plan.
A defensible employer payroll tax budget uses three inputs, not one
A single percentage cannot represent a system with three independent caps and fifty different state rate structures. A defensible budget replaces that single number with three inputs, each addressing one of the structural variables described above.
The first input is a per-employee annual cost estimate segmented by wage band, not a single company-wide average. Wage-base caps affect a $50,000 earner and a $220,000 earner differently, because the higher earner exhausts FUTA and SUTA within days of the calendar reset and may cross the Social Security wage base mid-year, while the lower earner's employer tax obligation for Social Security continues at the full 6.2% rate all year. Segmenting by wage band, rather than averaging across the whole payroll, captures that asymmetry instead of smoothing it away.
The second input is a within-year cost curve that maps each employee's expected wage-base exhaustion dates rather than assuming a flat monthly run rate. This is the input that catches the Q1 tax cliff before it shows up as an unplanned cash draw. Knowing that January and February will carry a heavier employer tax load than October and November is not a forecasting nuance. It is a direct consequence of how FUTA, SUTA, and Social Security wage bases reset on the calendar.
The third input is a state-by-state SUTA rate assumption for any employee working outside the company's primary state, using each state's new-employer rate as the conservative default until the company has enough claims history in that state to know its actual experience-rated cost. This is the input most growth-stage companies skip entirely, defaulting instead to their home-state rate as a stand-in for every location.
Compare that three-input model with the single-percentage approach it replaces. The three-input model takes more setup, because it requires wage-band data, a payroll calendar mapped to wage-base thresholds, and a per-state rate table. What it produces in exchange is a budget that holds through the year instead of one that looks accurate in the aggregate and wrong in every individual month.
Payroll software can automate the first two inputs in real time, since both depend on data the payroll system already processes every pay period. AsureCentral surfaces employer cost reporting that reflects wage-band segmentation and within-year cost curve data in a connected dashboard view, so finance teams can model headcount scenarios without rebuilding the tax math by hand each planning cycle. The third input, state-by-state SUTA assumptions, still requires a one-time state registration and rate lookup for each new jurisdiction, a task Asure's compliance support can help growth-stage teams work through directly. For companies without deep in-house payroll tax expertise, AsureWorks offers the same underlying platform as a managed service, a PEO alternative with no co-employment where the client remains the employer of record, so building the three-input discipline does not require hiring a payroll tax specialist from scratch.
Bottom line
Employer payroll tax burden is non-linear. Three structural variables, the flat-percentage assumption, within-year wage-base timing, and multi-state SUTA variance, are the specific, nameable mechanisms that cause growth-stage payroll budgets to break, not hidden or unknowable rates. The fix is not a better guess at a single percentage. It is replacing that percentage with a three-input model, wage-band segmentation, a within-year cost curve, and a state-by-state SUTA assumption, before your next headcount plan cycle. The cost of upgrading the model is smaller than the cost of a single mid-year cash-flow surprise. Asure's payroll tax management support is built to make the three-input model the default rather than a manual exercise. Talk to an Asure expert to work through the curve for your own payroll before you build your next budget.
Related questions
How much does a $20 an hour employee actually cost an employer in payroll taxes?
At $20 an hour, roughly $41,600 a year, the employer owes 6.2% for Social Security all year, since that wage stays well under the $184,500 2026 wage base, plus 1.45% for Medicare on every dollar, per IRS Topic No. 751. FUTA adds up to $42 for the year, the net 0.6% rate applied to the first $7,000 of wages, per IRS Topic No. 759. State unemployment tax adds a further amount that depends entirely on the state of employment, and the FUTA and SUTA portions front-load into the first pay periods of the year rather than spreading evenly across twelve months. Asure's payroll tax specialists can work through a state-specific figure for this wage level with you.
What percentage of payroll goes to employer payroll taxes?
There is no single fixed percentage, because the answer depends on wage level, pay period timing, and state of employment. The federal floor is 7.65% for combined employer Social Security and Medicare, but that number excludes FUTA and the state unemployment tax that every employer also owes, and it says nothing about how the cost concentrates in the first quarter as wage bases reset. Treat any single blended percentage as a rough planning placeholder, not a budgeting input.
Do employers pay the same payroll tax amount for every employee?
No. Two structural factors create the variation. Wage-base caps mean higher earners exhaust FUTA, SUTA, and eventually Social Security earlier in the year, which reduces the employer's per-dollar tax cost for that person in later quarters. State of work location determines the SUTA rate and wage base, so a remote employee in a high-wage-base state like Washington, at $78,200 for 2026 per the Washington State Employment Security Department, costs more in state unemployment tax than an identically paid employee in a state with a lower wage base. This is the core reason a single average employer tax rate is unreliable for budgeting.
What is the employer payroll tax cost per paycheck?
Per-paycheck employer tax cost depends on pay frequency, year-to-date wages, and state, not just the gross amount of that specific paycheck. A biweekly paycheck issued in January carries a higher employer FUTA and SUTA cost than the same employee's paycheck in October, because the wage bases for those taxes may already be exhausted by the third quarter. AsureCentral's payroll reporting tracks this at the pay-run level, so finance teams see the actual obligation for each pay run rather than an averaged estimate.
How should a small business estimate payroll taxes for budgeting purposes?
Use the three-input model instead of a single national average. Segment employees by wage band since wage-base caps affect earners differently, map the within-year cost curve so the first-quarter tax concentration does not surprise the cash plan, and apply a state-by-state SUTA assumption using each state's new-employer rate as the conservative starting point. Treat any single commonly cited percentage as a starting placeholder only. The AsureCentral platform keeps wage-band and payroll tax data in one connected system, so a finance team can work through the wage-band and cost-curve model before payroll runs, not after.
