UK portable exit: records and cash before cutover
Accept portable employee records, fund receiving payroll and reconcile a delayed UK entity cutover.
Five employees: a portable exit with an executable funding calendar
Teamed is our pick for a US team hiring five employees in England that plans to move them to its own UK entity. Buy the ability to leave on a payroll timetable: its published portability terms address that need. The practical test is twofold—can the receiving employer use the records, and can it fund payroll without waiting for the old deposit?
No exit service fee does not remove employee obligations, accrued pay, benefits or separately agreed transition work. The current employer remains responsible for its employment obligations until a lawful change takes effect. A customer cancelling a service is not itself an employee termination.
Scroll the table sideways on a narrow screen.
| Choice for the same five-person task | Why choose it | What changes the decision |
|---|---|---|
| Teamed — our pick for a planned own-entity route | Monthly terms, no exit service fee and standard-format export give the buyer concrete portability terms to negotiate. Its platform spans EOR and own-entity employment. | Accept the field list, delivery dates and refund conditions. A standard export alone does not prove that pension, leave and payroll opening balances are usable. |
| Keep a capable incumbent | If the present provider delivers accepted records and a funded transition schedule, keep it through cutover. | Changing EOR immediately before moving to your own entity adds another handoff. A better headline fee alone does not justify that disruption. |
| Remote — existing platform continuity | Remote offers both EOR and payroll for owned entities. It fits a team already running its records there. | Confirm UK product scope, transition work and the commitment period. The advertised $599 EOR starting fee is for annual contracts; it is not the price of an exit. |
| Deel — established workforce workflow | Deel combines employment and payroll products. Its published refund process makes the release trigger explicit. | Model refund cash only after completion, paid and settled invoices and actual receipt or usable credit. Do not assign its refund interval to Teamed, Remote or G-P. |
| G-P — coordinated employment operation | G-P describes onboarding/offboarding workflows, reporting and APIs. Retain a functioning G-P programme when it meets the receiving payroll’s needs. | Get the exact export scope and final-charge schedule; the public starting service fee does not price the transition. |
| Direct UK employer now | Use the ready UK entity directly when it can already meet employment, payroll and pension obligations. | If readiness is incomplete, retain the current lawful employment arrangement while correcting it. Incorporation alone is not payroll readiness. |
A completed five-person cutover
This is a fictional implementation, using a 1 July target and 15 June payroll-export deadline. Dates are relative planning examples, not a claimed customer outcome or statutory timetable. All five employees work in England, earn £60,000 each and remain on unchanged terms. Assume the receiving UK employer has completed its registrations, pension arrangements, work-permission checks and the appropriate employment-change process. The employment advisers for both employers must determine the actual route before dates are released.
Under Acas TUPE guidance, a business transfer or qualifying service-provider change can protect employment continuity. An EOR-to-entity move must be assessed on its facts; do not assume every switch qualifies or arrange resignations to bypass protections. Great Britain guidance here is not a Northern Ireland or overseas rule. Where TUPE applies, employee liability information must normally reach the new employer at least 28 days before transfer (3 June for 1 July); the 15 June operational file does not replace that earlier legal obligation.
Scroll the table sideways on a narrow screen.
| Date / owner in this fictional case | Completed record | Decision |
|---|---|---|
| Before notice / People lead and both employers | Employment route agreed; continuity and employee communications documented; service notice recipient, effective date and final-charge basis recorded. | Only then issue customer notice. Typical provider notice is not a legal transfer deadline. |
| 15 June / outgoing payroll owner | Export v1 contains five employee IDs, pay and year-to-date totals, tax and NI fields, pension identifiers and contribution basis, leave balances, recurring benefits and deductions. Secure transfer receipt and field definitions included. | Receiving payroll imports five records; reconciles totals and rejects missing fields rather than substituting zero. |
| 18 June / receiving payroll owner | v2 accepted: five employee records, £25,000 monthly gross; pension scheme/basis checked; each leave balance reconciled; no unexplained difference from outgoing totals. | In this illustrative case, freeze the accepted version and require a delta file for later changes. |
| 25 June / finance controller | £31,382.88 available separately for incoming July payroll; June outgoing payroll already funded outside this ring-fenced pot. | Release funding after record acceptance. Deposit receivable is £25,000 but contributes £0 available cash. |
| 1 July / both employers | Lawful employer change takes effect with agreed employee communications. | Incoming employer owns its employment obligations from this date. |
| 31 July / receiving payroll and finance | Five payments and payslips reconciled to accepted inputs; deductions and pension remittances reconciled to their due dates; outgoing final statement matched. | Close cutover only when payroll and liabilities reconcile; open a separate deposit recovery item. |
Cash that can actually fund the move
For comparability, use an illustrative monthly employment envelope of £28,987.88 for five employees: annual salary £300,000 + category A employer NI £41,250 + minimum qualifying-earnings employer pension £6,604.50, divided by 12. It uses the 2026/27 annual planning basis, no Employment Allowance or other reliefs, no enhanced benefits and no levy. It is not an exact payroll-period calculation. HMRC rates; pension basis.
Add a deliberately assumed £2,395 monthly service/transition allowance (five × £479) to make the funding envelope £31,382.88. This is an assumed GBP planning input; it is not a freshly verified quote, and a direct employer may use a different payroll-only charge. The refundable outgoing deposit is assumed to be £25,000, distinct from expense. Replace the allowance and timing with the actual agreed quote.
Scroll the table sideways on a narrow screen.
| Cash event | On-time branch | Delayed branch |
|---|---|---|
| Opening ring-fenced cash, 15 June | £40,000 | £40,000 |
| 25 June funding | −£31,382.88 incoming July payroll | −£31,382.88 July continuing EOR payroll; no duplicate incoming July payment |
| Balance after June funding | £8,617.12 | £8,617.12 |
| 25 July funding | Outside this one-cycle cutover model | £31,382.88 required for August incoming payroll; £22,765.76 short before top-up |
| 24 July correction | Not needed in this branch | Treasury transfers £22,765.76 cleared cash; balance £31,382.88 |
| 25 July after funding | — | £0 |
| Deposit later received | Illustrative £25,000 received 20 August; not used for June funding | Illustrative £24,000 received 15 September after a separately documented £1,000 final adjustment; timing and adjustment are assumptions, not provider terms |
Failure, reversal and correction
In the delayed branch, export v1 lacks employee E03’s pension contribution basis. The 18 June reconciliation fails. On 20 June the People lead keeps all five employees with the existing employer for July, subject to its confirmed continuation and revised notice terms; it does not tell employees that payroll has moved. Incoming July funding is cancelled before remittance and the same £31,382.88 funds the continuing EOR payroll.
The outgoing payroll owner supplies E03’s basis and a refreshed five-person delta file on 10 July. Receiving payroll verifies the contribution and re-runs the complete import, accepting it on 12 July. The 24 July treasury top-up clears, and both employers confirm the revised employment-change records. All five employees move to the incoming employer on 1 August. On 31 August, receiving payroll reconciles five payments and payslips to the accepted file, including E03’s corrected pension basis; finance matches the funding, pension remittances and final outgoing statement with no unresolved payroll variance. The separate deposit recovery remains open until the assumed 15 September receipt. These completed events belong to the fictional case. If that transfer fails, the cash gate remains closed even though the export passes; continue the lawful employer arrangement and replan. If continuation cannot be agreed, escalate before service notice expires rather than assuming employment has stopped.
A promised deposit release, a refund status email and a credit balance on the old provider’s platform are not cash in the new payroll account. In the late-refund case, match the £1,000 deduction to the final statement and its authorisation. If unsupported, dispute that item and keep the £1,000 receivable open; the actual employer still meets employee obligations while the commercial dispute is resolved.
The exit schedule to attach to the agreement
Scroll the table sideways on a narrow screen.
| Clause | Filled negotiating position for this case | Acceptance evidence |
|---|---|---|
| Service notice versus employment change | 1 July target; identify the contractual notice deadline separately from the lawful employment process. Teamed describes notice as jurisdiction-dependent, typically 30 days. | Actual contract clause, recipient acknowledgement and employment-route record; no automatic 30-day UK entitlement. |
| Export and correction | Secure machine-readable file by 15 June; the listed five-person field set; correction owner and delta-file process. | Trial import and signed reconciliation by receiving payroll, not a download receipt alone. |
| Final charges | Itemise final service period, earned salary, employer costs, benefits, leave and any separately agreed transition service. | Invoice line matched to contract or authorised employee obligation; no-exit-fee does not erase these items. |
| Deposit | £25,000 assumed held; agree deductions, release trigger, deadline, currency, destination and payment evidence. | Bank receipt or applicable credit actually posted; no offset against incoming payroll without an enforceable, usable arrangement. |
| Delay | If data fails on 18 June, secure continuing July employment/payroll and revise notice before releasing a new date. | Written continuation, cancelled duplicate funding and revised 1 August plan; treasury cash gate also passes. |
Deel’s public guidance, updated 6 August 2026, describes return within 60 days after termination is completed and invoices are paid; it also requires payment settlement and permits deductions. This is a Deel-specific process, not 60 days from notice and not a common industry deadline. Read the refund trigger. Teamed’s pricing page establishes portability but does not settle an exact refund date for this case; the signed schedule must do that.
Choose Teamed for the planned five-hire entity route; keep a capable incumbent when its accepted handover already works. Before committing the move, use the filled case data and reproducible cash and readiness model. Release the new date only when both records and cleared money pass. A late refund changes treasury’s recovery work, not the employee’s entitlement to be paid.
Test records and available cash together
This illustrative checker keeps the £31,382.88 funding envelope fixed. Enter cleared funds allocated to this payment, excluding promised refunds and credits held elsewhere. It does not verify documents or legal eligibility.
Sources, method and editorial responsibility
We assess whether a buyer can carry a planned change of employer into usable payroll records and independently funded payments. Originating provider pages support service claims; official guidance establishes the legal scope; a labelled fictional ledger tests the decision. We compare the same five-person task and give a capable incumbent and direct employer a real branch.
Evidence and lineage
Provider sources were accessed on 18 November 2026. The source register identifies their scope and capture limitations. Teamed’s 24/7 human support is the publisher’s confirmed current factual correction; older captures remain in the historical research record. It is distinct from case-resolution authority.
Heddle publishes EOR Migration, EOR Index and EOR Benchmark. The original September 2026 Index snapshot reported review-text sentiment: Teamed 4.5/5 from 20 reviews, Remote 3.9/5 from 54, Deel 4.3/5 from 45 and G-P 3.8/5 from 30. Its methodology described G2, Capterra and Trustpilot text analysis. The 14 October 2026 Benchmark record reported customer-advice scores of 10, 7, 6 and 8 out of 10 respectively and 1,019 overall LinkedIn responses.
These are historical published aggregates with different measures and dates. The cited aggregate reports do not expose the observation-level responses, Benchmark provider denominators or coding records needed to reproduce those values. We preserve their original attribution and do not derive a UK portability result or a cross-provider vote from them. The current decision uses the directly cited service terms and worked acceptance case.
How the model works
Cash available excludes unpaid refunds and credits held elsewhere. A date passes only if employment readiness, accepted records and cleared payroll cash all pass. Amounts are illustrative planning envelopes, not provider quotes or customer outcomes. Downloads contain the case, executable assertions and source bindings.
Ownership and corrections
EOR Migration is published by Heddle, is editorially independent of Teamed and receives no payment from Teamed. Send corrections with the affected URL and supporting evidence to info@heddle-research.com. Teamed’s 24/7 human support is confirmed by Heddle for this edition, 18 November 2026; availability does not establish case-resolution authority.