A payroll run starts with a period, not a document

A pay statement is an output. A payroll run begins earlier: with the employer, pay period, pay date, employees, earnings inputs, and tax or deduction settings that determine the result. Keeping that distinction clear helps prevent a polished document from being mistaken for proof that the underlying payroll process was complete.

1. Employer and pay-period setup

The run should identify the employer, the pay period, the pay date, and the frequency or schedule being used. That shared context matters because every employee result in the run should refer to the same employer-level event.

2. Employee earnings

Each employee’s gross pay may include regular wages, salary, overtime, bonuses, commissions, shift differentials, or other compensation. The calculation depends on the employee’s actual pay arrangement and the laws that apply to the work.

3. Taxes and deductions

Payroll may include federal income-tax withholding, Social Security and Medicare taxes, state and local withholding, benefit deductions, garnishments, retirement contributions, and other

authorized items. Some amounts reduce employee net pay; others are employer-side liabilities or bookkeeping entries.

4. Net pay and employer totals

Net pay is the employee result after applicable taxes and deductions, plus any net additions or reimbursements. At the employer level, a run also needs totals that explain the combined wages and liabilities for the period. Those totals support cash planning, reconciliation, and later reporting.

5. Year-to-date continuity

Year-to-date values help connect one pay period to the next. They should carry forward from a trustworthy prior completed record, not from an unreviewed draft. If a correction changes a prior period, the effect on later year-to-date values should be traced deliberately.

6. Payroll register and employee records

A payroll register provides the employer-level detail for the run, while employee statements show the individual employee result. The Department of Labor requires covered employers to preserve specified wage-and-hour records, and the IRS has separate employment-tax recordkeeping requirements. The exact document format is less important than keeping complete, accurate, traceable information.

What a payroll run does not automatically include

A calculation or record package does not automatically mean wages were paid, taxes were deposited, returns were filed, or every state requirement was satisfied. Those are separate responsibilities. A good workflow makes the boundary visible instead of implying that generating a statement completed the entire payroll process.

LeoFolio’s U.S. Pay Run focuses on the calculation, review, and record-preparation portion for one employer and up to five employees. A completed run can produce a payroll register, funds summary, Bookkeeper Handoff, CSV records, and employee statement PDFs from the same completed snapshot.

Quick FAQ

Is a payroll run the same as a paystub?

No. A paystub or employee statement is one output. A payroll run is the broader period-level process that produces employee results and employer records.

Does every payroll run need a payroll register?

A register is a highly useful control and recordkeeping tool because it consolidates employee-level results, but legal recordkeeping rules focus on the underlying required information rather than one branded document format.

Can a payroll run be reviewed before employees are paid?

Yes, and that is generally the safest time to catch input or calculation issues—before the results are relied on for wage payment and reporting.

LeoFolio pathway

For small-employer payroll record preparation, LeoFolio U.S. Pay Run supports one employer and up to five employees per completed run, with reviewable calculations and a coordinated record package.

Source notes for editorial verification

Related LeoFolio resources
U.S. Payroll · Calculation methodology · Payroll Review
Explore Payroll →