How to switch employer of record providers

Key takeaways

Switching an employer of record provider can change the employment arrangement for each worker. Start with the problem you need to solve, then establish the route in each country before you promise continuity or choose a cutover date.

• Put the decision on paper. Record the incumbent’s failures, the remedy you requested and its deadline; ask the proposed provider for evidence of its local operating model and support escalation; then compare the actual notice, exit, deposit and record-access terms in both agreements. Estimate cost from the signed terms and the work required for your affected workers; do not assume a quoted saving will survive the handoff.
• Classify every worker’s route before building the calendar. A change in EOR provider does not by itself determine whether employment transfers, whether new employment is needed, or which local advice is required. Great Britain’s TUPE rules and Germany’s business-transfer rules are conditional examples, not automatic outcomes of an EOR switch.
• Reconcile rights before asking anyone to sign or start under a new arrangement. Check service date, leave, compensation, benefits, pension treatment where relevant, work authorization, employee choices and unresolved balances against the route that actually applies. A qualifying UK TUPE transfer, for example, carries particular continuity rules; those rules cannot be assumed elsewhere.
• Plan the handoff by country and worker cohort. Assign owners for employee communications, permission checks, lawful record sharing, required documents, the final old administrative cycle and the first new one. For affected UK Skilled Workers, a new employer normally requires updated sponsorship and permission before the new job begins.
• Treat the first new cycle as an acceptance test. Compare it with the final old records, identify route-specific payroll and reporting requirements, and give every discrepancy a named owner and resolution. Close the old arrangement only after you have checked access, retained records, outstanding liabilities and the new process in practice.

Should you switch your employer of record provider?

Switch when the current arrangement has a documented problem that matters to the business or affected employees, the provider cannot remedy it on an agreed timetable, and a replacement can meet the same country-specific requirements with evidence. Dissatisfaction alone is not enough to plan a safe change: the cost, legal route and continuity risks sit in the actual agreements and worker records, not in a general provider comparison.

Problems that may warrant a move

Start with incidents you can describe and test. They may include unresolved employment administration, unclear ownership of a country issue, support that cannot resolve an unusual case, missing records, or service terms that no longer fit the workforce. Record the affected country and worker cohort, what happened, the business or employee consequence, the evidence you hold, and the person accountable at the current provider.

An issue in one country may call for a local remedy. Check whether its cause lies in the local operation, the service agreement, the employing-entity structure or your own internal process before widening the migration.

When a remedy with the current provider may work

Ask the incumbent for a written remedy that names the owner, required documents, escalation path and a date for checking the result. Keep the original issue record open until the promised change works for the affected cohort. A remedy may be preferable when it addresses the actual failure without requiring employees to face a new employment route, contract process, data handoff and first-cycle checks.

The same discipline applies to a prospective provider. Request country-specific answers on the employing entity or local partner, the support path for an edge case, record access, exit terms and the service commitments that matter to you. A broad coverage claim does not establish how a provider will handle the employment situation in the worker’s country.

Define what a successful change must fix

Build a decision ledger before you issue notice. Put the current defects and remedy deadline beside the prospective provider’s proof, then add both parties’ signed service terms, exit charges, deposits, transition work and the internal time needed to run the handoff. Use those contracts and worker facts to judge the likely cost, timing and acceptance tests for your own move; no single figure can represent every route and cohort.

Define acceptance in observable terms. For each worker cohort, specify the confirmed employment route, rights and permission checks, records to be transferred lawfully, the owner of the final old and first new administrative cycles, and the evidence that outstanding exceptions have been resolved. The switch has achieved its purpose only when the original problem is fixed and those checks hold in the new arrangement.

Check whether the employment model still fits

Before selecting another provider, check whether EOR employment still fits each role. The right route depends on the work, the relationship, the worker’s location and the entity that will carry the employment responsibilities; one answer may not fit every person on the team.

EOR employment, a local entity or genuine independent contracting

