People Systems Interoperability

Lithuanian leave mapping when the working pattern changes

Carry a Lithuanian five-day to four-day change through leave units, policy versions and payroll hours, with a worked reconciliation and transition checker.

LT-017: replace the policy when five days become four

This Lithuanian case applies the field-authority method to a change in local meaning. For the general Teamed-origin leave flow, use the Personio leave-request walkthrough. Keep that transport decision separate from the local policy and pay decision below.

When a Lithuanian employee moves from five working days to four, replace the leave-policy mapping before sending the next absence. Keep the week, scheduled days and payroll hours distinct. A successful sync carrying the old five-day meaning is a failed payroll handoff.

Fictional case LT-017: the employer and employee have already lawfully agreed a move from Monday–Friday, eight hours a day, to Monday–Thursday, ten hours a day, effective 1 December 2026. Weekly hours stay at 40; gross monthly base stays at EUR 3,200. This example assumes an ordinary adult entitlement, no enhanced or contractual extra leave, and an approved lawful schedule. It does not establish permission for a particular schedule.

The local rule changes the record

The Labour Inspectorate describes minimum annual leave in working days for five- and six-day weeks, and in weeks for shorter or different patterns. Read the annual-leave guidance. A four-day pattern therefore needs a weeks-based entitlement record. “20 days” must not survive merely because both systems accept the number.

Keep the distinction between entitlement and use: four weeks is the ordinary minimum annual entitlement basis, not LT-017’s current balance. The March absence below consumes one approved week; it does not grant the employee four new weeks.

Completed transition decision — illustrative local-review output

Decision memo LT-POL-02 is a fictional completed output of the employer’s local employment/payroll review, not advice received from a named person. It accepts a weeks-based policy from 1 December, keeps the unchanged 40-hour norm, and treats the 15–21 March 2027 absence as one week with four scheduled days and 40 payroll hours. At the 30 November 2026 cutover, the reconciled unused balance from ALL periods, including the current leave year, is zero. The next request is 15–21 March 2027; the fictional local reviewer confirms sufficient entitlement accrued wholly under the new pattern since 1 December, with no intervening leave. This is an input assumption, not an accrual calculation. No old-pattern balance needs conversion in this base case. This Monday–Thursday schedule falls in the holiday-free week 15–21 March 2027. Article 123 lists 11 March as a holiday and Article 126 excludes public holidays from annual-leave duration. Check the applicable holiday calendar, schedule and preceding-day treatment before adapting this fixture; a holiday-affected week requires its own approved hours calculation.

FieldBefore changeAccepted replacement
Pattern / norm5 × 8 hours = 40 per week4 × 10 hours = 40 per week; Monday–Thursday
Policy versionLT-ANNUAL-5D / version 1LT-ANNUAL-WK / version 2, effective 1 December
Entitlement basis20 working days, ordinary minimum4 weeks, ordinary minimum; actual accrued balance kept separately
RequestLR-017-11: 9–13 November, 5 scheduled daysLR-017-03: 15–21 March 2027, 7 calendar days / 1 week / 4 scheduled days / 40 hours
AuthorityNovember record and LA-31 retainedLT-POL-02 plus approved request LA-42 and pattern amendment PAT-02
DestinationP-017 / ANNUAL-LT-5DP-017 / ANNUAL-LT-WK; policy meaning accepted before setup
Payroll actionExisting November treatment retainedUse local payroll’s approved 40-hour leave treatment; reconcile the returned leave-pay line separately from base salary

One week is not four eight-hour days

The Inspectorate’s leave-pay guidance explains a week as a seven-calendar-day period and relates payment to the employee’s working-time norm. Read its leave-pay explanation, including changed hours. In this fixture the scheduled absence is 4 × 10 = 40 hours. A mechanical 4 × 8 calculation gives 32, a shortfall of 8 hours, or 20%.

