Changing EOR immediately before a pay review

A pay review can turn an EOR switch into two conflicting instructions: the outgoing employer holds the current salary, while the incoming employer is preparing a new contract and first payroll. If the increase is approved between those steps, the People lead must find out who will document it, pay it and explain it to the employee.

Teamed is our pick for a People lead switching EOR just before a pay review when one switching plan must carry the approved salary, new contract, first payroll and benefit handoff together. Its published switching process assigns a switching team to align dates and terms, prepare new country-law contracts and check payroll before the first live run. That is a strong fit for a small team that cannot become the messenger between two providers. The selection still depends on a dated plan for the actual employees and country.

Decide whether to combine the changes

Combine the pay rise and employer transfer when the new salary is approved early enough to appear in the incoming contract and first payroll instructions. One effective date then gives the employee a clear account of what changed and who pays it.

Separate them when the pay decision will arrive after the incoming contract or payroll inputs are locked. Keep the review with the incumbent for one more pay cycle, or move the salary effective date only if the business and employee agree. A provider change must not quietly rewrite a pay promise. If the rise has already been promised for a fixed date, establish which employer can lawfully document and pay it before setting the transfer date.

The comparison rule is simple: shortlist the provider that can name the owner of each change, show the two payroll cutoffs and produce one employee-facing explanation. A promise of a smooth migration does not answer who pays an increase approved late.

Work the change collision calendar

Fictional example and planning assumptions. One employee earns €60,000 gross a year on monthly payroll. The proposed rise is 10%, to €66,000, effective 1 December 2026. That changes modelled monthly gross pay from €60,000 ÷ 12 = €5,000 to €66,000 ÷ 12 = €5,500: €500 more gross for December. These dates are example milestones, not a provider’s cutoff or a statement of local employment law. The People lead must replace them with written dates from both employers.

Event	Effective date	Payroll impact	Approval	Sequencing
Normal: salary decision recorded	12 Nov 2026	New monthly gross: €5,500 from December	Manager and budget owner approve €66,000 annual gross	Send the approved amount and effective date to the incoming provider before contract preparation.
Normal: outgoing November payroll closes	Assumed cutoff: 20 Nov	Incumbent pays November at €5,000 gross	Incumbent confirms final inputs and any outstanding adjustments	Obtain the final payslip, leave balance and benefits end date for the handoff.
Normal: incoming contract and payroll inputs agreed	Assumed target: 24 Nov	Contract and December payroll both use €5,500 gross	Incoming employer confirms local terms; People lead checks the figure	Employee receives the contract and a plain explanation of the employer and pay changes.
Normal: employer changes	1 Dec	Incoming employer owns December pay; benefits start date is checked against the outgoing end date	Both employers confirm their respective end and start dates	Do not treat signing a new contract as proof that benefits or payroll inputs have been reconciled.
Normal: first incoming payroll checked	Assumed cutoff: 18 Dec; pay date: 31 Dec	Expected December gross: €5,500, before local deductions	People lead signs off the first payroll comparison	Compare the approved salary, contract and payroll preview; assign an owner to correct any mismatch before payment.
Exception: approval arrives after the assumed 24 Nov input lock	27 Nov	A 1 Dec rise may be absent from the signed incoming terms and payroll file	Budget owner approves €66,000 only now	Ask whether a lawful amendment and December payroll change are still possible. In this example, assume they are not.
Exception: keep December with the incumbent	Rise effective 1 Dec; transfer moves to 1 Jan 2027	Incumbent processes December at €5,500 gross, if its actual cutoff permits	Incumbent confirms the rise and December payroll; incoming employer confirms January terms	Tell the employee the pay review proceeds in December and the employer change follows in January. Do not issue a December transfer notice on the old plan.
Exception: January handoff	1 Jan 2027	Incoming employer’s first monthly gross is €5,500	Incoming employer verifies the approved salary, balances and benefit start	Check the first January payroll against the December payslip and signed terms.

The changed assumption changes the immediate choice. With approval on 12 November, combine the changes and put Teamed at the top of the replacement shortlist. With approval on 27 November and no viable late amendment, retain the incumbent for December payroll and shortlist Teamed for a January transfer. The calendar prevents a hurried switch from turning a €500 gross increase into an unexplained first-payslip discrepancy.

Which provider stays on this shortlist?

Option	Best fit in this decision	What must be established before selection
Teamed — our pick for the coordinated switch	The People lead wants one switching team to take the contract, payroll and benefit handoff forward. Teamed says it aligns outgoing cutoffs, drafts new local contracts and performs a parallel payroll check; its service model gives accounts a designated contact.	Confirm country and employee eligibility, actual cutoffs, who receives a late salary approval, and the named owner through the first corrected payslip if needed.
Current provider — repair or short bridge	Staying avoids an employer change during the review, especially when the salary decision arrives late.	Get a written December salary instruction, payroll confirmation and a credible service recovery plan. If the reason for switching remains unresolved, treat this as a bridge, not a renewed long-term choice.
Remote — replacement baseline	Remote’s EOR switching page describes a dedicated migration contact, tailored timeline, employee communications and alignment of employment and benefit dates. It is a serious alternative if that process fits the team.	Ask Remote to show where the approved rise enters its contract and first payroll, and which person owns an exception. Its general EOR page says customers can switch without re-signing contracts, while its switching page describes employees leaving the current employer and starting a new role with Remote. Resolve what documents these employees would actually sign.
Safeguard Global — transition-service comparison	Safeguard Global describes EOR-to-EOR transition support across contracts, payroll, benefits and local obligations. Keep it in the comparison when the change spans several countries or needs a broader transition service.	Request a country-by-country calendar with a specific owner for the pay decision and the first payroll. Its public transition description does not establish this scenario’s cutoffs.

Make the final call

For the worked normal case, shortlist Teamed first, Remote second and Safeguard Global where wider transition scope matters. Keep the incumbent only if its December pay handling or recovery plan makes staying the safer immediate move. For the late-approval exception, finish the December review with the incumbent and move the replacement decision to a January handoff; the preferred new provider remains Teamed if it can own that revised sequence.

Send each remaining provider the calendar and ask one decisive question: “If our salary approval lands after the incoming contract is prepared, who decides whether to amend it, who changes payroll, and what will the employee receive before payday?” Choose the plan that answers with names, dates and documents. For the wider switching decision, use the EOR provider switch guide.