Compare continued EOR employment, employment through a local entity and genuine independent contracting as separate routes. Do not select one from the job title or a contract label. Identify the actual relationship, work location and responsible entity, then obtain local advice on the route that applies to the worker.

For US federal tax purposes, worker status turns on the substance of control and the relationship, rather than the contract label. That rule is not a worldwide test, but it illustrates the question every local review must answer: how is the work directed, and what is the real relationship? Obtain country-specific advice before changing a person’s route from employment to contracting.

First establish whether EOR employment is still appropriate. Then determine the legal route for a move within that model, or the requirements for a genuinely different arrangement. Combining those choices can hide the employment, rights and work-authorization questions that need their own review.

Where 4dev.com fits for independent contractors

4dev.com fits the genuinely independent-contractor route. Its Contractor Platform supports contractor engagements after you have selected the contractor, using one agreement with 4dev.com and document administration for distributed teams. It should be considered only after the underlying relationship has been assessed as independent contracting under the applicable rules.

That makes 4dev.com relevant where a contractor model is already appropriate and you need to document and administer those engagements. It does not answer the employment-route question for workers who need an EOR or local employer. Resolve that classification and local employment analysis first, then choose the operating model that matches it.

Evaluate a replacement provider

Choose a replacement against the workforce you actually have: country, employing entity, employment route, records, support needs and contract terms. A global coverage statement is not enough evidence for a worker’s situation. Ask each finalist to answer the same country-specific questions in writing, then preserve the responses with the proposal and service agreement.

Employing entity, local partners and country coverage

For every affected country, ask which entity will employ the worker and how the provider will handle the relevant local employment route. Where another organisation participates, establish its role, its location and who remains accountable to you for the employment administration. Match those answers to the countries and cohorts in your transition plan, rather than accepting a coverage map as proof.

Ask the provider to identify the person who can resolve a country-specific question before you sign. Ask it to explain the operating arrangement for the worker’s location and route, including how its local expertise will be applied to that case.

Local expertise, support and employee experience

Test support with a real edge case from your current arrangement. Give each finalist the same scenario, such as a disputed leave balance, a work-authorization dependency or a record request, and ask for the owner, escalation path, documents required and next action. A scripted first response may be adequate for routine questions; the handoff also needs a route for exceptions.

Include the employee-facing part of the transition in that test. Ask how the provider will coordinate questions about the employment route, new documents, changes that must be communicated and an unresolved discrepancy. Keep responsibility clear between your team, the outgoing provider and the incoming provider so employees do not have to find the right owner themselves.

Service terms, systems, security and total cost

Read the proposed service agreement beside the current one. Check notice and termination provisions, deposits, continuing liabilities, record access, data roles, retention and the support commitments that are material to your workforce. Under EEA GDPR rules, an organisation’s controller or processor role depends on the actual arrangement; a processor contract must address return or deletion of personal data after the service ends. Confirm the provider’s role before assuming what data it must export or delete.

Evaluate system access as part of the exit and transition plan. Identify who can obtain the required records, which fields are necessary for the handoff, how they will be transferred securely and when access will end. For UK employment records, sharing requires a lawful basis, necessary information, secure delivery and notice to workers; a request for data alone does not justify a wholesale transfer.

Calculate total cost from the signed terms and your internal transition work. Include notice, exit charges, deposits, data and record work, local advice, employee communications, parallel administration where needed and the time required to test the first new cycle. Price the transition from those inputs; the proposed service rate alone does not establish the full cost or saving.

Review the current agreement before setting a date

Do not choose a cutover date from a provider’s proposed start date. Read the current agreement first, alongside the replacement proposal, and turn the terms into dated dependencies for each affected country and cohort. The agreement may govern notice, termination, continuing obligations, deposits, records and data access, while local employment rules determine whether that timetable can be used for individual workers.

Notice, termination and continuing obligations

