Average Payroll Tax: Rates, Costs, and Budgeting

For 2026, the employer and employee Social Security rates are each 6.2 percent up to the $184,500 wage base. Medicare is 1.45 percent each with no wage base limit. Employers also withhold 0.9 percent Additional Medicare Tax from an employee’s wages above $200,000, but there is no matching employer share of that additional tax. FUTA begins at 6.0 percent of the first $7,000 of covered wages, often reduced by a credit of up to 5.4 percentage points when requirements are met. State unemployment rates and wage bases vary by employer, state, history, and notices. Therefore, 7.65 percent is only the employer FICA component below the Social Security wage base, not a full payroll-cost estimate.

This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Employer FICA is employee-specific

Social Security stops at the annual wage base, while Medicare continues.

Additional Medicare is employee withholding

The employer starts withholding above $200,000 of wages paid to that employee and does not match the extra 0.9 percent.

FUTA is not simply 6 percent of all pay

It uses a $7,000 wage base, credit rules, deposit thresholds, and possible credit-reduction states.

State unemployment can dominate the variance

New-employer rates, experience ratings, wage bases, surcharges, and multiple states change cost.

Local employer taxes may apply

Head taxes, occupational taxes, transit assessments, paid-leave programs, and local payroll taxes vary.

Benefits are not payroll tax

Health, retirement, workers’ compensation, paid leave, and provider fees belong in a full labor-cost budget but not the tax rate.

Pretax treatment changes taxable wages

A benefit can reduce one tax base but not another, so apply plan-specific rules.

Owner and related-party wages need review

Entity classification and benefit rules can change tax and deduction treatment.

Deposits are not new expense

They clear previously recorded liabilities.

Averages can mislead cash planning

Model each employee by state, wage level, benefit election, and expected pay date.

Step-by-step workflow

1. List employees and states. Capture annual wages, pay periods, work locations, unemployment accounts, and benefit elections.
2. Calculate employer Social Security. Apply 6.2 percent to projected covered wages up to each employee’s 2026 wage base.
3. Calculate employer Medicare. Apply 1.45 percent to projected covered wages without a wage cap.
4. Calculate FUTA. Apply the wage base, expected credit, credit-reduction risk, prior payments, and quarterly deposit rules.
5. Apply state unemployment. Use the official employer rate notice, wage base, surcharges, and employee location.
6. Add other employer assessments. Include paid leave, disability, local tax, workers’ compensation, and industry charges where applicable.
7. Model benefits separately. Add health, retirement, bonuses, leave, payroll service, and other labor costs without calling them payroll tax.
8. Build monthly cash timing. Forecast wages, employer costs, employee withholding liabilities, deposits, returns, and annual wage-base changes.
9. Reconcile actuals. Tie payroll registers, tax returns, agency rate notices, deposits, and the ledger to the forecast.
10. Refresh after changes. Update for hires, terminations, raises, bonuses, new states, rate notices, acquisitions, and law changes.

Worked example

An employee earns $80,000 in 2026 in a state where the employer’s unemployment cost is projected at $480. Employer Social Security is $4,960 and employer Medicare is $1,160, for $6,120 of employer FICA. Adding the state amount produces $6,600 before FUTA, local assessments, workers’ compensation, benefits, and payroll fees. Calling the entire cost 7.65 percent would understate it. For an employee above the Social Security wage base, the effective employer FICA percentage changes again because Social Security stops while Medicare continues.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Using 15.3 percent as employer tax. That combines employer and employee FICA below the wage base and is not the employer-only cost.
• Calling 7.65 percent the total. It excludes unemployment, local programs, benefits, and wage-base changes.
• Applying Social Security without a cap. Use the employee-level annual wage base.
• Matching Additional Medicare. The additional 0.9 percent is employee withholding without an employer match.
• Using a generic state rate. Use the employer’s official unemployment notice and correct state wage base.
• Expensing employee withholding. It comes from gross wages and becomes a liability.
• Ignoring credit-reduction FUTA. A state’s status can increase the net federal unemployment cost.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Assign one owner and one reviewer to the calendar. The owner prepares the source schedule and resolves open items; the reviewer tests identities, totals, rule references, filing status, and evidence. Record the date of the official guidance used because form pages and software menus can change during the filing season. If a rule is uncertain, document the question and escalate it before the deadline rather than placing an unsupported assumption in the final file. This short control list protects both accuracy and continuity when another bookkeeper, payroll specialist, or tax preparer takes over the work. Save the checklist with the return so next year’s team can see which controls were completed and which exceptions required follow-up.

Practical implementation notes

Employee tax model

Use one row per employee with state, wage, FICA bases, unemployment rates, local assessments, benefits, and monthly cash.

Rate-source file

Attach the current IRS publication and every state rate or wage-base notice used.

Quarterly forecast bridge

Explain differences from hires, terminations, bonuses, wage-base exhaustion, rate changes, and corrections.

Labor-cost view

Present wage expense, employer taxes, employee liabilities, benefits, insurance, and service fees as separate categories.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.