Most business owners signing a PEO agreement assume they’ve just handed off their compliance headaches. And in many ways, they have — payroll taxes, benefits administration, workers’ comp. The PEO takes on the employer-of-record role, and suddenly HR feels manageable again.
But here’s where a lot of operators get into trouble: they assume that compliance shield extends to worker classification. It often doesn’t. And the gap between what business owners think their PEO covers and what the service agreement actually says is where misclassification liability quietly accumulates.
Misclassification isn’t a paperwork technicality. We’re talking back employment taxes, IRS penalties, state unemployment assessments, workers’ comp exposure, and in some cases, wage and hour lawsuits. The financial hit can be severe, and it lands on whoever the relevant agency decides is the responsible employer — which isn’t always the PEO.
This article is a narrow, practical look at how misclassification risk plays out specifically inside co-employment arrangements. It’s not a broad overview of PEO relationships — if you want that foundational context, you’ll find it in our broader PEO risk management guide. What this covers is the specific question of who holds the bag when a classification dispute arises, and what real enforcement patterns reveal about that answer.
Co-Employment Doesn’t Simplify Classification — It Complicates It
The co-employment model splits the employer role between two parties. The PEO handles payroll processing, tax filings, and benefits. The client company handles the actual work: who does what, when, how, and with what tools. That division sounds clean in a brochure. In a classification dispute, it creates real ambiguity.
Federal and state agencies don’t use a single test to determine whether someone is an employee or an independent contractor. The IRS applies a common-law test that weighs behavioral control, financial control, and the nature of the relationship. The Department of Labor uses an economic reality test for purposes of the Fair Labor Standards Act, asking whether the worker is economically dependent on the employer. Many states — particularly California, Massachusetts, New Jersey, and Illinois — use some version of the ABC test, which presumes a worker is an employee unless the hiring entity can prove all three prongs: the worker is free from control, performs work outside the company’s usual business, and operates an independent trade or business.
Here’s the critical point: a PEO relationship doesn’t automatically satisfy any of these tests. The IRS isn’t impressed that you have a co-employment agreement. The DOL doesn’t care that someone else is processing your payroll. What these agencies care about is who actually controls the work — and in almost every PEO arrangement, that’s the client company.
There’s also an important distinction that gets blurred constantly. PEOs cover W-2 employees. If your workforce includes 1099 independent contractors, those workers are almost certainly not covered under your PEO agreement. That seems obvious when you say it out loud, but in practice, many businesses operate with a mix of W-2 employees (covered by the PEO) and 1099 contractors (not covered), and they carry a vague sense that the PEO relationship provides some protective umbrella over the whole operation. It doesn’t.
The misclassification risk that gets businesses in trouble inside a PEO arrangement tends to fall into two buckets. First, there’s the scenario where W-2 workers covered by the PEO are later challenged on their classification status by a state agency applying a stricter test than the PEO anticipated. Second, and far more common, there’s the 1099 contractor situation — where the PEO has nothing to do with those workers, yet the client assumed the compliance relationship extended to them. The second scenario is where most of the enforcement pain actually lands.
How Liability Ends Up With the Client Company, Not the PEO
When the IRS or DOL pursues a misclassification case, they’re looking for who exercised control over the worker’s day-to-day activities. In a co-employment arrangement, that answer is almost always the client company. The PEO set up the payroll system. The client told the worker what to do, when to show up, and what equipment to use. Under the common-law test, that operational control is what matters most.
The enforcement pattern that has emerged across construction, trades, and service industries is consistent: businesses use a PEO for their core W-2 workforce, but also bring in subcontractors for project work. When state or federal agencies audit those businesses, they examine the subcontractors and apply the applicable classification test. If the subcontractors were working under conditions that look more like employment than independent contracting — fixed schedules, client-supplied tools, work that’s central to the business’s core operations — the agency reclassifies them. Back taxes, penalties, and interest follow. The PEO is not part of that equation because those workers were never on the PEO’s payroll.
Construction is the most documented example of this pattern. States including California, Massachusetts, and New York have run targeted regulatory enforcement initiatives against construction employers specifically because the industry relies so heavily on subcontractors, and the line between a legitimate subcontractor and a misclassified employee is frequently blurry. A framing crew that shows up to your job site every day, uses your equipment, and works only for your company looks a lot like employees under most classification tests — regardless of what the contract says.
What makes this worse for PEO clients is the indemnification language buried in their service agreements. Standard PEO contracts include clauses that require the client to indemnify the PEO against any losses arising from the client’s classification decisions, particularly for workers not covered under the agreement. This is boilerplate in the industry. It means that if a misclassification dispute arises and somehow pulls the PEO into the legal process, the client is contractually obligated to hold the PEO harmless.
Most business owners never read these clauses carefully before signing. They see “employer of record” and assume the PEO is absorbing classification risk. The contract says otherwise. The PEO is the employer of record for the specific W-2 employees enrolled in the program — full stop. Everything outside that boundary is the client’s problem, and the indemnification clause makes sure the PEO can enforce that boundary if a dispute arises.
The Subcontractor Blind Spot
Here’s the scenario that plays out more often than most PEO providers will tell you about upfront. A business owner sets up a PEO arrangement for their 12 full-time employees. It goes smoothly. Benefits are handled, payroll taxes are filed, workers’ comp is covered. The owner feels like they’ve solved their HR problem.
Meanwhile, the same business regularly uses four or five 1099 subcontractors for overflow work. These folks have been around for years. They’re reliable. They work primarily for this one company, use equipment provided by the company, and follow schedules set by the company. But they’ve always been paid as 1099s, and nobody’s questioned it.
The PEO relationship creates a false sense of security around those workers. The owner has a compliance-focused HR infrastructure in place. There’s a professional employer on the letterhead. Surely that provides some protection, right? It doesn’t. The PEO has no visibility into those subcontractors, no contractual relationship with them, and no liability for how they’re classified.
State-level ABC tests are what make this genuinely dangerous. California’s AB5, which codified the ABC test from the landmark Dynamex Operations West v. Superior Court decision, is the most aggressive version. Under AB5, a worker is presumed to be an employee unless the hiring company can prove all three prongs of the ABC test. Prong B alone — that the work performed is outside the usual course of the hiring entity’s business — disqualifies most subcontractors in service businesses. If your company builds houses and your subcontractors build houses, they’re employees under California law regardless of your contract language.
Massachusetts and New Jersey have similarly strict ABC tests. Illinois applies a version for unemployment insurance purposes. If your business operates in any of these states and uses 1099 subcontractors, you carry real exposure that your PEO arrangement does nothing to address.
A practical way to audit your situation: pull a list of every person your company paid in the last 12 months. Separate W-2s from 1099s. For each 1099, ask three questions. Does this person work primarily or exclusively for us? Do we control their schedule, location, or methods? Is their work central to what our business does? If the answer to any of those is yes, you have a classification question worth examining before an auditor does it for you.
Reading Your PEO Contract Before It’s Too Late
PEO service agreements aren’t short, and the classification liability language isn’t in the summary section. It’s in the indemnification provisions, the representations and warranties section, and the definitions of “covered employees.” Most business owners read the pricing schedule and sign the rest.
The typical contract structure works like this: the PEO agrees to act as co-employer for workers specifically enrolled in the program. The client represents and warrants that those workers are properly classified as employees. If they’re not, the client indemnifies the PEO. Workers not enrolled in the program — including any 1099 contractors — are explicitly excluded from the PEO’s obligations. Some contracts go further and require the client to notify the PEO of any worker classification changes during the contract term.
One distinction worth understanding is the difference between a standard PEO and a Certified PEO (CPEO). The CPEO designation was established under the Tax Increase Prevention Act of 2014 and is administered by the IRS. Under IRC Section 3511, CPEOs are treated as the employer for federal employment tax purposes, which means certain federal tax liabilities can shift to the CPEO. This is a meaningful distinction for clients who want cleaner federal tax liability allocation.
But CPEO status doesn’t resolve state-level classification disputes or DOL enforcement actions. It’s a federal tax designation. If California’s Employment Development Department decides your subcontractors are employees under AB5, CPEO certification is irrelevant to that determination. Business owners sometimes conflate CPEO status with broader compliance protection — they’re not the same thing.
Before signing or renewing a PEO agreement, ask your provider these specific questions. First, which workers are explicitly covered under the co-employment agreement, and how are “covered employees” defined? Second, what does the indemnification clause say about classification disputes, and who bears liability if a covered employee’s classification is challenged? Third, does the agreement require you to represent that all enrolled workers are properly classified, and what happens if that representation is later disputed? Fourth, does the PEO offer any classification audit support or legal guidance for workers outside the agreement? Fifth, is the PEO a CPEO, and what specifically does that mean for your federal tax liability exposure?
If your PEO can’t answer these clearly, that’s information worth having before you’re locked into another contract year.
Auditing Your Workforce Before an Agency Does It for You
The best time to identify a misclassification problem is before someone with a government ID shows up asking questions. An internal classification audit doesn’t require outside counsel, though it’s worth involving an employment attorney if you find gray areas. The process itself is straightforward.
Start with a complete workforce inventory. List every person your business pays — W-2 employees, 1099 contractors, project-based workers, anyone. For each 1099, document the actual working relationship: how long they’ve worked with you, whether they work for other clients, who controls their schedule, what equipment they use, and whether their work is core to your business or genuinely peripheral. Apply the relevant test for your state. If you’re in California, Massachusetts, or New Jersey, apply the ABC test. If you’re primarily concerned about federal exposure, work through the IRS common-law factors.
When you find gray areas — and you will — document your reasoning. The IRS Section 530 safe harbor can protect businesses from back taxes if they had a “reasonable basis” for their classification decision and applied it consistently. That reasonable basis needs to be documented. Relying on a PEO relationship for workers who were never enrolled in the PEO doesn’t qualify as reasonable basis.
The conversion question comes up constantly: should you move 1099 workers onto the PEO’s payroll as W-2 employees? Sometimes yes. If a subcontractor is functionally an employee by any reasonable test, conversion eliminates the exposure and may actually simplify your operations. The PEO can often absorb the additional W-2 headcount without major friction.
Other times, a different structure makes more sense. An employer of record (EOR) arrangement might be appropriate for genuinely project-based workers. Direct hire works when the relationship is clearly employment from the start. The point is to match the legal structure to the actual working relationship — not to force everyone into the cheapest classification.
On cost: yes, converting a 1099 to a W-2 adds payroll tax and potentially benefits cost. Businesses resist this for understandable reasons. But compare that ongoing cost against IRS penalty exposure, which includes back employment taxes for all open tax years, failure-to-file penalties, and interest. For a worker who’s been misclassified for three or four years, the back-tax assessment alone can be substantial. The math usually favors getting the classification right.
The Bottom Line on PEO and Classification Risk
A PEO is a genuinely useful tool. It handles payroll, reduces administrative burden, improves benefits access, and can meaningfully reduce certain compliance risks. But it’s a tool with a defined scope — and classification liability sits at the edge of that scope in ways that aren’t always obvious when you’re signing the agreement.
The pattern across enforcement actions is consistent: the client company bears classification liability for workers it controls, especially those outside the PEO’s enrolled workforce. The PEO’s service agreement almost always confirms this in the fine print. Co-employment doesn’t create a compliance guarantee; it creates a compliance framework with specific boundaries.
If you haven’t reviewed your workforce classification recently, do it now — not because an audit is necessarily coming, but because the exposure is real and the fix is usually manageable when you catch it early. Read the liability sections of your PEO service agreement. Understand what your PEO actually covers and what it explicitly excludes. Ask your provider direct questions about classification support.
And when you’re evaluating whether your current PEO arrangement is actually serving your business, compare it against alternatives with clear eyes. Different PEOs handle classification risk support very differently. Some offer proactive audit support; others offer indemnification language that pushes everything back to you. Knowing the difference matters.
Don’t auto-renew. Make an informed, confident decision. The right PEO for your business is the one that actually covers the risks you’re carrying — not just the risks that are easy to sell in a pitch deck.
