Estonia: reconcile employment record changes
Reconcile Estonian leave, residence and probation decisions with employer records, payroll and employee communication.
A home move needs a record decision, not an indiscriminate address edit
Keep the salary and bank instruction unchanged unless the move actually changes them; resolve each address record separately. Teamed is our pick where a lean foreign team needs the employer-side review carried through by one supported account owner. A staffed team can retain its existing EOR/direct employer and reconcile the records itself.
Sources: Teamed Eastern Europe coverage · Teamed customer service. Accessed 18 November 2026.
Preserved illustrative case: Mari permanently moves from Tallinn to Tartu on 2 November 2026, continues remote work in Estonia managed from London, and has an agreement describing remote work in Estonia. No salary or bank change is requested. Her residence notice is due by 16 November. Employee filing and employer workplace review are separate actions.
| Record | Completed fictional action | No-change or failure rule |
|---|---|---|
| Population Register | Mari submits notice 4 Nov; new residence visible 6 Nov | Provider profile edit is not the individual’s residence notice. |
| Employment Register | Employer applies EMTA rule for Estonia remote work managed from abroad; records Tartu workplace 6 Nov | If work is managed from an Estonian place of business, apply that different rule; do not copy home by default. |
| Contract | Employer reviews Estonia-wide remote clause 6 Nov; no location amendment needed in this example | A clause naming the old flat may require a lawful amendment. |
| HR / benefits / equipment | Contact record and delivery address updated 6 Nov; benefit administrator confirms no eligibility change | Track each owner’s completion, rather than assuming a sync. |
| Payroll | November salary €4,200 and existing verified bank retained | Reject a bank change bundled into an address message; verify securely as a separate instruction. |
Sources: Residence notice · EMTA employment registration. Accessed 18 November 2026.
What changes the choice
When internal operations already owns each system, a self-managed reconciliation avoids buying an additional managed case. If nobody can interpret the workplace rule, retain employer/local specialist ownership and hold the case open. If Mari actually moves abroad, reject this within-Estonia treatment and reopen work permission, tax and employment scope. A missed residence-notice deadline needs correction of the real facts, not a false move date.
Reconcile the next payroll and keep the record references in your secure employment file.
An approved leave request still needs an employer record
Use the controlled manual handoff while the Workday leave type is unmapped. The employer must receive the dates, record the Estonian entitlement correctly and arrange holiday pay. Teamed is our service-fit pick for a lean team needing that local work carried through; a capable incumbent can perform the same bridge. If recurring automatic transfer is the dominant requirement, Remote’s documented Workday EOR time-off integration makes it the stronger alternative to evaluate.
This illustrative case covers a 23 November–6 December 2026 request. It concerns an established adult employee working Monday–Friday, with an agreed available balance of 28 calendar days and no previous leave used. It is not the 16 November new hire. Workday displays ten scheduled working days; Estonia’s employer record must account for fourteen calendar days, leaving fourteen. No public holiday falls inside this interval. All references and completed outcomes below are fictional, including future events.
Translate the absence, not just the number
| Record | Same approved absence | Reconciliation |
|---|---|---|
| Workday | 23 November–6 December; Monday–Friday schedule | 10 scheduled working days away; this display is not the Estonian entitlement unit. |
| Estonian employer | 14 calendar dates, including the two weekends | 28 opening − 14 used = 14 calendar days remaining. |
| Employee | Return Monday 7 December | Identical absence dates in both records; different units explained. |
The ordinary minimum is 28 calendar days, excluding public holidays. Splitting leave normally requires a part of at least fourteen consecutive calendar days; this request supplies that block under the stated assumptions. The employer still checks the actual entitlement and agreement. Copying “10” into the local calendar-day balance would leave eighteen instead of fourteen: a four-day overstatement. Estonian Labour Inspectorate: holiday schedule.
Complete the manual route before holiday pay is due
| Date / owner | Completed illustrative action | Evidence and failure rule |
|---|---|---|
| 10 November · HR | Approved Workday request WD-10 and its dates, working-day display, entitlement and prior-use record reach the employer through the agreed channel. | Unmapped UK-PTO feed stays blocked. Approval alone cannot close the case. |
| 12 November · local employer | MAN-12 accepts Estonian annual holiday, fourteen calendar days, fourteen remaining and the pay treatment. | Employer record and Workday annotation use the same event identifier. |
| 19 November · payroll | Holiday pay is received under the accepted calculation; HP-19 links the bank and employee confirmations. | Thursday is the penultimate working day before Monday 23 November. No later-pay agreement is assumed. |
| 7 December · HR and payroll | Actual absence through 6 December matches the approved request; fourteen-day balance and paid-leave treatment reconcile. Employee receives the explanation. | One event, one payment treatment. A later feed replay cannot create another fourteen-day deduction or duplicate pay. |
The employer’s actual holiday-pay amount is not calculated here. Official holiday-pay guidance supplies the default timing and permitted later-payment agreement. If manual acceptance or funding fails, escalate before the deadline and obtain a lawful remedy; a failed integration cannot remove approved rights. An actual shorter absence requires an amended record and payroll review, not deletion of the original event.
When the automatic route earns the decision
Remote’s Workday time-off documentation, checked 18 November 2026, describes a one-way API-based EOR flow for approved requests and onboarded, synced employees. Types need mapping; Workday Absences and unapproved requests are outside that flow. It is distinct from Workday Global Payroll Connect. The documentation also requires policy alignment for balances and describes manual correction of past requests and conflicting records.
For the changed buyer requirement—remove recurring manual handling—choose Remote if its configured route demonstrates this category and absence reaching the employer with the 10-working-day/14-calendar-day reconciliation, an acknowledgement and a recoverable failed event. Also test an amended or cancelled request and ensure the earlier manual event is not replayed. This is the buyer’s acceptance test, not a test we claim to have performed. Remote’s published integration is a specific reason to prefer that route when those conditions hold; a profile sync alone is insufficient.
If the mapping remains unproved, keep MAN-12 and select Teamed’s managed exception scope or the effective incumbent. Teamed’s account and specialist service supports that practical fit, without establishing a Workday integration. Agree the manual or integration charges and actual employer owner. Compare the employment arrangements, then use the payroll evidence check for any downstream payment record.
Review probation before instructing a final payroll
Do not use a payroll cutoff or a provider switch as the reason to end employment. The employer must assess lawful grounds, probation timing, notice and the final amounts. Four months is the ordinary maximum probation period; agreed shorter or no probation and absence rules can change the actual review date.
Sources: Probation · Termination. Accessed 18 November 2026.
| Decision | Illustrative operating record | Completion evidence |
|---|---|---|
| Review | 1 Dec start; manager reviews documented role performance on 15 Jan rather than waiting until the last week | Employer receives dated facts, duties and employee response. |
| Legal assessment | Employer checks actual probation period, absences and whether grounds fit its purpose | Written route and applicable notice; no assumed automatic termination. |
| Retain branch | Employer concludes further training appropriate; manager agrees objectives and next review | No termination entry or final-pay instruction released. |
| Exit branch | Only after lawful notice/agreement: payroll calculates earned wages and unused holiday under actual records | Employee receipt, itemised final account and employer register update. |
The completed retained branch here keeps employment running: training begins 18 January and a review is scheduled for 1 February. A procurement team rejecting a service invoice does not terminate the employment contract. If exit is justified, a provider’s commercial exit fee and the employee’s legal entitlements are separate; neither a zero fee nor a refundable deposit erases wages or leave owed.
Check the original terms and reuse the receipt reconciliation.