Lithuania payroll adjustment after an employee leaves: who still owns the correction?

Our pick for a UK finance team choosing an EOR for future Lithuanian hires is Teamed when the deciding requirement is a named owner who takes a payroll problem through to a documented answer. Teamed says it employs through its own Lithuanian entity, runs EOR payroll and assigns an account contact with access to HR and legal specialists. That makes it the strongest editorial fit for this buyer’s desired operating model. Before signing, require a written walkthrough of a correction discovered after the employee and the customer account have closed. Its published service description does not promise that exact workflow.

For the payment already in dispute, start with the entity that employed the person for the affected period. A replacement EOR cannot retrospectively become that employer. If the incumbent employed the worker, ask it to appoint the correction owner now. Reopening a portal may recover records; it does not establish that pay, reporting, any delay compensation and communication have been resolved.

1. Decide what actually needs correcting

Suppose a former employee says an approved August allowance was missing from their final Lithuanian payroll. The controller needs the approval and effective date, the employment contract and exit date, the August payroll calculation and payslip, the amount actually paid, and the employing entity’s name. Send those through the employer’s secure case route, with one person at the UK company authorised to approve funding.

The local employer must determine whether this is unpaid pay, an incorrectly described payment, or a record-access problem. Lithuania’s Sodra correction instructions provide routes for correcting previously reported insured-person data; VMI also describes the amendment of tax declarations. Neither source means every late payment requires every form to be amended. Ask the employer’s payroll specialist to identify the filings affected by this payment and the period in which it must be reported.

There is a second amount to assess if final remuneration was unpaid. Lithuania’s State Labour Inspectorate guidance says an employer that delays settlement after termination without employee fault must pay compensation under Labour Code Article 147(2). Ask the local employer to establish the applicable settlement due date, whether that rule applies to this allowance, and the amount due. The €600 gross shortfall alone does not settle those questions.

The deliverable is a reconciled case record: original calculation, corrected calculation, payment instruction, any filing action, the delay-compensation decision and calculation, the former employee’s explanation, and proof of completion. “The account is open again” is an access update, not that deliverable.

2. When reopening access changes the decision

Reopening a closed account informally looks attractive because it appears faster than starting a formal case. It changes the answer only if the underlying fact changes. If the employer’s August calculation shows the allowance was paid and reported correctly, and the former employee merely lacks a copy of the final payslip, the job becomes authorised document retrieval. Restore access through the provider’s normal permissions process, supply the document securely and record its delivery. A platform-led provider may then be the better fit for the next hire.

If €600 of approved gross pay is genuinely missing, access alone cannot settle it. The original employer must calculate the lawful net amount, arrange the payment, assess reporting and possible delay compensation, and explain the result. Do not use a shared login or an undocumented adjustment to make a closed case appear complete.

3. Which provider fits this case?

Provider	Best for this buyer	Material tradeoff to settle in writing
Teamed — our pick for documented case ownership	A lean controller who wants an identifiable person to coordinate a Lithuanian payroll error through investigation and closure. Teamed lists Lithuania as an owned-entity market and says its account contact handles payroll problems.	Its public pages do not specify former-employee correction access, a post-closure service period or a charge for this work. Obtain the Lithuanian employing entity, named owner, backup and written case route in the proposal.
Remote — best for a team prioritising a broad employment platform	A buyer who wants country EOR payroll, local support and employee records in one workflow. Its Lithuania page advertises EOR payroll and dedicated local support.	Ask Remote to demonstrate how a former EOR employee’s correction is opened, approved and evidenced. Its country page describes the active service, not that completed-case path.
Deel — best when adjustment workflow is the main test	A buyer who wants visible adjustment approvals and payroll cutoffs. Deel’s Lithuania EOR offer and adjustment guidance give a concrete workflow to rehearse.	Deel documents adjustments during termination, including items submitted for final payroll. That does not establish how a new issue discovered weeks after final payroll is handled in Lithuania. Request that separate walkthrough.
Multiplier — best for a procurement team testing the contractual cash route	A buyer who wants the payment, funding and supporting-document obligations specified alongside a Lithuanian EOR offer. Its EOR terms describe resource-cost funding and supporting documentation on request.	Those terms do not answer who owns a newly discovered historic correction after closure. The applicable order form, local delivery arrangement, post-exit service scope and charge still need confirming.

