Wage statement

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

A wage statement explains one payroll result

A wage statement is often called a pay stub or earnings statement. It commonly shows the pay period, pay date, gross earnings, hours, rates, deductions, taxes, and net pay. Required fields vary by jurisdiction and worker type.

The statement is distinct from the paycheck or deposit, the underlying time record, a tax return, and Form W-2. Each record answers a different question.

Build a jurisdiction register

Federal wage-and-hour law requires employers to keep specified payroll records, but it does not create one national pay-stub format. DOL Fact Sheet 21 describes the federal recordkeeping baseline.

States and localities may require itemized statements and prescribe fields, timing, electronic-consent rules, access, language, correction, or penalties. Use the DOL state labor directory to locate authorities, then save the current primary rule and effective date.

Map each required field

Create a versioned field matrix for employer identity, employee identifier, pay period, pay date, total hours, rates, gross wages, overtime, premiums, piece rates when applicable, additions, deductions, taxes, employer contributions when required, leave balances, and net pay.

Map every field to a reliable source. Payroll calculation should supply earnings and deductions. Timekeeping should supply actual hours. Benefit and leave systems should supply their own balances. Avoid deriving a required value from a display label.

ABA earning labels should be understandable

An ABA practice may pay direct service, documentation, travel, training, supervision, meetings, administrative time, overtime, differentials, and leave. A statement should use labels that an employee can connect to the policy and underlying record.

Billing codes and payer units belong in the claim workflow. They should not replace wage categories or conceal paid work that is not billable.

Delivery must remain usable

Electronic delivery can be efficient, yet the practice should verify whether consent, notice, access, printing, or post-employment availability rules apply. Record when the statement became available and which version the employee received.

Provide an accessible correction channel. Plan for employees who lose portal access, change contact information, need a disability-related accommodation, or receive a final payment outside the usual cycle.

Reconcile before release

Compare each statement with the approved time record, payroll register, benefit elections, tax setup, leave ledger, payment file, and general ledger. Check pay period, pay date, hours, rates, gross-to-net math, deductions, taxes, and employee identity.

IRS Publication 15 supports the federal payroll and tax records that feed this review. It does not supply every state statement field.

A fictional two-state review

Stonepath ABA locks 33 wage statements for employees working in California and Oregon. Thirty-one match the applicable field map, approved time, payroll register, leave balance, payment, and delivery route. One omits a required state field. One contains an outdated deduction label.

Release readiness is 31 of 33 statements, or 93.9%. Both held statements remain in the queue. The result measures agreement with the configured review, not legal compliance or employee receipt.

Corrections need a traceable version

When a statement is wrong, identify whether the source error affects pay, time, tax, leave, benefits, or display only. Follow the jurisdiction's timing and correction route. Pay any wage shortage under the applicable deadline rather than waiting for a convenient payroll when the law requires earlier action.

Preserve the original statement, corrected version, reason, approval, payment evidence, delivery, and employee communication. Update downstream tax or benefit records when affected.

Protect and retain statement data

Statements contain compensation, tax, bank, leave, and identity information. Use role-based access, secure delivery, audit logs, and limited retention access. Do not expose another employee's record in a shared folder or email thread.

Retain statements and their source records for the longest applicable federal, state, tax, contract, and litigation-hold period.

Test what the employee actually sees

Review the rendered statement rather than only the payroll register. Test mobile and printed views, long earning labels, multiple rates, overtime, leave, reimbursements, garnishments, zero-net checks, off-cycle payments, final pay, and a corrected statement.

Confirm that required fields remain visible, totals reconcile, labels are understandable, and the employee can retrieve the record after delivery. Check accessibility, language support, secure login, printing, and post-employment access under applicable rules.

Measure statements passing every required field and delivery check divided by all statements due for release. Keep held statements in the denominator and separate display defects from pay errors. A correct net payment does not cure a missing required statement, and a polished statement does not validate the underlying wages.

Maintain a field matrix by jurisdiction and effective date, then test each payroll configuration against rendered output. Require approval for label, balance, deduction, address, and delivery changes. When a statement is corrected, link the prior and revised versions and confirm whether wages, taxes, benefits, or accounting also require correction.