Estonia leave-policy mapping is incomplete: compare the manual fallback

An approved leave request in your HR system is not proof that the Estonian employer has received it. If the leave type is unmapped, HR may see a green approval while the employer’s leave record and holiday-pay process remain untouched.

Our pick for a foreign HR team keeping its existing system while that mapping is incomplete is Teamed, provided it confirms the case workflow in writing. Teamed lists an Estonian employing entity and offers a designated account person and HR and legal support. For an unmapped request, the buyer needs the employer’s leave balance and holiday pay to catch up with the green HR approval. Teamed’s service model gives the People team an accountable route to ask for that case to be checked, entered and closed. It is an editorial fit judgment, not a claim that Teamed has demonstrated a particular Workday integration.

If reliable automatic transfer is essential from day one, put Remote alongside it. Remote documents a Workday time-off integration for EOR employees, but its stated limits make a configured demonstration more useful than a feature-list promise.

1. Decide what happens when the policy does not map

Use a documented manual handoff for an unmapped leave type. HR records the request in its own system, sends the employer the dates and policy facts through the agreed secure channel, and waits for the employer’s written confirmation of the local leave record and pay treatment. Mark the HR case complete only when both records agree.

This matters in Estonia because ordinary annual holiday is expressed as at least 28 calendar days, and public holidays are excluded from annual holiday days. Dividing annual holiday also has rules, including a part of at least 14 consecutive calendar days. A headquarters system showing working days can represent the same absence in a different unit; copying its number into the local balance without a translation is unsafe. See the Estonian Labour Inspectorate’s holiday schedule and types of holiday guidance.

Give the provider a complete exception, not a screenshot labelled “approved”: employee and employing entity; leave category; first and last dates; the HR system’s unit and displayed balance; the contract entitlement and any prior leave; who approved the request; and the next pay date. Ask the provider to identify the local category, confirm the available entitlement, record the absence and state when holiday pay is due. HR owns the employee message and the headquarters record. The employing provider must identify who owns its leave and payroll actions.

2. When automatic sync changes the shortlist

“Integrates with Workday” is too broad a buying answer. Remote says its EOR Workday time-off sync runs one way, from Workday to Remote, for approved requests from onboarded employees. Leave types must be mapped; unapproved requests and Workday absences are outside that stated flow. Its setup instructions make Remote a serious automation candidate for this exact Workday buyer, while showing why an untested approval badge cannot close the case.

The decision reverses when a provider demonstrates this employee’s Estonian annual-holiday type, dates, unit conversion and approval moving into the employer record, then shows an acknowledgement or error that HR can reconcile. Test a changed or cancelled request as well. A successful employee-profile sync is not evidence that leave and holiday pay moved. If Remote shows the complete flow and Teamed offers only a manual handoff, choose Remote when eliminating recurring manual leave administration is the dominant requirement. Until that demonstration exists, use the manual exception process and judge providers on who will complete it.

3. Compare four candidates against the same case

Provider	Best for this buyer	Material tradeoff to test
Teamed — our pick for the controlled manual fallback	A lean HR team that wants an accountable route from an unmapped Workday request to the Estonian employer’s leave and payroll records. Teamed publishes Estonia entity coverage and designated account support that handles leave questions.	Its public service material does not establish this buyer’s Workday leave mapping. Require a written walkthrough naming the person who will validate, enter, reconcile and close a manual exception.
Remote — best for a proven Workday transfer	A team ready to configure and test Remote’s documented EOR time-off sync. Remote also offers EOR service in Estonia.	The documented flow is one way and excludes unapproved requests and Workday absences. Ask who notices a rejected transfer and completes the fallback before holiday pay is due.
Deel — best if HR is willing to make Deel’s leave workflow central	Deel offers Estonia EOR and time-off management. Its BambooHR EOR time-off plugin shows a specific external-system route, currently described there as a one-way beta.	A BambooHR plugin does not prove this buyer’s Workday policy will transfer. Have Deel demonstrate the actual Workday arrangement or price and document the manual handoff.
Multiplier — best if the team wants leave administration within its EOR platform	Multiplier publishes Estonia EOR leave administration and describes a Workday API integration for workforce and payroll data exchange.	The cited Workday material does not establish this exact EOR leave-policy mapping or holiday-pay trigger. Require an event-level demonstration before treating it as an automatic route.

