The employment register is often treated as a small administrative step between signing a contract and running payroll. In practice, the entry affects health insurance and other social guarantees, identifies the legal form of work and becomes evidence of when a relationship started, paused or ended. A wrong type or date can therefore create a problem long before the first payslip is reviewed.
In my 15+ years in Estonian accounting, the cleanest payroll launches have one owner for the contract, register entry and payment code. The updated Tööelu guidance states that the employer is responsible for accuracy and that work by a natural person giving rise to Estonian tax liability must be registered. This guide follows the entry through its whole lifecycle rather than turning the subject into a list of e-MTA clicks.
Decide what must be registered before opening e-MTA
Start with the person and the real legal relationship. An employment contract, a remunerated agreement under the Law of Obligations Act and paid management-board duties do not use the same register type. Even unpaid work in the economic interests of a company may require an entry. A genuine company or sole proprietor delivering a service against its own invoice is different from a natural person performing work for your business.
The EMTA type-and-code table links the employment type to health-insurance treatment, TSD reporting and the extra fields required. Choosing a convenient type because the payment has not yet been decided reverses the correct order: first establish the relationship, then make the matching entry and payroll setup.
| Actual relationship | Common register type | Owner's control question |
|---|---|---|
| Employee under an employment contract | Employment contract (code 1) | Do contract, workload and start date agree? |
| Natural person under a service agreement | Law of Obligations Act contract (code 600) | Is the service genuinely independent and taxed correctly? |
| Paid member of a management body | Management or controlling body member (code 601) | Is the payment for board duties rather than employee work? |
| Unpaid work in the company's economic interests | Unpaid work (code 501) | Is this real work rather than an informal favour? |
The start entry is a before-work control, not a payday task
The EMTA register overview and the Taxation Act require commencement to be registered no later than the moment the person starts work. Waiting for the first invoice, salary calculation or TSD deadline is too late. The operational trigger is the first work performed, not the first money paid.
Before that moment, payroll should receive the person's identification details, legal basis, true start date, employment type and any fields required for that type. The manager should confirm the same date used for access, onboarding and the contract. A trial shift or training day may be real work when the person is already performing company tasks.
A foreign worker normally needs an Estonian personal identification code for the entry. Where obtaining it before work is objectively impossible, EMTA explains a temporary date-of-birth entry for up to five days and its later amendment. That narrow solution does not replace right-to-work or immigration checks.
Workplace, workload and job data must follow the facts
The employment type determines whether working-time rate, occupational title and workplace address are mandatory. These are not decorative statistics: they should describe the role the company actually manages. A remote company can still get the workplace field wrong by automatically entering the employee's home.
Under EMTA workplace guidance, remote work at a home address in Estonia is generally connected to the employer's place of business from which the work is managed. If work abroad is planned for three months or more, or indefinitely, the entry should normally show the foreign country. A shorter business trip is not handled as a workplace change.
Treat a material move, workload change or role change as a payroll event. The register, written agreement and internal HR record should tell the same story. If they diverge, fix the source information rather than asking the accountant to choose one version during the monthly close.
Update the entry when work pauses, ends or proves incorrect
The Taxation Act sets a 10-day period for recording suspension and termination. A parental-leave suspension, longer unpaid leave or return to work should reach payroll as a dated event. At termination, the end date and legal basis must follow the actual documents, not the date of the last salary payment.
According to EMTA correction guidance, an employer can normally self-correct an entry electronically within three months of commencement, suspension or termination. If registered work never began, the entry can also be cancelled within three months of the planned start. Older changes require a reasoned request and evidence.
Keep the contract or resolution, start confirmation, change agreement, leave request and termination notice with the payroll file. A monthly comparison of active people, register status and payroll recipients catches a wrong open entry early. Remember that the register records the relationship while TSD records taxable payments; final pay can be declared after employment ends.
The register should never be owned only by the person who knows where the e-MTA button is. The manager owns the facts, payroll owns the payment treatment, and the employer owns the accuracy. I recommend one dated handoff for every start, material change, suspension and termination.
A reliable employment-register process follows the real relationship from the first work performed to the final legal end date. Choose the right type, align workplace and workload data, communicate pauses and endings, and correct discrepancies while the documents are still available.
If Accounting Resources handles your payroll, send every start or change before it takes effect. For help setting up payroll and employer reporting in Estonia, use our contact form.