Briefing: What Actually Changes When an EOR Arrangement Converts to a Direct Entity

"Seamless" conversion from an employer-of-record arrangement to direct employment describes the employee's experience, not the underlying mechanics. Behind it sits a defined sequence: new employment contracts under the receiving entity, continuity provisions covering tenure and accrued benefits, and a coordinated cutover of payroll, social insurance, and housing fund registrations so no contribution cycle is missed in the handover.

Why employers reach for conversion in the first place

An employer-of-record arrangement is usually chosen for a specific reason: headcount is needed before an entity exists, or before an existing entity's own registrations are ready to support direct employment. Conversion becomes relevant once that gap closes — the entity is formed, or its registrations catch up — and the employer wants the commercial and reporting relationship to run through its own structure rather than through an intermediary. The decision to convert is usually straightforward; the sequencing of how it actually happens is where most of the practical risk sits.

What has to happen on the contract side

Converting an employee is not a transfer in the legal sense — it is the termination of one employment relationship and the commencement of another, structured so that the employee experiences no gap and loses no accrued entitlement in between. This means a new employment contract under the receiving entity, drafted with explicit continuity provisions covering tenure (so length of service is not reset to zero for entitlements that depend on it) and any accrued but unused leave or benefits carried over from the employer-of-record period. An employer that treats this as a simple contract swap, without addressing continuity explicitly, risks creating a dispute later about what the employee is actually entitled to and from which date.

Registration readiness is the real gating factor

The timing question that matters most in practice is registration readiness on the receiving entity's side — social insurance and housing fund accounts, in particular, need to be active before the first payroll cycle under direct employment, not arranged retroactively once conversion has already begun. An entity that sets a cutover date based on when it wants the conversion to happen, rather than on when its own registrations are actually confirmed active, risks a payroll cycle where contributions cannot be correctly processed under either the old arrangement or the new one — precisely the gap the conversion was supposed to avoid creating.

Sequencing the cutover to avoid a missed contribution cycle

• Confirm the receiving entity's social insurance and housing fund registrations are fully active, not merely submitted, before setting a cutover date.
• Draft the new employment contract with explicit continuity provisions for tenure and any accrued, unused entitlements.
• Align the final employer-of-record payroll cycle and the first direct-employment payroll cycle so no contribution period falls between the two, unaccounted for.
• Notify the employee of the practical changes — new employer of record for tax and social insurance purposes — clearly enough that year-end filings are not confusing to them later.
• Confirm the deregistration or wind-down of the employee's status under the employer-of-record arrangement is completed, not left open after cutover.

What tends to go wrong when this is rushed

The most common failure pattern is not a disputed contract term — it is a cutover date set against an internal target rather than against confirmed registration status, producing a payroll cycle where the receiving entity's accounts are not yet active and the employer-of-record's accounts have already been wound down for that employee. The resulting gap is not merely an administrative inconvenience; it can mean a missed statutory contribution that later has to be corrected retroactively, at real cost in both time and credibility with the relevant authorities.

Communicating the change without alarming the workforce

From the employee's side, a conversion that is executed correctly should be close to invisible — same role, same manager, same pay date — which is exactly what makes clear communication easy to skip. Skipping it is a mistake: an employee who receives a payslip from an unfamiliar entity name with no advance explanation, or who encounters a different employer name on their year-end tax documentation without warning, reasonably wonders whether something has gone wrong with their employment rather than understanding it as a planned administrative change. A short, plain explanation in advance — what is changing, what is not, and why — costs little and avoids a wave of individual questions arriving at once on the cutover date itself.

Treat conversion as a project, not a form to be filed

Employers converting more than one employee at the same time benefit from treating the exercise as a coordinated project with a single owner, rather than a series of individual conversions run in parallel by whoever happens to be handling each employee's file. A single point of accountability for confirming registration readiness, sequencing contracts, and verifying the cutover across every employee involved is what prevents one employee's conversion from proceeding cleanly while another's stalls on a registration nobody checked.

This is a general description of a common conversion pattern, not a substitute for a conversion plan built around a specific entity's registration status and headcount. Timing should be confirmed against the receiving entity's actual registration readiness before a cutover date is set.