Professional Employer Organization (PEO)

How does a PEO arrangement work?

A PEO arrangement connects a client business, a provider, and the employees covered by their service agreement. The agreement identifies those employees, the administration the provider will perform, and the work the client will retain. Those terms show what the parties intend by “co-employment” in daily operations.

Map the three parties and the service agreement

Consider a Texas company that enters a PEO agreement for its existing warehouse team. The company still runs the warehouse and directs the employees’ work. The PEO takes on the employment administration specified in the agreement. The employees are the third party to the arrangement: identifying exactly which workers are covered matters because the agreed services and duties attach to that population, rather than automatically to everyone the company employs.

Texas Labor Code Chapter 91 gives a concrete example of how that division can work. For covered employees, the written agreement must assign the PEO responsibility for wages it contracts to pay and for specified payroll-tax handling. It also sets out shared rights concerning hiring, discipline, employment policies, and workers’ compensation administration. The client retains responsibility for directing its business and for the goods and services it provides. If the client promises wages that the PEO has not contracted to pay, the client remains responsible for those wages. A business reading a proposed agreement should therefore trace each duty to the named party and the covered workers, instead of treating “payroll” or “shared employer” as a complete allocation.

Texas calls this an ongoing coemployment relationship under its own PEO law. That describes a particular state-law arrangement; it does not resolve every legal question raised by the same workforce. For example, the IRS explains that “co-employer” is not itself a federal employment-tax status. The contract and applicable legal test must be checked separately for each duty.

Caption: Texas Labor Code Chapter 91 illustration for covered employees. The agreement and statute govern these Texas roles; this map does not decide federal employment-tax liability or FMLA joint employment. Texas Labor Code Chapter 91

Follow payroll, benefits, HR, and employee changes

The service has handoffs from employee setup through recurring administration, changes, and departure. Each needs an owner and a record of what was sent or completed.

For example, when the warehouse company hires another worker, it identifies whether the person is covered by the PEO agreement and supplies the details needed for the contracted services. If employee setup and benefits enrollment are included, the provider enters the worker into its systems and handles the agreed enrollment steps. The company should confirm the first payroll date, benefit eligibility, and who keeps the source records; an HR portal alone does not answer who must correct an incomplete or late submission.

At each pay cycle, “handles payroll” needs particular care. In a US arrangement, the work may include calculating wages and sending pay each cycle, making employment-tax deposits on the applicable schedule, filing returns, issuing Forms W-2, and retaining accessible records. These acts can be assigned in different ways. IRS Publication 15 distinguishes third-party payer arrangements by the acts they perform and the filing identity they use. The service schedule should identify who supplies and approves pay data, who funds and sends wages, who files and deposits taxes, which EIN appears on returns, and what evidence the client can obtain. Performing a step does not, by itself, establish who bears every statutory tax duty.

Other work depends on what the provider actually offers and what the client buys. The schedule might include benefit enrollment and administration, workers’ compensation claim handling, HR or safety support, or optional recruiting and reporting tools. For each item, the useful question is what the provider will do, what information the client must supply, and which plan, policy, or system governs the result. If a worker changes location, pay, or benefit choice, the parties need a route for updating the relevant records before the next affected payroll or enrollment event.

The same division matters at termination or a provider switch. The parties should identify who calculates and sends any final wages, ends or transfers benefit administration, corrects outstanding payroll records, and gives the client copies it will need afterward. Those steps and deadlines depend on the contract and applicable law; an advertised “offboarding” service is not a substitute for assigning them.

Separate provider administration from the client's management

Assign decision rights alongside administrative tasks. For the warehouse team in the example, client managers decide which work needs doing, set shifts and proposed pay, supervise performance, and supply approved changes. The PEO may maintain employee records, process payroll, or advise on HR matters within its contracted scope. If it also offers recruiting or management advice, the agreement should say whether it recommends an action, carries it out, or has authority to approve it.

Suppose a manager approves a pay increase after payroll data has been sent. The contract should identify who can authorize the change, the cutoff for sending it, who updates the payroll record, and how an already processed payment is corrected. A move to another work location likewise needs a named route for updating the employee record and checking which payroll, benefit, or workplace requirements now apply. The provider can administer the information it receives under the agreement, but the client must make its own business decisions visible in time for that work.

