Leaving a PEO: align the contract, payroll and benefits dates

When is leaving actually the right decision?

A PEO can become a constraint: the benefit choices no longer fit, the service disappoints, or comparable separate services cost less. Those are legitimate reasons to leave. “We have reached 50 employees” is not a complete business case. Two employers with the same headcount can have very different insurance offers, HR capacity and appetite for managing suppliers.

Write down the three outcomes that must improve. For example: a specific benefit choice employees cannot get today, faster resolution of payroll exceptions, and a lower recurring cost after replacing the services you use. If the proposed system improves the dashboard but leaves those outcomes untouched, negotiate with the incumbent before launching a migration.

Estimate the hours returning to HR for payroll, benefits administration and system errors. If one generalist cannot absorb them, include external support or additional staff in the replacement budget.

Agree the three transition dates

Do not collapse the first two into “last payday.” Paychex's published PEO terms, for example, define termination by the final day of payroll responsibility, rather than simply the paycheck date. Its notice and fee provisions also refer to the customer's signature documents. Read your signed agreement; a generic checklist cannot supply your notice period.

A convenient payroll date can be an awkward benefits date. Ask the broker to show the employee experience for somebody in active treatment, somebody on leave and somebody with an unresolved enrollment correction. Do not promise that deductibles, authorisations or accumulated amounts transfer until the receiving arrangement confirms the relevant treatment. These are buying questions to resolve with the plan's specialists, not assumptions to put in an employee announcement.

CPEO status can change the route your new provider will accept

Start with the legal entity on the agreement and its EIN. The IRS's CPEO guidance distinguishes worksite and non-worksite employees and describes federal tax responsibilities; it does not turn every PEO arrangement into the same thing. The IRS also requires notification of the start and end of a CPEO contract through Form 8973.

Do not accept the blanket claim that every midyear PEO exit necessarily resets every wage base. The CPEO regulations provide predecessor/successor treatment for specified federal wage-base purposes on termination for qualifying worksite employees. That is a defined rule with conditions, not a promise about every worker, state or receiving platform. Have the payroll tax adviser document what applies to your exact transition.

The software can impose a separate constraint. Gusto's current employer onboarding instructions say it supports CPEO transitions only at the start of the year, and distinguish other PEO transitions by whose EIN and accounts were used. This is a Gusto implementation boundary, not a universal legal deadline. A salesperson's willingness to sell a subscription does not settle whether your intended cutover is supported.

Request written acceptance of the actual old entity, certification status, employee population and proposed start date from the new provider before committing to notice.

A $57,600 service saving can still be a bad exit

This is an invented USD scenario for 80 employees, with no assumed growth. The current PEO service fee is $110 per employee per month: $105,600 a year. The replacement quotes below are fictional. Unchanged wages, taxes and benefit costs cancel out of this comparison; the benefit row shows only the assumed increase over the current arrangement.

The replacement services total $48,000, giving the apparent $57,600 saving. The premium difference reverses it. That does not automatically mean stay: better coverage or a materially better service could justify the extra spend. It does mean “we cut the PEO fee in half” is an incomplete presentation to the CFO.

Now replace the premium assumption with your actual comparable proposals. At a $36,000 increase, the same model saves $21,600 a year before the $15,000 transition charge, leaving a $6,600 first-year saving. Benefits scope is doing more work in this decision than the software discount. Keep additional internal hours alongside the cash model; do not count time released as cash saved unless spending actually changes.

The exit pack must survive losing the old login

Request a sample export early enough to check it against the records you need. Confirm that you can open the files and identify missing employees or documents before access ends.

Your pack should identify the employee population, payroll and tax records, benefit elections and effective dates, leave balances and policies, signed documents, open cases, and the period each provider remains responsible for. The exact contents depend on your services and retention obligations. Assign an owner to each category; restrict access to people who need it.

Choose three fictional handover cases: an employee paid under both periods, a person on leave at the boundary, and a recently terminated employee with outstanding administration. Make the outgoing and incoming teams explain who resolves each remaining item. A clean active-employee import does not answer those questions.

The Form 8973 instructions generally place the start/end notification filing within 30 days on the CPEO. Put confirmation of that notification in the handover checklist where applicable. Do not let both parties assume the other party's payroll software has taken care of it.

Three reasons we would delay the exit

For each unresolved item, agree who will obtain the written confirmation and by what date. Check that timetable against the notice deadline so a delay does not trigger an unwanted renewal.

Questions buyers ask