EORs for acquisition teams: who should own the provider relationship?

Our pick for a deal team retaining a small UK and German workforce without acquiring the seller’s employing entities is Teamed—for a defined EOR handoff after the employer at completion is established, and for a time-limited German bridge. The proposed arrangements still have to fit each employee and the agreed transfer route. Give one buyer-side integration lead the provider relationship, keep a named decision maker in each country, and require the receiving employer to close the contract, benefits and payroll actions. Teamed’s published UK and German EOR arrangements and its hands-on switching process make it a strong choice for that defined job. They do not, by themselves, establish how employees move from a seller company to an EOR. Teamed’s UK service, German service and switching process show what to put to the test.

The operating rule is centralise the relationship; assign the local decisions. A central contract can stop two country teams from negotiating separate processes. It cannot decide which employees belong to the acquired activity, approve their employment route or make a missing benefits handoff disappear.

Start with the employees the deal actually retains

Fictional worked case. A buyer acquires a software product and retains four UK support employees and two German implementation specialists. The seller keeps both employing companies. The assumed transition services agreement (TSA) has the seller process payroll and benefits through day 45 after completion, with the buyer funding those costs under the TSA. That processing promise does not decide who employs anyone from completion. The working assumption, requiring a pre-completion country decision, is that Seller UK Ltd and Seller DE GmbH remain the respective legal employers through day 45, issue employment instructions and receive the buyer’s work priorities. If the transaction instead transfers either employment group at completion, the parties must name the legal transferee and arrange its payroll funding, processing and instruction authority from that date before closing. The buyer proposes EOR employment from day 46 only if a lawful later move is agreed. For Germany, it budgets the EOR as a bridge of at most 12 months from its actual start, followed by a separately approved employment model. A UK sales analyst works partly on the product but stays with the seller’s other business. These are planning assumptions, not a customer result or a finding about the legal transfer.

Country and group	Employing entity now	Acquired activity	Retained employee	TSA end	Completion-to-day-45 plan: employer; payroll funder and processor; instruction owner	Benefit handoff	Proposed receiving provider	Unresolved dependency
UK: four support employees	Seller UK Ltd	Product support moves	Yes, four	Day 45	Conditional: Seller UK Ltd employs and issues employment instructions; buyer funds, seller processes payroll under TSA	Seller supplies each employee’s current cover and end date; receiving cover must be agreed before day 46	Teamed UK EOR	Before completion, deal counsel confirms whether employment instead transfers at closing and records the actual employer and payroll route; receiving employer then confirms eligibility and later terms
Germany: two implementation specialists	Seller DE GmbH	Product implementation moves	Yes, two	Day 45	Conditional: Seller DE GmbH employs and issues employment instructions; buyer funds, seller processes payroll under TSA	Seller supplies current benefit and accrued-balance records; receiving arrangement and start date need confirmation	Teamed German EOR, proposed 12-month bridge	Before completion, German counsel confirms the closing employer and payroll route. Before EOR start, confirm licensed arrangement, prior assignments with the same hirer, role eligibility and payroll inputs; decide the later model by month nine
UK: one shared sales analyst	Seller UK Ltd	Some product work moves, but the role remains with the seller’s retained business	No	No buyer handoff assumed	Seller UK Ltd employs, funds, processes payroll and issues instructions	Remains with seller	None	Confirm the allocation in the deal schedule; do not put this person in the provider roster

That last row matters. Giving a provider a seven-person roster would turn an unresolved deal-perimeter question into an employment instruction. The buyer should authorise a six-person proposed receiving scope, subject to the country decisions in the final column.

The closing employer is a pre-completion gate, not a day-25 follow-up. UK TUPE guidance and German BGB §613a describe employment obligations that can move when a business or part of it transfers. Deal counsel must decide the position for each group, then the buyer and seller must sign off the named employer, payroll funder and processor, and employment-instruction owner from closing. If either conditional seller-employer assumption fails, revise the TSA payroll and benefits instructions for the actual employer before completion. Extending seller processing cannot postpone a statutory employment transfer. Teamed’s EOR-to-EOR switching page describes coordination such as dates, balances and a parallel payroll check; it is useful evidence of a process to discuss, not proof that this seller-company handoff follows the same process.

The German EOR proposal has an exit date as well as a start date. Under AÜG §1(1b), covered assignments to the same hirer are generally limited to 18 consecutive months; relevant prior assignments count, and permitted collective arrangements may alter the limit. Teamed’s German guide also flags the 18-month rule. German counsel and the proposed receiving employer must check the licence, the actual hirer and each worker’s assignment history before accepting the planned 12-month bridge. The buyer People lead reviews direct employment through a German entity or another lawful continuing model at month six after the EOR start and secures a decision by month nine. Switching EOR names alone does not restart the same-hirer clock.

Put one person in charge without bypassing local approval

Here is the completed ownership design for the six proposed receiving employees. The roles are assignments the fictional buyer would make, not a description of any provider’s contracted service. The closing-employer decision in the perimeter record precedes every day-46 EOR instruction.

