What Is Payroll? Process, 2026 Taxes, Cost & Who Owns It

I have put more than 250 people a year onto a payroll. In eight years of running high-volume hiring inside a large enterprise, the only HR mistake I ever watched reach a director inside an hour was a wrong paycheck.

Your team runs payroll every other week and it works. It keeps working right up until a misclassified worker, a state nobody registered in, or a bonus coded to the wrong earnings type turns an invisible process into a very visible one.

Payroll is the only HR process where being right 99 percent of the time counts as a failure. Release 400 payslips with four errors and you have not had a good run. You have four people who now check every line, a manager fielding questions they cannot answer, and a correction that has to touch the tax filing as well as the payment.

Most HR leaders price payroll as the salary line. It is not the salary line.

Translation: on a $33.85 hourly wage the employer is carrying $15.61 more per hour that payroll has to calculate, fund, remit, and report. That second number never appears on a payslip and it never appears in the salary a hiring manager quotes.

By the end of this guide you will be able to:

• Define payroll in one sentence you can put in a board paper tomorrow
• Run the nine steps of a payroll cycle, and name the two that prevent most errors
• Carry one employee from gross pay to net pay, and then to what that employee cost the company that period
• Quote the 2026 US payroll tax rates with the year and the cap attached to each one
• Benchmark your payroll spend against an independent number, not a vendor price card
• Say who is accountable for each of the ten decisions in the payroll cycle, and defend the answer to finance

HR Insights Lab approach: every figure here carries its year and its source. Every calculation is performed, not asserted. No payroll vendor is named, rated, or priced anywhere in this guide, because the moment an article about payroll cost quotes a per-employee price it has become the thing it was written to replace.

What Is Payroll? A Working Definition for HR Teams

Payroll is the end-to-end process of calculating what each employee earned in a pay period, withholding taxes and deductions from those earnings, paying the net amount, remitting the withheld money to the right agencies, and recording all of it. For an HR team it is a financial transaction, a compliance filing, and an employee experience event at the same time.

The word carries a second meaning, and it matters. Payroll names the list of people entitled to be paid, and the department that pays them. Someone who says “we have 4,000 on payroll” is using the noun; someone who says “payroll closes Tuesday” is using the process.

Payroll as a function covers the architecture: pay policy, tax registrations, worker classification, the earnings and deduction catalog. Payroll processing is the recurring cycle that runs inside that architecture, every week or every other week, without end.

Define payroll as an accounting function and you have handed it straight to finance. That definition is where HR loses the argument before it opens. Payroll is the system where HR decisions become money.

Here’s the difference:

Payroll has five working parts. Every later section of this guide expands one of them, in this order.

• Earnings. What was earned in the period, including overtime, bonus, shift differential, and commission. The distinction between basic wages and total earnings starts here, and getting it wrong bends every statutory calculation that keys off the base rate.
• Deductions. What comes out, pre-tax and post-tax. Sequence decides the tax outcome, so a deduction in the wrong bucket produces a wrong withholding, which is far harder to spot than a wrong deduction.
• Employer contributions. What the company owes on top of the wage. Budget this at zero and your headcount number is short by roughly a third.
• Remittances and filings. Where the withheld money goes, and by when. Late deposits carry statutory penalties that scale with how late they are, and nobody negotiates them down.
• The record. What has to be kept, and for how long. Retention periods differ by record type, and an audit tests the record you did not keep.

Payroll vs. Salary vs. Basic Wages: What Payroll Actually Includes

Three terms get used interchangeably in budget meetings and they are three different numbers. The gap between the first and the third is where headcount business cases fall apart.

Here’s the difference:

Basic wages are the contractual base rate, before anything is added or taken away. Most statutory calculations and many benefit formulas key off this figure, which is why an imprecise definition of it propagates quietly into everything downstream.

Gross pay is basic wages plus everything else earned in the period: overtime, bonus, commission, shift differential, allowances. Total payroll cost is gross pay plus the employer-borne layer, which the employee never sees.

Here is the same employee at all three numbers, across one year.