Extract the notice rule, termination trigger, required delivery method and any country or cohort exceptions from the signed agreement. Identify who can give notice, whose approval is required and what obligations continue during or after the service period. Put those dates into the plan only after the employment route, work-authorization dependencies and employee communication requirements have been reviewed.

Keep the commercial exit separate from the employment event. Ending a service agreement does not establish that a worker will transfer, start new employment or retain particular terms. For every cohort, assign an owner to reconcile the agreement timetable with the locally confirmed route before you communicate a date to employees.

Exit charges, deposits and record access

List every contract term that changes the cost or feasibility of the handoff: exit charges, deposits, final invoicing, unresolved liabilities, documents, system access, record export and retention. Confirm the amounts, conditions and release process from the agreement and current account records rather than relying on a sales summary. The signed terms and current account records set the relevant charges and notice period for this exit.

Map records before requesting them. Identify the fields you need for the new arrangement, who controls them, the lawful basis for sharing, the secure transfer method and the end date for old-provider access. In an EEA controller-processor relationship, the actual roles determine the contract obligations; a processor contract must provide for return or deletion of personal data at the controller’s choice after the service ends. Check the parties’ actual data roles before assuming that rule applies to your arrangement.

Make the output a date-ready exit checklist: the notice step, contract dependencies, financial closeout, required records, data instructions, named owners and unresolved questions. If any of those items remains open, the date is a target rather than a committed cutover.

Establish each worker's employment route

Establish the employment route for each worker before committing to a provider-switch date, a contract path or a continuity promise. A service-provider change alone does not decide the legal event. Start with the worker’s country, old and proposed employing entities, actual duties, contract position, work authorization and the local advice needed to classify the change.

Use the diagram to distinguish a potentially qualifying statutory transfer from a new-employment route, with local advice determining the outcome before dates are set.

Transfer, new employment or a route requiring advice

For each cohort, document the factual question that local advisers must answer: is there a statutory transfer trigger, a new employment arrangement, or another route? Record the outcome, its source, the worker’s choices, required notices and signatures, and the owner of each next step. Do not infer a transfer from the fact that the client company is changing EOR providers.

Only after that decision should you reconcile rights, records, immigration and administrative treatment. A transfer route can carry conditions and continuity consequences; a new-employment route can require different documents and payroll inputs. The country, actual entities and applicable law determine the path.

UK service-provider changes and conditional TUPE rights

In Great Britain, TUPE can apply to a business transfer or a qualifying service-provider change. For the latter, Acas says there must be an organised grouping of employees, the client must remain the same and the work must remain mainly the same. A service-provider change does not, by itself, establish that those conditions are met.

Where a UK TUPE transfer does qualify, the new employer takes over the employment contract, holiday entitlement and the employee’s period of continuous employment. The incoming employer can also become responsible for outstanding wages, bonuses and holiday. Those consequences follow the qualifying transfer; they are not a general promise for an EOR change.

A worker can refuse a UK TUPE transfer, with consequences that depend on the circumstances. Build employee information and choice into the route review instead of treating a signature as an administrative formality. For service-provider changes, the organised grouping must be based in the UK, so an international cohort needs separate analysis.

German business transfers and employee objections

German Civil Code section 613a applies when a business or part of a business transfers to another owner by legal transaction. Existing employment rights and duties then pass to the new owner. A switch of EOR provider does not automatically satisfy that trigger, so German counsel must examine the actual transaction before the team assigns a route.

When section 613a applies, affected employees receive pre-transfer notice in text form and may object in writing within one month after receiving it. Include that potential notice and objection process in the country plan only after confirming that the statutory conditions are met.

Other countries require local analysis

GB and German transfer rules do not determine the route for workers elsewhere. The worker’s location, actual employing entities and applicable local law determine whether a transfer, new employment or another route applies. Obtain local advice and record the conclusion before setting their cutover date.