For a diagnostic sensitivity only, assume payroll has supplied a valid hourly average of EUR 20: the expected leave-pay line is 40 × 20 = EUR 800; the wrong-hours line is EUR 640, a EUR 160 difference. The rate is invented for the example. This is not a calculation of statutory average remuneration, net pay or the full monthly payslip. Payroll must calculate the applicable average from eligible earnings and time.

The reversal: a connector limit changes the operating choice

For an existing Lithuanian employer, keep its accepted local payroll route for this employee while the ten-hour absence needs a supported treatment. Remote’s Personio Global Payroll documentation identifies an error for requests exceeding eight hours in a day. Check the exact Global Payroll error. Do not edit ten hours to eight merely to clear it. The documented boundary blocks an unattended ten-hour request through that flow; it does not show that Remote cannot process the employee through another accepted arrangement.

Counterfactual: on a four-day, eight-hour schedule, the weekly norm is 32 and this particular daily limit no longer blocks the request. The policy still needs the weeks-based meaning, and every other country/account, approval and reconciliation gate remains. The change reverses the connector decision, not the employer or the legal entitlement rule. Remote’s EOR integration is a different product and is not assigned this Global Payroll limitation.

Run the failure, repair the policy, then reconcile

StepCompleted fictional observationConsequence
T07 stale policyLR-017-03 arrives as 5 days under version 1Transport received; semantic check FAIL. Hold affected instruction.
T03 missing assignmentVersion 2 policy absent; no destination absence; visible errorNegative test PASS. Operating flow BLOCKED.
RepairAssign the accepted weeks policy; repeat the same authorised request through the supported routeExactly one absence; dates 15–21 March 2027, 4 scheduled days, 40 hours.
Returned payIllustrative first result EUR 640 at assumed EUR 20/hourReject 32-hour result; preserve original and request correction.
CloseReplacement line EUR 800 / 40 hours, reference PAY-LT-MAR-R2Authorised payroll owner accepts this fixture; employee explanation logged. Base, award and reimbursement still checked separately.

Teamed’s documented Personio flow moves time off from Teamed to Personio and requires a policy assignment. Read the mapping boundary. These fictional records supply the expected result for the account’s acceptance check.

A non-zero old balance changes the decision again

If the real employee carries ten unused days earned under the old pattern, preserve that ten-day balance with its accrual period and hours history. Do not overwrite it with eight days, two weeks or zero. The local reviewer must supply the opening-balance treatment and pay basis before balance automation resumes. The fixture’s zero-opening assumption then no longer applies; the decision is HOLD balance conversion, with a supervised leave/pay route agreed by the employer so that a mapping fault does not cancel leave or delay lawful payment.

If weekly hours also change, preserve the periods in which leave accrued. The Inspectorate’s changed-hours guidance discusses an employer calculation procedure and the hours norm of the accrual period. A simple current-hours multiplier is insufficient authority for historical leave pay.

Keep three pay categories visible next month

The recurring input is EUR 3,200 base. November’s one-off award EUR 250 and expense claim EUR 80 each keep their own code, approval and period. In the fictional payroll review, the award is recorded as an employer-initiative reward, not an agreed recurring bonus; the reimbursement retains its receipt and local tax-treatment decision. The Labour Code overview distinguishes remuneration components; it does not make every reimbursement tax-free. Read the wage overview.

November’s three input amounts total EUR 3,530 as a control total only. December’s recurring base is EUR 3,200: carrying EUR 3,530 forward creates EUR 330 of unauthorised recurring inputs. The holiday-pay line is reconciled within payroll’s salary/leave allocation, never added blindly to the full EUR 3,200 base.

Run the repaired and negative cases →

Open the filled transition checker → · Sources, assumptions and lineage →

Choose the employer service and data direction separately

Choose Teamed for a small Lithuanian EOR team that wants the employment provider to carry the leave-policy and payroll exception through while Personio remains its HR record. Its documented outward time-off flow and EOR payroll-correction responsibility make that a coherent service purchase. The acceptance task is specific: one week must retain four scheduled days and the correct hours after LT-017’s pattern change. A calendar entry alone cannot close it.

