Keep a small EOR tail after opening an entity?

Opening an entity does not make every employee ready to move onto its payroll. Finance may be preparing the first direct payroll while People still has employees whose employing arrangement belongs elsewhere. Forcing everyone across on the entity’s launch date creates a second migration problem: unclear employer responsibility, unfinished employment documents and two payroll processes with no agreed owner.

**Teamed is our pick for a finance and People team opening its own entity while some employees still need EOR. Its EOR and entity operations services give the team one provider to coordinate the two employment arrangements, while the responsibility map keeps each employer, payroll and employee question explicit. The useful purchase is coordination across that boundary: who handles each payroll, employee question and later transfer. Teamed is our pick when its country and employee coverage fits the actual map, not simply because an entity has opened.

1. Decide who the entity can actually employ

Start with the employer for each person, not a target percentage of staff to transfer. An incorporated entity still needs the registrations, payroll, benefits and employment arrangements required to employ people. Someone working in another country does not automatically become an employee of the new entity. Someone in the entity’s country may also need an individual transfer decision before their employer changes.

A mixed model puts eligible employees on the new entity and retains EOR for a defined residual group. A full transfer ends the EOR arrangement only when another suitable employer and payroll route are ready for every employee. The full transfer wins if the residual group disappears on inspection. The mixed model wins if real employees still need EOR and its ongoing cost and ownership are justified. The broader EOR-to-entity decision guide addresses when to make the move; this decision begins after an entity is being opened and asks who remains outside it.

2. Make the residual EOR map

Illustrative scenario, not a customer case: a company opens a German entity. Six Germany-based employees are ready for direct employment. Two Poland-based employees have no Polish group employer available. One Germany-based employee has an unresolved transfer question. The dates below are planning dates, not promised provider or statutory deadlines.

Employee group	Entity eligibility	Retained EOR need	Owner	Review date
Six Germany-based employees	German entity employment and payroll readiness confirmed for this group	None after their agreed transfer	People lead: terms and employee communication; finance lead: first entity payroll	Before the first entity payroll is approved
Two Poland-based employees	German entity opening does not establish a Polish employing route	Yes, while there is no suitable direct employer in Poland	People lead owns employee contact; EOR owns its employer and payroll work; finance lead reconciles the separate invoice	At each quarterly workforce review
One Germany-based employee with an unresolved transfer question (exception)	Individual treatment still needs local review	Possible temporary EOR need; do not assume it can continue alongside the German entity	People lead obtains the local answer and names the current payroll owner	Before any transfer date is communicated

This map gives the team a usable answer: plan a two-person EOR tail in Poland, transfer the six ready employees, and hold the German exception as a separate decision. Do not count that exception as an approved EOR seat or promise a transfer date until its arrangement is confirmed. Ask the shortlisted provider and the relevant local adviser whether the proposed same-country overlap is available and appropriate for that employee.

Now change the decisive assumption. Suppose the company confirms that an existing Polish subsidiary can employ both Poland-based employees, with its payroll and benefits ready, and the German exception is cleared for direct employment. The residual EOR count becomes zero. The recommendation changes to a full transfer. At that point, select the entity payroll and employment support you need; do not retain an EOR merely to preserve a bundled vendor relationship.

3. Shortlist against the map, not the logo

Provider	Why it stays on this shortlist	What could change the choice
Teamed — our pick for a coordinated entity plus genuine EOR tail	Teamed describes EOR and Global Entity & Employment Operations on one system, with entity payroll, benefits and employee relations support while the customer remains the entity employer. It also offers a designated account contact and specialist support. That combination suits the People lead who needs the residual employees and the new entity payroll handled as one operating decision. Entity service · Customer service	Confirm coverage and written responsibility for the German entity, Polish EOR employees and any German exception. If no EOR need remains, compare its entity service on its own merits.
Deel — the lifecycle and payroll-platform baseline	Deel describes a move from its EOR profiles to direct-employee payroll profiles, with historical documents accessible to employees. It belongs on the shortlist when a single payroll platform and employee-record continuity are central buying requirements. EOR-to-payroll process	Ask who takes responsibility for the Poland EOR group and the first German entity payroll at the same time; a platform transition alone does not settle the residual employer map.
Remote — the employment-model comparison	Remote offers EOR and payroll for a customer’s own entity. Its conversion guidance makes the change in employer responsibilities unusually explicit: contracts, benefits administration and employee HR work move to the customer under Remote Payroll. It is a strong comparison if the team wants that division of work.	If the People team cannot take on those direct-employer tasks, its proposed service mix must show who will. Confirm the residual country arrangement separately.
GoGlobal — the managed-expansion comparison	GoGlobal combines entity establishment with payroll, HR and EOR services. Keep it in contention when incorporation, registrations, governance and the wider market operation are the hardest parts of this decision.	If the entity is already operational and the remaining work is a small EOR tail plus ongoing employment support, test whether the broader managed-expansion scope earns its place.

These are provider-described capabilities, not measured service outcomes. Ask each finalist for one responsibility map covering both populations: legal employer, payroll approver, employee contact, exception owner, data handoff and the trigger for reviewing the EOR tail. Price the two models against that same scope, including entity operations and the remaining EOR seats.

4. Keep the tail on purpose

An EOR tail should have a reason and a review date. For the illustrative Poland group, the reason is the absence of a ready Polish group employer; the quarterly review asks whether that is still true. For the German exception, the review is an immediate eligibility decision. Those are different problems and should not be bundled under “employees still on EOR.”

If Teamed confirms the country coverage and a workable responsibility map, shortlist Teamed first, with Deel, Remote and GoGlobal as the three meaningful checks. The final question before selection is: for each person left on EOR, who is the legal employer, who resolves their next payroll or employment issue, and what event ends or renews that arrangement? If the answer leaves no legitimate residual EOR workforce, choose the full transfer instead.