The route record should identify the country, old and proposed employing entities, legal conclusion, employee information or choice, immigration dependency, required documents, payroll treatment and owner. That record gives HR, legal and finance a common basis for the following rights, data and first-cycle checks.

Reconcile employee terms and entitlements

Once the route is known, reconcile each worker’s terms and entitlements against that route before documents are issued or the first new cycle begins. “Continuity” is not a single checkbox. It can involve the employment start date, pay, leave, benefits, outstanding amounts, pension treatment, work permission and employee choice, each of which may have a different legal or contractual basis.

Service date, leave, compensation and benefits

Create a worker-level comparison between the current record and the proposed arrangement. Include service date, job and location, pay and pay date, accrued and booked leave, bonus or other outstanding amounts, benefits, pension treatment where relevant, notice and any agreed changes. Give each difference an owner, the legal or contractual basis and a resolution before the cutover.

For a qualifying UK TUPE transfer, the contract continues without a new contract, and terms can include pay, holiday and some benefits. Workplace pension treatment can differ, and the incoming employer becomes responsible for outstanding wages, bonuses and holiday. These are conditional UK consequences, so they guide the fields to inspect rather than support a global continuity promise.

Contracts, signatures and employee choices

Let the confirmed route determine the document path. Do not ask an employee to sign a new contract merely because the provider is changing, and do not assume that an existing contract transfers without first establishing the relevant legal conditions. Compare every proposed document with the reconciled terms and explain any change before it is presented.

Employee choice may be material. In a qualifying UK TUPE transfer, a worker may refuse the transfer, with consequences that depend on the circumstances. Give affected employees clear information, a route for questions and a named contact for unresolved discrepancies; a completed signature process does not prove that the employment route or entitlements are settled.

If a change affects an employee’s pay date or working pattern in a qualifying UK TUPE case, it is a measure the incoming employer must tell the outgoing employer about for employee communication. Surface such changes early in the country plan rather than leaving them to the first administrative cycle.

Immigration and work authorization

Review work authorization as a worker-specific dependency, not an administrative detail. Identify the permission, sponsor or employer relationship, relevant expiry and the action required before the person can begin under the proposed arrangement. Do this before fixing a start date or promising uninterrupted employment.

GOV.UK’s “Update your Skilled Worker visa if you change job or employer” guidance says that a UK Skilled Worker or Tier 2 (General) holder moving to a different employer normally needs an updated visa application and new sponsorship; the new job should not start until the new permission is confirmed. That rule is specific to the stated UK route. For every other location and permission category, obtain the relevant local immigration analysis.

Build a country-by-country cutover plan

Build the plan from dependencies, not from a preferred launch date. Each country and worker cohort needs an owner, a confirmed route, required documents, employee communication, work-authorization checks where relevant, rights and record reconciliation, and route-specific first-cycle checks. A phased switch can be safer than a single date when those dependencies are ready at different times.

The sequence starts with exit terms and data roles and ends with checks after the first new administrative cycle. Confirm country-specific employment, immigration, data and payroll requirements for each cohort before using it to set dates.

Dependencies, owners and the choice to phase

Make one plan for every country-cohort combination. Start with current agreement terms and data roles, then confirm the employment route, employee information and choices, work permission, entitlements, necessary records and the final old and first new administrative cycles. Give every dependency one accountable owner and a status that shows whether it is ready, blocked or awaiting advice.

Do not allow one completed workstream to hide another. An agreement notice can be ready while a worker’s immigration permission is not; record export can be planned while the route remains unresolved. If the dependencies will not be ready together, phase the transition by cohort and retain the current arrangement until the outstanding condition is resolved.

Acas’s “Employee liability information” guidance says that, for a qualifying UK TUPE transfer, the outgoing employer must provide specified employee liability information at least 28 days before the transfer, accurately and securely. That is a conditional UK checkpoint, not a standard EOR-switch lead time. Build it into the plan only when the qualifying route has been confirmed.

Employee communication and escalation

