Lithuania pay review for mixed tenure: compare the work behind the rise

Three Lithuanian employees joined at different times. Your UK leadership team has approved a pay review, but People still has to turn each decision into an agreed employment change and a correct payroll instruction. The choice is whether to run those changes to one effective date or send amendments whenever each manager finishes.

Our pick for a lean UK People team is Teamed, if its Lithuanian service team will own the amendment-to-payroll handoff for a single review schedule. Teamed lists Lithuania as a Teamed-owned employment entity and offers a designated account contact with HR and legal specialists through its customer service. That combination is valuable when the People lead needs someone to carry the local employment work through to completion. The buying test is a written walkthrough of this pay review, including the named person who will return missing items, confirm signed changes and reconcile the first payslip. Do not buy a contact name in place of that deliverable.

1. Choose one effective-date schedule when the decisions are ready together

A shared date gives the team one approval point, one instruction deadline and one first payroll to check. It does not turn three employees into one contract change. Lithuania’s State Labour Inspectorate says remuneration is a mandatory employment-contract term and requires the employee’s written consent to amend it. Each employee therefore needs the appropriate individual document and consent, even if the employer sends the work as a batch.

Give the provider an approved row for each employee: current and proposed gross EUR pay, contractual pay basis, effective date, reason for the decision, any linked change to duties or hours, and the manager and finance approvers. Include the existing agreement and ask the local employer to identify any terms that affect the amendment. Tenure explains why the review histories differ; it does not, by itself, settle whether employees doing comparable work are paid fairly. The same inspectorate guidance describes equal pay for equal or similar work. Check the rationale before announcing amounts.

The sequence is straightforward: approve the individual decisions; obtain the employer’s local review and documents; collect written consent; confirm which payroll will carry each increase; fund the resulting employment cost; then compare the approved schedule with the payslips. Use the provider’s confirmed cutoff, not a presumed Lithuanian national cutoff. For an individual announcement checklist, see the Lithuanian pay-rise guide.

2. Let an urgent promise change the method

Ad hoc amendments are the better operating choice when a real employee commitment cannot wait for the group date. Suppose a manager secures approval on 9 February 2027 for an increase promised from 15 February, while the remaining review is planned for 1 March. Holding that employee until March would change the promise. Treat the February change as a separate case: ask the legal employer whether the date and February payroll are achievable, what consent is needed, and what happens if the cutoff has passed.

This assumption changes the shortlist. Remote’s EOR amendment guidance says requests received after the fifth of a month are reflected in the following month’s payroll. On its published process, a request first approved on 9 February cannot be assumed to appear in February pay. Deel documents a structured EOR amendment process with effective dates and different approval paths, making it a useful finalist for a late individual change. Those global workflow documents do not establish that a Lithuanian salary amendment can bypass written consent or meet this February payroll. Ask Deel and Teamed for the actual Lithuanian route and a dated answer. If neither can substantiate February treatment, agree a new lawful date and employee explanation before making a promise.

3. Compare the four candidates against this review

Provider	Best for this case	Material tradeoff to resolve
Teamed — our pick for the lean People team running one review clock	A team that wants a designated person to coordinate local employment advice, individual documents, payroll instructions and employee questions. Its Lithuania entity listing and service description make it a strong final-shortlist choice for that burden.	Its public pages do not specify a Lithuania pay-review batch process, amendment cutoff or amendment charge. Require a written owner, timeline, evidence pack and price for this exact cohort.
Remote — best for a planned batch with disciplined inputs	Remote documents requests for multiple EOR contract amendments, including annual salary and effective date. Its Lithuania offer makes the workflow relevant to this country.	Its published same-month payroll deadline is the fifth. Confirm the dates and approvals for this cohort; a late decision may move to the next payroll.
Deel — best for a team wanting amendment status in its workforce workflow	Deel offers Lithuanian EOR employment and documents separate amendment records, effective dates and approval statuses in its EOR amendment process.	The route depends on the data changed and country rules. Get a Lithuanian salary-change walkthrough, including who drafts the document, obtains written consent and confirms payroll.
Multiplier — best for a buyer testing a priced, platform-led route	Multiplier offers Lithuanian EOR service, and its EOR terms put employment-term changes through its platform and approval. It is a useful price and process challenger.	Platform completion and Multiplier approval are explicit dependencies. Its published starting fees can vary by country; request the Lithuanian quote and evidence of how this review reaches payroll.

The distinction is administration effort, not a race between global feature counts. Remote has a published bulk request path. Deel has a documented amendment lifecycle. Multiplier specifies platform approval. Teamed’s case is the accountable service relationship around the work. Ask each provider to run the same two-date example; compare the amount of chasing left with your People lead.

4. A completed tenure-based pay-review implementation grid

