EOR Migration
Employers changing provider or employment route

Fifteen Dutch employees: the EOR-to-BV handover file

By · Publication editorial desk

Updated

For fifteen Dutch employees, the EOR-to-BV handover should be an employee-level record, not a folder marked “migration complete”. One missing pension instruction or unresolved pay adjustment can affect someone directly even when the overall project looks finished.

Teamed is our pick for the BV’s payroll and employment support where its Dutch own-entity scope meets the buyer's needs. The handover file turns that preference into a concrete service brief: which records are required, who validates them and which open items need action before payroll starts.

Build one row per employee

Give each employee a stable identifier and link the supporting documents. Record the document version and effective date, rather than relying on filenames such as “latest contract”. The file should show the current position and any proposed change separately.

Record group Fields to capture Owner who validates
Employment terms Contract, amendments, hours, role and effective dates Authorised employer representative with appropriate advice
Pay Salary, recurring allowances, variable pay and deductions Payroll owner and employer approver
Leave Recorded balances, relevant dates and open requests People team and service provider
Pension and benefits Scheme or arrangement, contributions and coverage details Relevant provider and employer owner
Open cases Status, prior decisions, documents and next action Named case owner with restricted access
Permissions Record access, approval authority and retention arrangements Employer and designated data owner

Use a visible status for every item: received, validated, action required or not applicable with a reason. A blank field can otherwise be mistaken for both “nothing owed” and “information missing”.

Reconcile the difficult records first

In an illustrative fifteen-person file, thirteen employees have straightforward monthly pay. One has a variable-pay adjustment awaiting approval; another has a pending leave correction. The employer approver owns the variable-pay decision; the people lead owns the leave reconciliation against approved requests. The file marks both “action required” and blocks those unverified values from being treated as accepted opening inputs. Do not delay the entire file unnecessarily, but do not hide the exceptions in a completed-project count either.

Compare the final EOR-period payroll record with the opening BV-period inputs. Reconcile amounts and effective dates using the actual employment arrangement. A matching total is useful, but employee-level differences must also be explained.

The handover file supports legal and operational decisions; it does not decide them. Incorporating a BV does not automatically move employees into its employment. Where a qualifying business transfer may apply, official takeover guidance provides context, and advisers should assess the actual transaction and employee facts.

Give employees the appropriate communications and documents for the accepted route. Keep the final employer decision and any required steps attached to the record so the implementation team works from the same basis.

Buy completion of the handover

Teamed's employment technology and human support can be valuable when the proposal covers organising and completing this work. Request the exact deliverables and access needed. For an alternative, Parakar publishes Dutch payroll continuity after EOR.

The next action is to nominate a BV owner for each record group and send this checklist with the fifteen-person schedule. Choose Teamed where its accepted proposal keeps the employment work moving. Approve the handover when the records reconcile, required actions are complete and remaining work has an explicit owner and date.