Two employees can share the same job title, sit in the same office, and still work under two entirely different employers when it comes to who actually answers for a legal problem. A Professional Employer Organization (PEO) arrangement splits employer responsibilities between the client entity and the PEO by contract – but courts, the EEOC, and the NLRB don’t decide liability by reading that contract. They decide it by asking who actually controlled the decision that caused the harm.
Joint Employer Doctrine Doesn’t Care What the Contract Says
When a discrimination claim, wrongful termination suit, or wage-and-hour violation surfaces at a PEO client, both the PEO and the client business can be named as co-defendants under joint employer doctrine, regardless of how the service agreement allocates responsibility between them. Courts look at who actually made the hiring, firing, discipline, scheduling, and pay decisions – and because a properly structured PEO arrangement leaves those exact decisions with the client (the PEO only handles tax and administrative employer functions), the client entity typically remains the party legally exposed for its own day-to-day employment decisions, PEO contract or not.
What EPLI Coverage Through a PEO Actually Covers
Most PEO agreements include the worksite employees under the PEO’s own Employment Practices Liability Insurance (EPLI) policy, extending coverage for discrimination, wrongful termination, harassment, and retaliation claims to the client business as an additional insured. This is a genuine cost advantage – EPLI purchased individually by a small business is often expensive or hard to obtain at all, while PEO-sponsored EPLI comes bundled into the service fee. The coverage typically has policy limits and exclusions the client never negotiated directly, so reading the actual PEO master policy (not just assuming full protection exists) matters before treating it as a liability solution.
Who’s on the Hook If the PEO Itself Fails
A separate liability question is what happens if the PEO fails to remit payroll taxes or benefit contributions it collected. With a standard, non-certified PEO, the client entity can remain legally liable to the IRS for unpaid federal employment taxes even though the PEO collected the money to pay them – the co-employment contract doesn’t shift that statutory liability away from the client. A Certified PEO (CPEO) under IRC Section 7705 is solely liable for the federal employment taxes on wages it processes, which is the real legal reason CPEO certification matters more than a marketing label.
State PEO Licensing Requirements Vary Sharply
Most states require PEOs to register or obtain a license before operating, but the requirements and the resulting client protections differ significantly by state – some states require PEOs to maintain minimum working capital or bonding specifically to protect client businesses if the PEO becomes insolvent, while others have comparatively thin registration requirements. Checking a prospective PEO’s state registration status and any available financial-responsibility disclosures is a real due-diligence step, not a formality.
Practical Takeaway
A PEO arrangement genuinely reduces administrative burden and can extend real EPLI protection, but it does not eliminate the client business’s own legal exposure for the employment decisions it actually makes. The contract’s allocation of duties matters for figuring out who indemnifies whom afterward – it does not control who a plaintiff can sue in the first place.
Affiliate Disclosure: This page may contain affiliate links. If you make a purchase or sign up through these links, we may earn a commission at no extra cost to you.
Related reading: Professional Employer Organizations (PEO) and Workers’ Compensation Requirements by Entity Type.
Recent Comments