Employer of Record vs PEO: Choose the Hiring Relationship
Updated: Nov 4
An employer of record and a PEO can both appear on a shortlist for payroll and HR help. The deciding question is what employment relationship your company needs. Are you arranging for a provider's local entity to employ someone, or buying support for employees your own business already employs?
In common international hiring comparisons, an employer of record, or EOR, employs the worker through the provider's employing entity. A professional employer organization, or PEO, usually supports an existing employer through a co-employment arrangement. Those descriptions are a starting point. The country, named entities and actual agreements must establish what a particular offer does.
Use this guide before choosing the payroll platform or accepting a start date. It provides a hiring relationship decision tree, a reusable decision record and examples of offers that should reach different shortlists. It does not rank providers or replace advice on a specific country's employment, tax or immigration requirements.
Once you know which employment relationship you need, you may still need help comparing payroll and HR administration options. SelectSoftware Reviews offers advisor-led payroll software matching. Use that conversation for the software decision; obtain country-specific employment advice separately.
Contents
What relationship are you trying to create?
Begin with the worker, not the vendor. Write down the country where the person will actually work, the proposed role, the intended start date and whether an employment relationship already exists. A new hire abroad and an existing domestic team seeking better benefit administration present different problems even when the same platform sells both services.
For a business with a suitable employing entity, the choice may be direct employment with payroll support, a PEO arrangement or another HR administration service. The company needs to decide how much administration to buy, what coverage fits and what work it will retain. Changing software alone does not answer those questions.
For a business without a suitable employing entity in the worker's country, the first question is how the proposed employment can be established lawfully. A country-specific EOR offer may be an option to evaluate alongside establishing the company's own employing arrangement. A payroll-only service is not a substitute for resolving that employment decision.
Remote's entity guide illustrates the commercial distinction within one provider's products: its EOR employees are hired by Remote, while its PEO and global payroll employees are hired by the customer. In all three cases, the customer can be the managing and billing entity. The company paying the invoice and supervising the work is therefore not enough to identify the employing entity.
Treat each worker population separately. A company can have its own U.S. employees, employees of a foreign subsidiary, EOR employees in another country and independent contractors using the same vendor portal. The login is shared; the relationships are different.
Why the label cannot settle the legal answer
“Employer of record” is not a universally exclusive label for a single international hiring model. Indiana's unemployment guidance, for example, uses the phrase for a PEO operating through a co-employment agreement while the customer retains hiring, firing and management responsibilities. That is a specific state unemployment context, not a definition of every EOR offer worldwide.
PEO also needs clarification. Ask the seller what co-employment means under the proposed agreement and applicable law, which employees it covers and which entity has each obligation. Do not infer that the PEO takes every employer duty or that the customer ceases to be an employer.
The IRS explains that a common-law employer generally remains responsible when payroll duties are outsourced, subject to particular statutory arrangements that may share or shift employment tax obligations. It also notes that the term co-employer is not defined in the Internal Revenue Code. A marketing description cannot establish the federal tax treatment, much less the answer under every other law.
Have the provider describe the offer without acronyms: “This named entity signs the employment agreement with this person in this country; these other entities provide these services.” If the seller cannot complete that sentence, keep the employment model unresolved. An attractive product demonstration cannot supply the missing parties.
Trace the parties behind the platform
Request the legal name, registration details and country of the proposed employing entity. Identify the entity signing your commercial agreement, the entity issuing invoices, the payroll processor and any local partner involved. Ask whether the employing entity is part of the provider's group or an independent partner, and how a change of partner would affect the worker.
Oyster's current data processing addendum expressly distinguishes its subsidiary from a third-party EOR through which a worker may be employed. It also distinguishes payroll employees of the customer from other service populations. This is a practical reason to ask about the actual delivery structure rather than assume that every country uses the seller's own entity.
An owned entity and a partner arrangement both need examination. Ownership alone does not prove that the proposed role is permitted, the service is well supported or the commercial terms are acceptable. With a partner, establish who can give binding answers, who handles employment events and how your company obtains records if the central platform relationship ends.
Ask to see a country-specific employment agreement sample and the relevant service terms before signing. Match the employer's name in the sample to the proposed country arrangement. Resolve differences between a sales proposal, an order form and incorporated local terms through the provider's contracting process.
Keep three identities visible: who employs the worker, who directs the work and who receives the invoice. Record the payroll processor separately when it is another entity.
A readable entity map can be a short list rather than a corporate organization chart:
Employment: worker and named employing entity.
Work direction: worker's manager and the customer entity receiving the services.
Commercial service: customer contracting entity, provider contracting entity and any local delivery partner.
Money and records: invoice recipient, payroll processor, funding route and record-access owner.
These relationships may share an entity, but record that explicitly. Do not use an invoice header as evidence that the same company is the employer.
Run the Hiring Relationship Decision Tree
Use the following questions for one country and one worker population at a time. The tree produces a route for investigation, not a legal approval or a provider recommendation.
1. Is this an employee hiring decision? If the intended relationship is independent contracting, assess classification and the contracting arrangement separately. A contractor payment account or contractor-of-record product should not be treated as evidence that the person has become an employee. Return to this tree if the approved relationship is employment.
2. Which entity can employ this person in the actual work country? If your company has an entity, confirm that it is ready and suitable for this role, including required registrations and local review. An incorporated company that has not completed the necessary employment setup is not a ready payroll population.
3. Will your entity remain the employer under the offer? If yes, examine payroll-only support, PEO co-employment or other administration services according to the applicable country and contract. Compare the work and coverage those services add. If the provider's entity will employ the person instead, examine the proposed EOR structure and its local eligibility.
4. Is the specific role and arrangement supportable? Obtain country-specific confirmation for the job, actual worksite, intended duration, worker eligibility and required permissions. A seller's country list does not establish that this particular engagement is accepted.
5. Can the parties operate the arrangement? Confirm who supplies employment inputs, makes decisions, communicates with the worker, funds obligations and manages changes or exit. An eligible model can still be unsuitable when its approval process conflicts with the business's operating needs.
Route the population before comparing vendors. Both the customer-employer route and provider-employer route require country-specific confirmation before a start date is approved.
If a branch remains unanswered, record the missing evidence and the person obtaining it. Do not convert “provider reviewing” into an assumed approval because the recruiting team has already discussed a start date.
Ask for country evidence that matches the job
Send a concise role brief rather than ask whether the vendor “covers” a country. Include where the person works, whether work occurs at your premises or a customer's site, the activity performed, planned travel, proposed hours and whether the person supervises staff or negotiates customer contracts. Separate facts from plans that may change.
Ask the provider and your qualified local advisers which legal arrangement applies and whether licensing, registration, assignment restrictions, collective terms or other conditions need examination. Request the basis for the answer and the limits of the provider's acceptance. This is a due-diligence question, not a claim that every country imposes the same rules.
A useful response says which entity can support which worker and work, under which documents and conditions. A general statement that the provider handles compliance leaves too much open. Ask who will revisit the decision when the role, worksite or country changes.
Country rules can also preserve responsibilities for the business using the worker. GOV.UK's guidance on using a recruitment agency, for example, identifies hirer responsibilities for agency-worker health and safety, access to shared facilities and information about vacancies. Whether a particular EOR arrangement falls within that framework requires its own assessment; the EOR label does not establish the classification.
Keep immigration permission and corporate tax exposure as separate questions for qualified advisers. Ask whether the proposed worker needs sponsorship or other authorization, what the provider actually offers and whether the intended activities create issues for your business. Do not treat an EOR agreement as a guarantee that permanent-establishment, immigration or other local obligations disappear.
Write any restrictions into the operating instructions. If approval covers remote work from one country, a manager should not casually authorize a month at a customer site elsewhere. Give the worker and manager a clear route for obtaining a new decision before changing the facts.
Preserve the employer work that remains with you
Outsourcing an employment function does not remove your team's role in supplying accurate information and running the work. Decide who records hours and leave, approves compensation changes, reports incidents, evaluates performance and obtains local advice. The provider needs usable inputs; your managers need to know which actions require coordination.
Remote's Employment Services terms provide a concrete example: customers must supply accurate information such as hours, overtime and leave, while Remote implements employment changes and termination requests through its employer process. The example is specific to those terms. It demonstrates why day-to-day direction and authority to change an employment agreement should be recorded separately.
Use a responsibility list with verbs and outputs. “HR: employee changes” is too broad. “HR submits the approved salary change; the provider confirms the local document and effective date; payroll checks the first resulting payment” gives the participants something they can perform and verify.
For each sensitive event, agree on the communication path:
Pay or benefit change: who requests it, who confirms it is permitted, who issues the document and who checks the first payroll result?
Leave or absence: who receives notice, who records the facts and who confirms the pay and benefit treatment?
Complaint or workplace incident: who receives the report, what immediate action is needed and who coordinates the employment response?
Performance or separation: who documents the business concern, who reviews the employment steps and who is authorized to speak to the worker?
Require a named escalation route for urgent events. If your manager and the provider's employment team work in different time zones, resolve how an urgent incident reaches an authorized person. A payroll support ticket alone may not be the right route for an employment matter.
Include benefits, confidentiality, intellectual property and data access in the agreement review. Ask how employee obligations connect to your company, which documents create that connection and what local limitations or additional documents require advice. Do not assume that a benefits summary or a platform's security page answers those contract questions.
Treat U.S. CPEO status as a separate tax question
A certified professional employer organization is an IRS-certified entity with specific federal employment tax treatment. CPEO status does not make the service an international EOR or establish who bears every employment obligation.
The IRS states that a CPEO generally has sole responsibility for the federal employment taxes on remuneration it pays to work site employees under the covered arrangement. The CPEO and customer may both be liable for remuneration paid to non-worksite employees. The distinction depends on the statutory rules and actual arrangement, not simply whether a proposal uses the word certified.
Verify the exact CPEO legal name and EIN, its certification effective date and the covered contract. Form 8973 notifies the IRS of contract starts and ends. The IRS also states that customers cannot view the CPEO's federal tax deposits and payments through EFTPS, so obtain an appropriate evidence route rather than promise a customer-account view that does not exist.
Have the tax owner identify the treatment of the actual workforce and any transition. Keep state unemployment, insurance, benefits and other obligations in their own review. A federal certification answer should not silently become an answer to a different jurisdiction's question.
If your immediate decision is whether a PEO's administration and benefits are worth buying for an existing U.S. employer, compare that contract with payroll service on a matched basis. If the immediate decision is who can employ someone in another country, settle that relationship first. A U.S. CPEO checkbox cannot fill the missing country employment agreement.
Take these requirements into a payroll software conversation
Once you have defined the hiring relationship, discuss your payroll requirements with SelectSoftware Reviews if a provider search would help. Confirm which arrangements and countries the service covers; verify legal employer details separately.
Compare the economics of eligible arrangements
Ask for prices only after the provider has accepted the population and described the service. Otherwise, the lowest quote may price a different relationship, omit a required country service or assume that your own entity will employ the worker.
Request a country-specific schedule that separates service fees, employee compensation, employer costs, benefits, setup or transition charges and any additional services. Identify the currency, conversion method and who bears changes in exchange rates or statutory amounts. Use quoted terms and adviser-confirmed assumptions; a generic per-employee headline is insufficient for a hiring budget.
Keep recurring expense, cash required before payroll and possible exit exposure distinguishable. A refundable deposit can tie up cash without being the same thing as a recurring service expense. A contingent termination cost is not necessarily due every month. Ask finance to determine the accounting treatment instead of adding every amount into one unexplained “monthly cost.”
Compare alternatives over the intended employment period and a realistic change scenario. For a small number of hires, establishing and running your own entity may involve work that is absent from a payroll subscription. For an existing entity, an EOR quote may introduce an employment structure the company does not need. Neither observation proves that one model is universally cheaper.
Check what the fee assumes your team will do. Country payroll can still require approved inputs, treasury funding and financial records. An EOR arrangement can still require managers, timely employment-event information and contract administration. Include that retained work in the operating plan without pretending that the service fee buys your entire HR function.
Avoid a headcount-only rule such as “switch to your own entity at ten employees.” Set a review point using the company's expansion plans, local requirements, acceptable employment structure, internal capacity and actual proposals. The review point is a business decision to obtain new evidence, not a legal threshold invented from a pricing example.
Follow two hiring situations to different shortlists
An established employer wants more HR administration
Fictional Northline Studio has 24 U.S. employees already employed by its operating company. Its payroll process works, but its owners want to evaluate broader HR and benefit administration. It has no proposed change in the employees' country or employing entity.
Northline's first shortlist is payroll and HR administration options, including an applicable PEO arrangement. It asks what co-employment changes, which plans cover the employees, what the customer retains and which entity has the relevant tax responsibilities. It does not treat an international EOR product as necessary merely because it also processes payroll.
The comparison should move forward only with a usable description of the actual service. If the PEO benefit terms do not fit, Northline may prefer another administration arrangement while keeping direct employment. If they do fit, Northline still needs funding, management and transition responsibilities that its team can perform.
One planned hire has no ready customer employing entity
Fictional Northline also wants to hire an employee who will work in another country. Its U.S. entity and payroll subscription do not establish the required local employment arrangement. The proposed worker has not started, and the country-specific review is still open.
For that population, Northline evaluates an EOR proposal and the alternative of establishing its own suitable employing arrangement. It requests the exact local employer, a contract sample, acceptance of the role and worksite, worker eligibility confirmation, fees and the path for later moving to its own entity.
Suppose the provider has not accepted the proposed customer-site duties. Northline records that issue as unresolved and obtains a specific decision before promising the start date. It does not substitute the country-coverage page or a salesperson's general onboarding estimate.
The two populations may eventually use the same vendor. Northline should still maintain separate employment decisions, service scopes and evidence. Success with the domestic team does not approve the foreign-country hire.
Use the Hiring Relationship Decision Record
Copy this record for each country and worker population. Use short entries and reference the documents that support them. Keep personal identity documents and sensitive employee information in the approved restricted system, not in a broadly shared vendor comparison.
Population and route
Population: Country, actual work location, role, approximate headcount, proposed start and intended duration.
Existing relationship: Current employer, or proposed new employment; identify any intended change.
Customer entity readiness: Named entity, readiness evidence and any unresolved registration or local-review condition.
Proposed route: Customer employment with payroll support, PEO co-employment, provider employment through EOR, or unresolved. Record the reason.
Parties and acceptance
Named parties: Employing, customer contracting, provider contracting, managing, billing and payroll-processing entities; identify any local partner.
Country acceptance: Role, worksite and worker eligibility accepted; supporting document, limits and approving contact.
Controlling documents: Order form, country terms, employment agreement sample, relevant service and data terms, and document precedence.
Retained responsibilities: Who supplies inputs, approves changes, communicates employment decisions, funds payroll and handles urgent incidents.
Terms needing specialist review: Employment, tax, immigration, benefits, insurance, intellectual property or data questions; adviser and open issue.
Commercial decision and later change
Budget and funding: Quoted service scope, currency, recurring cost, prefunding or deposit, and material assumptions still unconfirmed.
Transition or exit: Required notice, employment steps, final-pay and benefit handoff, records, deposits and any transfer conditions.
Decision: Proceed, hold for evidence, or reject this offer; responsible approver, date, unresolved condition and next review trigger.
A proceed decision means the responsible people accepted a defined arrangement for a defined population. It does not authorize a different country, role or employment model. Reopen the record when those facts change instead of editing the old approval so that it appears to have covered the new situation.
Filled example: the unresolved foreign-country hire
Population and route: One proposed employee working remotely in Country A; no ready customer employing entity; EOR route under evaluation.
Named parties and acceptance: Proposed local employer identified in the draft agreement. Customer-site work has been discussed but has not been accepted in writing. Worker eligibility review remains open.
Commercial decision: Hold the start-date commitment. HR obtains the provider's role/worksite decision and the local adviser's remaining advice. Finance confirms the actual funding terms once the accepted scope is known.
Review trigger: Reconsider when both open acceptance issues have documented answers. If the provider cannot support the work, evaluate another eligible arrangement rather than change the description of the job to fit the offer.
Country A and Northline are fictional. This example demonstrates the record's use; it does not establish that an EOR is permitted for any particular jurisdiction or role.
Plan for a change of employer before it happens
Moving from an EOR to your own entity is not merely moving employee data between software accounts. Identify which employment relationship ends or changes, which one begins and which local documents, consultation, consent or other steps your advisers say apply. Do not promise uninterrupted service credit, benefits or identical terms without establishing the required treatment.
Ask how the provider distinguishes ending the commercial service from ending an employee's employment. Remote's current Employment Services terms, for example, connect service termination with termination of employment agreements under those terms. Read the actual local and commercial documents before issuing a cancellation notice.
Create a person-by-person transition plan where the approved process requires it. Include the responsible employer at each stage, the effective dates, final and first payroll responsibilities, benefit coverage, leave balances, record delivery and access to later corrections. Ask which amounts remain payable and when any deposit can be released.
Confirm the receiving entity is ready before treating the current provider as replaceable. Entity formation, employer setup, bank funding, benefit arrangements and the employee's documents may run on different schedules. A system import can finish while the employment transition is still incomplete.
Keep evidence of the agreed transition and the records needed after the portal closes. Assign a contact for later employee questions, payroll corrections and tax documents. The provider's service may end before every question about the employment period has been resolved.
Questions that change the route
Can one vendor provide EOR, PEO and payroll?
Yes, a vendor can offer different services, as Remote's entity guide illustrates. Confirm the product, employing entity and agreement for each population. A broader product menu does not mean that every service is available or appropriate for every country and role.
Does having a local subsidiary mean an EOR is unnecessary?
It means you should examine whether that entity can and should employ the person. Readiness, the intended activity and the accepted arrangement still matter. Compare the proposed EOR with a real direct-employment alternative, including the work required to make the entity ready, rather than assume incorporation settles the decision.
Can the same employee simply move to another country?
Obtain a new country and work-location assessment before agreeing to the move. The employer, service eligibility, worker permission and operating requirements may need reconsideration. Keep an approved temporary trip distinct from a permanent change, and give managers a route for escalating either.
Which offer belongs on the final shortlist?
Keep offers that identify a suitable employment relationship, accepted country scope, usable responsibilities and terms your company can fund and operate. Resolve missing acceptance or specialist advice before authorizing the hire. Then choose among those eligible offers using the actual service, cost and transition terms.
Use your requirements to guide the provider search
Use the Hiring Relationship Decision Record to brief an optional SelectSoftware Reviews advisor conversation. Keep the legal relationship, country eligibility and contract review as separate checks before choosing.
Explore related payroll 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.