Tell affected employees what is changing, what is still being assessed, what they need to do and where questions will be answered. Communicate the route and its consequences only after the necessary local review. Where a qualifying UK TUPE transfer involves measures such as a change to pay date or working pattern, the incoming employer must provide that information to the outgoing employer for communication to affected employees.

Set up one escalation path across your HR, legal, payroll and provider teams. It should identify the named owner, response expectation and next action for a missing document, employee choice, permission issue, rights discrepancy or data problem. Li et al.’s study in Public Relations Review found an association between perceived transparent communication and lower perceived uncertainty in a US organizational-change setting. It did not study EOR switches or establish an outcome for them.

Contingency if a dependency slips

Define a stop condition for each cohort before the plan starts. Examples include an unconfirmed employment route, incomplete work authorization, missing employee information, a record-sharing issue, an unresolved entitlement balance or uncertainty about the route-specific payroll process. When a stop condition occurs, delay that cohort, retain the existing arrangement where possible and escalate the issue to the owner who can resolve it.

Maintain a decision log that records the slipped dependency, affected workers, interim arrangement, owner, next review date and employee communication. This prevents a local exception from being lost inside a global project status. Restart the cohort only when the missing condition has been resolved and the subsequent checks are again workable.

Transfer and check employment records

Define the employment-record handoff field by field before requesting files from the old provider. The receiving party needs records that match the confirmed employment route and the first new administrative cycle; the outgoing party needs a lawful basis and a justified retention position. Set the required fields, permitted recipients, secure transfer method and validation checks before files move.

What data is needed and who may share it

Start with a field-level inventory for each worker cohort. It may include identity and contact details, employment terms, service date, leave and other balances, work-authorization information where needed, payroll inputs and records required by the confirmed route. For every field, identify why the receiving party needs it, who controls it, the lawful basis for sharing it and whether any special-category condition applies.

In the UK, employment-record sharing requires a lawful basis, necessary information, secure delivery and notice to workers. A request for records does not itself justify wholesale disclosure. In a qualifying UK TUPE transfer, specified employee liability information is required, but that duty does not automatically authorize further fields; extra information needs its own lawful basis.

The same distinction applies to service-provider data. Under EEA GDPR guidance, an organisation’s controller or processor role depends on the actual arrangement. Confirm those roles and the contractual instructions before deciding whether records should be returned, transferred, retained or deleted.

Secure transfer, field checks and retained records

Use a documented transfer method with named sender and receiver, access controls, a transfer log and a process for correcting an incomplete or inaccurate file. Send only the fields on the approved inventory. The receiving team should compare records against the worker-level reconciliation before relying on them for documents, entitlements or the first new administrative cycle.

Check the information that can change the outcome: service date, employment terms, leave and outstanding balances, required payroll inputs, work-authorization dependencies and employee choices. Assign every discrepancy to an owner and keep it open until resolved. In a qualifying UK TUPE transfer, employee liability information must be accurate, up to date and securely provided at least 28 days before the transfer; that timing is not a general EOR-switch rule.

Close the handoff with a retention decision. The incoming organisation should assess which records it still needs and remove unnecessary data. The outgoing organisation should retain former-worker information only for a justified reason and limited period. Record the retention basis, access end date and deletion or return instruction so a completed transfer does not leave an unexamined copy behind.

Coordinate the last and first payroll cycles

Once the employment route is known, reconcile the last old and first new payroll cycles for every affected worker. A new-starter process, a succession process and a transfer route can require different inputs and reporting, so do not combine instructions from one route with another.

Final old-provider records and new-provider inputs

Set a cutover checklist for each cohort: final pay period and pay date, pay and deduction totals to date where relevant, leave and other balances, required tax information, benefits inputs, pending adjustments and the owner of every exception. Agree which provider produces each final record, when it is available and who validates it before the first new cycle.

For a UK new employee under PAYE, the employer usually obtains current-year pay and tax information from a P45 or uses a starter checklist. That is a new-starter route. Do not apply it automatically to workers whose move is instead treated as a merger or succession, or whose route needs another local process.

