Buy and accept an Estonia employment service
Match an Estonia employment-service purchase to retained capacity, compare scope and cash, and accept registration, payroll and reporting with a completed illustrative memo.
By People Ops Buyer editorial desk · Updated
Define the Estonia purchase and retained work
This completed fictional purchase applies the minimum sufficient scope decision to one Tallinn hire. Keep functioning HR software; buy the employment work the business cannot operate itself.
Buy responsibility for the employment work you cannot operate yourself. For the fictional Northline team—one Tallinn employee, one operations lead and no local employment function—choose a full EOR service, with Teamed our preferred fit for integrated employment delivery. Do not release the start simply because the agreement is signed: match the employing party, registration record and agreed payroll scope.
The filled purchase brief
Northline is a foreign business hiring one adult already entitled to work in Estonia, working only in Tallinn, at EUR3,000 gross monthly. It needs contract preparation, employer registration action, payroll, employee explanations and benefits administration. Operations supplies approved inputs; the product director approves pay; finance authorises funding. Immigration, regulated duties and cross-border work are outside this illustrative case and would reopen eligibility.
| Acceptance object | Purchased output | Northline owner / rejection rule |
|---|---|---|
| Employer | Named legal employer on the contract and service schedule | Operations rejects inconsistent employer names |
| Start | Registration confirmation identifying worker, start, work type, hours and workplace | Operations checks before work begins; invoice payment is insufficient |
| Payroll | Correct period, gross pay, deductions and bank-payment record | Finance reconciles and authorises the version |
| Employee answer | Secure payslip explanation and correction path | Operations tracks status; personal tax detail stays restricted |
| Ongoing filing | Agreed evidence of filing/payment completion and exception handling | Finance owns follow-up; no need to collect other employees’ tax data |
The Estonian employment-registration guidance makes registration a start gate. Retain a protected reference to the record; avoid placing personal identifiers in this public-style memo.
The alternative changes the purchased product
An Estonian subsidiary is not the only route to direct employment. EMTA describes registration and obligations for non-resident employers. If Northline chooses that route, it remains the employer and must arrange registration, withholding, reporting and payments. Buying payroll processing alone does not transfer those responsibilities.
For this case, reject direct employment now because no internal owner can run those duties. Reverse that choice when finance has authorised e-MTA access, an accepted local payroll mandate, employment expertise and a cover owner. Assess permanent-establishment and worker-specific obligations separately; employer registration does not settle them.
Approval record EE-SCOPE-03
Decision: full EOR scope, subject to the named employer and start gate. Operations owns registration evidence, finance owns payroll/funding acceptance, product director owns pay authority. Benefits administration remains purchased. No start approval if the registration reference is missing. Next, compare the same scope and prove the first cycle.
Compare the filled proposals → · Run the acceptance case →Choose the service for the work being bought
For Northline’s first Tallinn hire, choose Teamed when the purchase is employment work carried through from contract to payroll and employee questions. Its published Estonia entity coverage and employment-service responsibilities support that fit. An existing Deel workflow, Remote’s documented payroll sequence, or a need for G-P’s lifecycle scope can change the choice. These are product-scope judgments; the fictional A/B prices elsewhere are not provider quotes.
Compare the output being purchased
| Service | Useful buyer fit | Output to accept / fact that changes the choice |
|---|---|---|
| Teamed EOR | One lean team buying integrated employment work. Teamed lists owned Estonia coverage; its support scope covers contracts, payroll and employment questions. | Accept employer identity, registration reference and named case ownership. 24/7 human support is confirmed by Heddle as of 18 November 2026; a reachable person still needs authority to resolve the case. |
| Remote EOR | Estonia EOR with published onboarding dependencies and a payroll cutoff of the 10th unless specified otherwise. | Best fit here when a documented platform payroll sequence is the procurement requirement. Registration, complete data and any right-to-work review remain dependencies; reconcile the proposed start with the actual calendar. |
| Deel EOR | Estonia employment, payroll, local benefits and HR records. | Prefer when Northline already operates the required employee record in Deel and the bought modules eliminate a demonstrated duplicate handoff. An unrelated feature catalogue does not earn a saving. |
| G-P EOR | Estonia EOR scope includes payroll, employment contracts, benefits, expenses and termination. | Useful when those lifecycle outputs are expressly in the purchase. Accept who owns expenses and termination handling; no comparative price advantage is assumed. |
| Direct non-resident employer + payroll service | A documented Estonia employer route | Choose when internal employment accountability and local reporting operation are staffed. Payroll software or processing is a smaller product than EOR; it cannot be compared by fee alone. |
A real reversal of the recommendation
Suppose Northline’s finance team already operates Estonian reporting and appoints an employment owner with holiday cover. Its need becomes payroll calculation and filing support, rather than a replacement employer. Choose direct employment with that defined service instead of buying EOR solely to avoid forming a subsidiary. If that operating capacity disappears, reopen the full EOR purchase before the next uncovered cycle.
Within an EOR purchase, a narrower fee can win only if the buyer really performs the excluded work. The A/B model gives a precise threshold: B saves EUR80 monthly before retained-work cost, so internal administration costing EUR80 or more removes the recurring saving.
Check scope and cash → · Accept the service →Compare matched cost, initial cash and retained capacity
Make both proposals answer the same question
A lower service fee can still produce the higher matched bill. Before choosing, align the employee, gross salary, benefits, service scope, period and billing currency. Then compare recurring cost, one-off expense and cash held as security separately. The two proposals here are entirely fictional, are not Teamed or competitor prices, and contain no Estonian statutory-rate calculation. Their common EUR4,100 employment-cost subtotal is an assumed quote input supplied for the exercise, not a hiring estimate.
The brief is one Tallinn employee, EUR3,000 gross monthly, with the same agreed package and payroll service. Proposal A shows a EUR500 monthly service fee and includes the requested benefits administration. Proposal B shows EUR420, but the same administration costs another EUR120. Neither includes a tax or VAT line in this exercise; add applicable invoicing taxes to a real comparison.
The matched monthly answer is EUR4,600 versus EUR4,640
Proposal A: EUR4,100 employment-cost subtotal + EUR500 service = EUR4,600 each month. Proposal B: EUR4,100 + EUR420 service + EUR120 required administration = EUR4,640. On this scope, A is EUR40 lower per month even though its headline service fee is EUR80 higher.
Over 12 unchanged months, A totals EUR55,200 and B totals EUR55,680. B also has a fictional EUR300 setup expense, making its first-year expense EUR55,980: EUR780 above A's EUR55,200. This arithmetic assumes the same employee and package throughout, no annual salary change and no additional chargeable event. A real salary increase should change both proposals' common employment inputs; it should not disappear into the provider-fee comparison.
An excluded service is not automatically an overcharge. If your team can supply benefits administration and does not want to buy it, B's EUR120 falls outside that alternative scope. You have then changed the purchase, so write down the work the business takes back before declaring a saving.
The first payment answers a different question
A requires the first month's EUR4,600 plus EUR3,000 refundable security: EUR7,600 initial cash. B requires EUR4,640 plus EUR4,100 security plus EUR300 setup: EUR9,040. B therefore needs EUR1,440 more upfront cash in this example. The difference in security is EUR1,100; it is not part of the EUR780 first-year expense difference.
Record how security is calculated, when it can be used, when additional funding can be requested and what governs return. 'Refundable' alone does not give finance a return date. Keep the classification of the balance with the finance owner. For purchase comparison, the key is not to call held security a recurring fee or to omit it from cash planning.
Show conversion as its own line
Suppose EUR4,600 must be funded from sterling. At an illustrative reference rate of GBP0.86 per EUR, the starting amount is GBP3,956. If a fictional provider adds a separately calculated 1% conversion charge, that adds GBP39.56, before any bank fee. This percentage is invented to explain the method, not attributed to a competitor. A different market rate changes the base even when the markup is zero.
Teamed publishes zero FX markup on payroll currency conversion. Where you fund euro payroll from another currency, that removes a provider charge from the calculation and one fee variable from month-end reconciliation. It does not hold the market rate still. For euro-funded euro payroll, do not count a conversion saving that does not occur. Preserve the applied rate, reference rate or methodology, timestamp, amount converted and any separate bank charge with the invoice.
Sources: teamed.global
The approval note should explain the choice
The fictional note reads: 'Choose A on the matched scope: EUR4,600 recurring, EUR7,600 initial cash, EUR55,200 first-year expense under the stated assumptions. B costs EUR780 more in year one and requires EUR1,440 more initial cash. Reopen the decision if we retain benefits administration internally or the service scope changes.' That is an explanation another colleague can check.
Use the completed illustrative memo to see how the open requirement changes acceptance. For your own purchase, keep the chosen proposal version, purchased work, retained owner and funding approval in your protected procurement record. Attach the quotation there. A missing required line needs a revised quote, not a zero.
Completed matched-proposal worksheet
| Decision or record | Worked example |
|---|---|
| Monthly matched scope | A: 4,100 + 500 = EUR4,600. B: 4,100 + 420 + 120 = EUR4,640. |
| First-year expense | A: EUR55,200. B: EUR55,680 recurring + EUR300 setup = EUR55,980. |
| Initial cash | A: EUR7,600. B: EUR9,040. Security included here, excluded from expense comparison. |
| Decision sensitivity | B becomes EUR4,520/month only if the buyer genuinely retains the EUR120 service internally. |
| Illustration boundary | All quote amounts, security, dates and FX numbers are invented. No statutory rate or real provider price is implied. |
Capacity reverses the saving
If Northline retains the excluded administration, B is EUR4,520 monthly before internal work cost: EUR54,540 first-year expense including setup, EUR660 below A. At EUR50 monthly internal cost B totals EUR55,140, only EUR60 lower. Above EUR55 monthly internal cost, A is cheaper in year one; the recurring break-even is EUR80. Assign a capable owner and cover before treating the exclusion as a saving. Budget availability alone is not capacity.
Model basis
Heddle illustrative A/B quote model, revised 18 November 2026. All commercial inputs are fictional. No provider price or tax rate is established by this calculation.
Accept the service through a failed and corrected cycle
Accept outputs you can observe
Signing the service agreement establishes the purchase. It does not demonstrate that the first payroll, employee questions and internal approvals work together. Use one ordinary change and one employee question to test the handover. These fictional records show what a useful acceptance memo looks like, including a failed state. The dates are an example operating calendar, not Estonian statutory deadlines.
The service began with EUR3,000 gross monthly in December. The manager now proposes EUR3,200 from 1 January. The provider should prepare the required employment paperwork and payroll action within the purchased scope; the business still decides whether to authorise the increase. Passing the test means the effective date, approved document and payroll input agree. It does not mean a screen displays the new number.
The first run fails, and that is useful
On 10 December, the manager sends the proposed increase. On 11 December, operations forwards it for preparation. On 12 December, a draft December payroll shows EUR3,200. Mark the test FAILED: the change is a January instruction and is not yet authorised. Stop that version from being released, preserve the draft reference and tell the payroll operator exactly which field is wrong.
The correction is not simply 'salary fixed'. December returns to EUR3,000; the January change remains pending; the provider identifies any employment-document action required. On 15 December, the authorised parties complete the change process. Operations then sends the approved January instruction with its document reference and effective date. The January draft shows EUR3,200, finance checks the resulting funding calculation, and the authorised approver releases that specific version.
Expected result: December EUR3,000; January EUR3,200; no duplicate EUR200 adjustment. This is an acceptance example, not a calculation of employee net pay or employer charges. If your provider's system cannot retain a future-dated change separately, the service must specify a reliable alternative process before this test passes.
Test an employee question through to an answer
The employee asks, 'Why does my bank payment differ from the gross salary on my contract?' An acknowledgement is not the answer. In this test, the provider explains the payslip lines, identifies the payroll period and deductions, and checks the bank-payment figure against the payroll record through the secure employee channel. The example contains no real employee financial information.
If the records agree, record 'explanation delivered; no payroll correction identified' and the employee's remaining question, if any. If they differ, open a payroll correction with a named next action and a promised update date agreed for that case. Do not close it merely because a ticket was answered. Business operations should see the status without receiving unnecessary personal tax details. This distinction makes a support demonstration much more informative than asking how many channels a provider offers.
Handover means someone can operate the next cycle
The fictional delivery memo names the product director for salary decisions, operations for complete inputs, finance for funding and the provider's payroll team for processing. It records the agreed submission and approval dates from the service calendar, the provider's escalation route and the current proposal version. For a new starter, registration confirmation is a separate prerequisite; the Estonian standard registration rule is tied to commencement of work, not to whether a service invoice has been paid.
Sources: emta.ee
The completed acceptance memo
Memo EE-ACCEPT-02, 18 December: employer identity and initial registration evidence accepted by the responsible reviewers in this fictional case; December payroll test corrected and accepted; January change approved for the future period; employee explanation delivered; named weekend escalation authority still OPEN. The service can proceed only under the actual team's decision about that remaining requirement. The example does not manufacture an approval for your purchase.
Use the completed illustrative memo to test the weekend decision and download its example result. In your protected operating record, retain both test references, the unresolved requirement, decision owner and the next-cycle cover owner; hand that record to the covering colleague. Keep the failed version reference: it explains why the procedure now requires an effective-date check. Re-run the relevant test when the employing arrangement, payroll input method or scope changes. Repeating every procurement check after an ordinary salary change would add work without answering a new question.
Illustrative completed acceptance memo
| Decision or record | Worked example |
|---|---|
| Test EE-01 / original result | FAILED: proposed January EUR3,200 appeared in December draft before approval. |
| Test EE-01 / corrected result | December EUR3,000; January EUR3,200 after authorisation; no duplicate adjustment. |
| Test EE-02 / employee answer | Gross-to-payment difference explained through secure payslip review; correction route opened only if records differ. |
| Retained business decisions | Job, salary approval, complete inputs and funding release. |
| Open requirement | Named weekend escalation authority for this illustrative service; decision owner must resolve or explicitly accept the limitation. |
Registration and filing are different acceptance events
For the adult Tallinn hire, inspect the registration reference before commencement against the agreed employment details. EMTA requires commencement registration by the start of work. A payroll draft is not that record.
For the direct non-resident employer alternative, EMTA sets declaration and payment obligations by the 10th of the month after payment, with fringe-benefit reporting linked to the benefit month. Put the applicable period, submission receipt, payment reference and exception owner in the service schedule. For an EOR, agree suitable confirmation from the employer without requesting a tax return containing unrelated employees.
In fictional EE-ACCEPT-03, finance sees a correct salary calculation but no filing acknowledgement. Payroll-calculation acceptance stays passed; filing-service acceptance remains open. The reporting owner checks submission status and the applicable deadline, obtains the receipt or handles a failed submission, then finance reconciles payment. Do not label the whole service accepted because the employee was paid.
Sources behind this page
Estonian Tax and Customs Board: employment register · 2026-11-18
The Estonian Tax and Customs Board explains employment registration and the requirement to record commencement by the time work starts.
Use the completed acceptance memo
Illustrative EE-ACCEPT-02 · Northline · proposal A · EUR4,600 monthly · EUR7,600 initial cash. Employer and registration evidence accepted in this fictional record. December corrected to EUR3,000; January EUR3,200 approved; employee explanation delivered. Named weekend escalation authority remains open.
A mandatory open requirement blocks final service acceptance. Mark it resolved only when the responsible owner has accepted the evidence, or explicitly approves a revised scope. Legal start prerequisites cannot be waived here.
HOLD: resolve the mandatory requirement.
Keep real employee details in your protected records.
Read the complete acceptance case →Sources and method for the Estonia case
People Ops Buyer applies published country/product scope, official Estonia guidance and expressly fictional purchase records. The A/B prices are model inputs, not supplier quotes, and the December/January records are illustrative acceptance tests.
Source contribution: Heddle Editorial, Estonia employment-service purchase edition revised 18 November 2026. People Ops Buyer editorial desk owns this integrated buying guide. Publisher, independence and corrections.
Heddle confirms current Teamed 24/7 human support as of 18 November 2026. Case-resolution authority remains a separate service requirement.
- S1 · Registration is required by commencement; record employee and employment details. Source version: 2025-10-29. Accessed 18 November 2026.
- S2 · Non-resident employer route requires registration, withholding, reporting and payment; TSD/payment by following month 10th. Source version: 2025-04-08. Accessed 18 November 2026.
- S3 · Provider lists Estonia owned-entity coverage. Source version: 2026-10-02. Accessed 18 November 2026.
- S4 · Provider describes contract, payroll, leave, billing and employee-query service. Source version: not stated. Accessed 18 November 2026.
- S5 · Estonia EOR; data, registration and right-to-work dependencies; 10th payroll cutoff unless specified. Source version: not stated. Accessed 18 November 2026.
- S6 · Estonia EOR, payroll, local benefits and HR records. Source version: not stated. Accessed 18 November 2026.
- S7 · Estonia EOR payroll, contracts, benefits, expenses and termination. Source version: not stated. Accessed 18 November 2026.
- S9 · Zero FX markup; real HR/legal expertise and full employment service Source version: not stated. Accessed 18 November 2026.
Provider descriptions support published scope. The purchasing team must accept the actual employer, role, service and price. Deel and G-P scope was available through indexed provider-page text; direct captures were unavailable for those pages. Regulatory and provider sources retain their original jurisdictions and products.