Decision rights also affect legal analysis, although this operational map does not decide legal status on its own. For US federal employment-tax purposes, the IRS examines actual day-to-day direction, hiring and firing authority, wage setting, and control of wage payment. Texas, for its separate state-law PEO arrangement, gives the client sole responsibility for direction needed to conduct its business while requiring the agreement to allocate shared hiring and discipline rights. Readers should compare those distinct questions with the parties’ actual conduct, not assume that either “the PEO handles HR” or “the client manages staff” settles every duty.

What legal responsibilities does a PEO arrangement change?

The service agreement assigns work between the client and provider. Legal duties require separate analysis: a contract's “co-employer” label does not decide federal employment-tax responsibility, FMLA joint employment, or state PEO requirements for the same employees.

Commercial co-employment is not one legal test

“Co-employment” can describe the parties’ agreed sharing of employment functions without settling their status under every law. In the Texas warehouse example, the PEO agreement can allocate specified wage and payroll-tax administration while the client directs the warehouse work. Texas Labor Code Chapter 91 sets duties for that state-law relationship and its covered employees. The agreement matters, but its wording cannot replace a different statute's test.

For US federal employment taxes, the IRS says the Internal Revenue Code does not define “co-employer” or use that label to decide liability. The tax review instead asks who is the common-law employer, who controls wage payment, and whether the provider acts, for example, as a reporting agent or a designated payer under the applicable third-party payer rules. A provider that prepares payroll and a client whose managers direct the work may therefore have different operational roles without the contract alone resolving which party files, pays, or remains liable under federal tax law.

The FMLA joint-employment rule asks a different question about the actual relationship. A state-law co-employment agreement and a payroll assignment do not answer it. Before attributing a duty, a business should identify the law at issue, the employees and work it covers, the relevant facts, and the document or action that assigns each party's operational role.

US federal employment taxes depend on the payer arrangement

When a US company outsources payroll, the party processing it is not necessarily the only party responsible for federal employment taxes. The answer depends on the client's status as an employer, the provider's authorized payer role, the filing EIN, and—in a certified PEO arrangement—the contract, workers, and wages covered. The client should establish those facts before treating a payroll invoice or service description as proof that its tax duties moved.

Ordinary PEO and payroll-service arrangements

A payroll service provider or reporting agent can calculate pay, make deposits, and prepare or file returns under the client's EIN. Under those arrangements, the employer remains responsible for the federal employment taxes even though another company performs the work. IRS Publication 15 gives different consequences for other roles: an agent authorized by Form 2678 can share liability with the employer for the duties it is authorized to perform; a designated payer under section 3504 uses its own EIN and shares liability with the employer for its designated duties. A non-certified PEO is not automatically any one of these categories. The contract, authorizations, wage-payment facts, and returns must show which arrangement applies; the IRS notes that a PEO may file using its own EIN while the client remains the common-law employer.

If the client remains the common-law employer, assigning tax administration to a PEO does not by itself release it from federal tax liability. The IRS directs examiners to the actual relationship and the relevant tax-law payer rules, including who directs daily work, can hire or fire, sets pay, and controls wage payment. For the warehouse company, a useful check is to compare its managers' actual control with the payroll authorization and filed returns: whose EIN is on them, who deposits the tax, and what statutory role the provider claims. Those answers can differ from the agreement's broad “co-employer” wording.

Certified PEO status and covered wages

An IRS-certified PEO (CPEO) is a specific legal entity that has obtained voluntary certification. The customer should match the exact contracting name and EIN required by IRS customer guidance against the current public listings, rather than rely on a parent company's badge. Certification changes certain federal employment-tax results only when the qualifying contract, worker category, and wages paid by that CPEO meet the rule; it does not settle every employer duty.

Suppose that under a qualifying CPEO contract, Worker A is a worksite employee and Worker B is a covered employee who does not meet the worksite definition. For specified federal employment taxes on remuneration the CPEO pays to A, the CPEO is generally solely liable. On remuneration it pays to B, the customer may also be liable. The IRS states this worksite versus non-worksite distinction; it is why a buyer must check each worker and pay period, not just the provider's certification. The exact wages the CPEO pays and the tax provisions involved matter as much as the label on the contract.