Layer	What it includes	The same employee
Basic wages	Contractual base salary only	$95,000
Gross pay	Base salary plus an $8,000 performance bonus	$103,000
Total payroll cost	Gross pay plus employer FICA ($7,880), unemployment tax ($500), employer benefit contribution ($14,000), and workers’ compensation premium ($900)	$126,280

The hiring manager quoted $95,000. The P&L absorbed $126,280. That is a 32.9 percent gap on one person, and it is the number finance was using the whole time.

Old way: budget headcount at salary and treat the rest as overhead somebody else owns. Lab Way: budget at total payroll cost from the first requisition, because that is the number the business spends.

Who Owns Payroll: Is Payroll an HR Function or a Finance Function?

Why Payroll Ownership Is Contested in the First Place

Here’s the deal:

Payroll inputs are HR data. Hires, terminations, promotions, leave, classification, benefit elections: every one of them originates in an HR system, and every one of them changes a payslip.

Payroll outputs are finance artifacts. A general ledger entry, a tax remittance, a cash-flow event with a bank cutoff attached to it.

Both functions hold a legitimate claim, and in most organizations neither holds full control. That is the real problem, and the argument about reporting lines is a proxy for a different argument nobody is having: who owns the handoff.

The Payroll Ownership Model That Actually Works

Here is the position, stated plainly. HR owns payroll data. Finance owns payroll money, and the handoff between them is a controlled process with a named owner, a published cutoff, and a written definition.

Stop arguing about the org chart and assign these ten decisions. Lift this table into your next slide and make two people sign it.

Payroll decision	Accountable	Responsible	Consulted	Why it sits there
Employee master data	HR	HR Operations	Payroll	The record of who exists, at what grade, in what location begins and ends in HR
Time and attendance approval	Line management	Managers	HR	The person who saw the work done is the only one who can attest to it
Earnings and deduction setup	HR	Payroll	Finance, Tax	Every pay code is a policy decision about how something is taxed and accrued
The payroll calculation run	Payroll	Payroll	HR	Execution belongs with the team that owns the system configuration
Funding and disbursement	Finance	Treasury	Payroll	Moving money is a treasury control, never an HR one
Tax remittance and filing	Finance	Payroll or provider	Tax adviser	The signature on a return is a finance signature
GL posting and reconciliation	Finance	Accounting	Payroll	The ledger is finance’s book of record
Statutory reporting	Finance	Payroll	HR, Legal	Filed under the employer’s tax identity, not its people function
Employee pay queries	HR	HR Operations	Payroll	The employee has an HR relationship, not a finance one
Audit response	Finance	Payroll	HR, Legal	Auditors test the filing, and the filing belongs to finance

Notice that HR is not accountable for six of the ten. A RACI with HR in every Accountable cell is not an operating model, it is a land grab, and the first finance reader to see it will say so.

What Breaks When Payroll Ownership Is Ambiguous

Four failure modes show up again and again, and they share one root cause. Each one is a handoff with no owner.

• A termination is processed in the HR system after the payroll cutoff. The person is paid for a month they did not work, and recovering that money is legally constrained in several states.
• A promotion effective date is entered differently in two systems. The back-pay calculation runs on the wrong base and nobody catches it, because both numbers look plausible.
• An employee moves to a new state and nobody registers the employer there. Withholding goes to the wrong jurisdiction from the first run.
• A benefit election change never reaches the deduction file. The employee keeps paying for coverage they dropped, and finds out months later.

How Payroll Works: The End-to-End Payroll Process in 9 Steps

Most published payroll processes blur two things that behave nothing alike. Separating them is the difference between debugging the right system and debugging the wrong one.

Here’s the difference:

Setup happens once. The cycle repeats forever. Most payroll disasters trace back to a setup decision made at go-live and never revisited, and a wrong pay code installed then produces a quiet, correct-looking error across thousands of payslips for years.

Payroll processing is the recurring half of that split. The nine steps below describe it, and steps 2 and 7 are the two that prevent most of what goes wrong in the other seven.

Here’s how to build it:

Of every control in that cycle, step 2 and step 7 are the two I would install first in any payroll team I took over. They cost nothing. Between them they catch most of what your employees would otherwise catch for you, which is the worst detection method available to anyone.

