Employment transfer rules in Estonian M&A can move the hardest work out of the purchase-price clause and into payroll, consultation, and liability planning. In some deals the real surprise is not valuation. It is the point at which employment contracts, accrued leave, and old wage claims start travelling with the business. Read this together with Corpenza's share-versus-asset guide, the Estonian OÜ due-diligence checklist, and the note on post-acquisition integration.
The first bad assumption usually appears early. Teams see a change of ownership and assume the staff automatically slide into a new setup. Estonian law asks a narrower question first: is there a transfer of an enterprise or an organised part that keeps its identity? Only after that test do the employee-transfer, payroll, and consultation issues fully open up.
What happens to employees when an Estonian business transfers?
If there is a transfer of enterprise, employment contracts and collective agreements move to the new employer unchanged. Tööelu and section 112 of the Employment Contracts Act point in the same direction: no new employment contract is required, the employer name may change, and the agreed core terms stay in place.
That includes more than the paper contract. Tööelu explains that unused holiday rights, continuity of service, and other employment-related rights also continue. So a buyer should not look only at headcount. It should also map leave balances, payroll practice, and any open employee claims before signing.
| Rule | Source | Practical effect |
|---|---|---|
| Contracts transfer unchanged | Employment Contracts Act section 112 | No mandatory re-papering of staff on transfer day |
| Collective terms continue | Tööelu + EU transfer framework | Pay and working patterns cannot simply be reset |
| Leave and service history continue | Tööelu | Hidden labour costs survive beyond the headline price |
Does every M&A deal count as an employee transfer?
No. The transaction label is not enough. Sections 180 to 185 of the Law of Obligations Act and the EU transfer-of-undertakings framework look for an economic entity that keeps its identity. That is why the first legal question is not whether the deal is called an asset deal or a share deal. It is whether an operating business whole is moving to another employer.
That distinction matters. In a straight share purchase, the employing legal entity may stay where it is. In a wider transaction, though, a business line, team, customer base, and operating process can move to another employer even if the headline deal description sounds broader. Before signing, map the staff, managers, key assets, and customer contracts that are actually moving.
Do not leave that map to the final week. Corpenza's share-purchase versus asset-purchase guide is useful here because a wrong classification distorts the payroll and liability analysis from the start.
What must employees be told, and how early?
Section 113 of the Employment Contracts Act requires the transferor and transferee to inform employee representatives, or the employees themselves if there is no representative, at least one month before the planned transfer in a format that can be reproduced in writing. The notice must cover the date, reasons, legal and economic consequences, and any planned measures affecting employees.
This is more than a courtesy update. If measures affecting employees are planned, a consultation duty follows. The same section says employee representatives may submit written proposals within 15 days, and reasons must be given if those proposals are not taken into account. A common deal mistake is letting HR, legal, and corporate teams run separate calendars instead of one shared employee-communication plan.
Even a modest operational change can trigger real timing pressure. If reporting lines, workplace arrangements, support functions, or scheduling will move, design the notice and the consultation track together. A rushed email at the end of the process is a weak substitute.
Which labour liabilities follow the business?
Section 182 of the Law of Obligations Act says enterprise-related obligations move to the transferee. Section 183(1) adds the sharper point: for obligations that arose before the transfer and were due by the transfer date, or become due within five years after it, the transferor and transferee are jointly and severally liable.
That makes old payroll issues a buyer problem too. Delayed wage items, overtime disputes, bonus calculations, unused leave, weak time records, or other employee claims can surface after closing. So diligence should test the payroll support pack, not just the employee list.
The practical trap is maturity, not visibility. A claim may be quiet today and still fall inside the five-year joint-liability rule later. That is why section 183 belongs in the deal file, not only in outside counsel's memo.
Can the buyer rewrite contracts or dismiss people because of the transfer?
No. Tööelu states clearly that an employment contract may be amended only by agreement between the parties unless the law allows otherwise. The European Commission's transfer-of-undertakings summary, echoing Directive 2001/23/EC, also says that the transfer itself is not a valid ground for dismissal.
So a buyer cannot demand fresh contracts from everyone just because the business moved, and it cannot use the transfer alone as a shortcut reason for termination. If there is a separate economic, technical, or organisational reason, that requires its own analysis and evidence. The transfer event does not replace that work.
If the operating model will change after closing, sort the true contractual terms from the looser working arrangements first. Then build any needed agreement process. Otherwise the integration team creates friction in month one that could have been avoided in diligence.
What should buyers and sellers check before signing?
Good files do not leave employee-transfer work until after closing. Before signing, identify the transferring unit, the employee list, any collective arrangements, accrued leave, payroll claims, and the information-and-consultation timetable in one table. Once that is done, price, conditions precedent, and the integration plan start lining up.
- Write down whether the deal really transfers an enterprise or an organised part.
- Match the transferring employees and critical managers by name.
- Test salary, bonus, leave, service-history, and open-claim data against payroll evidence.
- Work backwards from closing to plan the information and consultation calendar.
- Decide who owns the first post-closing payroll cycle, ideally with support from Corpenza's global recruitment and payroll team.
- If the structure still looks grey, bring the deal and payroll workstreams together through Corpenza's contact channel before signing.
This is not a small HR annex. If the employee-transfer file is built badly, the closing can look finished while the first salary cycle immediately proves that it was not.
FAQ
Do employees need new contracts after transfer?
Usually no. If there is a transfer of enterprise, the existing contracts move unchanged and only the employer identity may change.
Do unused holiday balances also transfer?
Yes. Tööelu treats unused holiday rights and continuity of service as part of the package that continues with the new employer.
Does every share sale automatically trigger employee transfer?
No. First test whether an economic entity or organised part is actually transferring to another employer while keeping its identity.
If the seller and buyer split old payroll risk between themselves, does that bind employees?
Not automatically. Section 183 protects third parties with joint and several liability unless the legal conditions for a different result are met.
What is the mistake seen most often?
Late information and consultation planning, followed by weak payroll data that gets pushed into the post-closing phase.
This is general information, not legal or tax advice. Rules change, and the right answer depends on the structure of the transaction.