Caption: US federal employment taxes only. These results concern CPEO-paid remuneration under a qualifying contract and specified tax provisions. The customer may also be liable for non-worksite employees; other employment duties require separate checks. IRS: CPEO customers, what you need to know · IRS: CPEO public listings · US Treasury final regulation 31.3511-1

FMLA joint employment requires its own factual test

Using a PEO does not automatically make it a joint employer under the US Family and Medical Leave Act (FMLA). Under 29 CFR 825.106, a PEO that merely performs administrative functions—such as payroll, benefits, regulatory paperwork, or policy updates—does not enter a joint-employment relationship with the client's employees on that basis. If the PEO can hire, fire, assign, direct, or control employees, or benefits from their work, those facts may support joint employment. The decision rests on the economic realities and the whole relationship, not one contract term or a single factor.

If the facts establish FMLA joint employment, the parties still have to identify the primary employer. For a PEO arrangement, the FMLA rule says the client is most commonly primary. The primary employer gives required notices, provides FMLA leave, maintains health benefits during leave, and has the main job-restoration duty. A secondary employer is not duty-free: it must comply with the rule's prohibitions on interference and retaliation, and restoration obligations can arise in the circumstances the rule describes. Employer coverage and the employee's eligibility must also be checked before applying leave entitlements.

Suppose client managers retain hiring and day-to-day control but ask the PEO to receive employees' leave requests and manage the paperwork. Routing those requests is an administrative task; it does not by itself make the PEO an FMLA joint employer or transfer the primary employer's duties. The client and provider should document where a request goes, how the client is alerted, which employer bears the notice and leave duties if FMLA applies, and who performs each administrative step through the employee's return. If the PEO has broader rights or gains from the employees' work, they need to assess those facts before assigning the primary and secondary roles.

Caption: US FMLA only. Assess the whole relationship if the PEO has a broader role. If joint employment exists, the client is most commonly primary; both employers can have duties. Check employer coverage and employee eligibility separately. 29 CFR 825.106, joint employment · US Department of Labor Field Operations Handbook, Chapter 39

State, local, and other employment duties need separate checks

The federal tax and FMLA answers cover only those federal rules. They do not establish whether a PEO must hold a state license, how unemployment or workers’ compensation is handled, which state or local payroll requirements apply, or what a benefit plan and workplace policy require. A company needs a separate check for each place its employees work and each service or plan in the agreement.

Texas shows why. Texas Labor Code Chapter 91 requires a PEO license, addresses unemployment and workers’ compensation within its own scheme, and requires disclosures about a PEO-provided benefit plan, including its type, insurer, benefits and limits, and funding status. Those requirements are additional to the wage and control allocation in the Texas agreement; they cannot be inferred from a federal tax filing or an FMLA joint-employment conclusion. A client considering a Texas arrangement can check the provider through the state regulator's license search and request the actual insurance, benefit-plan, and policy documents before assigning tasks.

If that client adds workers in another state, it should repeat the review there rather than carry the Texas answer across the border. List each work location, the relevant registration and payroll accounts, unemployment and workers’ compensation arrangements, employee notices and workplace policies, and the plans offered to those workers. Then identify which party performs each applicable task, who holds the underlying policy or account, and what record will show completion. The answers come from the governing jurisdiction and documents, not from a nationwide “PEO” label.

What does PEO mean outside the US?

Outside the US, offers called “PEO” can use different employing relationships. Identify which entity signs the employment contract, pays and reports wages, directs the work, and holds any required local registrations before applying a US co-employment explanation.

UK and German market labels can describe different employer structures

A company that already employs local workers may buy payroll and HR administration for that team. Another proposal may have the provider employ people and supply their work to the client. Even if both proposals say “PEO,” the buyer needs to establish whose employment contract applies, who gives instructions, and which entity carries each local payroll or registration duty.