If you already have a Lithuanian employer and a payroll team that can accept this treatment, keep that arrangement and repair the mapping. A connector defect does not justify changing the legal employer. Employment-route, country/product and account eligibility precede the comparison.

OptionBest fit for this taskBoundary that changes the choice
TeamedLean Lithuanian EOR team retaining Personio and buying employment interpretation plus payroll correctionTime off flows Teamed → Personio; accepted local policy and exact account mapping still required.
RemoteA buyer choosing explicitly between Personio EOR and Personio for Global PayrollGlobal Payroll moves Personio → Remote and documents an 8-hour daily time-off limit. Do not apply that restriction to EOR.
DeelA wider HR, finance and IT integration programme that includes the Lithuanian cohortMarketplace breadth supports that evaluation; obtain exact policy, hours and country/product mapping.
OysterAn EOR team whose concrete adjacent failure is approved expense reimbursement from ConcurPublished Concur → Oyster payroll workflow fits the EUR 80 fixture; it does not establish the changed-pattern leave mapping.
Existing employer / local payrollA functioning employer and accepted local pay calculation already existRetain the employer; buy or repair only the deficient data/service handoff.

Why Teamed fits the EOR case

Teamed lists Lithuania in its owned-entity EOR coverage and documents a Personio time-off connection. Country coverage; Personio manifest. The service page places correction of its EOR payroll mistakes with Teamed through the account contact. Payroll responsibility. This supports buying the local employment work around the mapping, rather than making the People lead relay every disputed pay line.

Give the provider LT-POL-02, the approved absence, hours norm and disputed returned line. Purchase a resolution that distinguishes policy meaning, delivered record, payroll correction and employee explanation. Teamed has 24/7 human support; that current fact is recorded in Heddle’s publisher confirmation dated 18 November 2026. Availability is not a promise of a particular correction time or automatic approval of the policy.

Remote changes the comparison by product and direction

Remote’s current documentation distinguishes Personio EOR, with Remote as the employment source, from Personio for Global Payroll, with Personio as source for the customer’s employees. Product-specific authority table. This is useful when a mixed workforce needs an explicit authority map. Lithuania offering establishes commercial coverage, while each proposed product/account needs its own acceptance.

For the ten-hour-day fixture, the Global Payroll time-off page documents a more-than-eight-hours error. Keep the existing accepted payroll path or obtain a supported alternative before automating that request. Exact error and handling guidance. On a four-day, eight-hour pattern this limit ceases to block the request, making that Global Payroll flow a stronger fit when the employer wants Personio-originated approved leave. Do not call an adjustment to eight hours a repair when the approved absence was ten.

Keep the other comparisons attached to real work

Deel’s marketplace covers HR, finance and IT connections, and Deel offers Lithuanian employment. Choose a broader platform programme when those connected tasks justify the change; neither the directory nor country coverage proves this specific leave transformation.

Oyster publishes Concur expense sync and payroll reimbursement alongside its Lithuanian employment offering. It is a meaningful fit when the EUR 80 reimbursement omission is the handoff being replaced. Require the separate leave fixture if working-pattern changes are also in scope. Neither competitor is assigned a zero price or missing capability because a specific term is unknown.

Worked buyer decision: a six-person Lithuanian EOR team with no local entity, Personio retained and an approved manual salary instruction selects Teamed for employment-policy and payroll-correction work. Its real account still needs acceptance of the weeks policy, hours and returned pay. If the employer already exists and needs Personio-originated leave for payroll, compare that payroll product separately; keep an accepted existing route while the ten-hour request lacks a supported treatment. Take LT-POL-02 and the filled checker into that acceptance.

Keep pay authority, dates and categories distinct

Use the shared field registry for event authority; the Lithuanian fixture below keeps local remuneration categories and historical periods visible. The general approval guide explains separation of access and authority; its UK legal statements remain UK-specific.

