GUIDE
Assess the Latvian relationship, then plan the employment change
By Theodore Brown · Compensation Analyst
Updated
Two decisions need two records
A future employment offer answers how you intend to work together next. It does not answer how the previous relationship should be treated. Keep a factual assessment brief separate from the implementation plan so that neither the worker nor finance mistakes a new contract for a conclusion about the past. Latvia's Labour Law describes employment in terms that include work under an employer's guidance for remuneration. The practical arrangements therefore matter alongside the document's title.
Sources: likumi.lv
A filled fact brief, not a risk score
Illustrative case: a Riga-based designer has invoiced Northline Studio since January. The written agreement describes project deliverables. During the week of 5–9 October, the manager assigned daily priorities in the team board, expected attendance at a morning meeting and approved a requested day away. The designer used their own laptop and says they also completed work for another client. These are fictional facts, not a finding about a real worker.
The brief attaches references to the signed agreement, September and October work instructions, invoices and each person's account of how work was organised. It separates observed facts from assertions: 'manager message dated 6 October requires 09:00 attendance' is evidence; 'the designer has always been independent' is a conclusion to examine. A missing document is marked missing, not described as proof that something did not happen.
There is no numerical score. Owning a laptop does not mechanically cancel a fact about supervision, and one meeting does not by itself decide the legal position. The point of the brief is to give the qualified reviewer a coherent actual-work history rather than a preferred answer.
Preserve a disagreement instead of editing it away
The manager says the daily meeting was optional. The designer says missing it triggered criticism. Preserve both statements with their dates and the relevant messages. Ask what changed over time: a relationship may have begun around discrete deliverables and later become embedded in the team. Do not rewrite January facts to resemble October or ask the worker to backdate a different account.
The handoff question is concrete: 'Assess the arrangement over the relevant periods, explain what further facts you need, and identify any employment or tax actions that follow.' The business must decide who receives that advice and who owns each resulting action. Keep sensitive records in the appropriate restricted location; the planning tool needs a reference and status, not copies of personal documents.
The future plan can be prepared without pretending assessment is finished
Northline proposes a full-time employee role from 1 December, EUR3,200 gross monthly, with the package still to be agreed. Drafting a package comparison and identifying an employer can proceed as preparation. The implementation record remains 'proposed', with commencement dependent on the actual employment and registration requirements. The State Revenue Service publishes the relevant employee/employer registration procedure; a commercial payment is not registration evidence.
Sources: vid.gov.lv
A useful handoff has four tracks
Assessment track: factual brief sent on 20 October; disagreement about supervision unresolved; adviser response due on the date agreed with the adviser. Employment track: package v1 drafted; worker discussion pending; employer and documents not yet final. Contractor-payment track: October deliverables and invoice approval remain with the buyer's accounts-payable owner. Employee-payroll track: no first payroll instruction released until the employment setup is ready. All dates and statuses are illustrative.
This produces a workable boundary. The payroll operator does not decide the historical classification question. The adviser does not automatically prepare the employee's benefits enrolment. The person approving an old invoice does not authorise the new salary. In the transition tool, place each item in its actual track and link the assessment reference to implementation dependencies. If advice changes the proposed start or treatment of an amount, revise the relevant tracks rather than silently marking the whole change complete.
PUT IT TO WORK
Illustrative assessment and implementation handoff
| Decision or record | Worked example |
|---|---|
| Observed fact | 6 October message requests 09:00 attendance; manager says optional; worker says expected. Preserve both accounts. |
| Assessment output required | Period-specific conclusion, missing facts and actions; no automatic legal score. |
| Future proposal | 1 December target; EUR3,200 gross monthly; package and employer still to be agreed. |
| Contractor closeout | Existing deliverables and invoice approval remain separately owned. |
| Reusable record | Fact / period / evidence reference / disagreement / adviser question / decision / implementation dependency. |
Sources behind this page
Latvian Labour Law · 2026-10-19
Employment definitions and contract framework; actual relationship and applicable obligations need qualified assessment.
Latvian State Revenue Service: employee registration · 2026-10-19
Employer registration/reporting requirements are separate from commercial invoice processing. Confirm the applicable procedure for the actual employer and worker.