Provider descriptions illustrate both structures. Sage Advice UK's explainer describes a PEO as the employees’ “employer of record” within what it calls co-employment. International Management Answers advertises a “PEO UK” service that employs UK-based staff for an international client's small team and presents a possible later move to a UK subsidiary. Germany-based International Payroll Services describes a different model on its English-language page: the client remains the legal employer, signs the employment contract, and outsources agreed payroll and HR tasks. These are descriptions on those sites, not evidence of any particular contract's legal effect or a rule for either country.

In the UK, if the client is the employer and pays a payroll provider to run PAYE, GOV.UK says the client remains legally responsible for the PAYE tasks. It must also collect and keep the employee details the provider needs. This rule concerns that employer-and-payroll-provider arrangement; it does not identify the employer in every UK offer marketed as a PEO. A buyer should check the signed employment contract and payroll setup before applying the PAYE conclusion.

Germany calls for a different boundary check. Where the client employs its own workers and purchases administration, that alone does not describe a provider supplying its employees to the client. If the provider instead employs workers who are integrated into the client's organization and work under its instructions, the arrangement may fall within Arbeitnehmerüberlassung (employee leasing). The German Federal Employment Agency says permission is generally required for that route, subject to statutory exceptions and details. Before treating a German proposal as routine payroll outsourcing, a buyer should identify the actual employer, who directs the work, and whether the provider is supplying workers under that separate regime.

Choose a local employment route before relying on the label

First decide who can employ the worker in the country concerned. If the client already has a suitable local employing entity, it can compare proposals for administration of its own employees against the work its team can do internally. If it does not, administrative support alone does not supply an employer. A proposal under which another entity signs the employment contract, pays the worker, and holds the employer registrations needs to be assessed on those facts, whether it is marketed as an employer of record (EOR), a “global PEO,” or something else.

The next question is what the worker will actually do for the client. In Germany, a provider-employed worker integrated into a client's operation and subject to its instructions may raise the employee-leasing question described above. That route has different checks from outsourcing payroll for employees the client already employs. Before choosing, ask the provider to identify the employing entity and registration, show the proposed employment and service contracts, explain who gives daily instructions, and state who runs payroll and reports wages. Those documents and the local rules determine which route the proposal describes.

If a provider offers to employ someone now and move that person to the client's future subsidiary, treat the later move as a separate transition to plan. Ask which employment contract would end or change, what employee agreement or rights need review, how accrued pay and benefits would be handled, which entity would run the first payroll after the move, and who would retain the prior records. The proposal alone cannot establish that the transfer will be automatic or that service and legal obligations will continue without change.

When is a PEO a good fit, and what does it cost?

Fit depends on the provider's contracted work, the client's existing capacity, usable benefit plans, and the full proposal cost. An employee-count cutoff or advertised saving cannot answer those questions for a particular company.

Match services and benefits to the workforce

A PEO proposal is worth examining when recurring payroll or HR administration strains the client's team, when it needs specialist support, or when several work locations make coordination harder. Start with a task inventory: who runs payroll now, handles employee changes and questions, maintains records, manages insurance or benefits, and resolves exceptions? Compare that workload with the provider's service schedule, systems, response path, and the client's retained tasks. A long list of advertised services has little value if the needed work is outside the agreement or duplicates a capable internal team.

Benefits require a separate comparison for the people who would enroll. Request each actual plan's eligibility rules and Summary of Benefits and Coverage, then compare covered services, the provider network, premiums, employee contributions, deductibles, copayments, coinsurance, and out-of-pocket limits with current options. The official Summary of Benefits and Coverage guidance explains how the standardized document helps compare job-based plans; the plan documents and quote supply the terms for this workforce. Access to a pooled plan does not establish a lower total cost or better coverage.

For example, a proposal could lower the employer's premium while moving several employees' regular doctors outside the plan's network. Network rules can change what those employees pay, so the lower premium would not settle the choice. Ask which employees and dependents are eligible at each location, whether their providers participate, and what both the business and employees would pay under plausible use of care. Then weigh that answer alongside the administrative work the provider would take over; neither benefit marketing nor a service bundle proves the proposal fits on its own.

Recognize poor-fit conditions and retained control

