System control that restricts ordinary edits to a reviewed payroll run so approval and payment use a stable version.
A payroll lock is the point at which payroll data for a run is restricted from ordinary editing so the run can be processed and controlled consistently.
Locking matters because payroll cannot stay reliable if data keeps changing during review, approval, and payment preparation. A lock helps preserve the version of payroll that was actually reviewed.
Payroll lock matters because it affects:
It is one of the clearest system-side controls in payroll operations because it turns “current working data” into “data that payroll is actually using for this run.” It protects payroll against quiet last-minute edits that were never part of the reviewed version.
Payroll lock appears after the run is substantially prepared but before or during the approval stage. In practice, payroll may:
That makes locking a control mechanism closely related to cutoff and approval. Cutoff says when ordinary changes should stop. Lock is the system-side step that enforces that discipline for the specific run being processed.
| Term | What it controls |
|---|---|
| Payroll cutoff | The deadline for getting ordinary changes into the current run |
| Payroll lock | The system restriction that stops ordinary edits to the reviewed run |
| Payroll approval | The decision to move the reviewed run forward |
| Payroll close | The final closeout after processing is complete |
Payroll prepares the current run and then locks it for review.
If a manager submits a change after the lock, payroll may need to handle that change separately instead of quietly editing the already reviewed run. The lock protects the integrity of the payroll version being approved.