From the paymaster to the payroll system
For most of human commercial history, paying employees was a manual affair: a business owner or designated paymaster counted out wages in cash or issued handwritten checks, kept ledgers by hand, and managed the whole process through a combination of arithmetic and institutional memory. The complexity was low because payroll was low: wages, perhaps some overtime, handed over on Friday. No standardized withholding, no benefit deductions, no multi-state obligations.
Two changes transformed payroll into the complex, high-compliance process it is today. The first was mandatory payroll withholding, introduced in 1943, which turned employers into tax collectors — required to calculate, withhold, and remit federal income taxes and FICA from every paycheck, on a strict deposit schedule, with penalties for failure. The second was the growth of employee benefits: health insurance, retirement plans, flexible spending accounts, and a proliferating set of voluntary deductions, each with its own tax treatment and remittance obligation. By the late twentieth century, even a small business’s payroll required knowing which deductions reduce which tax bases, applying each in the right order, and meeting a calendar of deposit deadlines that recurs every pay period. Payroll software emerged to automate the arithmetic; the compliance knowledge remained human. Today, payroll is simultaneously one of the most routine and most legally demanding processes in business operations — run every week or two weeks, without fail, with no tolerance for delay.
What is payroll?
Payroll is the process of calculating what each employee is owed, applying the correct pre-tax deductions and tax withholding, computing net pay, and distributing payment — along with the associated tax remittance and record-keeping that follows each pay run. For every employee, every pay period, it produces the paycheck they take home and the withholding the employer remits to the government.
Payroll follows a fixed sequence: collect and verify hours/time data → calculate gross pay → apply pre-tax deductions → calculate and apply tax withholding → apply post-tax deductions → compute net pay → review the payroll register → authorize and distribute payment → post the payroll journal entry → remit payroll taxes and benefit contributions. Deviating from this sequence — for example, processing deductions before verifying hours — is a leading cause of payroll errors.
What does payroll actually mean?
Payroll means the commitment to pay every employee correctly and on time, every single pay period — and the weight of that commitment is easy to underestimate from the accounting side. Payroll is not a month-end task; it runs on a fixed schedule that doesn’t pause for late time records, unclear circumstances, or incomplete data. It produces a legally binding obligation: the right to be paid the correct amount, on the scheduled date, is a foundational employment right, enforced by the Fair Labor Standards Act and every state’s wage-and-hour law.
Payroll that is one day late is not a minor administrative inconvenience; it’s a potential FLSA violation (if final pay is owed to a departing employee), a possible state wage-and-hour law violation (many states set strict timing requirements for wages), and a direct harm to the employee whose mortgage payment or grocery budget is tied to that deposit. Payroll tolerates a different standard of urgency than any other bookkeeping process — not because the accounting is more important, but because the human consequences of getting it wrong are more immediate.
Calculation sequence, pay frequencies, and key compliance rules
Pay period frequencies.
| Frequency | Pay periods per year | Key note |
|---|---|---|
| Weekly | 52 | Highest administrative burden; aligns cleanly with FLSA workweeks |
| Biweekly | 26 (sometimes 27) | Most common US frequency; some years have 27 pay periods |
| Semimonthly | 24 | Fixed dates (e.g., 1st and 15th); overtime calc more complex for hourly employees |
| Monthly | 12 | Lowest admin burden; least common; some state restrictions |
The payroll calculation sequence (order is mandatory).
- Collect and verify hours/time data — time records, PTO, leave; W-4 and benefit elections on file
- Calculate gross pay — hourly: rate × hours + overtime; salaried: annual ÷ pay periods + bonuses/commissions
- Apply pre-tax deductions — traditional 401(k), pre-tax health premiums (cafeteria plan), HSA, FSA, commuter benefits; each reduces federal taxable wages; some (like health premiums under §125) also reduce FICA wages; 401(k) does not reduce FICA wages
- Calculate tax withholding — federal income tax (per W-4 and Pub 15-T tables); FICA (SS 6.2% to $184,500 + Medicare 1.45% + 0.9% AMT over $200,000); state/local income tax
- Apply post-tax deductions — Roth 401(k), wage garnishments, voluntary deductions; these do not reduce any tax base
- Net pay = gross − pre-tax deductions − all tax withholding − post-tax deductions
FLSA overtime — the most common calculation error. The FLSA requires non-exempt employees to be paid 1.5× their regular rate for hours worked over 40 in a workweek. The workweek is a fixed, consecutive seven-day period — and overtime is calculated per workweek, not per pay period. For a biweekly payroll: if an employee works 45 hours in week one and 35 hours in week two, they earned 5 hours of overtime in week one — period. The 35-hour week two does not offset the 45-hour week one. The most common error: applying 1.5× to all hours above 40 across the biweekly period, rather than per workweek. Salaried exempt employees do not earn overtime; salaried non-exempt employees do.
The payroll journal entry.
Debit: Wages/Salaries Expense (gross wages) + Payroll Tax Expense (employer FICA — 7.65% of applicable wages)
Credit: Cash or Wages Payable (net pay) + FICA Payable (employee + employer shares combined) + Federal Income Tax Withholding Payable + State/Local Income Tax Withholding Payable + Benefits Payable (401k employee contributions, health premiums)
The entry is posted from the verified payroll register immediately after each payroll run.
Where payroll complexity rises
Payroll is universal for any business with employees, but complexity rises in specific contexts.
| Context | Why payroll is more complex |
|---|---|
| Hourly / mixed workforces | FLSA overtime per workweek tracking; variable gross pay each period |
| Multi-state employers | Multiple state withholding, SUTA rates, minimum wages, and overtime rules |
| Businesses with rich benefits | Many pre-tax deduction types, each with different tax treatment |
| High earners | SS wage base cap; Additional Medicare Tax threshold tracking |
| Seasonal / variable staffing | Changing headcounts; onboarding and offboarding mid-period |
(Rows reflect practitioner framing of where payroll complexity concentrates, not a vendor ranking.)
How do QuickBooks, Gusto, ADP, and Xero handle payroll?
Dedicated payroll platforms automate the calculation, compliance, and filing layers — but they depend entirely on correct configuration to produce correct results.
- QuickBooks Payroll. Integrated with QBO books; calculates and files federal and state payroll taxes; manages direct deposit; produces W-2s; automated tax deposits via EFTPS; updates FICA rates and wage bases annually.
- Gusto. Popular for small-to-mid-size businesses; handles multi-state payroll, benefits deductions, automated federal and state tax filings; employee self-service for W-4 and direct deposit setup.
- ADP / Paychex. Enterprise-grade payroll with multi-state capability, HR integration, time and attendance, and dedicated compliance support.
- Xero Payroll. Integrated with the Xero accounting ledger; handles UK payroll natively; US payroll through integration partners.
- The configuration dependency. Every platform is only as correct as the setup: employee pay rates, benefit deduction elections, W-4 withholding elections, state tax codes, overtime rules, and FICA settings must all be configured correctly before the first payroll run. The platform applies the rules it knows; it doesn’t validate whether those rules are correct for the employee or compliant with the applicable state. The offshore team or firm is responsible for ensuring the configuration is accurate and maintained as employee circumstances change.
How do CPA firms manage payroll?
For a CPA firm offering payroll services, the process runs every pay period without exception: collect time and payroll data, run the payroll calculation in the platform, review the payroll register (verifying gross pay, deductions, withholding, and net pay), submit for client approval, authorize the direct deposit run, post the payroll journal entry to the GL, schedule the EFTPS tax deposit, reconcile the payroll register to the GL, and retain the records. At year-end, the firm produces W-2s and reconciles them to the four quarterly Form 941s.
The firm also provides advisory support around payroll: ensuring compliance with FLSA and state overtime rules, advising on benefit election impact on payroll taxes, managing pay frequency changes, handling garnishment orders, and advising on the tax consequences of bonuses, commissions, and equity compensation. And it manages the compliance calendar — the deposit schedule, the quarterly 941 filings, the state withholding and unemployment filings — so that the payroll tax compliance that follows every payroll run is met without exception.
How does payroll work in offshore accounting?
Payroll is the process where the offshore team’s work becomes most directly personal — and understanding why that’s true is the key to understanding the offshore payroll discipline. Every other bookkeeping error has a correction path that the affected party may never notice: a miscoded expense is reclassified in the next period; an accrual is reversed and re-entered; a reconciling item is investigated and resolved over the next close cycle. A payroll error lands in an employee’s bank account. An underpaid employee may not be able to cover their rent. An employee whose benefits deductions were miscalculated may find their health coverage not in force when they needed it. Payroll that is one day late is not a minor administrative inconvenience; it’s a potential FLSA violation and a harm to a real person whose financial life is timed to that deposit. This is why the standard of care for offshore payroll work is higher than for any other process in this glossary — not because the accounting is more complex, but because the human consequences of getting it wrong are more immediate and more personal.
The payroll register verification is the non-negotiable quality gate that separates this standard from everything else the offshore team does. Before any payroll run is submitted for authorization, the offshore team reviews the complete payroll register — every employee, every line: gross pay (hours times rate, or salary divided by pay periods, correctly), overtime (calculated per workweek, not per pay period, for every hourly employee), pre-tax deductions (each deduction type applied in the correct order and against the correct tax base), tax withholding (FICA rates correct, cumulative wage bases tracked, federal income tax per the employee’s current W-4), post-tax deductions (applied after withholding), and net pay (the arithmetic correct for every employee). Every error found in the register before submission is an error that never reaches an employee’s paycheck. Every error that passes the register check becomes a correction, a reissuance, and a conversation with the employee. The register review is not a formality — it is the verification step that makes the offshore payroll process trustworthy, and no payroll run is submitted for authorization without it having been done completely.
The payment authorization boundary is absolute. The offshore team calculates and verifies the payroll; the employer or the firm authorizes the payment. The direct deposit run — the instruction to release funds to employees’ bank accounts — is never initiated by the offshore team. This is both a compliance boundary (the payment is the employer’s act, with legal and regulatory implications) and a practical control (no payment is made without the employer’s explicit review and approval of the verified register). The offshore team delivers the verified payroll register to the approver with enough lead time — typically two business days before the pay date — that the approver can review it thoughtfully and the direct deposit can be processed on time. Any issue that might compromise this timeline is escalated as soon as it’s identified, days before the pay date, not hours.
The FLSA overtime calculation is the most operationally specific accuracy requirement, and it is where the most common payroll errors occur for businesses with hourly employees. The FLSA requires overtime to be calculated per workweek — not per pay period. For biweekly payroll, this means the offshore team must track and apply overtime separately for each of the two workweeks that fall within the pay period. An employee who works 45 hours in week one and 35 hours in week two earned 5 hours of overtime compensation in week one; the two weeks do not offset each other. Processing biweekly payroll as a single two-week calculation and applying overtime to hours above 80 across the pay period rather than above 40 within each workweek produces incorrect gross pay — overstating it when one week is above 40 and another is below, or missing it when both weeks are above 40 by different amounts. This per-workweek discipline is not optional: it is the FLSA requirement, and violations create back-pay liability that compounds over time.
The payroll journal entry is a close-related deliverable that connects the payroll run to the general ledger, and it is where the payroll process intersects with the broader bookkeeping disciplines this glossary has documented. The payroll entry debits wages expense and employer payroll tax expense (both income statement) while crediting net pay cash (or wages payable if not direct pay), FICA payable (employee + employer shares combined, held until the deposit deadline), income tax withholding payable, and benefits payable — multiple balance sheet accounts simultaneously. The offshore team posts this entry from the verified payroll register immediately after the payroll run and reconciles the payroll register totals to the GL payroll accounts at month-end. If the payroll register and the GL don’t agree, there is a posting error, a direct deposit that wasn’t recorded, or a GL entry that bypassed the payroll subledger — and this is exactly the kind of discrepancy the month-end payroll reconciliation is designed to catch before the financial statements are finalized. Payroll is where the offshore team’s work is most personal, most time-pressured, and most consequential for real people’s financial lives — and it is, fittingly, where the disciplines this glossary has built across 50 terms come together: the accrual accuracy of wages expense, the FICA mechanics from the payroll tax page, the register-to-GL reconciliation from the reconciliation page, the W-4-to-withholding connection from the W-2 page, and the materiality standard that has appeared throughout — elevated here, at the last, to its highest expression.
What are the common misconceptions about payroll?
- “Overtime is calculated for hours over 40 in the pay period.” No — the FLSA requires overtime per workweek (40 hours in a consecutive seven-day period), not per pay period. For biweekly payroll, each of the two workweeks is calculated separately.
- “Pre-tax deductions reduce FICA taxes.” It depends on the type. Traditional 401(k) contributions reduce federal taxable wages but do NOT reduce FICA wages. Pre-tax health premiums under a §125 cafeteria plan reduce both. Knowing which reduces which is essential for accurate withholding.
- “Net pay equals gross pay minus taxes.” Net pay equals gross pay minus pre-tax deductions minus all tax withholding minus post-tax deductions. Multiple layers, applied in a specific order — missing any one layer produces an incorrect net pay figure.
- “The pay date can be moved a day if there’s a bank holiday.” Generally no — most states have specific rules about when pay is required and what adjustments are permissible. Always verify state law before changing a pay date.
- “Payroll software guarantees compliance.” The software applies the rules it’s configured with. If employee data, W-4 elections, benefit elections, or overtime rules are set up incorrectly, the software will calculate payroll incorrectly with equal precision.
What terms are commonly confused with payroll?
| Confused with | The key difference |
|---|---|
| Payroll Tax | The tax component of payroll (FICA, FUTA, withholding) — a part of the broader payroll process |
| W-2 Form | The year-end reporting document that summarizes the year's payroll for each employee; payroll is the recurring process that produces W-2 data |
| Gross Pay | Total earnings before deductions — one step in the payroll calculation, not the full process |
| Net Pay | Take-home amount after all deductions and withholding — the output, not the process |
| HR (Human Resources) | HR manages employment relationships, hiring, and benefits; payroll executes the payment calculation — related but distinct functions |
Common client questions about payroll
What pay frequency should we use?
It depends on your workforce type, state laws, and administrative capacity. Biweekly is the most common in the US — it aligns cleanly with FLSA workweeks for overtime calculation, is predictable for employees, and isn’t as intensive as weekly. Semimonthly is common for salaried employees but makes overtime more complex for hourly workers. Some states require a minimum frequency for certain employee types. We’d confirm what applies in your state before you choose.
How is overtime calculated?
Under the FLSA, non-exempt hourly employees earn 1.5× their regular rate for every hour over 40 in a workweek — a fixed, consecutive seven-day period. Overtime is calculated per workweek, not per pay period. For biweekly payroll, each of the two weeks is calculated separately: a 45-hour week and a 35-hour week don’t average out — the 45-hour week produced 5 hours of overtime regardless of week two. Some states like California have stricter daily overtime rules.
Why are there so many different deductions on the paycheck?
Because each serves a different purpose and follows different tax rules. Pre-tax deductions like traditional 401(k) and health insurance come out before taxes, reducing the taxable wage. Tax withholding (federal and state income tax, Social Security, Medicare) comes next. Post-tax deductions like Roth 401(k) come after taxes. Each must be applied in the right order for withholding to be correct. The payroll system handles this automatically once elections are set up correctly.
What happens if we make a payroll error?
The correction depends on the error type. An underpayment — you owe the employee money — is corrected as quickly as possible with a supplemental payment, and the associated withholding must be adjusted. An overpayment involves recovering the excess from the employee, which has its own rules depending on state law and how recently it occurred. In both cases, the payroll register and the journal entry need to be corrected, and depending on the amount, the Form 941 may need amendment. The best strategy is to catch errors in the register review before the payroll is submitted — which is exactly the discipline the payroll register verification step is designed to enforce.
How does payroll connect to our financial statements?
Payroll flows into your financial statements through the payroll journal entry. The gross wages are a wages expense on your income statement, reducing your profit. The employer’s share of FICA taxes is a separate payroll tax expense. The net pay goes out as cash, and the amounts withheld (income taxes, employee FICA, benefits) sit as liabilities on your balance sheet until they’re remitted to the government or the benefit plan. Getting the payroll entry right means your income statement shows the full cost of your workforce and your balance sheet correctly reflects what you owe.