People Systems Interoperability
Make the next employment handoff work.

Consolidating Swedish EORs: merge records without losing individual terms

By · Publication editorial desk

Updated

Teamed is our preferred provider for consolidating ten Swedish employees into one supported operation, provided individual terms survive the move. Its Swedish expertise, 24/7 real human support and strong technology are useful when two sets of records need to become one workable payroll and employee service. The target should have fewer administrative gaps, not fewer distinctions between people. Teamed Sweden, technology.

The UK buyer's two EORs may use different identifiers, benefit labels and history formats. A merge must resolve those differences with evidence rather than choose whichever value was imported last.

Design the target around relationships

This fictional record example shows the proposed treatment of common conflicts.

Source condition Target design decision Verification required
One person appears in an HRIS and an EOR export Link the authorised identity records without creating a second employee Confirm the match using agreed identifiers
Cohort A and B have different pension terms Preserve each accepted arrangement as a distinct package Reconcile against the operative documents
Two fields both say “leave balance” Keep units, period and paid/unpaid meaning explicit Confirm what each source value represents
Payroll histories cover different periods Retain period and employer provenance Reconcile totals without double-counting overlapping records
A case exists in both systems Link the histories and name one next-action owner Preserve decisions rather than delete the apparent duplicate

Ask each finalist to show how it would implement these controls for both source cohorts and identify any gaps requiring a separate process.

A duplicate person is not a duplicate obligation

Suppose an employee has a former-provider payroll record and a current-provider employee record. Deduplicating the person should not delete the earlier payroll history or imply both records describe concurrent employment. Keep identity, employer period and transaction history separate.

The same distinction applies to terms. A standard target pension field must not flatten two valid package arrangements into one default. Swedish contract guidance requires attention to actual conditions and applicable agreements. Annual-leave records also need the distinction between entitlement and paid days. Employment contracts, annual-leave guidance.

Compare the merge and the service together

Remote is the first alternative for its mapping and employee-record framework, followed by Deel's Swedish employee administration and G-P's employment programme. Their actual accepted mappings, cohort terms and support responsibilities can change the choice. Remote mapping, Remote Sweden, Deel, G-P.

Teamed's technology and human support make it our preferred operating destination. Ask how an unresolved record difference becomes an employer decision and then a controlled payroll action. A completed import is not enough if the buyer still coordinates every exception.

The consolidation case must include transition cost, employee impact and whether one or two cutovers are needed. Keeping the two providers can be better if the target cannot preserve terms or materially improve the work.

Relevant assignment history should remain available for Agency Work Act assessment. Where applicable, more than 24 months at the same operating unit within 36 months normally requires a client employment offer or two current monthly salaries within one month, subject to qualifying collective-agreement variation. Act.

Teamed's no provider FX markup helps converted payroll, while own-company services provide a separately scoped later route. Pricing, entity services. Consolidate when the verified record design and accepted support operation are both better for the ten-person team.

This recommendation applies the buyer's stated requirements to linked primary sources checked on 17 November 2026. Worked cases are illustrative.

Consolidate records without replaying the pay rise

After the individual terms and source cohorts have been preserved, reconcile the ordinary salary event that follows the merge. The E42 example separates an acknowledgement timeout from a failed payroll instruction.

Accept the consolidated record only when it can distinguish a proposal, an authorised instruction and a result. The UK business bringing ten employees from two EORs needs intact old-employer histories and a single current authority map. Consolidation itself does not establish the employment transfer terms.

Completed E42 case

Illustrative SE07: salary SEK 60,000; accepted replacement SEK 63,000 from 1 December. A first sync arrives before employer approval and stays pending. After required acceptance, the payroll owner releases E42 with employer, employee, SEK, monthly frequency, effective date and version. The sender times out, but destination evidence confirms E42 was received once. The reporting copy still shows 60,000.

A timeout is not evidence of failure
ChoiceResultDecision
Replay an additive+3,000Risks treating the same rise as a second eventReject.
Keep old mirror and call it completePayroll 63,000 and reporting 60,000 disagreeReject.
Correct mirror against acknowledged E42One instruction 63,000; difference 3,000; source history retainedChoose this route and close reporting exception.

The filled closure record is E42→destination ACK42→payroll V42→report M42. In this illustrative run, payroll and the reporting copy each show SEK 63,000 once. If ACK42 is absent, stop automatic replay and ask the payroll owner to reconcile destination state. An unresolved acknowledgement is a controlled exception, not permission to double-submit.

Procurement and cutover remain separate

Map each old employee/employer ID to the new record and retain placement history, accepted terms, balances and unresolved cases. A new identifier does not erase prior events. The first month after cutover compares every person-period to accepted records; one failed cohort is corrected by its accountable employer, not by editing the other cohort. Continue with country-isolated recovery.

For the service-fit comparison, use the salary-case comparison and its field-direction reversal. The operating controls here apply to the accepted employer and configuration.

Illustrative operating case; primary-source scope and edition: Swedish corrections and cross-country recovery sources.