Payroll processing is the recurring workflow employers use to turn employee and timekeeping data into accurate pay, tax deposits, payroll records, and accounting entries. It includes more than calculating a paycheck. Every payroll run depends on current employee information, approved hours, correct compensation and deductions, timely funding, accurate tax treatment, and a review process that catches unusual changes before employees are paid.For a small team with straightforward compensation, that workflow may feel simple. As a company adds employees, states, benefits, bonuses, commissions, leaves, and off-cycle payments, the number of inputs and handoffs grows quickly. Payroll software can automate much of the calculation and payment infrastructure, but the employer still needs a reliable process for supplying, reviewing, approving, and reconciling the information.
This guide explains how payroll processing works, how long it takes, what happens during each step, and where payroll errors commonly begin.
|
|
|
|
|
PAYROLL PROCESSING A typical payroll run follows this sequence: collect employee and time data, review payroll changes, calculate gross pay, apply taxes and deductions, approve the payroll register, submit payments, deposit and report payroll taxes, record payroll in the general ledger, and retain supporting records. |
|
|
|
Payroll processing is the end-to-end process of calculating employee compensation, withholding required and authorized amounts, issuing net pay, meeting related tax obligations, and recording the results.
Although the terms are sometimes used interchangeably, a pay period and a payday are not the same thing. The pay period is the span of time for which wages are earned. Payday is the date employees receive those wages. The interval between them gives the payroll team time to collect final inputs, review changes, resolve exceptions, approve the run, and submit payment instructions.
The payroll process also extends beyond payday. Employers may still need to deposit employment taxes, file required returns, remit benefit contributions or garnishments, reconcile cash activity, post payroll to the general ledger, and retain payroll records.
Before the first payroll run, an employer needs the legal, employee, and system information required to calculate and report payroll correctly.
At a minimum, that foundation commonly includes:
The IRS identifies Form W-4 as the document used to determine federal income-tax withholding and provides a broader employer checklist for hiring employees. State and local requirements vary, so a company hiring in a new jurisdiction may need registrations, accounts, forms, or payroll settings that were not required before.
Employee classification matters as well. Being paid a salary does not automatically make an employee exempt from overtime. The employee’s duties and the applicable wage-and-hour rules must support the classification. An incorrect classification can affect time tracking, regular-rate calculations, overtime, and payroll records.
The exact workflow varies by company and platform, but a well-controlled payroll process generally follows these nine steps.
The process begins with the information that changed since the prior payroll run. Depending on the company, inputs may include:
This is where many downstream payroll problems originate. A payroll platform can correctly calculate the data it receives and still produce the wrong result if a new hire is missing, a raise has the wrong effective date, an employee’s work state is outdated, or approved overtime never reaches payroll.
For that reason, mature payroll processes use a documented cutoff and a consistent way to submit changes rather than relying on scattered messages, spreadsheets, or memory.
Before calculations are finalized, managers or authorized reviewers should approve time records and confirm pay-impacting changes. The review should resolve missing punches, unapproved time off, unexpected overtime, duplicate entries, and changes that do not match supporting documentation.
This control is especially important for nonexempt employees. Under the Fair Labor Standards Act, covered nonexempt employees generally must receive overtime pay for hours worked over 40 in a workweek, subject to applicable rules and exceptions. State law may impose additional requirements.
A clean approval process establishes who supplied the information, who reviewed it, and when it became effective. That record is valuable when an employee questions a paycheck or when the company later needs to reconstruct why pay changed.
Gross pay is the employee’s compensation before taxes and other deductions.
For an hourly employee, the basic calculation begins with hours worked multiplied by the applicable rate, with overtime, shift differentials, bonuses, commissions, and other earnings added as required. For a salaried employee, the regular salary amount is generally allocated across the company’s scheduled pay periods, then adjusted for any additional earnings or permissible changes.
The calculation can become more involved when employees receive multiple pay rates, nondiscretionary bonuses, commissions, retroactive pay, taxable fringe benefits, or other compensation that affects the regular rate or taxable wages.
Once gross pay is established, the payroll system applies the employee’s tax settings and authorized deductions. These may include:
Not every deduction is treated the same way. Some reduce wages subject to one tax but not another; some are post-tax; and some are limited by law, plan terms, or employee elections. The employer may also owe amounts that do not reduce the employee’s net pay, including the employer share of Social Security and Medicare taxes, federal and state unemployment taxes, and employer benefit contributions.
That distinction matters: withholding from an employee, calculating the employer’s tax obligation, depositing taxes, and reporting taxes are related but separate activities. IRS Publication 15 explains federal employer responsibilities for withholding, depositing, reporting, and paying employment taxes.
Before payroll is submitted, the payroll register should be reviewed for accuracy and unusual changes. A strong review compares the current run with the previous payroll and explains material variances.
| COMMON PAYROLL REVIEW QUESTIONS |
|
This is the last practical opportunity to catch many errors before they reach employees. Separating payroll preparation from final review can add an important control, particularly as payroll becomes more complex or depends heavily on one person.
After approval, payroll is submitted through the company’s payroll platform or payment process. The employer must make sufficient funds available and meet the provider’s cutoff for the intended payday.
Employees may be paid by direct deposit, paper check, paycard, or another permitted method. Direct deposits generally travel through the ACH network. ACH credits can be processed on the same banking day, the next banking day, or up to two banking days later depending on how the payment is originated, but the employer’s actual submission deadline can be earlier because providers and banks need time to validate files and fund the transaction. The Nacha overview of ACH processing describes the network timing; the company’s payroll provider determines the operational cutoff it must follow.
Payroll tax work does not end when employees receive their pay.
Employers generally must deposit withheld federal income tax and both the employee and employer portions of Social Security and Medicare taxes according to their assigned deposit schedule. Depositing the money and filing the tax return are separate obligations. Employers that withhold federal income tax or Social Security and Medicare taxes generally report those amounts quarterly on Form 941, although different forms or schedules can apply in certain situations. The IRS provides current guidance on depositing and reporting employment taxes.
Employers may also have federal unemployment tax obligations and state or local withholding, unemployment, paid-leave, or other payroll-related requirements. The responsible party should know which tasks the payroll provider performs and which remain with the employer. A platform may automate filings and payments, but the employer still needs to ensure accounts are established, information is correct, notices are addressed, and exceptions do not sit unresolved.
At year-end, employers generally furnish Forms W-2 to employees and file wage reports with the Social Security Administration by the applicable January deadline. The SSA maintains current W-2 filing instructions and deadlines.
Payroll must also reach the accounting records correctly. The payroll entry commonly includes gross wages, employer payroll taxes, benefit costs, employee withholdings, employer contributions, cash, and liabilities still awaiting payment.
An integration or exported journal can simplify posting, but it does not eliminate the need for reconciliation. The accounting team should confirm that payroll reports agree with cash withdrawals and general-ledger entries, liabilities clear when payments are made, and compensation is recorded in the appropriate period, entity, department, or class.
A payroll run can pay every employee correctly and still create inaccurate financial statements if the journal entry is incomplete, duplicated, mapped incorrectly, or posted to the wrong period.
The final step is maintaining the supporting records and addressing any issues discovered after submission. Records may include payroll registers, time records, wage rates, deductions, approvals, tax filings, payment confirmations, and documentation supporting changes.
Federal retention periods are not identical for every record. The Department of Labor states that covered employers generally must retain payroll records for at least three years, while records used to compute wages—such as timecards and wage-rate tables—generally must be retained for two years. Tax, benefit, immigration, state, and local rules may require different information or longer periods. The DOL’s FLSA recordkeeping guidance provides the federal wage-and-hour baseline.
If an error is discovered, the response depends on what went wrong. A correction may require an off-cycle payment, a future-payroll adjustment, an amended tax filing, a benefit correction, a revised accounting entry, or direct communication with the employee. The company should document both the correction and the process change intended to prevent a repeat.
There is no universal number of days that payroll processing takes.
The answer depends on two different timelines:
The ACH network itself supports same-day and future-dated payments, but that does not mean every company can wait until payday to submit payroll. Provider rules, prefunding requirements, weekends, bank holidays, payment method, and risk reviews can all affect the deadline.
In practice, a company should build its payroll calendar backward from payday. The calendar should identify the employee or manager cutoff, timecard approval deadline, payroll preparation window, review and approval time, funding deadline, and payday. It should also account for bank holidays and the extra review required for bonuses, commissions, terminations, or large payroll changes.
So, how long does payroll take to process? The transaction may move quickly after submission, but the complete payroll workflow often begins several business days before payday. The reliable answer for a specific company comes from its own documented workflow and provider cutoff—not a generic industry average.
An off-cycle payroll is a payment processed outside the company’s regular payroll schedule. Companies may use one to pay a bonus, commission, severance amount, retroactive adjustment, missed wages, or payroll correction.
Not every bonus or commission requires an off-cycle run. When timing allows, these payments can often be included in the next regular payroll. A separate run may be appropriate when the payment has a different deadline, an employee was underpaid, a departing employee must be paid within an applicable state-mandated timeframe, or waiting until the next scheduled payday would create an operational or compliance problem.
Off-cycle payrolls require the same attention to approvals, taxes, deductions, funding, and accounting as regular payroll. They may also create additional processing costs or compressed review timelines, depending on the payroll provider. The company should document why the payment was issued, confirm its tax and deduction treatment, and reconcile it separately when appropriate.
Payroll errors often appear on payday, but their causes usually occur earlier in the process.
|
Error |
Where it often begins |
Control that helps |
|
Incorrect hours or overtime |
Timekeeping and manager approval |
Defined cutoff and documented approval |
|
Missed raise, bonus, or commission |
HR or finance handoff |
Centralized change log with effective dates |
|
Wrong withholding state |
Address or work-location change |
Location review and multistate registration process |
|
Incorrect benefit deduction |
Enrollment data or plan change |
Reconciliation between benefit and payroll systems |
|
Duplicate or missed payment |
Manual entry or off-cycle request |
Second-person review and payroll variance analysis |
|
Unexpected net pay |
Tax settings, deductions, or retroactive items |
Employee-level exception review before submission |
|
Payroll-to-GL mismatch |
Integration or account mapping |
Reconcile payroll reports, cash, and journal entries |
|
Late tax deposit or filing |
Unclear ownership or missing account |
Compliance calendar and documented responsibility |
The common thread is ownership. Payroll becomes fragile when no one is responsible for confirming that upstream changes reached the system, reviewing the completed run, and following the results into taxes and accounting.
Payroll technology, payroll operations, and broader back-office coordination are different layers of the process.
Payroll software provides the system for maintaining payroll data, performing calculations, generating reports, initiating payments, and often automating tax filings. Platforms such as Gusto, Rippling, and ADP can support much of that infrastructure.
An internal payroll owner manages the recurring workflow around the platform: gathering inputs, maintaining employee changes, reviewing exceptions, approving the run, answering questions, and coordinating with HR, finance, accounting, and tax.
Managed payroll support can assume some or all of that operational responsibility while working within the company’s payroll environment. The scope matters. A company should understand who handles routine and off-cycle runs, employee changes, tax notices, corrections, employee questions, variance reviews, and accounting coordination—not simply whether a vendor says it “does payroll.”
The right model depends on the company’s complexity and internal capacity. Warning signs that the current approach may be breaking down include:
Payroll is not an isolated administrative transaction. Employee lifecycle information begins with People Operations. Compensation and headcount affect financial planning. Payroll taxes and work locations create compliance obligations. Payroll entries affect accounting and the month-end close.
That is why a reliable payroll process needs more than correct calculations. It needs accurate upstream inputs, defined ownership, documented approvals, review controls, timely follow-through, and clean coordination across the back office.
Graphite’s Payroll Services provide operational ownership of recurring and off-cycle payroll within a company’s existing platform whenever possible. Our specialists manage employee payroll changes, variance reviews, corrections, and employee questions while coordinating payroll with Accounting, Tax, Finance, and People Operations when those functions intersect.
Learn more about Graphite’s Payroll Services or talk with our team about building a more reliable payroll operation.