People Systems Interoperability

The £416.67 gap: trace a UK pay change without replaying it twice

A correct HR profile cannot close a pay-change case. In this fictional England example, Finance and the employer agree £65,000 annual base pay from 1 December 2026, but the payroll preview still uses £60,000. The payroll operator owns the next repair because the earliest unfinished dependency is payroll inclusion.

The dates, people labels and outcomes below are illustrative. They describe the record we would require, not a transaction run in any provider account.

Completed fictional event record

Time / eventEvidence in the exampleResult and owner
2 November, 10:00 UTC: Finance approvesInstruction PAY-042-v1: GBP £65,000 annual base, effective 1 December; unchanged hoursBudget approved; People Ops submits through the employer's agreed channel.
3 November, 14:00 UTC: employer accepts changeAmendment AM-042 agrees amount/date; required execution completed for this exampleEmployment step complete; employer payroll team owns inclusion.
18 November, 09:00 UTC: preview checkedPAY-042-v1 versus payroll preview: £60,000 annual baseChange held for correction; unrelated payroll is not automatically stopped.
18 November, 11:00 UTC: discrepancy assignedOne matched employment record; no second request; case EX-042 openedPayroll operator confirms original request state before replay.
19 November, 12:00 UTC: corrected preview£65,000 annual base; £5,416.67 monthly gross baseFinance checks the revised preview; still awaiting final payroll/payment.
First affected payment: closure conditionActual payroll base, relevant deductions and payment reconcile to approved correctionClose only when evidence exists; tell employee the confirmed outcome. This last step is not marked completed.

For illustration the operator has agreed a 20 November preview-approval deadline for December. It is a scenario input, not a published provider or UK statutory cutoff. Real workflows require their own calendar and timezone. Remote separately publishes a general fifth-of-month amendment submission rule; do not replace a specific account calendar with the fictional date. Remote: Request amendment to employee agreement.

Reproduce the variance

£60,000 ÷ 12 = £5,000 monthly gross base. £65,000 ÷ 12 = £5,416.666…; rounded to pennies, £5,416.67. Difference: £416.67 for one full month under this convention. Payroll may allocate rounding across periods. No net payment or tax result is implied.

A mid-month effective date, changed hours, unpaid absence, bonus or another pay frequency invalidates this simple expectation. Set those cases aside for the payroll calculation; do not use £416.67 as a universal arrears instruction.

Three different failures require three different repairs

Amendment not accepted: People Ops routes the exact salary instruction to the employer's amendment owner. Do not label it a connector failure before checking whether an authorised change exists. Client budget approval is not the employment agreement. GOV.UK: Changing an employment contract: getting agreement.

Amendment accepted, payroll stale: The payroll operator reconciles the employer change to the payroll record. Obtain the current processing state, correct the input through the authorised channel and inspect the new preview. Ask for the expected payment date if the calendar cannot be met.

Payroll correct, Personio stale: The employment/payroll outcome may be correct while the HR mirror is behind. With Remote's EOR route, investigate Remote's authoritative value and Personio's integration behaviour. Re-entering a salary in Personio is not the reverse of that connection. Remote: Source of truth with Personio and Remote.

Replay only after establishing the original state

Search for the event and destination employee before sending another instruction. A missing HR value does not show whether an employer amendment is pending, accepted or already paid. Preserve the original instruction version, request reference and timestamps. If the state is unknown, assign it for investigation rather than sending a duplicate.

When the original failed permanently, use the provider's documented recovery action or an agreed manual correction, recording why replay is safe. Reconcile exactly one intended outcome. A duplicate salary request should be investigated even if both requests contain the same amount; dates and downstream payment actions can differ.

For Deel EOR specifically, an active amendment under review prevents another amendment request. That is a useful signal to inspect the existing request rather than imitate a network retry. Deel: Request changes to an EOR contract.

If the deadline is missed

The employer/payroll operator decides the lawful and available correction route, including any next-cycle arrears or supported off-cycle process. The client approves the resulting cost and People Ops communicates the confirmed date. Do not promise an off-cycle payment from a support reply target.

Hold the disputed change's acceptance, not the employee's undisputed wages. Capture any exception to the planned payroll date and its owner. A case closes with reconciled payroll and payment evidence, not an email saying “done”.

Run the scenario and its sensitivities, compare the operating routes or use the existing missing-record recovery playbook.

By People Systems Interoperability editorial desk · Updated