One artifact holds the whole cycle together. A payroll calendar is not a list of paydays: it is the input cutoff, the approval deadline, the run date, the funding date, payday, and the tax deposit due date, for every period in the year.

Two things make it non-trivial. Bank holidays move funding dates, and your deposit due dates follow the schedule the IRS assigned you under the lookback rules, which you do not get to choose.

How Payroll Is Calculated: Gross Pay to Net Pay, Worked Through

Every guide on this topic asserts the calculation. Very few perform it, and almost none carry it past net pay to the number an HR leader gets asked for.

Here is one employee, one biweekly period, both halves of the same two weeks.

How to execute:

How Payroll Is Calculated for a Salaried Employee

Take an employee on $78,000 a year, paid biweekly across 26 periods. Gross pay for the period is $3,000.00, and that is the last simple number in the sequence.

Line	Employee side	Employer side
Gross pay ($78,000 ÷ 26)	$3,000.00
Pre-tax 401(k) contribution, 6%	−$180.00
Pre-tax health premium, Section 125 plan	−$120.00
Wages subject to federal income tax	$2,700.00
Wages subject to Social Security and Medicare	$2,880.00	$2,880.00
Social Security, 6.2%	−$178.56	$178.56
Medicare, 1.45%	−$41.76	$41.76
Federal income tax (per Form W-4 and the IRS tables)	−$243.00
Post-tax life insurance premium	−$25.00
FUTA, 0.6% effective on the first $7,000		$18.00
SUTA at this employer’s experience rate, 2.7%		$81.00
Employer 401(k) match, 3%		$90.00
Employer health contribution		$480.00
Workers’ compensation premium		$30.00
Net pay	$2,211.68
Employer cost on top of gross		$919.32
Total cost of this employee, this period		$3,919.32

Two lines in that table deserve a second look. The wages subject to income tax are $2,700, and the wages subject to Social Security and Medicare are $2,880, which is a $180 difference on the same paycheck.

That difference is the traditional 401(k) contribution. It reduces federal taxable wages and it does not reduce FICA wages. The Section 125 health premium reduces both.

Not every pre-tax deduction reduces every tax the same way. A system configured on the assumption that they do will underwithhold quietly for years.

The federal income tax line is the one figure here you cannot memorize. It comes from the employee’s Form W-4 run against the IRS withholding tables, and it moves with filing status, dependents, and any extra withholding the employee entered. The $243 above is an illustration, and yours will differ for every person on your payroll.

Add state and local withholding where it applies. This example leaves it out to keep the arithmetic visible.

Old way: calculate to net pay and hand the rest to finance. Lab Way: every payroll calculation has two totals, what the employee receives and what the company spent, and HR should be able to produce both on request.

The single question I ask any team that tells me payroll is under control: can you produce both totals for one named employee for one period, right now? Most produce net pay in thirty seconds and the employer cost never.

How Payroll Is Calculated for an Hourly Employee

Hourly looks easier and is where the expensive errors live. Take an employee at $22.00 an hour who works 46 hours in a workweek and earns a $200 non-discretionary production bonus for that week.

The intuitive calculation: 40 hours at $22.00 is $880, six overtime hours at $33.00 is $198, plus the $200 bonus. Total $1,278.00. That number is wrong.

Under the FLSA, overtime is one and a half times the regular rate, and the regular rate includes the non-discretionary bonus. Total straight-time compensation is 46 hours at $22.00 plus $200, which is $1,212.00. Divide by 46 hours and the regular rate is $26.3478.

The overtime premium owed is half the regular rate for each of the six overtime hours: $79.04. Total due is $1,291.04. The gap is $13.04, for one employee, for one week.

Multiply $13.04 by the number of employees on a production bonus, then by the number of weeks since that bonus scheme started. That is your back-wage exposure, and it has been accruing the entire time.

One employee, one bonus, one recalculation. Now scale that to an organization carrying hundreds of distinct earnings types.

Translation: nearly half of large employers run more than a thousand distinct earnings and deduction codes. Every one of those codes is a rule about how something is taxed, accrued, or folded into the regular rate. A thousand pay codes is a thousand places for a calculation to be wrong, and the pay code catalog is the least-audited artifact in most payroll operations.