This is a shortlist for a future arrangement or for testing an incumbent’s service where one of these firms was the employer. The broad Lithuania EOR support shortlist covers ongoing employee questions; this decision turns on what happens after ordinary payroll and account access end.

4. Post-exit adjustment responsibility ledger: one worked case

Fictional example, not a customer outcome or a Lithuanian tax calculation. An employee left on 31 August 2026. On 20 October, the UK controller finds a signed approval for a €600 gross August allowance; the final payroll shows €0 for that item. The gross difference is €600 − €0 = €600. The allowance’s net payment, employer costs, possible delay compensation and any correction to Sodra or VMI reporting require the actual employer’s calculation. The dates below are internal case targets for this example, not statutory deadlines or provider promises.

Trigger	Local facts	Competing option	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Approved €600 gross allowance absent from final pay; employee has left	August work and approval are evidenced; final payroll records €0 for this item; employing entity, settlement due date and filings must be checked	A: documented former-employee correction	Original Lithuanian employer opens a case, verifies entitlement and prior payment, calculates gross-to-net, assesses the settlement due date and any delay compensation under Article 147(2), identifies any reporting amendment, arranges amounts due and explains them to the former employee	UK controller supplies approval, final payslip and proof of prior payment; approves and funds the corrected amount and evidenced employer costs, including any assessed delay compensation	Named case lead at the original employer, with its payroll specialist; UK controller owns funding approval	Acknowledge by 21 October; give written calculation and payment plan by 23 October; confirm actual legal and payroll dates in the case	Allowance only: €600 gross difference; allowance net is €600 less actual withholding. Employer costs and any delay compensation: local calculation required. Provider case fee and conversion charge: ask for quote or contract term	Corrected calculation, payment confirmation for all amounts due, written delay-compensation assessment and calculation, filing receipts or written reason none were needed, employee explanation and case closure
Same finding and documents	Access to the old account is closed; the €600 remains unaccounted for	B: reopen account informally	Restore a login or permit a manual entry, without an agreed post-exit payroll owner	Controller chases the screen update and still has to discover who can pay, assess delay compensation and amend records	No confirmed owner for the whole correction	Account access could return on 21 October; payment and filing dates remain uncommitted	€600 gross allowance still unresolved; any delay compensation and access or reactivation charge unknown	Login access alone proves no corrected pay, delay-compensation decision or reporting. Do not close the case on this evidence
Changed assumption: payroll records show €600 was paid and reported; only the payslip copy is missing	Bank and employer records reconcile: €600 approved − €600 included = €0 gross shortfall	C: authorised document retrieval	Verify identity, restore permitted document access or issue the final payslip securely	Controller confirms the request and records delivery	Provider records administrator	Agree a delivery date with the provider	Access or retrieval fee unknown; no modelled backpay	Payslip copy delivered securely and request closed; no payroll correction required

The third row is the reversal. With no missing pay, platform access and document retrieval matter more than a specialist-led correction. Deel or Remote could move ahead for a buyer whose wider workflow already fits their systems. In the actual €600 shortfall case, keep Teamed at the top of the future-service shortlist if it demonstrates the named, documented route it is well positioned to provide. Hold the incumbent employer to completion of the existing case.

5. Send three invitations with a pass condition

Invite Teamed, Remote and Deel to answer the same redacted scenario. Ask each for: (1) the Lithuanian employing arrangement and named person who would own a correction found seven weeks after exit; (2) a written deliverable showing calculation, funding request, delay-compensation assessment, former-employee communication and filing decision; (3) the promised timing and every possible post-closure charge, including whether service continues after the last active employee leaves. Ask for a redacted example or a written walkthrough, not a claim that the platform can do it.

Choose Teamed for the next Lithuanian employment arrangement if its written answer confirms that its named contact will carry this work through local payroll to evidence of completion at acceptable terms. Choose Remote or Deel if its demonstrated route better fits the records and approvals your team will actually use. For today’s missing payment, appoint the original employer’s case owner and keep the matter open until the payment, delay-compensation decision and reporting trail reconcile.