Accept the employee records before a UK employer cutover
Reconcile a ten-person England transfer, close record exceptions and distinguish operational readiness from legal transfer duties.
Nine ready records do not release a ten-person transfer
Keep the ten-person cutover on hold at the first cutoff. A payroll import can succeed while an employee loses three days of holiday, seven days of medical cover or a recurring £150 allowance. Release the employment change only against an accepted record for every person in the legally defined transfer population.
This worked case concerns ten employees in England moving from an EOR towards the buyer’s UK entity. It is illustrative, not a customer outcome. Case dates: snapshot 25 June 2026, intended transfer 1 July, reconciliation cutoff 26 June at 12:00 BST. The later November legal update is separate from that historical scenario.
Record readiness does not determine who legally transfers
Before scheduling the move, the outgoing and incoming employers’ advisers establish whether the arrangement is a relevant TUPE transfer and which employees are assigned to it. A change of payroll software alone does not establish that conclusion. Where TUPE applies, assigned employees transfer under the applicable rules; the buyer cannot select only the clean records. A spreadsheet hold is an operational escalation, not a power to stop a legal transfer that takes effect.
For a genuinely separable, lawful phased move, advisers must establish the population, process and dates before operations releases a subset. Otherwise plan the whole cohort together. If the transfer date cannot lawfully be changed, the incoming employer must prepare to fulfil its duties while correcting the unresolved records. The actual employer remains responsible for pay, benefits and employee concerns throughout; a commercial delay does not suspend those duties.
Scope: Great Britain guidance from Acas on TUPE applicability and Acas on transferring employees. Northern Ireland requires its own applicable assessment.
Keep legal notice and reconciliation deadlines separate
Where TUPE applies, Acas says employee liability information must be supplied at least 28 days before transfer, accurate and up to date. For the proposed 1 July date, this case assumes initial ELI supplied by 3 June; the 26 June register is a correction and final reconciliation checkpoint. It is not the start of the legal handover. The legal owners must also plan the applicable information and consultation process before transfer, including proposed measures. Rescheduling requires refreshed information, communications and legal timing checks.
Keep outgoing, proposed and resolved versions
Reconcile identity and role; pay and working pattern; original service and documented legal treatment; holiday entitlement, taken leave and opening balance; benefits, pension and effective dates; payroll inputs, deductions, bank details and required year-to-date data. Preserve the source value, explanation, approver role, timestamp and version. Restrict record sharing to authorised recipients through a secure channel; keep medical and grievance details out of the general payroll spreadsheet.
The five-row exception register at the cutoff
| Record | Outgoing v1 | Incoming v1 | Resolved version / evidence | At noon |
|---|---|---|---|---|
| Engineer A | 8 unused holiday days | 5 days | Three approved days were cancelled before snapshot; cancellation record A-17 restores 8 days. Outgoing HR and incoming HR accept v2 on 26 June 10:00. | Ready: 8 days |
| Analyst B | Medical cover ends 30 June | Replacement starts 8 July | Insurer confirmation B-4 amends start to 1 July; benefits owner verifies no gap and accepts v2 at 11:00. | Ready: zero gap |
| Manager C | Service began 12 March 2021 | Service date absent | Earlier contract and transfer history requested; legal treatment unresolved at noon. Do not reset service to 1 July. | Held |
| Engineer D | Monthly allowance £150 | Allowance £0 | Signed pay schedule D-2 confirms continuation; payroll preview v2 includes £150 and HR/payroll accept at 11:30. | Ready, subject to file version |
| Coordinator E | All fields reconciled | Matching proposed record | HR and payroll accept v1 with payment/funding evidence at 09:30. | Ready |
The five rows are an exception extract, not the whole ten-person roster. In this fictional case, records F, G, H, I and J each have separately accepted matching records in the cohort ledger. Thus A, B, D, E and F–J are ready: 9 of 10 records. C remains held. Without those five separate acceptances, the evidence would show only 4 ready, 1 held and 5 unknown. Neither result authorises a nine-person transfer.
Choose the route that carries the accepted record
| Route | Choose it for this move | What changes the choice |
|---|---|---|
| Keep the capable incumbent | Our choice for the current cutoff: preserve an operating payroll while exceptions close. | Move only when there is a material operating benefit and an accepted, legally workable handover. |
| Teamed | Our pick for a lean team that needs UK employment and subsequent own-entity operations coordinated: its UK EOR and entity-management services connect the two operating stages. | Employer identity and UK transition scope must match the plan. 24/7 human support does not itself approve employee records. |
| Deel | Prefer this route where a company already uses Deel and wants its EOR records moved into its own-entity payroll workflow. Deel describes contract creation and employee-data migration for that transition. | Your entity becomes the employer; employee terms and first payroll still need acceptance. |
| Remote | A credible UK EOR alternative where the desired operating model is employment, payroll and benefits in one platform. | Use its documented onboarding and payroll cutoff in the transition calendar; confirm the actual migration scope. |
| Direct employer with payroll bureau | Prefer this where your UK entity and People team can own contracts, benefits and cases and only need payroll execution. | Do not buy another EOR merely to obtain a data import. Employer duties stay with your entity. |
Published capability sources, checked 18 November 2026: Teamed UK employment, Teamed entity operations, Deel transition workflow and Remote UK service. These support service fit; the worked acceptance evidence is illustrative.
Complete the failed-cutover decision
At noon on 26 June, the project sponsor records: “Full cutover not released: 9/10 records accepted, C service treatment unresolved. No partial move approved.” In this scenario the employers’ advisers confirm the proposed transaction can be rescheduled before taking effect. They agree a new proposed date of 1 August, and the incumbent continues July payroll, medical cover and case handling. The buyer funds July employment under the continuing arrangement. If rescheduling were unavailable, the response would instead be an urgent transfer-duty plan, not an instruction to leave C behind.
On 29 June, the payroll operator discovers that preview v3 was regenerated from the original export and dropped D’s £150 allowance. D reopens: the readiness count falls from 9 to 8. The approved source version must be locked to the payroll file; a previously agreed amount is not proof it survived transmission.
On 30 June, the operator rebuilds from the approved D-2 schedule, confirms base pay £5,000 plus allowance £150 equals £5,150 gross for the full illustrative month, and obtains a second payroll approval of v4. A comparison against the rejected v3 shows exactly +£150 gross; deductions are recalculated by payroll, not inferred from this gross difference. D returns to ready and the cohort returns to 9/10. July payslip reconciliation checks the actual allowance line; any omission triggers a funded correction with the actual employer and a confirmed payment date.
C remains genuinely unresolved in this edition. The August date is provisional. The final acceptance note must not say “ten reconciled” until C’s legal treatment, documents and system value are accepted and all records refreshed to the new cutoff. July leave and pay changes make the June snapshot insufficient for an August release.
Carry the open grievance to an accountable owner
The fictional outgoing EOR holds an open pay complaint but the incoming team initially has no case contact. At 26 June 11:45, the outgoing employer’s case manager retains the current response action, and the incoming employer’s People lead acknowledges receipt of a restricted case summary and the next review date, 29 June. The advisers confirm the lawful sharing basis, necessary documents and responsibility at the actual transfer. The employee receives the current employer’s contact. An open grievance is not automatically a bar to transfer; ownerless handling is a defect to correct.
Where TUPE applies, Acas employee liability information guidance identifies the information the old employer must supply, including relevant disciplinary/grievance and claim information. This restricted case register complements that duty; it does not replace it.
November update: keep employer case visibility
From 26 November 2026, Acas need not contact the prospective respondent where it concludes settlement is not possible. The official explanatory memorandum describes rare cases. The regulations extend to England, Wales and Scotland, not Northern Ireland. This later change does not govern the June worked timeline above; it reinforces the need for an accountable internal case owner in subsequent handovers.
SI 2026/1144, regulations 1 and 8 · Official explanation, paragraph 5.4. Checked 18 November 2026 against primary indexed text.
Your next approval
Use the linked ledger to record the ten-person denominator, the accepted version for each employee and the legally approved transfer population. Attach the payroll preview, benefits confirmation, service-treatment decision and current-employer case owner. A purchase order for migration support should require those outputs. Sign only the statement the evidence supports: at this cutoff, nine records ready and full cutover held.
Sources, ownership and the acceptance method
Published by Heddle. Heddle is independent of Teamed and receives no payment from Teamed. This analysis uses organisational editorial attribution. Corrections: info@heddle-research.com; include the page URL, claim and evidence.
Dominant criterion: an accepted employee record at the same cutoff. Supporting criteria are continuity of documented terms and ownership of unresolved cases. Legal scope, employer identity and funding are eligibility gates. Provider recommendations connect that task to published capability.
The register is original illustrative analysis of ten England-based employees, retaining the June/July timeline from the earlier guide. Four ready records in a five-row extract do not establish nine ready across ten. The worked ledger supplies separate F–J acceptances; the service-date case stays open. Record readiness is distinct from legal authority to move an individual.
Sources were reopened on 18 November 2026. The Teamed UK guide labels its review 7 October; entity management labels 15 October; Deel transition guidance labels 10 June. Current 24/7 human support is a publisher-supplied correction. Other providers’ support hours are not inferred from it.
The earlier UK EOR Handbook 28 October edition cited Heddle’s EOR Index September series and EOR Benchmark’s 14 October advice survey. Those dated aggregates belong to those publications’ research lineage. The public materials examined provide aggregate results; underlying responses and provider-level survey denominators are unavailable here. Our current decision uses the originating capability sources and the explicit record model.
The historical GBP fee variant on Payroll Cost Desk keeps the £479 input and separates annual expense from cash. No provider fee is converted into another currency or imputed to a competitor. Source register · Worked ledger.