Leaving a PEO: Coordinate Payroll, Benefits and Employer Accounts
Do not make a PEO termination date carry every other deadline. The contract can end on one date, medical coverage on another, and the last payroll correction much later. A replacement payroll account does not establish that all three handoffs are ready.
For a U.S. business moving out of a professional employer organization, the practical decision is which responsibilities the business will take back, which it will buy separately, and what evidence each receiving party must accept before the old arrangement ends. Payroll, HR, finance, the benefits broker and the plan administrators need a connected departure plan.
This guide concentrates on a continuing business leaving its PEO for independently arranged payroll, benefits and related support. Use the PEO Exit Dependency Map below to connect those responsibilities. Legal, tax, insurance and plan specialists establish the applicable instructions; the map makes their decisions usable in the transition. The examples are fictional, and this analysis uses public primary sources rather than hands-on product testing.
Choose a receiving payroll service that can support the departure.
A SelectSoftware Reviews payroll-advisor conversation can help you discuss the payroll implementation, historical-data and service requirements of leaving a PEO. Ask each candidate which tasks its proposal actually includes. Arrange benefit coverage, insurance and plan decisions with their responsible specialists.
Contents
Start with the services and relationships you are leaving
Pull the executed client service agreement, amendments, benefit participation documents, current invoices and the actual payroll and benefit outputs. Build the replacement scope from those records. A website's general description of a PEO does not identify the services or legal entities on your agreement.
For each function, write what the PEO supplies today and what will exist after exit. Payroll calculation, tax filings, medical coverage, retirement administration, workers' compensation, HR assistance and employee self-service can have different receiving owners. One vendor may sell several of them, but a bundled quote still needs separate acceptance for each important responsibility.
Distinguish the company you pay from the entity named on an insurance contract or a tax arrangement. Record the legal names and identifiers that the receiving specialists need. For example, IRS guidance on CPEO customers explains that a certified PEO files aggregate federal employment-tax returns under its own EIN, with customer allocations on Schedule R. That is a different record request from asking an ordinary payroll service for the employer's individual return.
Name the internal transition lead and the person who can approve a changed departure date or bridge expense. A broker can confirm an insurance requirement without having authority to extend the PEO contract. An implementation consultant can confirm an import without accepting responsibility for a historical return. Keep those decisions with the people authorized to make them.
If payroll stays with the same corporate provider after the PEO service ends, still request a written product and responsibility boundary. Continued use of a familiar login or logo does not establish that benefits, agency authorizations or old-period support continue.
Let the slowest essential replacement set the exit
Start with the desired last date of PEO service, then identify what must already be effective or accepted by that point. The dependency is often outside payroll: carrier enrollment, employer-account activation, an insurance binder, plan setup or an authorization the new filer needs.
Obtain the agreement's notice method and deadline, effective-date rules, extension options and surviving obligations. Have the appropriate reviewer resolve ambiguous terms. There is no universal PEO notice period or guaranteed right to extend. A project schedule should not silently assume either.
The notice deadline can arrive before every replacement is ready. Decide how the company will handle that uncertainty before committing to an end date that cannot be changed. Possible routes include an agreed extension, a supported staged transition, another coverage arrangement, or a later departure. Confirm availability, cost and authority for the actual route. An internal note that the team could delay is not the PEO's acceptance of a delay.
Pay-period dates and pay dates also need to remain explicit. Suppose work through June 30 will be paid July 7. Ask which party is authorized to calculate, pay and report that payroll under the exit agreement. Do not assign it solely from the month in which employees performed the work.
Reserve time for the final old-system output to reach the new provider and for corrections to be reviewed. An old payroll submitted after the approved export changes the historical baseline. The receiving team needs that additional paid run before it relies on the opening record.
An unfinished prerequisite needs an approved bridge or a revised departure decision. Completing the payroll path does not complete the coverage or account path.
Trace federal tax responsibility to the actual arrangement
Ask the tax reviewer to identify the third-party payer arrangement and the wages it covers. The IRS distinguishes payroll service providers, reporting agents, section 3504 agents and CPEOs. Do not infer the applicable liability or filing treatment from the word outsourcing.
For a proposed CPEO exit, verify the named entity's status and the relevant contract and employee facts through the IRS CPEO resources. Federal rules distinguish work site employees from other covered employees. The resulting instruction should identify who pays and reports each wage stream before and after the boundary, including late bonuses, reversals and corrections.
Resolve wage-base treatment before the first preview
For the Social Security and FUTA wage bases, qualifying CPEO termination rules treat the CPEO as predecessor and its customer as successor for a work site employee performing services for that customer. Section 31.3511-1(d) also states a non-work-site-employee exception. This is not blanket continuity for every PEO, employee or tax.
Have the tax reviewer document eligibility and the specific history the receiving payroll must use. Do not apply the same carryover instruction automatically to Additional Medicare withholding or to state unemployment taxes. The federal successor rule covers the Social Security and FUTA wage bases, not the Additional Medicare withholding threshold. State unemployment wage bases follow each state's own rules. A single year-to-date gross-pay field cannot establish every calculation's treatment.
Reconcile the approved wages and taxes by employee and tax type, and test a person who has reached a relevant wage base. A receiving system may need historical amounts for calculations without being responsible for reporting all those amounts under its own filing identity. Record that distinction in the import instruction.
Assign the end-of-contract notification and later forms
Form 8973 instructions require a CPEO to report the end of a covered service contract, generally within 30 days; a customer may also separately report its termination. Ask the responsible parties to confirm applicability, the effective date, filing responsibility and the retained evidence. Do not treat a provider cancellation email as the tax notification.
Obtain a written year-end reporting instruction. Identify who will issue or correct each applicable wage statement and how employees will retrieve it. Do not promise one W-2 or two W-2s merely because two systems will be used. Tax reporting, wage-base calculations and employee document access are related questions with different evidence.
Keep the remaining tax work visible by period and task. A final PEO invoice, an accepted historical import and an employee wage statement do not, individually, prove that a deposit, return or amendment has been completed.
Check state accounts before creating replacements
Inventory the employer's actual withholding, unemployment and other applicable payroll accounts by jurisdiction. Confirm the legal entity, account status, rate or filing instruction, authorized access and the party that will submit the next required item.
The business may have an existing account that needs usable access or a changed representative. Another account may need registration or reactivation. Ask the relevant agency or qualified tax owner to establish the required action. Opening duplicate accounts because an old number was not immediately available can create a second problem.
The federal EIN also needs deliberate handling. IRS guidance generally connects a new EIN to changes in ownership or entity structure. Do not request another one simply to give the replacement payroll a clean setup; first establish the continuing business's correct identity and any actual entity change.
State PEO arrangements illustrate why a national assumption is unsafe. Pennsylvania's unemployment guidance treats the client as the UC employer, with wages on the client's account and contributions at its rate. Tennessee's PEO guidance describes a PEO client-account process and the PEO's responsibility for inactivating that client account when the contract ends. These are examples to investigate, not interchangeable instructions for other states.
For each account, retain the agency's supported status and the receiving filer's acceptance. Submitted registration paperwork is an intermediate state. Establish what the payroll provider can actually do while an account is pending, who owns the unresolved obligation and whether the proposed first payroll remains supportable.
Remove obsolete access through the agency's supported process when the remaining work allows it. Preserve employer-controlled access and the history needed for corrections. Do not share a former administrator's personal credentials to keep a deadline moving.
Establish the benefit coverage bridge person by person
Separate the end of participation in a PEO arrangement from the effective date and acceptance of replacement benefits. ADP's public PEO explanation notes that a business leaving a PEO needs to arrange its own benefits. Determine what that means under your actual plans and service agreements, including any retained arrangements.
A quote is not a complete enrollment handoff. Obtain the approved plan documents and effective dates, then confirm which employees and dependents the receiving administrator accepted. Check the actual coverage state, not just the fact that an enrollment file was sent.
Reconcile a person-level list with the broker or benefits owner. Include people on leave, employees with future effective dates, pending dependents, former employees with continuing coverage, and participants with unresolved changes. Ask how each exception will be handled and when the employee needs an answer.
Ask separately about deductibles and out-of-pocket accumulators, networks, ongoing treatment and prior authorizations. Obtain the receiving plan's written response rather than promising equivalent coverage because a carrier name or benefit tier looks familiar. If continuity cannot be established, the benefits owner needs to explain the real change and available options before employees rely on the new arrangement.
Do not mark continuing employees terminated solely to close a PEO connection. Confirm the correct administrative transaction with the providers. An incorrect employment-status event can send instructions that do not match the intended coverage or payroll change.
Resolve continuation coverage from the actual event
Federal COBRA involves a covered plan, a qualifying event and a resulting coverage loss. The Department of Labor lists the qualifying events and eligibility conditions. A business ending a vendor agreement is not enough information to promise an employee a particular continuation right or to decide which administrator handles it.
Have the plan administrator and benefits adviser identify the treatment of current continuation participants, pending elections and people with an actual qualifying event around the exit. Record who sends required notices, collects payments, handles claims and answers the employee. Check any applicable state continuation rules separately.
Keep this decision distinct from payroll deductions. Someone can have an accepted deduction instruction while coverage enrollment remains unresolved. Conversely, an accepted enrollment may need a direct-payment arrangement until the first new payroll can collect the correct premium.
Review the agreement, the person's coverage and the paycheck instruction separately. One green status does not answer all three questions.
Keep retirement and insurance work from falling between providers
For retirement arrangements, obtain the plan administrator's departure instructions and the replacement plan's acceptance. Identify who handles employee elections, contribution sources, eligibility and service history, loans, employer contributions and any continuing administration. Do not assume that a PEO departure itself authorizes a distribution, a plan termination or a payroll-system employment termination.
Trace the final old-payroll deductions through their funding and allocation. IRS guidance on employee deferral deposits explains the need to deposit deferrals promptly and follow applicable requirements; a provider transition does not supply extra time. Assign someone to obtain the actual deposit and participant evidence after the final run, even if software implementation has already ended.
Treat an open participant loan as a named handoff. Ask the administrator for the balance, scheduled collection, receiving instructions and the route for missed or interrupted payments. Do not convert an unexplained balance into a new recurring deduction or silently stop collections while the systems change.
Have the insurance adviser establish the workers' compensation and other employer-policy transition. Record the exact covered entity, employee population, effective dates, required evidence of coverage, outstanding claims contact and any later premium reconciliation or audit. A payroll service's ability to calculate a premium-related deduction does not prove an insurance policy is in force.
Where HR support, leave administration or another service ends with the PEO, assign the active cases before access changes. A replacement employee handbook does not explain who will answer an existing leave case tomorrow. Preserve the current decision, next action and responsible professional rather than importing only an active-employee flag.
Put the remaining payroll responsibilities into the provider discussion.
Tell the SelectSoftware Reviews advisor which tax-account setup, history import, benefit-deduction connections and post-launch support the receiving payroll must handle. Obtain each provider's written scope and exclusions. The referral does not establish an insurance policy, a plan decision or a tax determination.
Transfer usable history instead of an unexplained opening balance
Create a receiving specification before requesting the final export. The new payroll may need employee identity and employment dates, work locations, earning and deduction detail, historical wages and taxes, employer contributions and supported balances. The receiving owner should identify what will drive a calculation, what is historical reference and what it will report.
Use secure approved transfer methods and restrict the files to people who need them. Keep an accountable source version and a record of the receiver's acceptance. A file with a plausible total but no employee identifiers, period boundaries or tax types can be impossible to reconcile.
Keep already paid wages out of a new payment instruction. Ask the implementation team to demonstrate how the imported history affects a preview without paying it again. Compare relevant employee-level totals with the final PEO outputs and investigate the specific differences.
Preserve deductions that depend on cumulative history or remaining balances. The administrator may need loan, benefit or garnishment instructions that the ordinary payroll register does not contain. A year-to-date amount and a remaining amount are not interchangeable. Transfer the supported purpose and treatment with the number.
Reconcile PTO and service dates to the employer's approved policy and legal instructions. Establish what is retained, paid, adjusted or tracked separately. Do not erase service history or promise a PTO payout because a new system requires a start date.
Request the records needed for the residual relationship as well as the active payroll. Keep customer-specific tax allocations or support where applicable, available wage statements, benefit enrollment evidence, plan documents, remittance records, invoices and the continuing contacts. Confirm the export and access arrangements for the particular service before the old portal becomes unavailable.
Work through the PEO Exit Dependency Map
Use this map in the employer's controlled project record. Its purpose is to expose a missing prerequisite before the company commits to a handoff it cannot support. Complete one copy for each affected employing entity, and add jurisdiction or plan-specific copies when the receiving instructions differ.
Start with the desired departure and first replacement payroll dates. For each section, enter the named owner, the actual accepted evidence and any date the next section depends on. Write “unconfirmed” when evidence is missing. A completed text field is not approval.
Contract release
Notice and effective end: Agreement provision, notice recipient and delivery evidence, proposed final service date: ____.
Remaining PEO services: Tasks that continue after that date, with an accepting contact and supported end point: ____.
Change route: Agreed extension, staged transition or other supported option if a prerequisite fails, including approval and cost: ____.
Employer authority: Person who can authorize the departure, a changed date or a bridge expense: ____.
Employer and tax accounts
Reporting identity: Continuing legal entity and EIN, outgoing and incoming payer or filer, and the applicable periods: ____.
Agency readiness: Required state or local accounts, supported status and authorized receiving access: ____.
Tax-history instruction: Reviewer-approved wage-base and reporting treatment, affected employee population and accepted import evidence: ____.
Notification and filing owners: Applicable Form 8973 action plus final deposits, returns, wage statements and corrections, each with an accepting owner: ____.
Employee and payroll history
Population: Reconciled active employees, people on leave, former employees with remaining activity and other exceptions: ____.
Final source version: Last paid old-system run, export date and the supported change route for another late payment: ____.
Balance treatment: PTO, deductions, contributions, garnishments or other balances with the approved receiving instruction: ____.
Import acceptance: Employee-level comparison and proof that paid history does not become another payment: ____.
Benefit coverage
Coverage bridge: Last old coverage date and accepted replacement start date, with any gap or overlap explicitly addressed: ____.
Enrollment exceptions: Accepted employees and dependents, unresolved records, owner and answer date: ____.
Continuing cases: Continuation participants, claims or treatment questions and their responsible administrator: ____.
Collection instruction: Premium period, employer and employee shares, first deduction and any separately approved direct payment: ____.
Plans and insurance
Retirement route: Administrator-approved plan, election, service-history and loan handoff, including unresolved items: ____.
Final remittance: Last withheld amounts, funding route and the person obtaining deposit and participant evidence: ____.
Employer coverage: Accepted workers' compensation or other required policy evidence, effective dates and covered population: ____.
Later obligations: Remaining claims, premium adjustments, plan work or employee cases with a receiving owner: ____.
First replacement payroll
Pay boundary: Last PEO-paid run and first replacement run, with pay dates, work periods and responsibility for late wages: ____.
Release evidence: Approved preview, tax treatment, deduction periods, funding and employee exception review: ____.
Bridge decision: Any still-missing prerequisite, supported alternative, authorized decision and latest action date: ____.
Residual-work review: First follow-up date and the employer owner checking unfinished PEO and receiving-provider tasks: ____.
Keep supporting documents linked to the relevant section. Do not circulate bank details, government identifiers or medical records in a general project-status message. Use the employer's approved protected record location.
Read the dependencies in both directions. An accepted plan start can determine the deduction instruction; a final PEO pay run can determine the accepted history version; a late wage can change the reporting assignment. When an upstream fact changes, ask the affected receiving owners to approve the revised instruction before using it.
Resolve a midyear exit when coverage is the blocked dependency
Consider a fictional company planning to leave its PEO on July 31. Its next payroll provider can calculate the August 7 check, and the proposed replacement medical plan is intended to start August 1. Payroll implementation appears ready.
The broker reports that one leave participant's dependent enrollment is not accepted and that the requested deductible treatment has not been confirmed. Those are different issues. A person-level enrollment problem needs an accepted coverage answer. A deductible change needs an accurate benefit explanation and a business decision about its effect. Neither is solved by passing a payroll import.
The transition lead records the affected people and decisions in the coverage section of the map. The broker owns the insurer response; HR owns employee communication; the authorized business approver owns any supported bridge cost or revised departure. The team asks the PEO whether an extension or staged route is available under the actual agreement. It does not promise an extension before receiving acceptance.
In parallel, the tax owner reviews the CPEO facts and supplies the approved employee and tax-type history instruction. The new provider accepts the final old-payroll version and tests the August 7 calculation. The coverage issue does not justify discarding usable payroll preparation, but payroll readiness does not justify calling the entire exit ready.
The company approves its final departure only when the unresolved coverage treatment has a supported outcome and the other essential dependencies have accepting owners. If the date cannot move, escalate the actual available arrangements before coverage ends. Do not substitute a reassuring employee announcement for an arrangement that has not been accepted.
For an end-of-year departure, apply the same method to the renewal boundary and the last prior-year pay dates. A January software launch does not answer who completes the December liabilities, wage statements, plan funding or later corrections.
Compare transition cash and ongoing cost separately
Build the ongoing comparison from the services the business will actually replace. Separate payroll administration, benefit and insurance costs, HR support and work the employer will retain. Use comparable populations, coverage periods and service scope.
Then build a transition-cash schedule. Include implementation charges, overlapping services, separately funded payroll and taxes, benefit premium timing, insurance-related amounts, professional review and possible post-exit charges. Some amounts are expenses; others may be refundable deposits or temporary cash requirements. Keep their treatment and expected recovery separate.
A fictional company pays $4,000 a month for its outgoing PEO administration and expects $1,500 of replacement payroll and HR administration. The apparent monthly difference is $2,500. If an approved transition requires $4,000 of additional overlap and $2,000 of setup charges, the one-time expense is $6,000. Dividing $6,000 by $2,500 gives 2.4 months of that illustrated administrative difference, before any benefit, insurance, tax or retained-work changes.
That calculation does not establish savings or the right exit date. It shows which assumptions need review. If replacement coverage costs more, the ongoing difference changes. If a deposit is refundable, it affects cash timing differently from an expense. If the business must hire an administrator, leaving that cost out makes the comparison incomplete.
Obtain written treatment for credits, deposits, refunds, audits and remaining fees. Put the expected result, evidence and owner on the residual-work review. A vendor's preliminary credit estimate is not cash already recovered.
Give employees instructions for the changes they will experience
Tell employees which organization and portal will support the first new payroll, the first pay date and any action they must take. Distinguish that from changes in medical coverage, retirement administration or insurance contacts. Give separate effective dates when the underlying arrangements differ.
Use the broker's and administrators' approved benefit information. Avoid “nothing changes” unless the responsible owners have confirmed the relevant details. If cards, networks, deductions or claims contacts change, explain those changes and provide a verified route for questions.
Account for employees who are absent, on leave or without access to a work email account. HR should confirm how those people will receive required information and how a reply reaches someone who can resolve the issue.
Describe how prior pay statements and wage statements will remain available under the actual exit arrangement. Give employees a verified contact for a missing or incorrect document. A new payroll login should not be presented as evidence that every historical document is already there.
Keep sensitive requests in the approved portal or secure process. Announce where to verify an invitation rather than asking people to send banking or identity information in response to an unfamiliar email.
Close the first independent run and the remaining PEO work
Review the first receiving-provider preview against the approved population, wage history, tax instruction and benefit collection periods. Resolve exceptions by employee and obligation. A matching company net-pay total can hide an omitted person or a duplicated deduction.
After payment, verify the actual wage funding and settlement, then follow the accepted tax, benefit and plan handoffs to their own evidence. Assign the employer owner who will review the next result. Do not end oversight at the implementation team's final meeting.
Maintain a short residual list for the PEO: final tax work, wage statements, corrections, contributions, coverage cases, refunds and authorized records access. Close an item when its agreed result is supported, not merely when the contract end date passes.
Keep only the access needed for approved remaining work, and remove obsolete access through the supported process. Retain the records the employer and its advisers need under their applicable requirements. The departure is operationally closed when the replacement responsibilities work and the remaining obligations have documented, accepted homes.
Review the payroll service gaps before the departure is committed.
Discuss payroll providers against the work the map leaves unresolved, including supported history imports, account setup, deduction connections and follow-up service. Use the SelectSoftware Reviews advisor route for payroll selection, and keep coverage, plan and tax decisions with the professionals responsible for them.
Continue with practical payroll transition resources:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
