The Lithuanian payroll data contract: a completed example

Start with the amount and the period, not the application

A successful upload can still put the wrong salary into the wrong month. The practical output of this guide is a field contract: the meaning of each value, the evidence that authorises it and the destination result you expect. You can copy the completed example below before adapting it to your provider’s actual input format.

Our fictional employee LT-017 earns EUR 3,000 gross per month. A signed amendment changes that to EUR 3,200 from 1 November 2026. People Operations enters it on 20 October; finance approves the payroll instruction on 21 October. The October base-salary input stays EUR 3,000. The November base-salary input becomes EUR 3,200. These are full-month input examples, not net-pay or employer-cost calculations. An integration that overwrites October with 3,200 has failed even if both applications now agree.

Assign authority by field

Use employee ID LT-017 as the match key. Keep the approved contract amendment as authority for the employment term, the payroll-change record as authority for the version being sent, and the provider’s returned payroll result as evidence of what was processed. A management directory can own the employee’s display name without becoming authority for pay.

The completed salary record is: event SAL-017-202611, version 2, old amount 3000.00, new amount 3200.00, currency EUR, frequency monthly, basis gross, effective date 2026-11-01, instruction approval AP-214, contract reference AM-017-02. The illustrative record uses references rather than copying the contract into a shared workbook. Version 2 must appear on both the approval and the delivery record.

Give joiners and leavers their own event shape

A joiner event J-021 records employee alias LT-021, the confirmed legal employer, start date, working pattern, gross-pay basis, agreement reference and the intended first payroll period. In our example, start date 2026-11-02 is not replaced by 2026-10-26 merely because the record was created that day. A missing bank-validation result blocks payment setup; it does not justify changing the start date.

A leaver event L-009 records the approved last employment day, the separately confirmed final-pay instruction and the access-removal instruction. In the example, “disable access on 30 November” is an IT action, not evidence that all sums owed are settled. Keep final-pay calculation with the payroll specialist. A joiner, salary change and leaver should not share an ambiguous field called date.

Resolve the contradiction before replaying the change

Suppose the HR screen shows 3,250 but amendment AM-017-02 says 3,200. Put SAL-017-202611 into disputed, retain both references and do not send either value as a fresh approved instruction. The employer’s decision owner resolves whether the screen is wrong or a new amendment is needed. If 3,200 is confirmed, correct the screen, retain the correction note and resend the same approved version through the agreed delivery route.

This is a proposed operating control, not a claim that every vendor automatically rejects conflicts. In a manual workflow, the payroll instruction log can carry the same discipline. What matters is that a correction cannot masquerade as an already approved change.

Keep employment meaning separate from transport

Lithuania’s Labour Inspectorate distinguishes components of remuneration. Do not combine base pay, a one-off award and a reimbursement into a single salary column. Give the provider separate items and obtain the local treatment for each category. That preserves an explainable bridge between the approved input and the returned payslip.

Finish this contract before choosing automation: identify the fields that can travel automatically, the fields requiring manual submission and the person who checks the returned result. The test is whether another colleague could reconstruct November’s 3,200 input without asking the original editor what they meant.

Sources: vdi.lrv.lt