What Are Payroll Taxes? 2026 US Employer and Employee Payroll Tax Rates

Payroll tax gets treated as a constant in most budget models. It is not a constant. It is a set of annual parameters that reset every January, and several of them reset in ways your payroll system will never handle on your behalf.

Quote a rate without its year and its cap and you have published something with a twelve-month shelf life and no expiry date printed on it.

Payroll Taxes the Employee Pays

Four things come out of an employee’s gross pay under the tax heading. The first two are what everybody means when they say payroll taxes.

Employee-side tax	2026 rate	Cap or threshold
Social Security (OASDI)	6.2%	Applies up to the annual wage base, then stops
Medicare	1.45%	No cap, every dollar of wages
Combined employee FICA	7.65%	Up to the Social Security wage base
Additional Medicare Tax	0.9%	On wages above $200,000 in a calendar year, employee only, no employer match
Federal income tax	Per Form W-4 and the IRS withholding tables	No single rate; varies by employee
State and local income tax	Varies by jurisdiction	Several states levy none at all

The Social Security wage base is the parameter that moves. It resets annually and it is the most-cited number in this entire topic, which is why this section carries both the current figure and the one it replaced.

Translation: every employee earning above the base gets a Social Security withholding change in January, and their take-home pay moves without anyone changing their salary. Any year-end projection built on the prior base is wrong by up to $520.80 per affected employee on the employee side, and the same again on yours.

Payroll Taxes the Employer Pays

The employer-borne stack never appears on a payslip, which is why it gets budgeted badly. Half of it is fixed and half of it is not.

Employer-side tax	2026 rate	Base it applies to
Social Security match	6.2%	Same wage base as the employee side
Medicare match	1.45%	All wages, no cap. No match on the Additional Medicare Tax
FUTA (federal unemployment)	6.0% gross, 0.6% effective after the full state credit	The first $7,000 of each employee’s wages
SUTA (state unemployment)	Experience-rated, specific to your organization	A state-specific wage base that differs in every state
Workers’ compensation premium	Class-code rated	Not a payroll tax, but a payroll-driven cost that moves with your wage bill

The FICA match is fixed and you cannot influence it. Unemployment tax is variable and partly within your control, and that is where multi-state employers get surprised.

Here’s how to build it:

Turn the currency problem into a fixed December habit. Your payroll system updates the federal tables and almost nothing else, and the employer-specific settings are the ones that go stale.

Run this list before the first payroll of the year, every year.

• The Social Security wage base for the new year
• State unemployment wage bases, and the new rate your state assigned your organization
• State and local income tax tables for every jurisdiction you pay into
• Minimum wage changes at state and city level, which move on different dates than federal parameters
• Benefit contribution limits for retirement plans, HSAs, FSAs, and commuter benefits
• Your IRS deposit schedule for the new year, as determined by the lookback period
• Any new state registration needed for employees who moved during the year

The parameter I have watched go stale most is never a federal one. It is the organization’s own assigned unemployment rate, sitting in a system configuration screen that one person understood and nobody has opened since.

Payroll Deductions: Pre-Tax vs. Post-Tax and the Order of Operations

Two employees with identical gross pay and identical total deductions can have different withholding. Nothing in a list of deduction categories explains why.

Sequence explains it. Deductions are not a list, they are a waterfall, and an item’s position in the waterfall decides the tax outcome.

Why this works:

1. Gross pay. Everything earned in the period, before anything comes out.
2. Pre-tax deductions. Traditional 401(k), health, dental and vision premiums under a Section 125 plan, HSA and FSA contributions, certain commuter benefits. These reduce the wages subject to tax, and they do not all reduce the same taxes. A Section 125 health premium reduces both income tax wages and FICA wages; a traditional 401(k) contribution reduces income tax wages only.
3. Statutory withholding. Social Security, Medicare, federal income tax, and state and local income tax, each calculated on the base the step above produced.
4. Post-tax deductions. Roth contributions, after-tax insurance premiums, union dues, charitable giving, repayment of advances, and garnishments. These come out of money that has already been taxed and change nothing about the tax calculation.
5. Net pay. What lands in the bank account.