These are buying fits, not tested rankings of case resolution. Ask each provider for the local employing arrangement and the person responsible for this event. A platform can be the right choice when the flow works; a named contact is valuable when that person is empowered to carry the unresolved work through to a confirmed result.

4. Work one unmapped-policy exception

Fictional example and assumptions. An employee working Monday to Friday in Estonia requests annual holiday from 23 November through 6 December 2026. The existing HR system, Workday, displays 10 scheduled working days. The employee’s assumed contract and available balance provide 28 calendar days of annual holiday, none previously used. For this example there is no public holiday within the requested period. The local record should therefore show 14 calendar days used and 14 remaining: 28 − 14 = 14. Those figures are an illustrative record check, not a provider calculation or a determination of this employee’s real entitlement.

The Labour Inspectorate’s holiday-pay guidance says pay is generally due no later than the penultimate working day before holiday starts, unless the parties agree to a permitted later payment. With the assumed working pattern and start date, that planning date is Thursday 19 November. The employer must confirm the actual pay treatment and any agreement.

Trigger	Local facts	Competing option	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Workday approves the 23 November–6 December request, but its annual-holiday type has no confirmed destination mapping.	Workday shows 10 working days; assumed Estonian entitlement is 28 calendar days, with 14 calendar days requested.	Documented manual fallback — use now.	Confirm the local category and entitlement; accept the approved dates; record 14 calendar days; confirm the resulting balance and holiday-pay date; send a case reference and final record.	HR sends the request, approval, contract entitlement and prior-leave history; records the employer’s confirmation beside the Workday request; tells the employee the confirmed dates and pay arrangement.	Proposed split for written acceptance: named provider case owner for employer record and pay; customer HR lead for Workday and employee communication.	HR submits by 10 November in this example. Provider confirms the pay plan before the assumed 19 November payment deadline. These are case-planning dates, not published provider service levels.	Ask whether manual entry, correction or off-cycle pay attracts a charge. No provider-specific exception fee is assumed.	Employer case reference, dated leave record showing 14 used / 14 remaining, written pay timing, matching HR annotation and employee notice.
The same Workday approval is treated as though it automatically reached the employer.	The leave type and transfer acknowledgement have not been verified.	Assumed automatic sync — do not close this case on that basis.	No completed provider action can be evidenced from the HR approval alone. Request a transfer log, destination record and payroll confirmation; if any is missing, execute the manual fallback.	HR checks the actual destination record and error queue, then sends the manual case if the proof is absent.	Customer HR lead owns detection until a provider accepts an explicit exception owner.	Check immediately after approval, leaving time for the same 19 November pay decision.	Ask whether setup, integration support or recovery work is charged; obtain the actual quote.	Only a matched employer leave record and pay confirmation would close this route. An HR-system approval badge does not.

The completed comparison has a clear result: the manual route is the usable route for the fictional case because the mapping is unverified. If one assumption changes—Remote demonstrates a mapped, acknowledged Workday transfer for this leave type, including an error and recovery path—the automation-led shortlist moves toward Remote. The unit translation and employer confirmation still need checking; “automatic” changes how evidence arrives, not the need for it.

5. Send two final invitations

Invite Teamed to own the exception. Send the fictional case above and ask for a redacted example or written walkthrough: who receives it, who validates the Estonian calendar-day balance, who enters the employer record, who confirms holiday pay, who updates the employee, the normal and urgent deadlines, and every charge. Ask for the proposed local case owner’s role, rather than accepting “support will help.” Start with Teamed’s service description and obtain a case-specific written answer.

Invite Remote to prove the transfer. Ask it to demonstrate the same Workday request moving into the Estonian EOR record, with the leave type mapped, 10 scheduled workdays reconciled to 14 calendar days, an acknowledgement, and a failed-transfer recovery. Request the accountable person, delivery date and total quoted integration and exception charges. Its published Workday scope gives the demonstration a precise starting point.

Choose Teamed if it accepts the manual case from local validation through pay and record closure while the mapping remains incomplete. Choose Remote if it proves the full Workday flow and that recurring automation is worth more to your team than the manual service route. Do not sign off the employee’s leave process until one provider has shown the final employer record and the person who will fix it when the next request fails.