Apply dated pay changes without losing context
For an actual change of agreed terms, use consecutive compensation periods. A correction to an existing row is different from recording a new agreement from a new date.
Recommended procedure
- Confirm the approved effective date and exact new amount/basis/frequency.
- Open the current compensation record and inspect its employment and dates.
- End it the day before the new agreement starts, preserving all other intended fields and supplying the appropriate change reason.
- Save and verify the predecessor.
- Add the successor agreement from the new date within the same employment, or the correct new employment for a rehire.
- Reload both records and check no gap/overlap was introduced unintentionally.
- Tell the authorised Payroll preparer the exact HR boundary to use in service periods.
Worked timeline
| Agreement | Period | Amount/basis |
|---|---|---|
| Existing | 1 October–14 November | GBP 2,400 MONTHLY |
| Successor | 15 November onward | GBP 2,500 MONTHLY |
Starting the successor on 14 November would overlap. Leaving the earlier record open also overlaps. Both can be correct business amounts but still fail temporal validation.
The browser makes separate saves. If the new agreement fails after the old one closed, the old closure remains committed. Reload actual state, correct the new record and complete the approved change. No atomic multi-record “pay rise wizard” is provided.
Payroll implications
A service period covering 1–30 November cannot use one Employee snapshot when compensation changes on the 15th. The snapshot service requires one covering compensation record; the Payroll preparer must use appropriate split periods under that workflow. Employee does not calculate statutory proration or decide a divisor automatically.
Editing source HR does not rewrite an already frozen Payroll snapshot or approved run. Corrections to Payroll need its own permitted procedure.
Recovery
If another user changed the predecessor, preserve your intended change, cancel and reopen the editor for current values/version. Do not increase a version manually or repeatedly submit stale data. For an erroneous historic amount, record the approved correction evidence and assess affected Payroll snapshots separately rather than claiming a new source value automatically recalculated them.