Old way: Deductions are a list of things that come out of pay. Lab Way: deductions are an ordered waterfall, and putting an item in the wrong tier produces a wrong tax withholding, which no employee will ever notice and no manager will ever query.

One deduction sits outside all of that discretion. Garnishments arrive as legal orders, and they get handled as ordinary post-tax lines in more payroll operations than anyone admits.

Garnishment limits and the priority sequence sit under federal wage-protection law with state overlays that vary in both direction and detail. Have counsel confirm your process. Do not work it out from an article, this one included.

Payroll Frequency: How Often to Run Payroll and What Each Cycle Costs

Pay frequency gets presented everywhere as a list of four options with a paycheck count next to each one. The choice is a three-way trade, and in several states part of it has already been made for you.

Frequency	Periods per year	Relative processing cost	The friction it creates
Weekly	52	Highest	Four times the runs, four times the approval cycles, four times the correction opportunities. Suits hourly and high-turnover workforces who budget weekly
Biweekly	26	Moderate	The US default. Produces a 27-period year roughly every eleven years, which breaks salaried budgeting
Semimonthly	24	Moderate	Aligns neatly to accounting periods and awkwardly to workweeks, which makes overtime calculation harder for non-exempt staff
Monthly	12	Lowest	Cheapest to run and rare in the US outside exempt-only populations. Hard on anyone living close to their pay date

Here’s the deal:

Biweekly pay assumes 26 periods, which assumes 364 days. Calendars run 365 days, and 366 in a leap year, so the spare days accumulate.

Roughly every eleven years, a calendar produces 27 biweekly pay dates. Salaried pay is expressed annually and divided by 26, so a 27th period either pays out one period more than the annual salary or forces the per-period amount down.

Both responses are legitimate. Absorb the extra period as additional cost, or recalculate the per-period rate across 27 periods. The second one keeps the annual number intact and hands every salaried employee a smaller paycheck 26 times, which is an employee relations problem wearing a spreadsheet’s face.

Payroll Compliance: The US Regulations Every HR Team Is Accountable For

Most compliance sections are ordered by statute. That ordering is useless to someone deciding where to spend a limited audit budget this quarter.

Order it by exposure. What costs the most if it is wrong gets audited first.

Payroll Compliance: Federal Wage and Hour Rules

The FLSA governs what is owed. Minimum wage, overtime at one and a half times the regular rate for hours over 40 in a workweek, the exempt and non-exempt classification that decides whether overtime applies at all, and the records that have to support every one of those positions.

This layer carries the highest exposure for most mid-size and enterprise employers, because a wage-and-hour error repeats every period and applies to a whole population at once. An exempt classification applied to a whole job family, when it should have been tested role by role, is the version that costs the most.

Retention is where teams guess. The periods differ by record type, and the answer is to keep everything for the longest applicable period, not to run four separate calendars.

Record type	Minimum retention
Payroll records under the FLSA	3 years
Supporting wage computation records, including time cards and wage rate tables	2 years
Employment tax records	4 years after the tax is due or paid, whichever is later
Benefit plan records under ERISA	6 years

State rules can run longer than any of these. Set your retention policy at the longest period that applies to you and stop making the distinction operationally.

Payroll Compliance: Tax Withholding, Deposit and Filing Duties

This layer governs what is remitted and when. Withhold FICA and income tax correctly, match the employer share, pay FUTA and SUTA, deposit on the schedule you were assigned, and file the quarterly and annual returns that reconcile all of it.

Penalties here are statutory and they scale with lateness. Nobody negotiates a late-deposit penalty down because the payroll itself was accurate.

• Confirm your assigned deposit schedule every January, from the lookback period, not from memory
• Reconcile deposits to the payroll register every period, not every quarter
• Reconcile quarterly returns to the year-to-date register before filing, not after
• Reconcile annual wage statements to all four quarterly returns before they reach employees
• Name one person accountable for the filing calendar, and a named backup for every date on it

Payroll Compliance: Worker Classification and Multi-State Payroll

This layer governs who is on payroll at all, and it carries the two risks that grew fastest with remote work.

Classification first. Treat someone as an independent contractor who meets the test for an employee and you owe unpaid payroll taxes, unpaid overtime, and penalties, applied backward across the whole engagement.