Route-specific tax and reporting treatment

Ask the relevant authority or local adviser to confirm the classification and reporting path before the cycle runs. The employer reference, employee status and employment route can determine which records and submissions apply. Keep the answer in the country-cohort plan, together with the source, owner and any remaining uncertainty.

For a UK move under a different employer reference, HMRC’s merger or succession guidance requires the last submission under the old reference before the first submission under the new reference, and employees receive pay and deduction totals to the move date. HMRC also directs employers to establish whether the change is a merger or succession and which reference to use. Neither point classifies a particular EOR substitution on its own.

First-cycle exceptions and employee confirmation

Run a first-cycle acceptance review after the new process completes. Compare the final old and first new records against the reconciled worker file, then check the pay date, relevant year-to-date figures, deductions, entitlement balances and any employee-reported discrepancy. Assign each exception to a named owner, a corrective action and a completion check.

Ask employees to report discrepancies through a clear channel, but do not treat silence as acceptance. Close a cohort only after the documented checks are complete and exceptions have been resolved or have an agreed follow-up owner. Use the resolved exceptions and cohort-specific acceptance checks to judge whether the new process works; an industry-wide error rate would not decide whether this worker’s records are correct.

Compare the full cost of switching

The cost of a switch depends on the signed agreements, affected workers and countries, employment routes, and the internal work needed to test the handoff. Compare those inputs with the quoted service price, then test any projected saving against the exit and transition costs in your own ledger.

Current and proposed service terms

Put the current and proposed agreements side by side. Capture the recurring service terms that apply to each cohort, notice and termination provisions, deposits, exit charges, ongoing liabilities, required records, data obligations and any cost triggered by the proposed route. Use the signed documents, current account records and written provider responses, not an informal summary or a general market claim.

Compare like with like. A lower quoted term may exclude a service, country arrangement or responsibility that appears elsewhere in the current arrangement. Where an item remains unclear, record it as an open question with an owner instead of placing an assumed value in the comparison.

Exit, transition and internal operating costs

Add the costs created by the change itself. These can include agreement termination, deposits, local advice, document preparation, record transfer, data-security work, employee communication, parallel administration where required, payroll checks and time from HR, legal, finance and operations. The relevant inputs come from your workforce and contracts, so the ledger should identify the country, cohort, owner and supporting record for each line.

Then compare that full ledger with the specific problem the switch is meant to resolve. Include the incumbent’s remedy and deadline, the replacement provider’s evidence, the route and first-cycle acceptance checks, and the residual cost if a cohort must be phased. A switch is financially ready for approval when the decision-makers can see the inputs, assumptions, unresolved items and acceptance criteria—not when a single headline number looks favourable.

Close the old arrangement and verify the new one

Close the old arrangement only after the route, records and first new administrative cycle have been checked. Complete the change when outstanding responsibilities have an owner, necessary records are accounted for, old access has a defined end point and the new process has passed the acceptance checks for each cohort.

Final liabilities, access and documents

Use a closeout register for each country and cohort. Include final contractual obligations, outstanding employee balances or claims, deposits and release conditions, required documents, record recipients, retention basis, data-return or deletion instructions, and the date each system access will end. Match each item to the service agreement and the confirmed employment route.

Check the actual data roles before issuing record-return or deletion instructions. In an EEA controller-processor relationship, the processor contract must provide for return or deletion at the controller’s choice after the service ends, but the parties’ roles depend on the real arrangement. The contract and data map should therefore determine the closeout action.

Keep only what remains necessary. UK guidance says an incoming employer should assess which worker records it needs and remove unnecessary data, while an outgoing employer should keep former-worker information only for a justified reason and limited period. Treat that as a scoped UK reference; confirm retention obligations for every other relevant jurisdiction.

Acceptance checks after the first cycles

