GUIDE
Approve and recover Lithuanian payroll changes without losing the version
By Asher White · Senior Benefits Specialist
Updated
On this page
The approval belongs to the version
A payroll approval is not permission for every later edit to that employee’s record. In our fictional example, finance approves SAL-017-202611 version 2: EUR 3,200 gross monthly from 1 November. A colleague subsequently changes the amount to 3,250. Version 3 must return to draft and needs fresh supporting authority and approval. Version 2’s approval remains evidence of what was approved; it cannot be copied onto the edited amount.
Use the same rule whether changes move through an integration or an uploaded file. The editor prepares the instruction, an authorised approver approves its content, the operator delivers that version, and the payroll owner reconciles the result. A small team can combine some roles where its policy permits, but it must still preserve the separate decisions.
Use states that describe what has actually happened
Draft means editable and not cleared for processing. Approved means a named decision covers the exact instruction version. Sent means delivery was attempted; it does not mean accepted. Accepted means the receiver has acknowledged the particular record and processing destination. Reconciled means the returned result matches the approved instruction or has an explained, approved difference.
Rejected and disputed are working states with a reason. “Accepted with questions” is too vague for a pay-affecting change. If the amount is unresolved, leave that instruction disputed while the unaffected items continue only through the payroll owner’s agreed process. These are recommended operating states you can implement in a change log; they are not vendor status names.
Recover a duplicate without creating a second payment
In the example, delivery times out after SAL-017-202611 version 2 was sent. Do not create a new event number to make the error disappear. Search the receiving log for that event and version. If acceptance is confirmed, attach the acknowledgement to the original delivery attempt. If it is not confirmed, use the provider’s agreed retry or manual reconciliation process and check that only one change will be applied.
A useful incident record is: event SAL-017-202611; attempts A1 and A2; accepted record R-810; active instruction count one; November base input 3,200. “Retry succeeded” alone does not prove that A1 did not also succeed. Test duplicate handling explicitly before depending on it.
A late instruction needs a pay decision, not a hidden date change
Suppose a valid November change arrives after the provider’s agreed input cutoff. Preserve its real effective date and mark late pending payroll decision. The payroll owner decides the appropriate permitted correction route with the employer and local specialist, including whether an amended run or another payment action is required. Do not move the effective date to December to make the file pass.
Record the disposition against the original event: affected period November, received after agreed cutoff, current run state, chosen correction route, authoriser, employee explanation and reconciliation reference. This page does not set a Lithuanian payment deadline or authorise delayed pay. Its control is to expose the missed input while the responsible team resolves the actual payment obligation.
Close with a result, not an email
Close the incident when the returned payroll input or result shows the intended version and the exception has a documented resolution. In our worked example the first export incorrectly contains 3,250. The operator holds release, confirms version 2 with finance, obtains a corrected result of 3,200 and records the replacement file reference. The initial result remains attached to explain the correction.
For a colleague covering next month’s run, the useful handover is “version 2 reconciled against R-810; version 3 withdrawn; no duplicate active instruction”. That is more precise than “finance sorted it”. Keep the evidence in the authorised payroll repository and use aliases in the planning tool.
PUT IT TO WORK
Recovery log — fictional completed dispositions
| Record / decision | Completed example or rule |
|---|---|
| Edited after approval | Version 3 draft; AP-214 belongs to version 2 only. Obtain new authority before version 3 can proceed. |
| Timeout after send | A1 uncertain; inspect receiver before retry; A2 linked to original event, not a new salary change. |
| Duplicate found | One active instruction retained; duplicate suppressed through the agreed provider process; verify returned input. |
| Late November change | Real effective date retained; payroll owner decides lawful correction route and employee communication. |
| Final result | Version 2 / R-810 reconciled at 3200.00; version 3 withdrawn; incident closed with evidence. |