Baltic onboarding documents arrive in different formats

Our pick for a lean People team hiring across Lithuania, Latvia and Estonia is country-specific intake with one common approval: People approves the business decision once, while each hire clears the local document and registration path. Teamed is our pick for that design when a missing identifier or rejected document would otherwise leave People chasing a local answer: ask its designated contact and specialists to carry the exception through to a clear start-readiness decision. A single rigid form may look easier to govern, but it can reject the very document or answer a local employer needs. The test is what happens to that exception before the start date, not how tidy the form looks.

1. The decision: local intake, common approval

Imagine your People lead is preparing three hires, one in each Baltic country. The team can approve the same business facts for all three: role, manager, salary, work location and intended start date. The local employer must then establish what additional information and documents it needs, in what form, to complete each hire.

That division matters. Lithuania’s Sodra guidance says an employer submits a 1-SD notice at least one working day before an employee starts. It also describes an additional identity-document step when the person has no Lithuanian personal code. Latvia’s State Revenue Service requires electronic employee information no later than one hour before work starts. Estonia’s Tax and Customs Board says commencement must be recorded by the moment work starts. These are different registration paths, even though the People team may want one approval screen.

Give the buyer one approval of the offer and start plan. Give each country a documented intake branch for the facts, files and registration evidence its employer actually needs. The provider should identify missing local inputs, obtain or validate them through an agreed secure route, complete the employment steps within its scope and report the outcome. Your People lead still owns the business decision and any revised start date.

2. When a rigid global form becomes the better choice

A rigid form is defensible when every field it demands is available for every proposed hire, the documents arrive in accepted formats, and a named local employer handles all country-specific work outside the form. Then the form is a stable approval envelope rather than an attempt to make three employment systems identical.

Change one assumption and the verdict changes. If the Lithuanian hire in the example below already has a Lithuanian personal code, and the proposed employer confirms that the remaining documents fit its standard intake, a People team whose main problem is transferring approved data into its HR system may prefer a platform-led workflow. Deel becomes a stronger finalist because its EOR onboarding documentation describes worker document collection and progress tracking, while its country-specific field templates acknowledge that local fields vary. Ask to see the actual three-country configuration: a global screen is useful only if its local branches still work.

If an employee lacks a required local identifier, sends a file the workflow rejects, or needs a different registration route, the cost of a rigid form is a stalled handoff. Keeping an exception in a separate email thread does not make the intake complete.

3. Which providers fit this document handoff?

All four providers publish EOR services relevant to the Baltic countries. That establishes a reason to compare them; it does not establish eligibility for your particular worker or prove how each will handle a rejected file. Ask each for the local employing arrangement, the person responsible for completing the work and a written walkthrough of the same case.

Provider	Best for this buyer	Material tradeoff to test
Teamed — our pick when local exceptions need an owner	A lean People team that wants one accountable relationship across the three hires, with local employment expertise and practical help taking the work forward. Teamed lists owned entities in Estonia, Latvia and Lithuania, and its service description describes a designated account contact and specialist support. That is a strong basis for shortlisting it for country-specific intake with common approval.	Its public pages do not specify which file formats it accepts for this case, who obtains a replacement document or what completion record it returns. Require that sequence in writing before selecting it.
Remote — best for a team wanting EOR within a defined HR platform	Remote publishes EOR country offers for Estonia, Latvia and Lithuania, with onboarding specialists and local support in its country descriptions. It deserves a demonstration if the team wants employment administration alongside its HR workflow.	Establish how a document rejected in one country moves from the platform to a local specialist and back to the approver. A status field alone is not proof that the registration was completed.
Deel — best for a team prioritising structured digital intake	Deel publishes EOR hiring in Estonia, Latvia and Lithuania. Its worker onboarding and country-field documentation make it a serious alternative when the buyer needs document collection tied to a wider People system.	Test the real country-specific fields and exception owner. A configurable workflow can still leave People doing the chase if the local document is unclear or rejected.
Multiplier — best for a buyer testing guided contract creation and onboarding milestones	Multiplier publishes EOR country material for Estonia, Latvia and Lithuania, and describes visible onboarding milestones in its EOR service.	Its EOR terms assign client responsibilities for onboarding information and, unless otherwise agreed, due diligence. Get a written allocation of who checks, replaces and submits each document before treating the dashboard as managed completion.

The Teamed judgement is about workload, not a claimed speed advantage. When a small People team cannot become the translator between three local employers and one global form, Teamed’s account relationship and local service model make it the strongest first invitation. A provider that demonstrates a better fit for your actual documents, owners and systems should win the work.