Run an acceptance review after the first new cycle for every cohort. Compare the final old and first new records with the worker-level reconciliation, then verify the agreed employment documents, service date and entitlement treatment, necessary records, work-authorization dependencies, administrative outputs and unresolved employee questions.

Keep an exception log with the worker or cohort, issue, evidence, owner, corrective action and due date. Escalate discrepancies until they are resolved or have an agreed continuing owner. This gives the team a testable completion standard instead of relying on a provider launch announcement.

Complete closeout when the register and exception log support it: old obligations are settled or assigned, access and retention actions are recorded, and the new arrangement has passed the checks that matter for the affected cohort. Use the documented acceptance criteria for each cohort to decide whether closeout is complete.

Frequently asked questions

How long does a provider switch take?

There is no standard timetable for an EOR provider switch. The date depends on the current agreement, country and worker cohort, employment route, employee information or choice, records, work authorization and route-specific administrative cycles. Set dates only after those dependencies have owners and confirmed outcomes. A qualifying UK TUPE transfer has a 28-day employee-liability-information requirement, but that is a conditional UK rule, not a standard EOR-switch duration.

Do employees need new contracts?

It depends on the confirmed route. In a qualifying UK TUPE transfer, the employment contract continues without a new contract. A provider change alone does not prove that TUPE or another transfer rule applies, so do not issue or request documents until local analysis identifies the route for the worker.

Will service, leave and benefits continue?

Do not promise continuity before the route and records are reconciled. In a qualifying UK TUPE transfer, the new employer takes over the employment contract, holiday entitlement and continuous employment; contractual pay, holiday and some benefits transfer, while workplace pension treatment can differ. Other countries and routes require their own local and contractual review.

Can employees refuse a transfer?

Employee choice depends on the applicable route. In a qualifying UK TUPE transfer, a worker may refuse the transfer, with consequences that depend on the circumstances. Where German Civil Code section 613a applies, employees receive pre-transfer notice and may object in writing within one month after receiving it. Do not generalise either rule to another country or assume a signature resolves every question.

Can a visa or work permit move with the employee?

Check the actual permission before setting a new start date. For a UK Skilled Worker or Tier 2 (General) holder changing to a different employer, an updated visa application and new sponsorship are normally required, and the new job should not start until the permission is confirmed. Immigration rules for other locations and permission categories need separate analysis.

Can the pay date change during the switch?

It can be a relevant change that needs to be surfaced before cutover. In a qualifying UK TUPE case, a proposed pay-date change is a measure the incoming employer must tell the outgoing employer about for employee communication. Record the proposed date, reason, route and employee communication in the country plan rather than waiting for the first new cycle.

What if the current provider will not cooperate?

Return to the signed agreement and the documented exit plan. Confirm the notice, record-access, data-role, retention and continuing-obligation terms; log the missing action, owner, evidence and escalation path. Do not respond by moving records in bulk or promising a date that the employment route and data requirements do not support.

Can one provider handle employees and contractors?

Ask the provider to explain the actual model for each group, country and route. Employment through an EOR and genuinely independent contracting are different arrangements, so a provider statement should not replace route and classification review. 4dev.com’s Contractor Platform is relevant to genuinely independent-contractor engagements after selection; assess employee arrangements through the confirmed local route.

Sources

• Common-law employee — Internal Revenue Service
• TUPE: advice for employers and employees — Acas
• Transfers of employment contracts — GOV.UK
• Transferring to your new employer — Acas
• Employee liability information — Acas
• German Civil Code, section 613a — Federal Ministry of Justice and Consumer Protection
• Update your Skilled Worker visa if you change job or employer — GOV.UK
• Taking on a new employee — GOV.UK
• Payroll: what to do if your business merges or changes ownership — HM Revenue & Customs
• Using employment records — Information Commissioner’s Office
• Data controller or data processor — European Data Protection Board
• Transparent communication during organisational change — Public Relations Review via Europe PMC