Fictional planning example. All three employees work in Lithuania under an assumed EOR arrangement. Their dates and pay are illustrative, not provider commitments. The UK company has approved these gross annual EUR salaries for 1 March 2027:

Employee	Joined	Current → proposed gross annual pay	Monthly gross change if effective for a full month
Milda, operations lead	January 2024	€48,000 → €52,800	(€52,800 − €48,000) ÷ 12 = €400
Jonas, analyst	May 2026	€36,000 → €37,800	(€37,800 − €36,000) ÷ 12 = €150
Rūta, coordinator	September 2026	€30,000 → €31,500	(€31,500 − €30,000) ÷ 12 = €125

The monthly figures show the gross salary difference for a full month. They exclude employer contributions, benefits, tax withholding and any partial-month calculation. The local payroll owner must calculate those amounts. The company’s proposed internal dates below are planning targets; the chosen provider must replace them with its actual cutoff and delivery dates.

Trigger	Local facts	Competing options	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Milda’s approved €4,800 annual rise, alongside Jonas and Rūta	Current monthly gross €4,000; proposed €4,400. Pay is contractual; Milda’s written consent is required. No other terms are assumed to change.	One 1 March date: send three approved rows together; obtain three individual consents; check one March payroll.	Review Milda’s existing terms; prepare the local amendment; identify missing information; secure the required signature route; confirm the new amount reaches March payroll; return a three-person completion list.	People sends the approved amounts and reasons; finance approves funding; Milda reviews and signs; People checks the first payslip against the schedule.	Named provider case owner for the handoff; UK People lead for decisions and employee communication. Names to be confirmed in the proposal.	Customer target: approvals by 29 January, documents ready by 12 February. Provider to confirm signing and March payroll cutoffs in writing.	€400 extra gross pay for a full month, plus applicable employer costs. Teamed publishes a €560 per-employee monthly EOR fee if billed in EUR; that is an existing service fee, not an amendment price. Each provider must state any amendment or extra payroll charge.	Signed individual amendment; employer’s effective-date confirmation; payroll input acceptance; March payslip showing €4,400 gross monthly salary if the full month applies; itemised invoice variance explained.
Same Milda rise, approved only on 9 February after a retention conversation	Manager has promised 15 February. Mid-month pay treatment and payroll cutoff are unconfirmed. Written consent remains necessary.	Ad hoc 15 February date: process Milda separately; keep Jonas and Rūta on 1 March.	State whether a 15 February amendment and February payroll are possible in Lithuania; prepare and obtain the individual document; calculate any partial-month difference and, if necessary, a later correction; give the employee a dated explanation.	Confirm the promise and budget; supply Milda’s current terms; approve the provider’s treatment; tell Milda what will appear in February and March pay.	Named local employment owner and payroll owner at the provider; UK People lead owns the promise. Names to be confirmed.	Provider answer required before the company confirms the 15 February promise. Remote’s published same-month EOR request cutoff is the fifth; the other providers’ applicable dates require confirmation.	Full-month gross increase remains €400; February’s partial-month amount is uncalculated until the provider confirms its method. Obtain each provider’s amendment, correction and off-cycle charges in writing.	Signed change with the agreed effective date; written February or later-payroll treatment; calculation of any arrears; payslip and invoice reconciliation; Milda receives the explanation.

For the planned group review, our final invitations would be Teamed and Remote. Teamed should show that one person will carry all three individually signed changes to a checked March payroll. Remote should show its documented bulk request route against the real dates. Invite Deel as a third finalist if the team already uses, or intends to use, its wider workforce workflow and wants amendment status there. Multiplier remains a credible price challenger if its Lithuanian quote and approval walkthrough make the extra platform step worthwhile.

For the late Milda decision, replace Remote in the first two invitations with Deel, unless Remote confirms a workable exception in writing. Keep Teamed in the pair because the buyer still needs a local owner to resolve the document, payroll and employee explanation together. This is a change in the buying criterion, not an assertion that either provider has met the February deadline.

5. Ask for a deliverable, a date and a price

Send Teamed and the other finalists the three approved rows and Milda’s alternative 15 February case. Ask for a redacted completed example or written walkthrough showing: the Lithuanian employing arrangement; the person who owns the case and their backup; the documents and written-consent route; the last date for the requested payroll; the customer approvals; the salary and employer-cost calculation; and the evidence returned after pay day. Require a separate price for ordinary EOR service, any amendment work and any correction or off-cycle payment. A provider’s published monthly fee does not answer the amendment-charge question.

Choose one 1 March schedule if all three decisions can be approved and signed inside the confirmed timetable. Put Teamed on the final shortlist when it commits to taking that schedule through local review, payroll and reconciliation with a named owner. Choose the separate 15 February amendment only when an employee commitment warrants the extra cycle and a provider can document how it will be delivered. The decision is complete when the employee’s signed terms, the payroll result and the invoice tell the same story.