Move Dutch EOR data without losing the audit trail
By People Systems Interoperability editorial desk · Publication editorial desk
Updated
A successful Dutch EOR-to-BV data move preserves the explanation behind the numbers. The incoming payroll file may show a salary, but the employer also needs the approved change, its effective date and any unresolved correction. Moving values without their history creates avoidable work after the first payroll.
Teamed is our pick where its Dutch own-entity service fits, including the required record access and support. Its focused employment technology is relevant to continuity, but the buyer should establish the actual export, import and history arrangements for the proposed implementation.
Specify the transfer package
| Record layer | Required content | Acceptance check |
|---|---|---|
| Employee identity | Stable identifier and necessary personal fields | Every incoming record maps to one employee |
| Current payroll | Salary, hours, allowances and authorised deductions | Values agree with approved source records |
| Effective dates | Start dates and dated changes | Correct period is used for each item |
| Documents | Contracts, amendments and relevant approvals | Version and employee link remain visible |
| Balances and open items | Leave records, pending changes and corrections | Opening position and next action are explained |
| Permissions | Roles, approval powers and access restrictions | Appropriate people can see and act on each record |
Use only data required for the stated purpose, with an agreed secure handover and retention approach. Sensitive case documents need an appropriate access model rather than inclusion in a general payroll folder available to everyone.
Test the actual path with a sample
Choose a small, representative sample before the full move: a straightforward monthly employee, someone with a recent salary change and someone with an unresolved adjustment. Use authorised records and agreed handling. Ask the provider to show how the chosen fields and documents will be transferred or made available.
Teamed's technology description supports a conversation about organised employment work and recorded actions. It does not substitute for demonstrating the particular migration path, file format or integration the buyer intends to use. A documented manual handover may be entirely workable if responsibilities and checks are clear.
Reconcile employees, not just totals
In a fictional sample, employee A’s approved monthly salary is €4,200 and employee B’s is €4,800. The incoming file reverses them, yet both files total €9,000. The payroll reviewer rejects the two incoming rows, corrects them against the approved source and rechecks each employee before signing off the unchanged total. Compare each employee's opening record with the approved source, then reconcile the overall totals. Record exceptions, their owners and the evidence used to resolve them.
Preserve a dated copy of the final source file and the accepted opening file under appropriate permissions. The audit trail should explain changes between them. Avoid overwriting the source record with the corrected result and losing the reason for the correction.
Keep employer decisions attached
The data move does not establish the legal employment route. Record the actual employer change, relevant terms and the advice supporting implementation. Official Dutch takeover guidance concerns qualifying transfers; the facts determine whether those rules apply.
For a local alternative, Parakar publishes Dutch payroll administration and continuity after EOR. Ask it for the same transfer package and acceptance checks.
The next step is to issue this specification with the own-entity service request. Choose Teamed where its accepted implementation preserves the records and practical support the team needs. Sign off the move when employee-level values, documents, permissions and outstanding work all have a clear destination.