The part that catches people: the tests are multi-factor, and federal and state tests can reach different answers on the same worker. Passing one is not passing the other.

Multi-state is the second risk and the more common one. A remote employee creates a withholding and unemployment insurance obligation in the state where the work is performed, and a registration obligation that has to be completed before the first payroll run there.

Worker classification and wage-and-hour obligations carry retroactive statutory exposure, and multi-state employment creates state registration duties before the first payroll run. Have counsel or a tax adviser confirm your position on both.

One more flag worth carrying to your legal team. Where your payroll or HR systems apply automated decisioning to employment terms, some jurisdictions now regulate automated employment decision tools, with their own notice and audit requirements attached.

How to Run Payroll: In-House, Payroll Software or Payroll Outsourcing

Three delivery models, and most comparisons of them were published by someone who sells one of them. Here is the version with nothing at the end of it.

Here’s the difference:

Dimension	In-house	Payroll software	Outsourced or managed service
What you keep owning	Everything: calculation, filings, corrections, notices	The data, the inputs, and the full legal accountability	The legal liability for everything filed in your name
Headcount it requires	Genuine payroll expertise on staff, plus a trained backup for that person	One capable payroll owner and administrative support	A vendor manager who can read a service report and challenge it
Where the error risk sits	Entirely with you, at every one of the nine steps	Input quality. The calculation is handled; the data feeding it is yours	The relationship and the service levels. Escalation gets slower, not faster
What it is genuinely good for	Complex pay structures, heavy union or multi-agreement environments, unusual requirements	Most mid-size employers operating in a manageable number of states	Multi-country footprints and lean teams carrying more scope than headcount

Running Payroll In-House

Total control, and total consequence. You configure the earnings catalog, you calculate, you file, and you answer the notice when it arrives.

Running Payroll on Payroll Software

The hybrid, and the model most mid-size employers land on. Payroll software carries the calculation and much of the filing; you keep the data, the decisions, and the accountability.

The risk profile shifts. It does not shrink.

Calculation errors go down. Input errors become the dominant failure mode, which is why steps 2 and 7 of the cycle matter more on software, not less.

Payroll Outsourcing and Managed Payroll Services

Full-service delivery changes the operating model, not the tooling. Payroll outsourcing hands the cycle to a provider who runs it end to end, and managed payroll services sit on a spectrum from processing only through to full tax filing and employee query handling.

The calculus is different at small headcount, where the internal labor of running payroll eats a larger share of a smaller team’s capacity. Payroll services for small business are priced and scoped for that reality.

How to execute:

Answer these five before you take a single demo. The right model genuinely varies, and these are the parameters that decide it.

• How many states or countries do you pay in, today and in eighteen months?
• How many distinct pay structures, premiums, and allowances do you run?
• Do you have someone in-house who can read a tax notice and act on it without escalating?
• What is your tolerance for a late or wrong payroll, measured in actual consequence and not in sentiment?
• What does your current model cost fully loaded, including the internal time nobody counts?

The fifth question is the one almost nobody can answer. In most of the teams I have put it to, answering it properly changed the decision.

The next section is how to answer it. The model comparison in depth, and the vendor-level evaluation underneath it, belong on their own pages, and so do the mechanics of payroll processing once you have picked a model.

How Much Does Payroll Cost? A Vendor-Neutral Payroll Cost Benchmark

Ask what payroll costs and you will be handed a price card. The price card describes one of three cost layers, and it is the smallest one.

Here’s the deal:

Cost layer	What sits in it	Who measures it
Layer 1: platform or service fee	The per-employee-per-month invoice, implementation charges, module add-ons	Everyone. This is the only layer anyone negotiates
Layer 2: internal labor	Preparation, approval chasing, reconciliation, employee query handling, year-end close, audit response	Almost nobody, and it is the largest of the three in most operations I have looked at
Layer 3: cost of error	Correction runs, off-cycle payments, penalties, interest, and the hours spent on all of it	Nobody, until an auditor does it for you

Layer one is visible and negotiated to the dollar. Layers two and three are invisible and unpriced, which is how a team ends up optimizing the smallest number on the page.

