GUIDE
The first workforce operating map after a Baltic acquisition
By Samuel Moore · Talent Acquisition Coordinator
Updated
On this page
Map the current arrangement before proposing a replacement
An acquisition can leave the integration lead holding a list of people without a reliable answer to who employs them, who runs their next payroll or which seller service is still needed. The first useful deliverable is one operating row per employment cohort. A cohort is a group sharing a country, legal employer and current operating arrangement; it is not everyone who reports to the same manager.
Use the fictional Northline acquisition throughout this site. It has twelve employees at an acquired Estonian company, four Latvian employees assigned to a business unit whose transfer treatment is unresolved, and three Lithuanian employees with an existing EOR. These are invented planning facts, not a customer story or legal conclusions about a real deal.
Fill the row with evidence, not confidence
EE-A has employer Northline Estonia OÜ, twelve people and current payroll provider Local Payroll A. The signed employment records are indexed in repository EE-01. The transaction team confirms in this fictional scenario that the company remains the employer. The existing seller-administered payroll route and a finance deputy are identified for the next cycle; buyer-controlled access remains a handover dependency. Status: keep-current.
LV-B has four people employed by Seller Latvia SIA. The asset schedule suggests the operating unit is moving, but the scope of people and business activities still needs local assessment. The seller’s existing payroll service continues under the agreed interim arrangement. Status: investigate. Missing advice does not become permission to move the group to a new employer.
LT-C has three people employed by EOR C. The current agreement and payroll calendar are available, but the group’s benefits contact has changed. Status: keep-current for the next cycle; a later provider review is separate. A support problem is evidence for investigating service quality, not evidence that the employment route has changed.
Separate a missing document from a reason to change
The seller has not delivered LV-B’s latest working-pattern amendment. That is a records gap: obtain and reconcile the document. EE-A’s payroll portal uses the seller’s email domain. That is an access dependency: replace the administrator and test access. Neither fact alone proves that an EOR replacement is needed.
A change proposal needs a distinct reason and an approved route. For example, LT-C may later be assessed for a provider replacement because the buyer wants a receiving service to carry specified employment support tasks. Keep that proposal in a separate decision field so it cannot overwrite the current employer before the transition is ready.
Give the next payroll its own four names
Each cohort row needs an input preparer, approver with deputy, funder and employee-question contact. In EE-A, the existing local administrator prepares; buyer finance approves; the acquired company funds; the local People lead answers employees. Add the actual deadline and evidence location for each responsibility. “Finance” is not enough if nobody can act when the main approver is away.
The integration lead checks whether those four responsibilities are accepted and whether the people have access. The lead does not become the substitute payroll approver merely by maintaining the map. Use our next-payroll plan for the dated handover and exception route.
Change the status only when the reason changes
Keep-current means the present arrangement has an evidenced operating route for the period being planned. Investigate means a particular fact or assessment is unresolved, with an owner and a next decision date. Change-approved means the decision to pursue a specified change has an authority reference; it does not mean the migration is complete.
Store employer documents and personal records in the authorised repository. Put aliases, cohort counts and references in the operating map. The map is finished when another integration colleague can say what happens next for each group without inventing an answer or interpreting the colour of a status cell.
PUT IT TO WORK
Northline: completed opening cohort map — fictional
| Record / decision | Completed example or rule |
|---|---|
| EE-A / 12 people | Northline Estonia OÜ; repository EE-01; Local Payroll A; current route and approver/deputy identified; buyer access handover pending; KEEP-CURRENT. |
| LV-B / 4 people | Seller Latvia SIA; unit-transfer scope unresolved; interim seller payroll accepted; INVESTIGATE with local counsel. |
| LT-C / 3 people | EOR C; agreement and payroll calendar verified; benefits contact being repaired; KEEP-CURRENT for next cycle. |
| Records gap | LV-B working-pattern amendment missing: request and reconcile; no automatic employer change. |
| Decision control | Future LT-C provider review remains separate from the confirmed current payroll route. |