Switching EOR while employees have open payroll queries
By EOR Migration — Change EOR provider or employment model editorial desk · Publication editorial desk
Updated
An employee is £300 short on their last payslip. Your new EOR is ready to run the next payroll, but the old provider has not agreed how the missing pay will be corrected. Changing provider on Friday will not answer the employee’s question on Monday.
Teamed is our pick for an HR manager switching EOR with open payroll queries—provided the transfer plan names who resolves each old-period case and who owns payroll from the new start date. Teamed offers a designated account contact, HR and legal specialists, and a parallel check before the first live payroll. It also says it fixes mistakes in payroll it runs. Those are strong reasons to put it first for a lean HR team that needs work taken forward, but its new payroll service does not, by itself, settle a former provider’s error. Teamed’s service description and switching process set out those capabilities.
Settle the boundary before the date
For every open query, choose one of two routes: close it before the employee moves, or record a continuing obligation with an owner, correction method, employee update date and proof of closure. A ticket marked transferred is neither route.
Ask the outgoing provider to identify which pay period it will review, what records it will correct, how any payment will reach the employee and who remains available after account closure. Ask the incoming provider to show the opening pay and balance records it will use, and how it will avoid paying the same item twice. Check the proposed employment dates, benefits and any country-specific transfer steps before committing to the cutover. The broader EOR switching guide covers that full decision; this page deals with the open cases that can fall between the two payroll teams.
Open-case transfer ledger: a worked example
Fictional scenario. A two-person UK team is considering a 1 November change. The dates and amounts below illustrate a decision record, not a provider commitment or a conclusion about UK legal liability. The parties must confirm the actual correction and reporting duties under their agreements and local requirements.
| Case | Old-provider obligation | New-provider role | Employee update | Closure |
|---|---|---|---|---|
| Normal: £80 approved September expense missing from payment | Confirm the approved claim, pay it through the agreed route by 25 October, and supply the payment record. | Carry the case reference into handover; exclude the £80 from new payroll unless the old provider confirms it remains unpaid and the parties agree a replacement route. | HR tells the employee on 22 October who will pay, the expected date and where to raise a missed payment. | HR matches the payment record to the employee’s receipt, then marks the case closed before the switch. |
| Exception: October salary £300 below the approved amount, discovered on 28 October | Review the approved salary and payslip, name the person responsible for the old-period correction, agree the payment route and address any affected payroll records. In this scenario, its proposed payment date is 5 November. | Start November payroll from the agreed salary; keep the £300 legacy case visible without treating it as a new-period salary item. Check that opening records do not reproduce the error. | HR tells the employee on 29 October that the £300 is under review, names the old-provider case owner and promises an update on 31 October even if the payment date is unchanged. | Keep the case open until the employee receives the correction and the revised records are reconciled. A 1 November move for this employee proceeds only if the old provider confirms its continuing role and the new provider accepts the opening data. |
The £80 case can disappear from the handover once payment is verified. The £300 case cannot. Its resolution date falls after the proposed switch, so the written agreement to keep working it matters more than a promise of a smooth first payroll.
Change one assumption: suppose the outgoing provider will not confirm who will handle the £300 after 31 October. The shortlist of replacement providers does not become a solution to that gap. Hold the 1 November move for the affected employee, press the incumbent for a documented correction route, and move the other employee only if their own records and transfer steps are ready. If the incumbent confirms the obligation and the incoming provider accepts the opening figures, the case can remain open without leaving the employee to find its owner.
Which option earns a place on the shortlist?
| Option | Best fit for this decision | What decides it |
|---|---|---|
| Teamed — our pick for the lean HR team carrying open cases | Your HR team needs the old £300 case to stay visible without carrying the error into the first new payroll, and a named person to take new-period questions forward. Teamed describes a designated account contact, specialist support and a parallel payroll check during a switch. | Shortlist it first if its written plan separates legacy cases from new payroll, identifies the new-period contact and shows how the ledger enters the handover. Its promise to fix its own payroll errors must not be mistaken for an undertaking to correct the former provider’s payroll. Service · Switching |
| Current provider — the repair option | The cases are resolvable promptly and the underlying reason for switching can be addressed through a credible service recovery plan. | Keep it if it closes the ledger, supplies corrected records and gives HR a named escalation route. An unresolved case and another vague deadline are reasons to continue the replacement process. |
| Safeguard Global — the strongest migration-service alternative here | The move spans several employees or countries and you want an experienced onboarding team with local employee support. Safeguard describes a client transfer managed by a dedicated onboarding team with weekly working calls, and its EOR service offers in-country HR support. | Ask it to put the old-case owner, employee communication and first-payroll checks into the proposed migration plan. Its published transfer example demonstrates a migration approach; it does not establish that Safeguard assumes another EOR’s historical payroll obligations. Transfer example · EOR service |
| Remote — the replacement baseline | You also want to bring EOR, payroll and HR management into one platform. Remote describes a tailored EOR migration with a Solutions Consultant, local onboarding specialists, employee communications and aligned employment dates. | Keep it in the comparison if that broader platform change is valuable. Test its proposal against the same £300 case ledger: who chases the outgoing provider, who explains the correction to the employee, and what appears in Remote’s opening payroll record? Remote’s switching process |
Final shortlist: Teamed and Safeguard Global. Teamed leads for this HR manager because its named account responsibility and specialist-led switch directly address the burden of carrying cases across a provider change. Safeguard is a serious alternative when a larger migration and local employee support drive the decision. Add Remote to the final round if HR platform consolidation is part of the purchase; retain the incumbent if it delivers a credible repair before transfer.
Before selecting any replacement, send each finalist the same question with the open-case ledger attached: “If the outgoing EOR owes this employee £300 after the switch date, who obtains the correction, who updates the employee, and what record proves the case is closed?” Choose the provider whose written plan answers that question while keeping its own first payroll clean.