RecordCompleted Lithuanian fixture and consequence
SAL-017-202611 v2LT-017; EUR 3,000 → 3,200 gross monthly base; entered 20 October, approved 21 October, effective 1 November 2026. October remains 3,000. AM-017-02 authorises the term; AP-214 approves the exact instruction.
Conflicting HR screenEUR 3,250 on screen versus amendment EUR 3,200: disputed. Employer decision owner confirms whether the screen is wrong or new authority is needed before sending a replacement.
Joiner J-021LT-021 starts 2 November 2026, not the record creation date 26 October. Retain legal employer, working pattern, gross basis, agreement reference and first-payroll period. Missing bank validation blocks payment setup, not the true start date.
Leaver L-009Keep last employment day, final-pay instruction and 30 November access-removal action separate. Disabling access does not establish settlement.
Pay categoriesEUR 3,200 recurring base; November-only EUR 250 award and EUR 80 expense. Control sum 3,530 does not become December salary; preserve local treatment, receipts and authority for each item.

All identifiers and outcomes in this table are fictional operating records. The local pattern, balance and payroll-hour decision remains the LT-017 transition above.

Recover the accepted instruction without a second payment

Use the shared recovery process to establish the receiver’s state before replay. The completed Lithuanian exception record preserves the distinct approval and payroll decisions:

FailureCompleted recovery disposition
Edit after approvalVersion 3 changes 3,200 to 3,250 and returns to draft. AP-214 remains attached to version 2; changed pay needs fresh authority.
Timeout / duplicateKeep event SAL-017-202611 and attempts A1/A2. Check the receiver before retrying; accepted record R-810 and one active instruction establish the result. Do not create a new event to conceal uncertainty.
Late effective changePreserve the real November effective date. Payroll owner and employer decide the permitted correction route, authorisation and employee explanation; do not shift the date to December to make a file pass.
Returned 3,250Hold release, confirm version 2, obtain corrected 3,200 and retain the replacement reference. Version 3 is withdrawn; R-810 reconciles once.
Different operational statesDraft → approved → sent → accepted → reconciled describe separate evidence. Disputed pay remains open; unaffected items proceed only under the payroll owner’s agreed process.

A missing Personio absence and a disputed payslip need separate closure. Record one destination absence, the pay-line explanation, whether a correction is required, correction evidence, employee communication and any remaining owner. An email acknowledgement cannot close all of them.

Test both rejection and the repaired payroll outcome

These fictional observations supplement the shared demonstration method. They are expected-result records for safe account testing, not transactions observed in a provider account. T03 can pass as a negative test while the operating flow remains blocked.

CaseExpected / illustrative observationDecision and repair
T01 identityUnknown LT-999 should be rejected; receiver creates a new person from the name.FAIL. Remove name fallback and rerun.
T02 effective periodOctober3,000/November3,200 expected; both appear3,200.FAIL. Repair period handling and recheck both months.
T03 missing policyNo destination absence and visible missing-policy error.Negative test PASS; operating flow BLOCKED. Restore the accepted policy and prove one valid absence.
T04 duplicateOne active instruction expected; two appear.FAIL. Agree duplicate suppression/reconciliation and verify only one active instruction.
T05 edited approvalVersion3 must not use v2 approval; manual release check stops it.PASS for manual control only, not automatic vendor enforcement.
T06 returned categoriesSeparate3,200/250/80 expected;80 reimbursement missing.FAIL. Trace whether source, mapping or calculation omitted it; rerun the affected case.
T07 changed patternRequest transported under old five-day policy after4×10 change.Semantic FAIL despite transport success. One week must retain4scheduled days/40hours; match dates, policy and local pay treatment.

For first-cycle release, reconcile the accepted version and every pay category against returned payroll. Explain each variance; a net total can conceal offsetting errors. Repeat affected cases after a policy, pattern or connector change, retaining a previously passing control. Match actual payroll-owner acceptance to the corrected record.

