An Estonian employment-service purchase pack

The purchase is a service, not permission to hire

A good purchase pack lets three colleagues make three different decisions: the manager approves the role, finance approves the cost and funding, and the responsible reviewer accepts the employing arrangement. It also tells the person running payroll what was actually bought. The example below is a fictional adult hire, with invented company names, dates and commercial assumptions. It is a model to adapt, not an approved Estonian employment arrangement.

Northline Studio wants an analyst working in Tallinn from 1 December 2026. Its operations lead can supply accurate inputs and approve changes, but cannot administer Estonian employment alongside her other work. The buying question is therefore specific: who prepares the employment documents, operates payroll and resolves employee questions, while Northline retains decisions about the job and budget? A portal login alone does not answer it.

The completed brief you can copy

Brief EE-01, version 2, 19 October: one analyst; Tallinn workplace; proposed full-time working pattern; manager: product director; proposed gross salary: EUR3,000 per month; target start: 1 December; intended employer: the provider's identified Estonian employing entity. The salary is an example budget input, not a market benchmark.

Purchased outputs: employment documents reflecting the accepted package; a payroll input calendar; responsibility for employment registration; payroll calculation and employee payment under the agreed service; an employee-question route with an escalation contact. Northline supplies the job description, approved package, manager and required worker information through the provider's secure intake. It retains equipment provision, day-to-day management, business approval of salary changes and funding approval.

Acceptance example: a change from EUR3,000 to EUR3,200 effective 1 January must appear in the correct payroll period after approval. A question about a payslip must receive an explanation of the disputed line and an identified corrective action if required. The proposal must say which team does these things; the brief does not invent a response-time guarantee.

Connect the brand to the actual employer

The entity map has three rows. Northline Studio is the service buyer. The provider's contracting company signs the service agreement. The Estonian employing entity signs the employment contract. Put legal names, registration codes and document references beside those rows; do not replace them with a provider logo.

For the fictional pack, the employing-entity row remains OPEN until the actual name and code are supplied and matched against the Estonian e-Business Register. That is a sensible blocker: the buying team cannot approve an unidentified employer. It is different from a missing marketing brochure. The employment-registration row states that the employer performs the step and provides confirmation before work starts. The Tax and Customs Board's standard rule is registration no later than commencement; special cases require their own check.

Sources: ariregister.rik.ee · emta.ee

Answer the objections that actually hold up approval

Finance asks, 'Does EUR3,000 buy the whole service?' Answer: no. It is gross salary; the matched proposal separates employment costs, provider charges, any cash security and funding dates. Approval stays open until the total and initial cash requirement are visible.

Legal asks, 'Why is the service-agreement company different from the employer?' Answer: show both parties and their contractual roles in the entity map. The reviewer accepts the documented arrangement or records the precise missing explanation. Do not infer a defect merely from two names.

Privacy asks, 'Where is the processor agreement?' Answer: first map the employee-data flows and actual roles. The EDPB distinguishes roles by who determines processing purposes and means. A procurement template cannot settle the role by itself. The fictional pack sends identity documents through secure onboarding, keeps only an evidence reference in the purchase memo, and assigns the privacy reviewer the role/document decision.

Sources: edpb.europa.eu

A decision memo with a useful stopping point

The fictional 19 October memo reads: role and salary budget accepted by the product director; employing entity OPEN pending legal name and register match; commercial approval OPEN pending matched cash schedule; privacy OPEN pending role assessment. Purchase not authorised. This is an honest finished output, even though the decision is not yet yes.

When the missing answers arrive, change those particular rows and attach proposal version 3. Do not create a fresh disconnected checklist. In the service acceptance tool, use mandatory requirements for employer identity and funding terms, purchased work for documents/payroll/support, and retained decisions for salary approval and equipment. Export the memo with the proposal reference so delivery inherits the same purchase. If a new stakeholder requests a requirement, state what risk or buying decision it changes before adding another approval stage.