Here is the independent benchmark to place yourself against, and it belongs to nobody who sells payroll.

Translation: at $158 per employee per year, payroll for a 2,000-person company benchmarks at roughly $316,000 all in. That is a number you can test your own spend against tonight, across all three layers and not one of them.

Use the staffing ratio as the second test. A 2,000-person company with four people in payroll is running heavy against the benchmark. The same company with one is running thin, and thin is how step 7 quietly stops happening.

Payroll at Scale: What Breaks When You Put 400 People on Payroll in 10 Weeks

Payroll at rest is the only version anyone writes about. Payroll under load fails differently, and almost nothing written about it comes from someone who has watched it happen.

Here’s what changed everything:

Payroll under load fails in four specific ways, and none of them looks like a calculation error. Each one has a control that prevents it.

• Bank detail quality collapses when onboarding is batched. Documents get collected in bulk and validated in bulk, and a rejected payment on a first payslip is the worst possible introduction to an employer. The control: a data completeness gate that blocks a new starter from the first run until bank, tax, and work location fields are validated.
• Start dates cluster mid-period. The first payment for a large cohort becomes a part-period calculation performed at volume, which is the calculation type with the highest error rate in normal conditions. The control: a named owner for the cohort’s first two runs, with the part-period logic checked by hand against a sample before release.
• Tax elections arrive incomplete. Default withholding gets applied to a large group of people who will notice, and correcting it retroactively is a conversation with hundreds of new employees in week three. The control: tax election completeness belongs in the same gate, never as a follow-up task.
• Cost-center assignment lags the org design. Finance sees a payroll number that maps to no budget line, and the reconciliation at step 7 stops being meaningful. The control: cost centers assigned before offer acceptance, never after onboarding.

One more control sits outside those four. Run a first-payslip verification sweep across the whole cohort within 24 hours of the first run, before anyone complains.

Payroll Errors: The Six That Cost the Most and How to Correct Them

Most payroll error logs are dominated by small, visible mistakes that an employee reported the same day. Those are the cheap ones.

The expensive errors are quiet and they repeat. Rank by cost per period multiplied by periods undetected, and the list reorders completely.

1. Worker misclassification. Happens when a contractor relationship drifts into an employment relationship and nobody re-tests it. Expensive because the correction reaches back across the whole engagement. Detect it with an annual re-test of every contractor engaged longer than six months.
2. Incorrect pay-code setup. Happens once, at configuration, when a new earnings type is mapped to the wrong tax treatment. Expensive because it applies silently to every employee who touches that code, in every period, for years. Detect it by reconciling the pay code catalog against its tax treatment annually, code by code.
3. Overtime calculated on the wrong regular rate. Happens the moment a non-discretionary bonus or shift premium launches without a regular-rate recalculation. Expensive because it accrues per employee per week. Detect it by testing overtime for any population receiving a variable premium, every time a new premium launches.
4. Missed or late tax deposits. Happens when a deposit schedule changes under the lookback rules and nobody checked. Expensive because penalties are statutory and scale with lateness. Detect it by confirming your assigned schedule every January and reconciling deposits to the register every period.
5. Wrong state withholding for remote employees. Happens when someone moves and the address change reaches HR but not payroll. Expensive because it creates a withholding correction and an unregistered-employer problem at the same time. Detect it by reconciling work location against withholding state quarterly.
6. Unprocessed terminations. Happens when the offboarding date misses the payroll cutoff. Expensive because overpayment recovery is legally constrained, and in several states unrecoverable. Detect it by reconciling active headcount against the HR system at step 7 of every single run.

Here’s how to build it:

An error has been found after the run released. Here is the decision procedure, in this order, every time.

One flag before you build a recovery process. Recovering an overpayment from an employee is legally constrained in several states, with rules on consent, timing, and deduction limits. Treat it as a question for counsel, never a decision payroll makes alone.

AI and Automation in Payroll: What It Actually Changes

Every mention of AI in payroll you will find attached to a product is a pitch. Here is a position with nothing to sell behind it.

Here’s the difference:

Automation is good at five things in payroll, and it is genuinely better than people at all five. Calculation at volume. Applying one rule consistently across thousands of records.