A PEO proposal may be a poor match when its package duplicates work the company already does well, omits a service the workforce needs, or limits a choice the company intends to keep. A specialized workforce may need pay rules, schedules, HR support, or plan eligibility that the offered package does not cover. For a short project, setup and exit work may outweigh the value of ongoing administration. Check the actual schedule and workforce; company size alone is no test.

Control deserves its own check. Identify who can approve pay and role changes, choose policies and benefit plans, make personnel decisions, and access records after the relationship ends. The answer may differ by contract and jurisdiction. If the proposed benefit plan excludes an important employee group or network, or the provider bundles services the company does not want, ask whether the offer can be adjusted and what responsibilities the client would retain. A service that looks broad in a sales description can still leave the buyer's main problem unsolved.

For example, a company with a capable HR team and established benefits might need only reliable payroll processing. It should compare that narrower service with the PEO proposal instead of paying for a bundle whose extra functions it will not use. A company seeking one hire in a country where it has no suitable employing entity has a different problem: administration of its own employees will not provide that entity. It should examine who would sign the employment contract under a proposed EOR or other local route. In both cases, the needed relationship and work matter more than a headcount threshold.

Compare the complete quote and implementation costs

Put proposals on the same workforce, payroll, service scope, and time period before comparing their headline fees. One quote might state an administration charge per employee, while another might use a percentage of payroll; calculate the annual amount under each actual formula, including minimum charges and what happens when headcount or wages change. Neither format alone establishes the cheaper offer.

Ask for an itemized schedule that separates the provider's fee from wages and employment taxes, benefit-plan premiums and contributions, workers’ compensation or other insurance, and charges for optional services. Check which amounts the provider bills at cost, whether any margin or minimum applies, and which tasks remain with the client. Include setup and data migration, payroll corrections or special reports if charged, exit fees, and the staff time the client will still spend supplying data, approving changes, and checking records. The signed proposal and service agreement must answer those questions; “all-in” is not a cost breakdown.

Consider two hypothetical first-year quotes for 20 employees. Proposal A charges $80 per employee per month and includes benefits administration: $19,200 for 12 months. Proposal B advertises $60 per employee per month, then adds $25 per employee per month for benefits administration and a $2,000 setup fee: $22,400 for the same period. B's lower headline rate produces $3,200 more in these administration and setup charges. The business would still need to compare the actual benefit plans, insurance, taxes, any other charges, and retained work before deciding which complete proposal costs less or serves the team better.

How is a PEO different from nearby models?

First identify the work the business needs: payroll processing, HR support, software, or another entity to employ or supply a worker. Then compare the agreement, employing entity, filing arrangement, and services behind each provider's label.

Payroll service, ASO, HRO, and HRIS

A payroll service can have a narrower job than a PEO package. In a US payroll-service-provider or reporting-agent arrangement, the provider performs specified payroll and tax tasks under the client's EIN, while the employer retains federal employment-tax liability. The IRS distinguishes those arrangements from other third-party payer roles. A PEO proposal may cover payroll plus benefits or HR administration and may use a different payer arrangement. Ask which acts the provider performs, whose EIN appears on the return, and what responsibility the client retains; “runs payroll” does not answer those questions.

An administrative services organization (ASO) offer may provide ongoing HR or payroll administration without the co-employment structure proposed in a particular PEO agreement. Human resources outsourcing (HRO) may address only selected HR functions. These names describe possible service scope, not a fixed legal status: the buyer still needs to see who employs and directs workers, which functions are in the service schedule, and how any payroll filing is authorized. The ASO service-scope checklist develops that task-by-task review. An ASO label alone cannot establish federal tax treatment, just as a PEO label cannot.

An HR information system (HRIS) is software for employee information and workflows; purchasing it does not by itself assign payroll filing, benefit administration, or employer duties to a service provider. Suppose a company has a capable HR team but still calculates pay from spreadsheets. It could compare a defined payroll-processing service and suitable HR software with the broader PEO proposal, checking which option removes the actual manual work and which tasks staff will still own. If the gap is hands-on HR administration instead, the buyer should compare the contracted people and services as well as the software. The PEO-versus-payroll guide takes that comparison through cost and transition.

EOR and so-called global PEO