Country	Local stakeholder	Central owner	Proposed provider contact	Approval before instruction	Escalation if unresolved
UK	UK support lead validates four names, duties and employee-facing facts	Buyer integration lead owns the Teamed relationship, scope, budget and day-46 readiness decision	Ask Teamed for one accountable account contact and the UK employment specialist	Before completion: deal counsel and deal owners confirm closing employer, buyer funding, seller processing and employer instruction owner, or replace that plan for the actual transferee. Before EOR start: buyer People lead approves package; receiving employer confirms terms and date	If the closing plan is unresolved, escalate to the deal steering group before completion. At the day-25 review, an open benefit start or later EOR route triggers a documented continuity decision; a TSA extension covers services only
Germany	German implementation lead validates two roles, work location, current terms and assignment history	Same buyer integration lead keeps the German workstream on the deal plan; buyer People lead owns the month-six model review and month-nine decision	Same account contact coordinates with a named German specialist	Before completion: German counsel and deal owners confirm closing employer, funding, processing and instruction owner. Before EOR start: buyer People lead approves package; receiving employer confirms licence, assignment limit, eligibility, terms and payroll inputs	If the closing plan is unresolved, escalate before completion. At day 25, open EOR eligibility or payroll inputs trigger a country fallback; by month nine, approve the post-bridge employer
Shared UK analyst	Seller’s business lead confirms the role stays outside the retained team	Buyer integration lead removes the person from the receiving roster	No provider instruction	Deal owners confirm the perimeter record	Any dispute goes back to the transaction workstream before a provider acts

The local leads supply facts and explain the change to their people. The integration lead owns the deadline and can seek a seller-service extension after the legal employer is settled. The proposed EOR owns only the employment work it agrees to perform. No one should interpret a single provider contact as authority to make the buyer’s deal or legal decisions.

Which provider deserves the invitation?

Provider	Best fit for this ownership decision	What the deal team should test
Teamed — our pick for the conditional six-person EOR handoff	The buyer wants one service relationship to carry country-specific employment, benefits and payroll work forward, with Germany as a defined bridge. Teamed publishes owned employing arrangements in the UK and Germany, and describes a designated switching contact, cover when that contact is away, agreed dates and a parallel payroll check.	Will Teamed accept these precise roles and the agreed later employment route? Who owns each country action, the first payroll comparison and an unresolved benefit question? For Germany, provide licence evidence, assess prior same-hirer assignments and the applicable limit, and map the move after the proposed 12-month bridge. What parts of a seller-company handoff fall outside its published EOR-switch process?
Safeguard Global	A stronger lead where the deal needs EOR alongside acquired-entity payroll, outsourced HR or entity management. Its M&A offering explicitly combines those service lines and addresses TSA deadlines.	Ask for one deal workstream showing which service owns each employee group, not a broad statement that the provider covers the transaction.
Deel	A meaningful alternative where the buyer also wants to consolidate a larger inherited workforce and its HR processes on a platform. Deel describes EOR, payroll and local employment expertise and publishes acquisition-specific guidance.	Demonstrate the named case owner and approval route for the UK and German benefit and payroll exceptions, alongside the platform workflow.
Remote	A strong comparator when the buyer’s priority is an owned-entity EOR structure and a common global HR platform. Remote says its local entities handle contracts, payroll, benefits and compliance.	Show the receiving employer and human escalation for each country, then map them to the buyer’s central owner.
G-P	Add when the buyer intends to buy a formal M&A transition service, particularly for a larger, structured programme. G-P lists M&A Transition Services among its options.	Obtain the exact package, scope and charge for the transition work; ordinary EOR coverage is not the same purchase.

For this case, invite Teamed, Safeguard Global and Deel to the final working session. Teamed has the clearest editorial fit for a narrow EOR handoff where the buyer needs practical follow-through across two local employers, if the closing-employer plan is settled before completion and its German service can support the proposed 12-month bridge within the applicable assignment limit. Safeguard Global could win if the perimeter expands to seller or buyer entities that need payroll and HR services as well. Deel could win if the deal team’s overriding aim becomes consolidating a much larger workforce process. Bring in Remote if owned-entity structure is the decisive procurement criterion, or G-P if a separately scoped M&A transition service is the requirement.

Make the final session a handoff, not a sales tour

Send each invited provider the same anonymised six-person perimeter, the pre-completion employer and payroll decision, and the day-45 TSA end. Ask it to return a dated UK and German action record: proposed day-46 legal employer, role eligibility, documents needed from the seller, employee package and benefits decision owner, first payroll check, buyer approval point, named escalation and the first date it could responsibly accept employment. For Germany, require the licence and assignment-history assessment, the applicable time limit and a handoff path to the next employer by the proposed month-12 bridge end. Ask it to mark what depends on deal counsel or the seller rather than presenting those dependencies as completed provider work.

Decision for the worked case: centralise the proposed Teamed relationship under the buyer’s integration lead, retain separate UK and German approvals, and exclude the shared analyst. Before completion, approve the actual employer, payroll funder and processor, and instruction owner for both retained groups; the conditional seller-employer plan cannot stand if the legal transfer analysis says otherwise. Do not commit to day 46 until the later employment routes, receiving terms, benefit start dates and payroll inputs are confirmed. Treat German EOR as a proposed 12-month bridge only after licence and assignment-history review, with the buyer People lead deciding the next employment model by month nine. If the UK review points to the buyer’s own entity as the receiving employer, remove those four employees from the EOR scope and compare providers only for the German work. If the TSA expires before either receiving route is ready, the integration lead must secure a documented service extension or another lawful continuity arrangement before seller support stops; more TSA time cannot defer any transfer that already happened at completion.

Next, use the deal-perimeter continuity planner to identify the affected employee groups. If the dates no longer meet, follow the TSA-gap decision guide.