Anomaly detection across periods, which is pattern work humans do badly. Tax table maintenance. And the reconciliation checks a person performs poorly at 11pm on a release night.

Here is what it does not do. It does not own the liability, and it does not decide a classification question where federal and state tests disagree.

It cannot judge whether a variance is an error or a legitimate change. And it cannot explain a wrong paycheck to the person holding it.

The gap between what these tools promise and what organizations have banked is wide, and it is measurable.

Translation: the gap is not in the technology, it is in how the technology was deployed. Automating a payroll calculation that was already accurate produces a faster version of the same result, which is why the value shows up in the control design and never in the tool.

Payroll FAQs: The Questions HR Teams Ask Most

Five questions that come up in every payroll conversation I have been part of, answered directly.

Is Payroll Part of HR or Accounting?

Both, and the split is the answer. Payroll inputs are HR data: hires, terminations, promotions, leave, classification, benefit elections. Payroll outputs are finance artifacts: the ledger entry, the tax remittance, the cash movement. Organizations that run payroll well give HR the employee data and the pay decisions, and give finance the funding, remittance, and filing.

What Is the Difference Between Payroll and Salary?

Salary is one employee’s fixed compensation; payroll is the whole process that pays everybody. Payroll covers hourly pay, overtime, bonuses, commissions, deductions, taxes, employer contributions, remittances, and records, for every worker in the organization. Salary is a single input into it. The three-layer table earlier in this guide shows one employee at basic wages, gross pay, and total payroll cost.

How Much Does Payroll Cost per Employee?

The independent benchmark is a median of $158 per employee per year for payroll operations, per Deloitte’s 2025 Global Payroll Benchmarking Survey. That covers all three cost layers: the platform or service fee, the internal labor nobody measures, and the cost of error. A vendor price card prices the first layer only, which is the smallest of the three.

How Often Should Payroll Be Run?

Biweekly is the most common US cycle, at 26 periods a year. The choice is constrained: several states set a minimum pay frequency by employee type, so verify the cycle is lawful in every state you pay into before changing it. The trade is between processing cost, cash-flow rhythm, and what your workforce expects.

What Happens If Payroll Is Wrong or Late?

Classify the error before you correct anything. Underpayment, overpayment, and withholding-only errors carry different urgency and different legal footing. Correct the tax and filing position as well as the payment, because fixing one without the other creates a second error inside a submitted return. Then tell the affected employee before they discover it, with a specific date for the fix.

For most of my career I treated payroll as somebody else’s system. I sent it data, it produced payslips, and I thought about it only when something went wrong.

The results were predictable: terminations landing after the cutoff, internal moves arriving at payroll as a surprise, and a hiring ramp that modelled every kind of capacity except the one that had to pay the people I had just hired.

Here’s what changed everything: payroll is not an administrative function HR happens to sit near. It is where every HR decision you have ever approved gets settled in money, which is why the organizations that run it well treat it as a system with owners and controls and not as a task with a deadline.

That system has a shape. Setup as architecture and the cycle as operations. Nine steps with two named control points, a cutoff and a pre-release review.

Ten decisions with a named owner each, split across HR and finance. Three cost layers, of which the invoice is the smallest.

This isn’t theoretical. Every control in this guide is here because I watched its absence cost something.

What separates the teams who run payroll well from the ones who firefight it is not budget and it is not software. It is whether anyone in the building can name who is accountable for each of those ten decisions. Most cannot, so go and ask three people today and compare the answers.

Then pick two controls. Not all ten. One from the input side: publish the cutoff, with a named approver for every cost center.

One from the review side: the pre-release variance check, with a dollar threshold you set yourself. Run both for one quarter, then count how many payroll errors your employees reported and compare it to the quarter before.

Six more pages follow this one in the payroll series: what basic wages are and why so many statutory calculations key off them, payroll processing in operational detail, payroll software, payroll services, payroll services for small business, and payroll outsourcing. Subscribe to the newsletter and each one arrives as it publishes, with the annual parameter review landing every December.

If you are rebuilding payroll ownership in your own organization this quarter, come and tell me where your handoff sits. That is always the interesting part, and it is never in the same place twice.