A security company with guards posted across three states doesn’t have one payroll problem. It has three, running at the same time, each with its own rules.
More states mean more forms, more filings, and more line items in the payroll budget. State-specific compliance rules don’t surface until an audit, a complaint, or a state notice finds them, and by then the exposure has already built up.
Overtime doesn’t work the same way everywhere
Federal law calculates overtime on a weekly basis: over 40 hours, time and a half. A handful of states don’t follow that rule.
California requires daily overtime after 8 hours in a single shift, regardless of the weekly total. A guard who works a 10-hour shift and then takes the next 2 days off has already triggered overtime that a federal-only calculation would miss entirely.
If your payroll system defaults to the federal standard across every location, guards in daily-overtime states are being underpaid, and your company is carrying that liability.
Local minimum wage can beat the state rate
State minimum wage isn’t always the number that applies. Dozens of cities and counties set their own minimum wage above the state floor, and the rate changes almost every year.
A guard working a post in one of those cities has to be paid the local rate, even if the rest of your payroll setup runs off the state number. Multiply that across several contracts in several cities, and one missed local rate becomes a pattern an auditor will notice.
Sick leave is mandatory in more places now
Paid sick leave used to be a benefit companies chose to offer. In a growing number of states and cities, it’s a legal requirement, and the accrual rules differ by jurisdiction: hours worked per hour of leave earned, caps on accrual, carryover rules, and separate notice requirements telling employees how much leave they’ve built up.
For a distributed guard force, that means tracking sick leave accrual by work location, not by company headquarters. A guard who splits time between 2 jurisdictions may be accruing leave under 2 different sets of rules at once.
Final pay has a deadline, and it moves
When someone leaves the company, several states set a hard deadline for the final paycheck, and the deadline for an involuntary termination is often shorter than for a resignation. California requires immediate payment on the day of an involuntary termination. Other states allow until the next scheduled payday.
In several states, missing that window triggers a statutory penalty that accrues by the day until the final check is paid.
Pay stubs have to say more in some states
A handful of states require itemized wage statements that go well beyond gross pay and net pay. California’s pay stub law requires listing every applicable hourly rate, total hours worked at each rate, and specific identifying information for the employer.
A generic pay stub template built for one state often falls short of another state’s itemization rules. That gap doesn’t surface until an employee, or their attorney, asks for records.
Why this keeps happening
None of these traps come from a single bad decision. They come from applying one state’s rules, usually the company’s home state, everywhere guards happen to be posted.
The fix is a payroll process built to check jurisdiction by pay period: overtime rule, minimum wage, sick leave accrual, termination timing, and pay stub format, confirmed for every location where guards actually work, not just where the company is headquartered.
For a contractor bidding on posts in new states, run that check before the contract starts. Waiting until a guard asks why their check looks different from a coworker’s in another state means the mistake already happened.