Introduction
Payroll compliance should be straightforward. Pay employees time-and-a-half for overtime, deduct taxes, done. In reality, managing overtime across state lines is a minefield of conflicting regulations, daily minimums, salary thresholds, and calculation methods that trip up HR teams regularly.
The federal Fair Labor Standards Act (FLSA) sets a baseline: non-exempt employees earn at least 1.5× their regular rate for hours worked over 40 in a workweek. But 20+ states have layered on their own rules—some more generous to workers, some with industry-specific exceptions. A California employee hitting 8 hours in a day triggers daily overtime. A New York employee works under daily thresholds and a weekly calculation. A Texas employee might be exempt from state overtime entirely if federal law covers them.
Payroll software either handles this complexity elegantly or becomes a liability. This article walks through how the overtime patchwork works and what separates capable payroll systems from the ones that leave you exposed.
The Federal Floor: FLSA Basics
The FLSA's overtime rule is deceptively simple in principle. Covered, non-exempt employees must receive overtime compensation—at least 1.5 times their "regular rate"—for all hours worked exceeding 40 in a workweek (168 consecutive hours).
The regular rate calculation is where subtlety kicks in. It's not just the base salary. Commissions, bonuses, and shift differentials typically fold in. Expense reimbursements and gifts don't. Some payroll software auto-captures these; others leave you fishing through documentation.
The workweek is crucial too. A workweek doesn't have to be Monday–Friday. Manufacturing companies might run Sunday–Saturday. Call centers might use a rolling definition. Your payroll system needs to accommodate this. Most SaaS payroll platforms default to Monday–Sunday but allow customization—a critical feature when auditors check your records.
Exemption status matters enormously. If an employee meets the executive, professional, or administrative exemption, no overtime owed. The salary threshold is $35,568 annually (as of 2024, indexed to inflation). However, state minimums differ. California's threshold is effectively higher when you factor in state-specific overtime laws.
State Variations: The Complexity Layer
Daily Overtime
California, Colorado, Nevada, and a handful of other states impose daily overtime thresholds independent of the weekly 40-hour rule.
California's model:
- 8 hours in a day = 1.5×
- 12 hours in a day = 2×
- 8+ on a seventh consecutive day = 1.5× (and 2× for hours 12+)
This is strict. An employee working 9 hours Monday and 36 hours the rest of the week still owes 1 hour of daily overtime for Monday alone. Many small business owners miss this. Their payroll system says "40 hours for the week, no overtime," but California audits catch the daily violation.
Colorado, Nevada, and Washington have weaker daily thresholds, but they exist. Vermont and Minnesota apply penalties for missed meal breaks that mimic overtime penalties. None of this is captured by generic federal-only payroll logic.
Salary Threshold Variations
New York and Illinois have raised their salary thresholds for exemptions above the federal floor:
- Federal: $35,568/year
- New York (2024): $41,600/year (increases annually)
- Illinois: $43,453/year (also indexed)
If you have a salaried manager at $38,000 earning 50 hours a week, they're exempt federally but non-exempt in New York. Your payroll system must flag this.
Weekly Overtime Rules
New York applies overtime at 1.5× for hours over 40 and any hours worked on a seventh consecutive day (after six days of work), whichever yields more. This overlap creates edge cases. Some weeks you owe 10 hours of OT by the weekly rule; some weeks you owe 15 by the seventh-day rule.
State-Specific Exemptions
Texas and most Southern states follow federal exemption rules closely. But Nevada, for instance, exempts certain IT professionals, and Massachusetts has narrow exemptions for outside salespeople. These rarely come up in practice but can expose you if misapplied.
The Overtime Calculation Comparison
| State | Daily OT | Weekly OT | Threshold | Key Wrinkle |
|---|---|---|---|---|
| Federal (FLSA) | None | 40 hrs/week @ 1.5× | $35,568/yr | Baseline rule |
| California | 8 hrs/day @ 1.5×; 12+ @ 2× | 40+ @ 1.5× | Must meet both rules; 7th day rules apply | |
| New York | None | 40+ @ 1.5×; 7th day @ 1.5× | $41,600/yr | Weekly or 7th day, whichever is higher |
| Colorado | After 12 hrs @ 1.5× | 40+ @ 1.5× | $35,568/yr (federal) | Must meet both; day takes priority |
| Texas | None | 40+ @ 1.5× (if subject to FLSA) | Federal only | No state law; relies entirely on FLSA |
| Washington | None | 40+ @ 1.5× | $35,568/yr (federal) | Stricter meal-break penalties |
| Illinois | None | 40+ @ 1.5× | $43,453/yr | Higher exemption threshold |
| Massachusetts | None | 40+ @ 1.5× | $35,568/yr (federal) | Strict exemption rules |
Common Overtime Compliance Mistakes
Mistake 1: Applying Federal Rules to Multi-State Employees
A contractor in California works 38 hours and gets a federal system that skips OT. California's daily rule might still apply. The system shows green; your audit shows a violation. Modern payroll software, like Guidepoint or Zenefits, flags by state of employment, not headquarters location.
Mistake 2: Miscalculating the Regular Rate
You award a one-time bonus. Does it roll into the regular rate for that period's OT? Most do. Payroll software usually handles this automatically but not always for retroactive bonuses or commission corrections. Confirm your system's logic.
Mistake 3: Ignoring Shift Differentials
A night-shift employee earns $15/hour base + $2/hour differential. Their regular rate is $17/hour. Overtime is $25.50/hour. Many small payroll systems calculate OT from base only, underpaying by thousands annually.
Mistake 4: Missing Meal Break Violations
Washington and a few other states assess penalties for missed meal breaks (e.g., $13 in Washington). These aren't technically "overtime," but they accumulate fast. Basic payroll software doesn't track them.
How Payroll Software Handles the Patchwork
Tier 1: Enterprise Systems (ADP, Paychex, Workday)
- Coverage: All 50 states, all edge cases. Built-in rule engines. Automatic updates when laws change (California's thresholds increase every January).
- Cost: $5–20 per employee per month, often bundled with benefits and tax filing.
- Strength: Comprehensive, audit-proof. You're outsourcing compliance risk to a vendor with teams of compliance specialists.
- Weakness: Expensive for small payroll (<20 employees). Bloated with features you don't need.
Tier 2: Mid-Market SaaS (Guidepoint, Rippling, OnPay)
- Coverage: Most states handled well; some edge cases flagged as manual overrides. Frequent updates.
- Cost: $8–15 per employee per month.
- Strength: Better UX than legacy systems. Affordable. Usually handles 95% of scenarios automatically.
- Weakness: Misses rare scenarios. PayrollToolPick reviews often highlight that smaller platforms miss specific state rules or require manual configuration.
Tier 3: Budget Platforms (Square Payroll, Gusto)
- Coverage: Federal + most common state rules. Less frequent updates.
- Cost: $3–8 per employee or flat $20–50/month.
- Strength: Cheapest entry point for small teams.
- Weakness: Known gaps. California users report missing daily OT calculations. New York salary threshold updates are delayed. Manual workarounds required.
Red Flags in Payroll Software
- No state selection or only "Federal." Unacceptable for multi-state payroll.
- Vague documentation on how overtime is calculated. Ask for specifics.
- No audit trail showing how OT was computed. If you're audited, you can't defend the math.
- Doesn't update automatically for inflation-indexed thresholds (New York, Illinois). You have to manually enter these.
Choosing the Right Tool for Your Complexity
One state, under 50 employees: Gusto or Square Payroll is fine if your state isn't California. If you're in California, upgrade to OnPay or Rippling.
Multi-state, any size: ADP or Paychex is the safe choice. You pay more, but compliance risk is their problem.
California + one other state: Rippling or Guidepoint. They handle the California complexity well and don't bloat the rest of the system.
Lots of commissions, shift differentials, or unusual bonuses: Enterprise system only. The regular rate calculation complexity requires rule-engine power.
Conclusion
Overtime compliance isn't optional. A single misclassified month of overtime across a team of ten can cost $2,000+ in back pay, penalties, and admin time to fix in audit. Scaled to a year, it's a real line item.
The solution isn't to buy the most expensive system. It's to buy a system that handles your specific state complexity. Map your state's rules, test the payroll system's logic, and verify the audit trail before going live. Most payroll vendors offer sandbox environments and will run a test payroll to prove it.
Your payroll is one of the few areas where "close enough" isn't acceptable. The time spent validating overtime logic upfront saves hours of scrambling later.
Top comments (0)