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 — best for a buyer comparing a lower published entry fee with combined leave and payroll administration	Multiplier publishes a Lithuanian EOR offer and leave and payroll management. Its EOR Core price starts at $459 per employee per month on an annual contract, with country and plan conditions.	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.

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.