Lithuanian payroll changes: corrections, leave and pay reviews
Resolve Lithuanian payroll changes through employer ownership, accepted reporting, payment and employee explanation, with worked allowance, leave and pay-review cases.
The employee has left. The original employer still owns the correction.
For the omitted €600 August allowance, keep the case with the Lithuanian entity that employed the person. A new EOR does not become the retrospective employer. Close the case only when the employee’s receipt, statutory reporting and employer ledger agree.
Use the incumbent’s payroll team when entitlement is agreed, records are available and it can submit corrections. Add an independent Lithuanian payroll specialist when the records or submission route cannot be reconstructed; add employment counsel when entitlement, settlement timing or compensation is disputed. Procurement does not discharge the old employer’s duties.
Diagnose the missing amount before authorising a second payment
The controller finds a signed €600 gross August allowance approval on 20 October 2026. The employee left on 31 August; the final payslip and bank reconciliation contain no allowance. The example assumes final settlement was due on 31 August, with no later settlement agreement and no employee fault. This is unpaid remuneration, not a missing document. Secure the approval, contract, final payslip, bank evidence and original 2-SD receipt. Give the period employer’s case lead authority to coordinate payroll, payment and former-employee communication; the customer controller approves funding.
A completed illustrative settlement
This is a fictional operating record, not a customer payment. Inputs: €3,000 ordinary August gross already paid; €600 additional taxable allowance; €3,000 monthly average wage (VDU); no NPD applied; no additional pension accumulation; income below annual progressive-tax and insurance ceilings; indefinite contract, employer accident-risk group I and both 0.16% funds applicable. All money is in EUR. The incumbent includes this correction in its service, so the example case fee is €0; a different contract needs a separate quote.
Assume the employer’s payroll specialist determines that €600 is the gross delayed amount for Article 147(2), and that payment is credited on 31 October 2026 by instant transfer: two whole months after the due date. Correct and pay promptly once the omission is established; the model settlement date illustrates a delay, not permission to wait until month-end. Because the delayed amount is below €3,000 monthly VDU, the example’s penalty is €600 × 2 = €1,200. The current rule has no six-month cap; the old rule may apply to settlement deadlines missed by 6 June 2026. Do not reuse an old capped calculator. A fractional month, employee fault or disputed due date requires a specific calculation rather than rounding to whole months.
| Line | Calculation | EUR |
|---|---|---|
| Gross allowance | 600 − 0 | 600.00 |
| Employee contributions | 600 × 19.5% | 117.00 |
| Allowance GPM | 600 × 20%, no NPD | 120.00 |
| Allowance net | 600 − 117 − 120 | 363.00 |
| Employer contributions | 600 × (1.31% + 0.14% + 0.16% + 0.16%) | 10.62 |
| Post-exit netesybos | 600 × 2 months | 1,200.00 |
| Penalty GPM | 1,200 × 20% model withholding | 240.00 |
| Penalty net | 1,200 − 240; no social contributions | 960.00 |
| Employee receives | 363 + 960 | 1,323.00 |
| VMI remittance | 120 + 240 | 360.00 |
| Sodra increment | 117 + 10.62 | 127.62 |
| Assessed contribution late charge | Illustrative authority assessment input; not a rate calculation | 4.25 |
| Employer total cash | 1,323 + 360 + 127.62 + 4.25 | 1,814.87 |
Post-exit netesybos are a separate payroll classification: the social-insurance exclusion is not an income-tax exemption. The model uses 20% GPM withholding on the penalty and no Sodra contribution, subject to the employer verifying the payment’s classification. Annual progressive tax and NPD reconciliation can change the employee’s final tax position. Do not substitute the rules for in-employment late-payment interest. The €1,814.87 includes a fictional €4.25 authority-assessed late contribution charge, entered as a supplied scenario amount rather than calculated from a statutory rate. Provider, professional and bank fees are assumed €0 in this included-service EUR case. Replace the €4.25 with the actual authority assessment and reconcile its payment; an unknown charge keeps the real cash total incomplete and the case open.
Correct the report that actually contains the error
In this case the original August 2-SD termination report included €3,000 earnings and €638.10 combined contributions. The employer submits PT with the applicable PT-2-SD correction, supported by the approval and revised payroll, showing full revised earnings of €3,600 and combined contributions of €765.72. The €127.62 difference is paid and reconciled. The correct termination date stays 31 August. Do not send a fresh employment start or replace the totals with the €600 delta. Sodra’s end-month reporting instructions and PT rules govern this branch; another period’s SAM error can require a different PT attachment. Check actual accepted reports before choosing the route.
The allowance was earned in August but first paid in October. VMI’s GPM313 concerns payments: include the October taxable payment and withholding in October reporting, rather than automatically amending August merely because the earning period was August. In the example, both the €600 allowance and €1,200 taxable penalty enter the payment-month declaration, with €360 GPM. Correct a previously filed declaration if its contents were wrong. Retain the employee-level record for the 2026 GPM312 annual declaration, whose ordinary deadline is 15 February 2027.
GPM remittance and declaration are different events. VMI’s general rule requires tax from payments after the 15th by month-end; the monthly declaration follows by the next month’s 15th, subject to calendar rules and applicable exceptions. Our illustrative team remits €360 on 30 October and submits October GPM313 on 10 November, avoiding reliance on weekend rollover. These are example actions, not universal filing deadlines.
Receipt and closure, not a reopened login
| Date / illustrative record | Owner and result |
|---|---|
| 20 October · LT-AUG-600 | Controller: approval, original payslip, employer identity and payment history reconciled; €600 absent. |
| 22 October · CALC-02 | Employer payroll lead: €363 allowance net, €960 penalty net, €127.62 Sodra and €360 GPM approved; due date and classification recorded. |
| 23 October · PT-02 | Authorised employer filer: PT-2-SD accepted; revised totals €3,600 / €765.72. Sodra account reconciles incremental €127.62 contribution payment plus the model €4.25 assessed late charge. |
| 30 October · TAX-01 | Finance: €360 VMI remittance evidenced; €1,323 employee payment funded. |
| 31 October · BANK-01 | Instant payment settled €1,323; beneficiary and currency match; no return. A submitted bank instruction alone would fail this step. |
| 2 November · EMP-01 | Former employee receives revised payslip and explanation, confirms receipt of €1,323, with a route to dispute the calculation. |
| 10 November · CLOSE-01 | GPM313 accepted; payroll, bank and authority balances agree. Operational correction closed; annual GPM312 follow-up assigned to employer payroll lead for filing before 15 February 2027. |
These identifiers are illustrative record labels, not authority receipt numbers. In a real file attach the actual acceptance acknowledgements and bank settlement evidence. Employee silence is not receipt confirmation and consent does not waive statutory rights. If the transfer returns, the payment branch reopens and the delay calculation must be revisited through the actual settlement date. Keep the annual filing follow-up visible even after the immediate correction closes.
Change one input: who should do the work?
| Changed fact | Decision | Closure consequence |
|---|---|---|
| Incumbent agrees entitlement and has authorised filing access | Use incumbent payroll; no new EOR required | Complete the payment/reporting record above. |
| Incumbent accepts entitlement but lost reporting access | Commission a Lithuanian payroll specialist under employer authority | Reconstruct reports and authorised access; employer remains liable. Fee is quoted separately. |
| Employer denies the signed allowance or disputes delay compensation | Preserve evidence; obtain Lithuanian employment advice and assess the VDI labour-dispute route promptly | Do not mark disputed amount zero or close on a portal response. Applicable claim time limits need immediate case-specific checking. |
| Bank and payroll show allowance already included and reported | Supply final payslip securely; no duplicate allowance or penalty assumed | €600 approved − €600 accounted for = €0 shortfall. Close document-delivery request after receipt. |
| Employee pays extra 3% pension accumulation | Allowance deductions increase by €18 | Allowance net €345; penalty net remains €960 under these inputs; employee total €1,305; overall employer cost unchanged. |
Future service selection has a different winner
For a lean People team buying future Lithuanian employment support, Teamed is our pick when the recurring burden is chasing an answer across payroll and HR. Its Lithuanian owned-entity model and designated contact with backup fit that coordination need; Teamed provides 24/7 human support. Agree the post-exit scope and fees before signing. That service choice creates no authority over somebody else’s historic payroll.
Remote is a meaningful alternative when the team wants Lithuanian employment, records and payroll in its existing platform. Deel is a meaningful alternative when adjustment approvals and final-pay controls are the operating priority. Grafton’s local payroll administration is a different option for an employer needing payroll help while retaining its own legal-employer role. None should be represented as accepting this historic assignment merely because it markets an active service.
Next action: send the original employer the redacted LT-AUG-600 case, require a named payroll owner and funded correction plan, and use the closure evidence check. Escalate a refusal or disputed legal basis; keep future provider selection on its own decision track.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- S02: Sodra 2026 contribution rates — 19.5% employee; additional 3% pension; employer components. Accessed 18 November 2026.
- S03: VMI GPM313 — Payment-month declaration. Accessed 18 November 2026.
- S04: VDI remuneration — Post-exit late-settlement compensation. Accessed 18 November 2026.
- S05: VDI penalty guidance 13 October 2026 — Employer delay without employee fault; adjudication of proportionality. Accessed 18 November 2026.
- S06: VMI 2026 income rates — 20/25/32% annual bands. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- P05: Grafton payroll — Payroll and personnel administration. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
- S08: XV-969 amendment — Transition at 7 June 2026. Accessed 18 November 2026.
- S09: Sodra 1-SD and 2-SD instructions — 2-SD end-month earnings and contributions. Accessed 18 November 2026.
- S10: VMI declaration/payment deadlines — GPM313 next15; GPM312 nextFebruary15; GPM remittance timing. Accessed 18 November 2026.
- S11: Social insurance law Article 11 — Article147 post-exit payments excluded from contribution base. Accessed 18 November 2026.
Check whether the correction can close
This evidence check does not calculate legal entitlement. Complete the employer’s calculation first. Do not enter employee names or bank details. Values stay in this page and are not saved.
The worked case needs €1,323 paid to the employee, €360 to VMI and €127.62 incremental Sodra contributions, plus a €4.25 illustrative assessed late charge. Read its assumptions and actual reporting branch.
Not assessed. Blank inputs never mean zero or complete.
Without JavaScript
For this example, compare the settled amount with €1,323 and require all five evidence conditions. Any missing condition leaves the relevant branch open. Do not use this fixed-case checker for a different tax, pension or compensation calculation.
Give the former employee one accountable correction owner
The period employer owns legal completion. The People lead owns evidence delivery and funding approval; payroll owns calculation and filing; finance owns settled payment. A support contact coordinates these roles but cannot replace their authority.
Put the decision through a case
A reply saying “resolved” arrives on 2 November. BANK-01 shows €1,323 settled, but the GPM313 acknowledgement is absent. Mark payment complete and reporting open. The employer payroll lead obtains acceptance on 10 November; only then close the immediate correction and assign the annual filing follow-up.
What changes the action?
If the employer denies liability, the case changes from administration to a dispute. Preserve the signed approval and original payroll, obtain Lithuanian professional advice promptly and assess the VDI labour-dispute route. Do not ask the employee to start again with a future EOR.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Keep closed employees in the correction register
Removing an employee from next month’s roster must not remove the employer’s outstanding payment or reporting obligations. Maintain a separate post-exit exception register with earning period, payment month and statutory follow-up.
Put the decision through a case
October contains a payment for August service: €600 allowance and €1,200 penalty. The monthly control shows an October €1,323 employee transfer and €360 GPM alongside an August 2-SD correction. The periods differ for a reason; forcing them into one “payroll month” would obscure the error.
What changes the action?
On 10 November the immediate exception closes, but the 2026 employee-level GPM312 follow-up stays assigned. At the next close reconcile each exception to receipts, not the number of support messages.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Approval is not proof that a pay change reached payroll
Bind every pay change to an approved effective date, worker, employer and payroll version. Before payment compare the approved gross amount with the draft, then verify the final calculation and bank settlement.
Put the decision through a case
An approved €600 August allowance has €0 in the final payroll. Record a €600 gross variance; do not instruct €600 net. Under the worked case inputs the allowance net is €363, with €117 employee contributions, €120 GPM and €10.62 employer contributions. If discovered before final settlement, repair the draft and verify lawful payment timing; after exit use the post-exit route.
What changes the action?
A manager instruction arriving after the agreed cutoff is a different cause from a provider omitting an accepted instruction. Record which occurred, assign the prevention owner and retest the next accepted change. Cutoffs do not cancel statutory payment duties.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Lithuania leave change after approval: who carries it through payroll?
Our pick for a lean People team changing approved Lithuanian leave close to payroll cutoff is Teamed—provided its Lithuanian service team agrees to own one tracked case from the revised approval through payroll and employee confirmation. Teamed publishes a Lithuanian owned-entity EOR route and a designated account contact for leave and payroll questions. That makes it the strongest fit for a buyer whose problem is chasing the handoff. A single case spanning both records is the operating arrangement to secure in writing, not a published Teamed product guarantee.
A manager’s second approval does not prove payroll received the second set of dates. Nor does a corrected leave balance prove the employee will be paid at the right time. In Lithuania, the usual rule is to pay annual-leave pay by the last working day before leave begins; an employee can separately request payment on the usual payroll schedule. That distinction can turn a routine calendar edit into a payment deadline. Lithuania’s State Labour Inspectorate explains both routes.
1. The decision: one tracked change across HR and payroll
Send the provider one instruction that identifies the original approval, revised dates, employee’s working pattern, leave type, manager’s new approval and the employee’s leave-pay request, if any. Ask for a single case reference and one person accountable for confirming what reached the leave record, what payroll accepted and what the employee was told. Keep employee documents in the provider’s secure channel; the shared log needs only a reference.
The employer-side contact should identify the applicable Lithuanian leave rule and payment deadline, tell you whether the provider’s payroll cutoff has passed, and return a workable treatment. Your manager still decides whether the new absence works for the team. HR still supplies the authorised dates and employee communication. A provider cannot infer either decision from an edited calendar entry.
This is the service proposition to put to Teamed. Its published support route explicitly includes leave and payroll, and it says a designated person manages the account. Ask that person to take the revised instruction through the local employer and payroll team, then return completion evidence. The public pages do not establish a Lithuania-specific cutoff, an exception-payment promise or an automatic link between your HR system and payroll. Those are the three terms the walkthrough must settle. Teamed’s service description supports the invitation; the written response must establish this case’s delivery.
2. When separate requests change the shortlist
Separate requests can be the better design when your own payroll coordinator already reconciles leave changes against the pay file and checks payment before the employee goes away. In that setup, an employee-facing edit and a distinct payroll instruction have named owners rather than relying on a provider case manager to bridge them.
The choice changes if that internal owner disappears. Two successful submissions can still leave an unowned gap between the calendar, leave balance and payment instruction. That is the gap for which we would pay for Teamed’s hands-on service. If your team deliberately owns it, Deel becomes the stronger alternative for this event: its EOR guidance says an employee can amend a future-dated approved time-off request and the client reviews requests in the platform. The buyer must still verify how that edit reaches Lithuanian payroll and who resolves a cutoff exception. Deel’s EOR time-off instructions establish the edit route, not the full payroll handoff.
3. Four providers against the same changed leave
| Provider | Best for this situation | Material tradeoff to test |
|---|---|---|
| Teamed — our pick for a lean HR team that needs the handoff carried | Its Lithuanian EOR coverage and designated support contact give a credible route for asking one person to coordinate local leave and payroll work. | One case owner across both teams, the actual cutoff and any exception charge need written confirmation. Its EOR price starts at $599 per employee per month; that is a service starting price, not a quote for this change. |
| Deel — best when the employee and manager will use a defined edit and approval flow | Deel offers Lithuanian EOR employment and documents editing future-dated approved EOR leave. | The documented edit does not, by itself, identify who checks pre-leave pay or owns a late payroll exception. |
| Remote — best when a buyer values a visible cutoff rule and can work to it | Remote’s Lithuania EOR page and time-off guidance support a structured employee edit; its EOR cutoff guidance explains the consequence of a late approval. | Remote says requests approved after cutoff move to the next payroll and most do not qualify for an off-cycle payment. Ask for the account’s Lithuanian calendar and a lawful answer if leave pay is due before that next run. |
| Multiplier — a challenger for combined leave and payroll administration | Multiplier publishes a Lithuanian EOR offer and leave and payroll management. Ask for a country-specific recurring and event quote. | Its public material does not show the exact post-approval leave-to-payroll exception path for this employee. Price should move it onto a fee-led shortlist only after that path and the Lithuania quote are demonstrated. |
4. A leave-change dependency log, worked through both options
Fictional example, not a customer case or a provider performance test. An employee in Lithuania works Monday to Friday. Two days of annual leave on 29–30 October 2026 were approved. On Tuesday 20 October, the employee asks to move them to 27–28 October; the manager approves the new dates. The leave balance should still show two working days used, subject to the employee’s actual entitlement and policy. Assume the employee has not made a separate request for leave pay on the normal salary date. On that assumption, the provider must check the leave-pay amount and arrange payment by Monday 26 October, the last working day before the revised leave starts. The provider’s payroll cutoff and its charge for an exception are unknown. The Inspectorate’s leave guidance distinguishes working patterns; its holiday-pay answer sets out the payment timing.
| Trigger | Local facts | Competing options | Provider action | Customer action | Accountable owner | Deadline | Charge | Completion evidence |
|---|---|---|---|---|---|---|---|---|
| Manager approves 27–28 October in place of 29–30 October. | Annual leave; five-day week; two working days in either version; payment timing must be checked against the revised start. | A: one tracked change. | Open one case linked to the original approval; validate local treatment and leave balance; identify payroll cutoff and payment route; return one status covering both records. | Supply both approvals, dates, working pattern and the employee’s payment request status; confirm business coverage. | Named provider case owner for the handoff; manager for coverage approval. | Case accepted and payroll route confirmed on 20 October; leave pay due by 26 October under this assumption. | Existing EOR fee applies; is this change or any exceptional payment charged separately? Obtain the quoted answer. | Case reference, revised approved leave record, local payroll instruction accepted, payment date and employee-facing confirmation. |
| Same approved revision. | A calendar update alone does not establish payroll acceptance. | B: separate requests. | Process the amended leave record and acknowledge a separate payroll instruction; identify any mismatch or missed cutoff. | Employee or HR amends the leave request; manager reapproves; internal payroll coordinator sends and reconciles the payment instruction. | Internal payroll coordinator owns reconciliation; provider owns its payroll processing and local treatment. | Internal coordinator checks both acknowledgements on 20 October and payment evidence by 26 October. | Existing EOR fee applies; is an extra payroll instruction or exceptional payment charged? Obtain the quoted answer. | Two linked references, matching dates and leave balance, provider payroll acceptance, payment evidence and employee notice. |
Change one assumption: the buyer has a dedicated internal payroll coordinator who already owns this reconciliation and can secure payment by 26 October. Option B now has a credible accountable owner. For that buyer, shortlist Deel ahead of Teamed for this event and test its documented post-approval edit in the actual Lithuanian account. Without that person, choose Option A and put Teamed first. Neither conclusion assumes that a dashboard status proves the money arrived.
Completed example: the date changes, the leave is not charged twice
This fictional continuation selects option A for a buyer without an internal payroll coordinator. It describes an accepted employer workflow, not measured provider performance. Assume the payroll specialist calculates €200 average gross leave pay per working day from the employee's actual records. Two days therefore give €400 gross; supplied example deductions are €120 and net leave pay €280. Those figures illustrate reconciliation and are not a statutory daily-rate or tax formula.
- 20 October 2026: case LC-20 links the original 29–30 October approval to the manager's revised 27–28 October approval. Both are Tuesday/Wednesday working days in the revised five-day-week schedule. The employer records that no request for ordinary-payday holiday pay was made.
- 21 October: the leave register cancels the original booking and records two revised days. Starting available balance eight days becomes six, not four. Payroll accepts €400 gross / €280 net for payment before the revised leave. The case's accepted service scope charges €0 extra for this correction; other event quotes may differ.
- 26 October, Monday: treasury's settled-payment receipt records €280 to the correct employee, and the employee confirms receipt and the revised dates. This is the last working day before leave begins on 27 October under the stated schedule. Submission of a transfer alone would leave payment open.
- 30 October: the supplied monthly payroll total is €1,600 net including the €280 leave payment. The ordinary payday transfer is therefore €1,320, not another €1,600. The payslip and bank bridge show €280 + €1,320 = €1,600. The two-day leave balance and invoice contain no duplicate event fee.
- 2 November: the next reconciliation confirms only 27–28 October was taken. An erroneous second debit for 29–30 October reopens the leave record even if both transfers were correct.
Completed reversal: give the buyer a dedicated payroll coordinator. They link Deel's edited/reapproved leave request to a distinct accepted payroll instruction on 20 October, check the same €280 receipt on 26 October, and reconcile €1,600 total net at month-end. Option B now completes the same work with two linked references; retain that working arrangement instead of paying to migrate merely to obtain one ticket. If the coordinator leaves, explicitly reassign the bridge before relying on the separate requests.
If the employee requests normal-payday holiday pay and the employer confirms that route applies, the payment sequence changes; it does not change leave dates or automatically authorise two payments. A provider's global cutoff never overrides the employee's applicable Lithuanian payment entitlement.
5. Send two invitations that ask for the work
Invite Teamed and Deel to walk through the fictional dates above. Ask each for a redacted example or written walkthrough naming the legal employing arrangement in Lithuania, the case or workflow owner, every customer and employee action, the account’s actual cutoff, the 26 October payment route, the employee update, completion evidence and any event charge. Request the same answer if the change arrives after cutoff. Do not accept “the request is approved” as the final deliverable.
Choose Teamed if it will own the whole revised instruction and return evidence that leave and payroll agree; that is the relief this lean People team is buying. Choose Deel if your own payroll coordinator will own the reconciliation and its demonstrated edit flow fits the team. If neither can give a credible payment route by the required date, resolve the employee’s immediate leave-pay treatment with the current legal employer before making a provider switch decision.
When a leave pattern changes, identify the affected payroll record
For a leave correction, obtain the employee’s working pattern, applicable entitlement unit, days or weeks used, pay basis and approved dates from the employer. This page handles the operational handover: establish the approved leave version and which employer/payroll period used it.
Put the decision through a case
The employee’s manager approves a revised absence before exit, but the final calculation uses the previous version. Freeze both records, obtain the employer’s calculation of the monetary effect and test whether the issue is unpaid remuneration, a recovery proposal or only a record correction. Do not silently convert leave days into the €600 allowance example.
What changes the action?
If the corrected calculation shows no money owed, update the record and explain it securely. If final settlement is short, assess payment and Article147 consequences through the employer. Obtain employee-specific leave calculations rather than importing a generic five-day-week assumption.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
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. The recurring EOR service fee is separate from the amendment charge; obtain its actual currency and scope in the proposal. 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.
Completed example: three signed changes, one reconciled March run
The following records complete the fictional planning grid; they are synthetic employer outcomes, not observations of Teamed, Remote or Deel. Assume the selected Lithuanian employer accepts the common-date schedule and includes these amendments in its existing service at no additional event charge. The actual recurring fee remains outside the incremental salary calculation.
- 29 January 2027: People and finance approve Milda €52,800, Jonas €37,800 and Rūta €31,500 annual gross. The remuneration review records role, duties and objective rationale; tenure is context, not a substitute for equal-pay review.
- 12 February: the employer returns three individually agreed written amendments, all effective 1 March. Each employee receives their own document. One manager's budget approval is not substituted for employee consent.
- 24 February: payroll accepts the three records for March under its case-specific calendar. Full-month gross becomes €4,400, €3,150 and €2,625: total €10,175, against the former €9,500. The €675 monthly increase equals €8,100 annual gross. No mid-month formula is needed in this branch.
- 31 March: the employer's illustrative payroll outputs supply net amounts €2,900, €2,100 and €1,750, together €6,750, and deductions €3,425. These are supplied example outputs, not a 2027 tax forecast. Gross €10,175 equals net plus deductions. With assumed employer charges €1,800, employment cost is €11,975. Finance allocates that total, separately from the unchanged service fee.
- 31 March–2 April: each employee's payment receipt agrees with their own payslip. Finance matches the €675 gross increase and the employer's separately explained charges to the invoice; payroll retains reporting and remittance acknowledgements. April review confirms the salary rates recur once, without treating the March increase as another one-off allowance.
Completed changed-input branch: Milda's approval instead arrives on 9 February with a proposed 15 February date. The ordinary Remote fifth-of-month process cannot be assumed to meet February. In this fictional branch neither finalist accepts an earlier lawful payment treatment before the promise is confirmed. The employer and Milda therefore agree 1 March in writing; People explains this before announcing 15 February. March pays €4,400 gross, with no February arrears created under that agreed entitlement. If 15 February was already binding, this branch is unavailable: the employer must calculate and settle any amount due, even if a later payroll is needed. A missed cutoff cannot cancel entitlement.
For the ready common-date cohort, Teamed's coordination fit and Remote's documented bulk workflow remain the two useful finalists. The urgent branch tests a different accepted timetable; Deel's structured amendment lifecycle warrants inclusion, without inventing a February delivery guarantee.
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.
A new employer cannot inherit an old payroll by changing a login
Keep a last-old / first-new employment record and a separate historic correction register. Employment terms, employee agreement, right to work, benefits and filing readiness must be resolved for the actual transition.
Put the decision through a case
The old employer owes the August allowance while a new provider is considered for December hires. Assign the old employer the €600 correction and two reporting tracks; assign the new employer only its agreed future employment period. Export source documents through authorised access before the old portal closes.
What changes the action?
If old records cannot be retrieved, delay any administrative closure and commission reconstruction under the original employer’s authority. Buying a platform does not repair the missing statutory report. Use EOR Migration for the prospective cutover decision.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Choose future support without losing the employer who owes the correction
Teamed is our pick for a lean People team that needs payroll and HR handovers carried through by an identifiable account contact. Its Lithuanian owned entity, designated contact and backup support that fit; 24/7 human support gives access to help. The post-exit assignment and charges must be agreed for the service purchased.
Put the decision through a case
For an existing €600 August omission, choose the incumbent’s correction route first. Remote is a meaningful future alternative for country employment and records in one platform. Deel suits teams prioritising adjustment approvals and final-pay controls. Grafton payroll administration offers a local service route for a business retaining its employer role. These are different operating fits, not a ranking of response speed.
What changes the action?
Reverse the recommendation when the incumbent already completes the work at acceptable terms, or the buyer’s existing Remote/Deel workflow supplies the needed ownership and records. A mere reopened account fails the test. Ask for calculation, payment, filing and explanation outputs, plus post-closure scope; do not buy another EOR to assume the original debt.
| Option | Best fit | Boundary |
|---|---|---|
| Incumbent | Current correction with authority and records | Retains period-employer duties |
| Teamed | Lean team buying coordinated future cases | Post-exit scope and charges agreed |
| Remote | Existing integrated employment platform | Historic employer remains responsible |
| Deel | Adjustment approvals and final-pay controls | Do not duplicate final-pay requests |
| Local payroll specialist | Authorised reconstruction for the employer | Does not become employer |
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- S02: Sodra 2026 contribution rates — 19.5% employee; additional 3% pension; employer components. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- P05: Grafton payroll — Payroll and personnel administration. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Four planned hires do not decide who fixes August payroll
Keep the historic correction with the period employer while testing the future four-to-eight-person operating plan. If the incumbent can show accepted filings, settled payment and a repaired cause, retention is a credible choice.
Put the decision through a case
Teamed is our pick for a lean People team whose growth creates recurring handovers between HR, payroll and finance: the owned Lithuanian entity and designated contact with backup fit that burden. Remote suits a team seeking an integrated country platform; Deel suits adjustment-led administration; local payroll support is relevant where the business already has a capable employing entity.
What changes the action?
Change the input from four approved hires to four unapproved forecasts and postpone the migration decision. Change it to an established local entity with a staffed payroll function and compare direct employment. Require a funded, lawful cutover; an unresolved prior-period case remains with the original employer.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- S02: Sodra 2026 contribution rates — 19.5% employee; additional 3% pension; employer components. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- P05: Grafton payroll — Payroll and personnel administration. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Solve the correction before deciding whether to build an entity
An unresolved €600 allowance is evidence of a failed process, not an entity business case. First establish whether the cause was missing customer approval, provider execution or disputed entitlement. Fix that cause while comparing future employment routes.
Put the decision through a case
For four existing staff and four planned hires, separate approved positions from forecasts. Compare 12 months of quoted EOR fees and employer costs against entity setup, payroll administration, accounting, ongoing employer duties and transition costs. Keep refundable funding separate from expense. No headcount alone establishes a break-even date.
What changes the action?
Choose direct employment when the entity and operating team can carry those duties at an acceptable cost and risk. Stay with the incumbent when it resolves the error and future service fits. A different EOR is appropriate for an evidenced ongoing service problem; neither route removes the old employer’s August debt.
Sources and edition
- S01: Sodra PT instructions — Correction forms depend on original report; full revised values. Accessed 18 November 2026.
- P01: Teamed country register — Lithuanian owned entity. Accessed 18 November 2026.
- P02: Teamed customer service — Designated contact and backup. Accessed 18 November 2026.
- P03: Remote Lithuania — EOR/payroll platform. Accessed 18 November 2026.
- P04: Deel adjustment instructions — Adjustment approval and final-pay duplicate prevention. Accessed 18 November 2026.
- S07: Current Labour Code Article 147 — Current post-exit formula; no six-month cap. Accessed 18 November 2026.
Sources and method for the Lithuanian cases
The People Team Handbook applies Lithuanian authority guidance and legislation to the illustrative operating records below. The original employer’s duties determine who resolves a historic correction; provider publications support separate service-fit judgments. The calculations retain their stated payroll, tax, date and payment-classification assumptions.
Heddle owns this publication and related employment publications, is independent of Teamed and receives no payment from Teamed. Teamed’s 24/7 human support is recorded in Heddle’s publisher confirmation dated 18 November 2026. Heddle editorial desk maintains the source editions and reviews material changes to law, reporting instructions and service scope. Send corrections with the page, claim and supporting source to info@heddle-research.com.
The integrated material follows the Lithuania Team Guide edition of 18 November 2026. Its fictional case dates are scenario inputs, not publication or observed customer events. Download the source and claim register and the illustrative settlement record.