If you run an IT managed service provider, a PEO agreement is not just another vendor contract. It creates a co-employment relationship, and several of its default terms were written with a stable, office-based workforce in mind. Your workforce is not that: it has on-call rotations, overtime spikes, technicians at customer sites, and staff with privileged access to other companies’ systems.
That mismatch is where IT managed service providers PEO contract terms deserve a slower read. The clauses that decide whether the arrangement works are the ones covering fees, insurance, duties, and exit, and each interacts with the client service agreements you already hold.
This is general information, not legal, tax, or benefits advice. Your counsel and broker should review the actual document.
Why an MSP’s Workforce Makes PEO Contracts Harder to Read
In a PEO arrangement, the PEO and your company share certain employer responsibilities. Typically the PEO runs payroll, files payroll taxes under its own accounts, offers benefits through its plans, and supports HR compliance. You keep day-to-day control: who you hire, what they work on, how they’re supervised, and when they’re let go. The exact split lives in the client service agreement between you and the PEO.
That document is a separate layer from the master services agreements (MSAs) you hold with your own customers. The PEO contract does not replace, satisfy, or override anything in an MSA. Your customers may still demand specific insurance, background screening, confidentiality terms, and personnel standards, and you remain on the hook for them.
Where an MSP strains a standard agreement
- Hourly help desk staff work alongside salaried engineers, so overtime rules and pay structures differ within one team.
- After-hours on-call rotations create stipends, call-out pay, and overtime that move month to month.
- Technicians work at customer sites, sometimes in other states.
- Certification-driven raises and bonuses change pay mid-year.
Each of these touches a contract term, from how fees are calculated to how work locations are reported.
Know which structure you’re signing
A PEO contract is not a payroll vendor agreement. An ASO (administrative services organization) provides HR and payroll services without sharing employer responsibility. A payroll-only provider processes pay and taxes. An EOR (employer of record) typically employs workers on your behalf, often in a location where you have no entity. A CPEO is a PEO certified by the IRS under the Small Business Efficiency Act, which affects how it handles federal employment tax responsibility; check the IRS’s current CPEO program details before relying on that status. Before you read further, confirm which of these your draft actually describes. Sales material sometimes blurs them, and the contract controls. If you are still deciding whether a PEO is the right model at all, our look at the best PEO options for IT managed service providers is a useful starting point.
Fee Structure Clauses: Where MSP Margins Get Squeezed
For a services business, labor is the biggest cost line, so a PEO fee that scales with labor deserves scrutiny. The common models are a flat per-employee-per-month fee, a percentage of payroll, and some blend of the two. Benefits may be bundled into one price or priced separately from the administrative fee. Bundled pricing is easy to read and hard to compare, because you can’t see what the administrative layer costs by itself. For a sense of how these structures play out in a similar tech-driven business, see our breakdown of PEO pricing for tech startups.
Clauses that change cost over time
- Renewal adjustments. Look for language letting the PEO reset fees or benefit rates at renewal, and what notice you get before it does.
- Minimums. Some agreements carry minimum headcount or minimum fee terms. Whether yours does must be verified in the document itself, not assumed.
- Recalculation after headcount swings. If you lose a large client and cut a team, ask how fees, benefit pricing, and any minimums respond.
Don’t rely on a competitor’s quoted price as a benchmark unless it comes with a dated source. Rates vary by state, headcount, and plan design.
An illustration of percentage-of-payroll versus flat fees
Suppose, hypothetically, an MSP has a ten-person service desk and a PEO fee of a fixed percentage of gross payroll. In a quiet month, the fee tracks base pay. Then a major outage, a migration project, or a heavy on-call period pushes overtime and call-out pay up. Gross payroll rises, so the percentage fee rises with it, even though the PEO’s administrative work barely changed.
Under a flat per-employee fee, the same surge leaves the administrative charge unchanged. The reverse can also be true: a flat fee can cost more than a percentage fee for a team of low-wage, part-time staff. Neither model is better in the abstract. The right question is which one behaves better against your actual pay mix, including overtime and on-call. Ask each PEO to define precisely which pay types count toward the fee base.
Workers’ Comp, Insurance, and Client-Site Risk Allocation
PEOs generally place worksite employees under workers’ compensation coverage and assign class codes based on job duties. An MSP’s mix makes this less obvious than it sounds. Office-based engineers and help desk staff are usually low-risk clerical or professional classifications, but field technicians pulling cable, racking servers, or working in data centers may be assessed differently. Ask the PEO, in writing, how each of your role types will be classified and what happens if an audit moves someone to a different code.
Also ask whether classification is tied to the job description or to the work actually performed. A help desk analyst who occasionally runs cable on a site visit is the kind of edge case that causes disputes later. For background on how PEO master policies work, see our overview of PEO providers for workers’ compensation insurance.
What the PEO’s coverage does not replace
A common misconception is that a PEO’s master policy covers the company’s business risks. It generally addresses employment-related coverage such as workers’ compensation and, depending on the PEO, certain benefits. It does not substitute for your own:
- cyber liability coverage, which responds to data incidents tied to your services
- professional liability, or errors and omissions (E&O), which covers claims that your work caused a client loss
- general liability, which covers third-party property damage and bodily injury claims
Read the PEO contract for any language implying otherwise, and confirm with your broker that nothing in it affects the policies you carry independently.
Certificates and client-site injuries
Customer MSAs often require specific coverage types and limits, plus additional insured status. Check whether the PEO will issue certificates of insurance showing your customers as certificate holders or additional insureds on its workers’ compensation policy, how quickly, and whether it charges for them. Then look at claims handling: if a technician is injured at a customer location, who reports it, who communicates with the carrier, and what duties you have to cooperate. Define the process before an injury happens, not after.
Co-Employment Responsibilities, Confidentiality, and Client Data Access
The allocation-of-duties section is the heart of the agreement. Typically the PEO handles payroll tax filing, benefits administration, and often HR compliance support. You keep hiring decisions, supervision, discipline, and work direction. Read it line by line for gray zones, such as who runs terminations, who responds to a harassment complaint, and who owns the final decision when the PEO’s advice and your preference diverge. If workplace complaints are a concern, it helps to see which providers take workplace investigations seriously.
Privileged access meets an HR portal
Your technicians hold administrative credentials to customer environments. That makes employee data handling more than an HR convenience question. Ask how the PEO’s HR portal stores employee records, who at the PEO can see them, and what security standards apply. Find out which background-check vendors the PEO uses, since many customer MSAs set screening requirements for anyone with system access, and your screening may need to meet those standards, not just the PEO’s default.
Check whether onboarding passes through the PEO’s systems and whether any customer-specific information, such as site assignments or system names, would end up in them. If an MSA restricts where customer information can go, keep it out of PEO workflows or confirm the PEO’s handling meets those terms. Also see whether the agreement lets the PEO share employee information with subcontractors, and under what safeguards.
IP, non-solicit, and non-compete terms
Your existing employee agreements probably contain IP assignment, confidentiality, non-solicit, and possibly non-compete provisions. Confirm the PEO agreement and the PEO’s employee handbook or onboarding documents don’t contradict them. A handbook acknowledgement that quietly states a different confidentiality standard, or an onboarding package that substitutes a PEO form for your agreement, can muddy who the employer is for these purposes. Enforceability of restrictive covenants varies significantly by state, and it can change, so have employment counsel review how the documents fit together.
Term Length, Termination, and Exit Mechanics
Start with the basics: the initial term, the notice period to end the agreement, and whether it auto-renews. Auto-renewal clauses often require written notice well ahead of the renewal date, and missing the window can lock you in for another term. Look for early termination fees and any separate notice requirements. These vary by provider and must be verified in your actual contract, so calendar the dates the day you sign. For a concrete example of how cancellation language reads in another industry, see our piece on trucking PEO cancellation policies, and if you are already planning a move, our guide to switching an IT managed service provider to a PEO covers the process.
Exit problems that hit MSPs hard
- Benefit transitions. Leaving mid-plan-year can reset deductibles and out-of-pocket accumulations for your employees. An MSP with a tight talent market feels that in retention.
- Payroll tax accounts and wage bases. When you change providers, how wage-base amounts are handled for the year can affect tax outcomes. Ask how the PEO reports and transfers this information, and get your payroll or tax advisor involved.
- Records. Confirm how and when employee records and I-9 files transfer back to you or to a new provider, and in what format.
Acquisitions and change of control
Many MSPs grow by buying other MSPs, which makes this section matter more than it does for most employers. Check how the contract treats added entities, new states, and acquired employees. Some agreements require new entities to be formally added, and new states may mean different pricing or coverage availability. Ask whether a merger, sale, or change of control allows the PEO to terminate, re-underwrite, or reprice. If you expect to be acquired yourself, look at assignment language and whether the PEO’s consent is needed. A contract that works for your current footprint can become awkward the quarter after a deal closes.
A Pre-Signature Review Checklist and How to Compare Offers
Work in this order:
- Get the right document. Request the full client service agreement and every schedule and exhibit, not the sales proposal. Proposals summarize; the agreement binds.
- Mark it against the four areas above. Flag fee base and renewal language, insurance and classification, duties and data handling, and term and exit provisions.
- Send identical written questions to every PEO. Ask about on-call pay in the fee base, class code assignments, certificate issuance, background screening, renewal notice, and change-of-control treatment. Written answers can be compared; verbal ones drift.
Who should read it
Employment counsel should review duties, restrictive covenants, and termination. Your insurance broker should check coverage interactions and certificate requirements against your customer MSAs. Finance should model fees under different headcount and overtime scenarios. This article is informational and doesn’t replace advice from any of them.
Comparing on the same assumptions
Offers are only comparable if they rest on identical inputs: headcount, payroll mix including overtime and on-call, states, benefit design, and renewal terms. Without that, differences in fee structure hide inside bundles and one quote can look cheaper only because it assumed something different. Build one assumptions sheet and have every provider price against it. For a wider view of contract language, our guide on how to compare PEO contract terms covers clauses common to all industries, and our look at PEO flexible contract terms explains what to negotiate before you sign.
What to Test Before Renewing or Signing
The clearest signal in an MSP’s PEO contract is how fees, insurance, and exit terms behave when headcount or client mix changes. Anyone can look good in a stable quarter. Run the contract through the bad scenario: a big client leaves, overtime spikes, you acquire a firm in a new state, or you decide to switch providers. If the answers are vague or buried in a schedule, that’s your finding.
Before you sign that PEO renewal, make sure you’re not leaving money on the table.
Many businesses unknowingly overpay because of bundled fees, hidden administrative markups, and contracts designed to limit flexibility. We give you a clear, side-by-side breakdown of pricing, services, and contract terms, so you can see exactly what you’re paying for and choose the option that truly fits your business.