The first question is whether the client will employ the worker through its own suitable entity. If so, a PEO or another administration provider may support that existing employment relationship. If another entity will sign the employment contract and employ the worker for the engagement, the buyer is assessing an employer-of-record (EOR) route. Both offers may include payroll and HR support, so a similar service list does not settle who the employer is or what the client still must do.

“Global PEO” is a commercial label that can be applied to different structures, including administration for a client employer and an offer in which the provider employs the worker. For example, a company with employees already on its local entity's contracts needs to compare the administration it will retain or outsource; a company without a suitable local employing entity needs to establish who could legally employ the person before comparing service bundles. In either case, request the proposed employment and service agreements. Identify the employing entity, who pays and reports wages, who directs the work, and any local registration or permission the arrangement requires. In Germany, for instance, provider-employed workers integrated into the client's operation and subject to its instructions may raise employee-leasing requirements, a question that outsourced administration of the client's own workers does not answer.

If the proposal includes moving workers from the provider to a future client subsidiary, ask how the employment contracts, worker rights and consent, payroll records, benefits, and handover would be handled. Do not assume the move is automatic. The PEO versus EOR comparison develops the entity, control, and transition questions once the buyer knows which employment route each proposal actually offers.

Staffing agency, contractor services, and PPO

If the business needs people to fill a vacancy or a short assignment, ask a staffing agency whether it will find candidates for the client to hire or employ and supply workers itself. That is a different starting need from arranging payroll and HR administration for a workforce the client already has. A company covering a seasonal absence, for example, might seek an agency-supplied worker; a company whose existing team needs benefit enrollment and payroll support would compare the PEO's service schedule instead. Under Texas Labor Code Chapter 91, temporary help includes an organization hiring its own employees and assigning them to supplement a customer's workforce for a special situation, and the chapter excludes temporary help from its definition of professional employer services. That is a Texas distinction, not a rule that every staffing engagement is temporary. The Staffing Agency glossary takes the sourcing and supplied-worker paths further.

Contractor services address a different relationship: purchasing and administering work from someone who is genuinely independent under the applicable rules. A platform or contract labeled “contractor” does not make an employee into one. For US federal-tax purposes, the IRS examines the actual degree of control and independence, including behavioral control, financial control, and the parties' relationship. A buyer should establish the worker's status under the rules that apply before selecting employee administration or a contractor workflow.

PPO means a preferred provider organization, a health-plan type with a participating-provider network; using out-of-network care can cost more. It is not an HR outsourcing model. A PEO's offered benefit plan might be a PPO, but the buyer must check the actual plan documents and network rather than infer coverage from the PEO service label. To route the decision, ask whether the missing piece is a worker, an employing entity, payroll and HR administration, or a health-plan choice. Each leads to a different set of providers and documents to compare.

What should a business verify before signing and during transition?

Before signing, identify the exact services and legal entities, name an owner on each side for every recurring task, and decide what records will prove the work was done. Keep those answers and records for the first payroll, later corrections, and an eventual provider change.

Test provider scope, support, and references

Ask for a service schedule that names each included task, the countries or states and worker groups it covers, eligibility limits, the input the client must provide, and the output the provider will deliver. Check proposed payroll, benefits, HR, notices, and reporting work task by task rather than treating “full-service” as a contractual promise. For each task, record who makes the decision, who performs it, when it is due, and how the client can see completion or an error. This also exposes services quoted separately or available only in certain locations.

For example, “compliance support” could mean that the provider advises on a filing while the client must approve, submit, and retain proof of it. Ask the provider to point to the relevant agreement clause and demonstrate the actual workflow for that filing and for an employee notice. The question is consequential: in a US payroll-service-provider arrangement, the IRS says the employer retains federal employment-tax liability even though the provider performs specified payroll tasks. Another payer arrangement can differ, so the buyer needs its own service schedule and filing setup, not a general assurance that the PEO “handles compliance.”

Test the support behind the schedule. Ask who will handle routine employee questions, payroll corrections, benefit enrollment problems, and an urgent issue before a filing or pay deadline; request named contacts, coverage hours, escalation steps, and expected response times in writing. Ask what reports and underlying records the client can retrieve, including after termination, and how access is controlled. Comparable client references can reveal whether support works at the required workforce size, locations, and pay cycles; ask those clients about actual handoffs and corrections. A reference or security claim in sales material helps frame questions but does not prove a promised control exists or transfer a statutory duty.

