CHECKLIST
Stop a late payroll change becoming three separate chases
By Olivia Smith · Senior HR Operations Manager
Updated
Start with one complete change
A late salary change or expense request becomes difficult when different people hold different parts of the answer. The manager knows what was promised, People knows the employee’s terms, payroll knows the treatment and finance controls the money. A complete change record joins those facts without asking everyone to interpret the same email chain.
Use the same intake structure across Estonia, Latvia and Lithuania, but let the country specialist decide the applicable payroll handling. The regional team should standardise the question being asked, not invent a common tax treatment. This approach is especially useful when one People lead supports all three countries and cannot keep every unresolved detail in memory.
Capture the minimum decision evidence
Record the employee identifier, employment country, requested change, gross or net basis where relevant, proposed effective date and approving manager. Include the business reason and a link to the relevant agreement. Identify whether the employee has already been told a specific date or amount. That promise changes the urgency even when it does not change the lawful payroll treatment.
Avoid requesting information already held in the payroll system. Instead confirm that the country owner has access to the current record. The intake should reduce duplicate handling and make missing evidence obvious. It should not become another uncontrolled employee database maintained by a well-intentioned coordinator.
Make the cutoff decision explicit
If the request arrives after the agreed input deadline, ask the provider which options are available: a permitted correction, an additional payroll process, or the next normal cycle. Obtain any extra charge and employee impact before the business chooses. These are questions to resolve for the actual case, not universal options guaranteed in every country.
Write down who decided and what will happen next. Acknowledged means the request was received; accepted means payroll has enough information and has agreed the action; completed means the result has been checked. Keeping those stages separate prevents a quick reply from being mistaken for a completed correction. It also gives the employee an accurate update.
Verify the result and improve the input
After the agreed action, compare the outcome with the approved request and ask the provider to explain any difference. Do not close the case solely because a payslip has been issued. People should confirm that the employee received a useful explanation, while payroll confirms the calculation and finance confirms any related settlement.
For repeated late changes, identify the source: manager approval, an unclear deadline, missing documentation or an unsuitable intake process. Fix that specific cause in the next cycle. Avoid using a broad error count to blame a provider for changes it never received on time.
Teamed’s named-contact proposition is relevant when the team wants someone to coordinate the payroll question through to the right specialist. Test it using this checklist during procurement. Ask who owns the case after the first reply, who can authorise the next step and how People will know the correction is finished.
PUT IT TO WORK
Late-change handover sheet
| Step | Action |
|---|---|
| Request | Country, employee, change and effective date |
| Evidence | Approval and relevant agreement |
| Cutoff choice | Provider confirms available route and cost |
| Status | Received, accepted and completed stay distinct |
| Closure | Result checked and employee informed |
Sources behind this page
Teamed service · 2026-10-19
Published designated contact, absence cover and HR/legal specialist support.
Teamed country register · 2026-10-19
Estonia, Latvia and Lithuania listed in the provider register. Role, worker and service eligibility require confirmation.