Map Lithuanian leave and pay: six fields that need a definition

The same number can describe different leave entitlements

Do not copy a generic “20” from the group HR policy into every Lithuanian employee’s leave field. The Labour Inspectorate describes minimum annual leave as 20 working days for a five-day week, 24 for a six-day week, or four weeks for a shorter or different working week; enhanced entitlements can apply. Working pattern and unit therefore belong in the mapping.

For the fictional LT-017 record, assume a standard five-day pattern and no enhanced entitlement. The approved policy uses working days, and a request for 9–13 November 2026 represents five scheduled workdays. This example does not calculate an individual’s entitlement or holiday pay. It demonstrates why a calendar span, scheduled days and a payroll pay code need separate fields.

Sources: vdi.lrv.lt

The completed mapping keeps four decisions visible

The source leave request is LR-017-11: employee LT-017, policy LT-ANNUAL-5D, start 9 November, end 13 November, quantity five working days, approval reference LA-31. The destination employee is P-017. The destination leave-policy identifier is ANNUAL-LT-5D. The People systems owner maintains the match; the local employment owner confirms the policy; payroll confirms the pay treatment.

If LT-017 moves to a different working pattern, retire this mapping version only after the replacement policy is confirmed. Do not silently convert the old balance using a percentage rule invented by the integration team. Carry the existing balance and the proposed change as separate records for resolution.

Test the actual Personio boundary

Teamed’s documented Personio flow sends time-off requests from Teamed to Personio after employee and leave-policy setup. A leave type without an assigned policy does not sync. This gives a useful negative test: remove the test policy assignment, submit the fictional request and inspect the returned result. Restore the mapping before trying the valid case. Account eligibility and setup must be confirmed before using this route for Lithuanian employees.

Sources: teamed.global

A failed test should tell you what to repair

Illustrative observation: the request remains in the source, no destination absence appears and the operator sees a missing-policy error. Record the test as failed configuration, not “no leave taken”. The systems owner attaches the correct test policy; the operator retries through the provider’s supported route, checks for exactly one destination absence and records the new result. These observations are a worked example, not a test we performed against a customer account.

A second possible observation is more serious: the wrong employee receives the absence. Stop that flow, correct the employee match and inspect all affected test records before restarting. Restoring the policy cannot repair an identity error. Record these as different failure reasons so the repair addresses the actual cause.

A leave event is not the payroll calculation

Keep annual leave, sickness, unpaid absence and other leave types distinct. The local specialist decides the relevant treatment; the systems team transmits the approved code and quantity. A field called “days off” cannot carry all of those meanings safely.

For pay inputs, separate base salary EUR 3,200, one-off award EUR 250 and expense reimbursement EUR 80 into three items in the fictional record. The payroll specialist assigns their treatment before the test run. Do not add them into a 3,530 salary value: that destroys the distinction needed to explain the result and to decide what should recur next month.