People sometimes use the terms HR and People Ops interchangeably. But when they do differentiate, they put the wrong people in the wrong seats.

The PEO issues the paycheck, but you pay the wages, taxes, and employer portion of benefits. Since the PEO is the employer on paper, they handle registering for state agencies and tracking compliance laws. And because PEOs can pool all of their client-employees, you get access the more affordable and flexible large-group benefits.

When someone is paid for a day they didn't work, it MUST be entered into payroll as some kind of Paid Time Off type. Otherwise, there's no way to pay it. Most of the uncommon leave types don't allow negative balances in payroll systems. So if your time off isn't allocated to another bucket, it can't get paid. The discrepancy could even block payroll and prevent everyone from getting paid.

Let me give you a “hypothetical” example that has definitely never happened in real life. It’ll make your blood run cold.

This wasn’t payroll. It was a cold case. Policies contradicted payroll data. Contracts were locked behind sharing permissions from people who’d left the company. Folder names were gibberish. People paid hourly were getting flat rates with no timecards to confirm overtime. A million Scribe docs with no annotations. Hours of 20-minute videos with no transcripts.

People Ops doesn’t have to be in-house. It doesn’t have to be full time. It doesn’t even have to “feel” like HR. But it does have to be done right.