Verify the legal entity, CPEO status, registrations, and plan terms

Match each claimed credential to the legal entity that will sign and perform the agreement. If the US federal tax proposal relies on Certified Professional Employer Organization (CPEO) status, the IRS says the CPEO contract must give the exact name and EIN of the entity fulfilling the covered tax obligations. Check that name against the IRS's current certified, suspended, and revoked listings, and retain the check with the contract. A brand logo or certification held by an affiliate is not evidence that this contracting entity is certified. Identify which workers meet the CPEO worksite definition and which wages it will actually pay. For specified federal employment taxes on CPEO-paid remuneration, the IRS generally assigns sole liability to the CPEO for qualifying worksite employees, while the customer may also be liable for non-worksite employees. Certification alone therefore cannot settle the result for every worker, and it does not certify service quality or every employer duty.

State registration or licensing is a separate question for each work location. Texas, for example, requires a license for professional employer services under its Chapter 91 arrangement, and its regulator provides a PEO license search. Check the entity and current status through the relevant state regulator where a rule applies; an IRS CPEO listing cannot answer that state question. Private accreditation is different again: ESAC describes participation in its PEO accreditation program as voluntary. If a provider cites ESAC, ask which entity holds that accreditation and what the program covers. It is not IRS certification, a state license, or a government guarantee.

Read the offered plans and insurance evidence with the same care. Obtain the current health-plan Summary of Benefits and Coverage for each option, then compare eligibility, covered care, employee costs, and network against the workforce's locations. Request the retirement-plan documents and the workers' compensation policy or coverage certificate, checking plan or policy sponsor, covered workers, limits, dates, and any client employees outside the PEO population. In the Texas example, Chapter 91 requires a PEO providing benefit coverage to disclose its type, insurer, benefit amounts, policy limits, and funding status. A promise of pooled benefits cannot establish any of those terms or show that a plan fits a particular worker.

Plan the first payroll and the exit evidence trail

Set the cutover dates before moving worker data. Record the last pay period under the old process and the first pay date under the new one; give the provider an agreed file of workers, work locations, employment and pay details, year-to-date wages, deductions, benefit elections, and any balances needed for the services it will perform. Decide who checks that import, approves hours and changes, funds payroll, resolves rejected records, and answers employees. Match benefit enrollment and coverage effective dates to the payroll cutover so that a data transfer is not mistaken for confirmed coverage.

Identify the legal entity and EIN that will file each US federal return, then agree on evidence the client can actually obtain. When a payroll service provider or reporting agent deposits under the client's EIN, IRS Publication 15 recommends using EFTPS to monitor those deposits and keeping the employer's address on record so IRS correspondence reaches it. A CPEO instead files aggregate covered returns and deposits under its own EIN; the customer cannot view those deposits through its own EFTPS account. In that case, request the customer allocation, filing confirmation, wage records, and a process for investigating discrepancies. In either arrangement, assign an owner to reconcile pay registers, returns or allocations, deposit evidence, and agency notices, and to retain the correction record. A provider invoice alone cannot show that the filing or payment matched the workers and period.

Write the exit plan into the agreement while both parties still have access to the records. Specify who gives worker and agency notices, completes the final pay period, corrects earlier returns or wage statements, returns payroll and benefit data, and handles questions after access ends. Preserve the contract dates, filing identities, employee wage history, benefit records, notices, and proof for the last period as carefully as for the first. For a CPEO, Form 8973 notifies the IRS when the contract begins or ends. If a change occurs midyear, ask the payroll and tax teams to review the workers' prior wages before calculating the first new payroll: the federal CPEO regulation provides limited predecessor–successor annual-wage-base treatment for specified taxes when a contract starts or ends for a qualifying worksite employee; non-worksite employees can fall outside it. Neither a universal reset nor automatic carryover follows from the word “PEO.” The PEO payroll-tax filing guide develops the arrangement-specific proof trail.