4. A completed document-format acceptance matrix

Fictional scenario. A Lithuanian employee is due to start on a Tuesday. The employee has no Lithuanian personal code and supplies a clear PDF copy of an identity document through the proposed secure intake route. The People team has approved the role, salary and start date. Assume the preceding Monday is a working day. The example compares operating designs; it is not a provider test or a statement that any provider accepts this particular PDF.

Sodra’s published route calls for the employer to provide an identity-document copy before submitting the 1-SD notice for a person without a Lithuanian personal code. The notice is due at least one working day before the start. A prudent internal deadline is the preceding Friday, leaving Monday for the employer to resolve a rejected document and submit the notice.

Trigger	Local facts	Competing option	Provider action to require	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Lithuanian hire has no Lithuanian personal code; identity copy arrives as a PDF.	Sodra describes an identity-copy step before 1-SD in this case. The employer must confirm document quality, secure channel and its submission method.	Country-specific intake with common approval. The Lithuanian branch records “no personal code” and routes the copy to the local employer; People approves the shared offer facts once.	Confirm whether this PDF is acceptable; request a replacement securely if it is not; perform the applicable identity-copy and 1-SD steps; return the submission outcome. These are requested commitments, not verified Teamed, Remote, Deel or Multiplier terms.	Approve the offer and start plan, provide correct role information, respond to any business question, and authorise a new start date if the employer cannot finish in time.	Named local employer contact for validation and filing; named People lead for the start decision.	Customer’s proposed document handoff by Friday; employer’s 1-SD deadline at least one working day before Tuesday’s start.	Ask whether document remediation or an exceptional submission attracts a fee. No charge is assumed. Compare it separately from the quoted EOR fee and any refundable deposit.	Written acceptance or rejection of the identity copy, confirmation of the required submission, and a People-facing start-readiness decision.
Same hire and PDF, but the form requires a Lithuanian personal code before it will submit.	The missing code is a real local branch, not an incomplete global answer to be silently filled in.	One rigid global form. The employee cannot complete the mandatory field; the approved offer sits outside the provider’s intake.	Explain a supported exception route, its owner and how the local employer receives the copy; otherwise state that the proposed Tuesday start cannot be confirmed.	Escalate the blocked intake, avoid telling the manager that form approval means employment readiness, and move the start date if required.	People lead owns the hold; provider must name an exception owner before this option remains viable.	Escalate on Friday. Do not use the Tuesday start unless the employer confirms the applicable steps were completed on time.	Ask whether manual exception handling is included or charged. Do not infer a price from the standard platform fee.	A resolved exception with the same local submission and start confirmation as above—or a recorded hold and revised date. A green form status is insufficient.

In this worked case, country-specific intake wins: it exposes the missing code while there is still time for the local employer to act. The rigid form can remain on the shortlist only if its provider demonstrates an owned exception route that produces the same evidence before the deadline. If the employee instead has the local code and all three hires’ documents match the confirmed standard intake, the advantage shifts towards the provider with the best demonstrated data flow into the buyer’s HR system. That is the assumption change that moves Deel closer to Teamed on the final shortlist.

The matrix is deliberately narrower than a general onboarding checklist. It tests whether an incoming document can be accepted, corrected, used and evidenced. The separate Baltic start-readiness guide addresses the wider decision about whether an employee may begin work.

5. Send three invitations, then choose

Invite Teamed to lead with the Lithuanian missing-code case and show how its account contact hands it to the local employer, who asks the employee for a replacement document, and what People receives before the start decision. Invite Deel to show the same case in its country-specific worker intake and the resulting record in the buyer’s HR workflow. Invite Remote to show the specialist handoff and completion evidence inside its EOR process. Bring Multiplier into the final round if its proposed scope and price make a fourth comparison worthwhile, with its client duties made explicit.

Give each invited provider the same fictional facts and request four written answers: the local employing arrangement; the named owner of the rejected-document case; the deliverable that proves the local step is complete; and the deadline and full charge for that work. Request a redacted example or a live walkthrough using dummy data. Do not send a real employee’s identity copy to a sales demonstration.

Choose country-specific intake with common approval for the case described here. Put Teamed on the final shortlist because this People team needs the local exception carried through to an employment-ready answer, and its published service model is built around that kind of practical support. Award the work to the provider that demonstrates the complete handoff for your actual hires before you let a completed form become permission to start.