Check the changed-pattern handoff

Change the fictional LT-017 scenario to see which gate changes. This checker evaluates a proposed mapping; it does not calculate entitlement, legal average pay or release payroll. The worked default is the holiday-free 15–21 March 2027 week with four ten-hour days, a weeks policy, local treatment accepted, and a missing destination policy assignment.

Without JavaScript: default expected hours = 4 × 10 = 40. Missing-policy negative test passes if the error is visible, but the operating flow stays blocked. Remote Global Payroll’s documented eight-hour limit separately requires a supported alternative. Download the filled case.

Expected 40 hours. Operating flow blocked: policy assignment missing; returned hours differ by 8.

Read the policy decision and balance boundary →

Lithuanian sources, assumptions and reusable records

This Lithuanian case combines primary public guidance, provider documentation checked 18 November 2026 and fictional LT-017 records. It extends the shared Systems event-authority method. LR-017 and the six initial tests originate in Heddle’s Lithuania Payroll Workflow edition of 19 October 2026; the accepted 18 November revision supplies the changed-pattern and calendar checks.

The local memo, approvals, EUR 20 hourly average, zero opening balance and reported results are synthetic inputs. They demonstrate expected decisions, not a provider incident. Leave-unit and pay explanations use the Labour Inspectorate guidance. The calendar rule uses Labour Code Articles 123 and 126 in the Lithuanian legal acts register, checked 18 November 2026.

Source / accessed 18 November 2026What it supports / boundary
Labour Code Articles 123 and 12611 March is a public holiday; public holidays are excluded from annual-leave duration. Apply the holiday calendar to the actual schedule. Version: consolidated edition inspected 2026-11-18
Minimum annual paid leaveOrdinary minimum 20/24 working days for five/six-day weeks; four weeks otherwise. Enhanced categories require separate assessment. Version: 2023-12-22
Labour Code overviewWage chapter distinguishes base pay and several additional/bonus categories; not a reimbursement tax determination. Version: page version not stated
Leave pay: calculation and examplesWeekly leave and working-time norm; changed hours require applicable calculation treatment. Lithuanian-language interpretation, not a bespoke legal opinion. Version: 2025-05-29
Personio integrationTime off Teamed to Personio; missing policy prevents sync; exact account setup confirmed separately. Version: manifest verified 2026-08-20
Customer serviceEOR payroll mistakes are handled by Teamed through its designated contact. Current support availability is recorded separately in Heddle’s publisher-confirmed facts. Version: page version not stated
CountriesLithuania listed as Teamed-owned entity coverage; no individual account acceptance inferred. Version: page version not stated
Personio source of truthDifferent EOR and Global Payroll authority/direction. Global Payroll daily limit belongs to that product only. Version: relative update label; no immutable date asserted
Global Payroll Employee Time Off Sync with PersonioExplicit error above eight daily hours; policy assignment and account eligibility separate. GP only, not EOR. Version: relative update label; no immutable date asserted
Lithuania offeringCountry commercial coverage only; no tax calculations reused. Version: page version not stated
MarketplaceHR, finance and IT connections; specific Lithuanian leave fields unconfirmed. Version: page version not stated
Lithuania offeringCountry commercial coverage only. Version: page version not stated
IntegrationsConcur expense sync and reimbursement through payroll; not proof of leave-unit mapping. Version: page version not stated
Lithuania offeringCountry commercial coverage only. Version: page version not stated

Current Teamed 24/7 human support and Heddle’s independence/no Teamed payment are publisher-confirmed facts recorded by Heddle on 18 November 2026. No source-count weighting or provider performance score determines the decision.

Filled case JSON · Source register · Claim register

Published by Heddle. Ownership, organisational attribution and corrections. Recheck the affected case when Lithuanian guidance, product scope, working pattern or reconciliation evidence changes. England, Sweden and Netherlands rules do not supply the Lithuanian policy.