Pay Stub Requirements by State: What Employers Must Include

Federal Law vs State Pay Stub Law

The first thing to know: there is no single federal pay-stub rule for private employers. The Fair Labor Standards Act requires covered employers to keep accurate records of hours worked, wages paid, deductions, pay dates, and pay periods. It does not require the employer to hand every employee a pay stub.

That gap is filled by state law. California, New York, Ohio, Colorado, Washington, Oregon, and many other states require an itemized wage statement each pay period. Some states are light-touch and focus mostly on pay frequency. A small group still has no broad itemized wage-statement requirement, though payroll software often issues stubs anyway.

For employers, the practical rule is simple: build the stub to satisfy the strictest state where the employee works. A remote employee in California needs California-compliant information even if the company is incorporated in Florida. A worker who moves mid-year can create state-withholding and wage-statement issues at the same time.

Fields Most States Expect to See

State statutes vary, but most pay-stub requirements revolve around the same core fields:

• Employee name or employee identifier
• Employer legal name and address
• Pay period start and end dates
• Pay date
• Gross wages
• Net wages
• Itemized deductions
• Hours worked for non-exempt employees
• Hourly rates or salary basis
• Overtime hours and overtime rate where applicable
• Year-to-date totals, when required or customary

California is one of the clearest examples. California Labor Code §226 requires gross wages, total hours worked for non-exempt employees, deductions, net wages, pay-period dates, employee identification, employer name and address, and applicable hourly rates with corresponding hours. That level of detail is why California is often used as the model when multi-state employers build a national stub template.

New York requires employers to furnish a wage statement with every payment of wages under Labor Law §195. The statement must show dates of work covered, employee and employer details, rates of pay, gross wages, deductions, allowances claimed as part of minimum wage, and net wages. For non-exempt employees, it also requires regular and overtime rates and hours.

Ohio is a good recent example of a state moving into the regulated category. The Ohio Pay Stub Protection Act, ORC §4113.14, took effect in April 2025 and requires employers to provide a written or electronic statement showing earnings and deductions for each pay period.

State Rules Are Not Just About Pay Frequency

The Department of Labor's state payday table is useful, but pay frequency and pay-stub content are different questions.

Pay frequency asks: how often must wages be paid? Weekly, biweekly, semi-monthly, monthly, or some state-specific version of those.

Pay-stub content asks: what information must accompany the payment? That answer lives in state wage-statement statutes, wage-payment acts, or labor department guidance.

An employer can satisfy payday frequency and still fail wage-statement content. For example, paying twice a month on time does not help if the stub omits hours, rates, or deductions in a state that requires them.

Electronic Pay Stubs

Electronic stubs are common, but state rules decide whether portal-only delivery is enough. A good electronic process gives employees:

• Notice that stubs are available
• Access on payday
• The ability to download or print
• Continued access after termination, or a clear paper-copy process
• A way to correct login problems quickly

The risk with electronic delivery is not the PDF. The risk is access. If an employee cannot reach the portal after a password reset, termination, or phone-number change, the employer may have technically issued the stub but practically withheld it.

Multi-State and Remote Employees

Remote work makes pay-stub compliance messier. The state where the employee performs work often controls wage-payment obligations, even when the employer is headquartered somewhere else. A New York company with a Washington employee should not assume New York's wage-statement process is enough for Washington.

The safest workflow is to track work location, residence, and tax-withholding state together. When one changes, payroll should review all three:

• State income tax withholding
• Local tax withholding, if any
• Wage-statement fields and delivery rules
• Final-pay timing rules
• Paid sick leave or other state-specific balances shown on stubs

That is also why pay stubs for remote and multi-state workers deserve a separate review from normal payroll setup.

Compliance Checklist for Employers

Before issuing pay stubs, check five things.

First, identify the employee's work state. Do not rely only on company headquarters.

Second, confirm pay frequency. The DOL table is a starting point, but state labor offices and state statutes are the authority.

Third, build the wage-statement fields for that state. California, New York, and Ohio are useful examples because they spell out required items in statutory language.

Fourth, confirm electronic delivery rules. If consent or paper access is required, document it.

Fifth, retain the underlying payroll records. Under DOL guidance, payroll records must generally be retained for at least three years, and records supporting wage computations for two years. The stub is what the employee sees; the payroll record is what the employer defends.

Create a compliant-looking pay stub with the fields reviewers expect, then check it against the state rule that applies to the worker.