Because pay changes are usually applied by overwriting a figure. The new number is right, and the reasons, timing and approval are in an email nobody kept.
A dated change to somebody's pay, recorded as an event on the personnel record with its effective date, approver and reason.
Each revision is an event, not an edit. The previous structure remains, the new one takes effect on its date, and the approval and supporting review are attached.
An employee asks why a colleague hired later earns more. The revision history shows what changed, when, and what review supported it.
It does not model pay bands or flag inconsistency across a team. Those are analyses you run against the data, not judgements Nest makes.
Payroll applies revisions pro-rata from the effective date. Books posts the changed cost. Loop's cost rates update for future work, not retrospectively.
Yes, and payroll will calculate the arrears rather than requiring a manual adjustment.
Whoever you designate — usually a level above the reporting line.
Their own, yes.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.