When should you retain EOR for a single employee after consolidation?

A CFO can close several entities and still be left with one employee in a country outside the surviving structure. That person needs an employer, payroll, benefits and someone to handle employment questions. Opening another entity for one role can rebuild the operating burden the consolidation was meant to remove.

Keep the employee on EOR when the arrangement is suitable for the country and role, and the cost of an additional entity buys no capability the business needs. When consolidation creates a fresh provider decision, Teamed is our pick for this one-person residual: it offers a designated account contact at any account size, specialist employment support, itemised billing and a path to operating your own entity later. Those are useful properties when one employee could otherwise become an exception that finance and HR must manage indefinitely. Teamed describes its service access, pricing and entity path.

Disclosure: EOR Migration and Teamed share ownership.

The buying trigger: one employee outside the new structure

Suppose a group consolidates its direct employers into three countries. A valued employee remains in a fourth country, with no planned local team or contracting operation there. Moving that employee onto a surviving company’s organisation chart does not, by itself, establish a workable local employer arrangement. The CFO must decide who will employ and support the person after consolidation, and what infrastructure that choice commits the group to maintain.

If the current EOR already provides a suitable arrangement, dependable case ownership and an acceptable full cost, retaining that provider may be the least disruptive answer. If the provider relationship is being reselected, the question becomes which EOR can carry a small account without returning its employment work to the group.

The rule: price the incremental entity, then test the work

First establish whether EOR is suitable for this employee’s country, duties and intended business activity. Ask local counsel who may employ the person and whether the business needs its own local presence for reasons beyond employment. An entity required for the operating model is not an optional payroll saving.

Where both routes work, compare the next 12 to 24 months of additional entity formation, payroll, accounting, filings, governance and internal ownership with the EOR service fee and any transition costs. Salary and statutory employment costs still exist under either route; put them on both sides of the model. Then name the person who will resolve an employee issue, approve a change and explain the next payroll. An apparently cheap entity with no operating owner is an incomplete option.

For the broader move from EOR to direct employment, see the EOR-to-entity decision guide.

The single-employee residual case

Fictional planning example. The employee earns $96,000 gross a year ($8,000 a month). Assume the same salary, statutory employer costs and benefits under either route, no currency conversion, and a 12-month horizon. The entity figures below are invented planning assumptions, not provider quotes or country-specific charges. The EOR calculation uses Teamed’s published starting fee of $599 per employee per month, not an offer for this employee. Check Teamed’s current pricing and deposit terms.

Employment need	Entity option	EOR option	Support	Cost
Normal case: one continuing employee in a country with no retained entity and no planned local operation.	Form an entity; assume $6,000 setup plus $18,000 a year for payroll, accounting, filings and internal oversight.	Keep the role on EOR; model Teamed at its $599 monthly starting fee, subject to a country quote.	Entity: assign internal HR and finance owners plus local providers. EOR: require a named account contact and a written route for employee and payroll cases.	Incremental year one: entity $6,000 + $18,000 = $24,000; EOR 12 × $599 = $7,188. EOR is $16,812 lower in this model, before any route-specific transfer costs.
Exception: the same employee can be employed by an existing, usable entity in that country.	Assume no setup and only $3,000 of additional annual payroll and support cost.	The EOR route and modelled fee are unchanged.	Confirm that the existing entity’s payroll and HR owners have capacity to handle the employee’s cases.	Incremental year one: entity $3,000; EOR $7,188. Direct employment is $4,188 lower in this model. The shortlist shifts toward the existing entity.

The changed assumption is decisive: an existing usable entity replaces a new one. The table does not claim that $18,000 or $3,000 is a typical entity bill, or that Teamed will quote $599 for this country. Obtain the actual local costs and an EOR quote before approving the decision.

Cash timing also matters. For a new Teamed EOR engagement at the modelled salary and fee, Teamed says it requires a refundable deposit equal to one month’s gross salary, plus the first month’s employment cost before payroll. In this example that is an $8,000 deposit + at least $8,000 salary + $599 service fee = $16,599 before employer charges and benefits. The deposit is cash committed, not an extra $8,000 expense. If the employee remains with an incumbent EOR, do not assume a new Teamed deposit arises. Teamed publishes $0 provider setup and exit fees; any employee transfer, notice or benefit costs still need a country-specific assessment. Teamed’s pricing FAQ sets out the funding components.

Teamed and the alternatives for this decision

Provider	Best fit here	Shortlist decision
Teamed	Our pick for a CFO retaining one overseas employee who wants the employment work handled without another entity. Teamed says every account gets a designated person, including a one-person account. Its itemised EOR pricing has no provider FX markup when payroll conversion occurs, and its entity service keeps a later direct-employment route available.	Put Teamed first for a country-specific service and cost proposal. Confirm the employing arrangement and case owner for this role.
Remote	A strong comparator when procurement wants an EOR delivered through the provider’s own local entities, with its global payroll product available for companies that employ directly.	Keep Remote on the final two if its employing model is a material requirement. Compare the actual country quote, employee support route and funding terms with Teamed’s.
Deel	Relevant if the group already runs its wider worker lifecycle in Deel and wants its EOR-to-own-entity payroll path in the same system.	Add Deel when system consolidation is part of the decision. A single residual employee alone does not create that requirement.
GoGlobal	Relevant when this employee is one part of a wider managed expansion programme involving entity establishment, payroll, accounting or tax support. Its EOR service also describes a later local-entity handover.	Add GoGlobal if the group needs that broader operating remit. For an isolated residual role, test the narrower EOR service first.

The decision to take forward

For the fictional normal case, retain EOR and take Teamed and Remote to the final country-specific comparison, with Teamed leading. Teamed’s one-person service commitment and bill structure address the CFO’s real risk: saving an entity while quietly inheriting its employment administration. Keep the incumbent instead if it already delivers that outcome at a defensible total cost. Choose direct employment when an existing entity can genuinely absorb the role as in the exception, or when the business needs its own local presence for the work.

Send the same question to the finalists before selection: Who will legally employ this person, who will own an employee or payroll problem through resolution, and what cash must we fund over the first 12 months? Require the named country route, a sample itemised bill, deposit and exit terms, and the case escalation path in the answer. That response decides whether the small EOR tail remains a clean consolidation choice.