HR Handoffs and Late Leave Corrections
Payroll remains the owner of compensation, payment details, statutory deductions, pay runs, payslips, disbursements, and Payroll journals. HR owns workforce identity, organisation,...
Payroll remains the owner of compensation, payment details, statutory deductions, pay runs, payslips, disbursements, and Payroll journals. HR owns workforce identity, organisation, contracts, leave decisions, employee documents, and employee self-service. When both modules are enabled, they share one workforce employee but do not silently overwrite each other.
Ready for Payroll Enrollment
An HR-created employee does not automatically enter a pay run. HR reviews identity, employment, position, hire date, compensation, payment, and statutory prerequisites, then sends a Ready for Payroll handoff.
In HR and Payroll review:
- Open the employee handoff.
- Verify the HR readiness snapshot and effective date.
- Confirm pay basis, payment method, and statutory readiness.
- Apply the handoff to create exactly one linked Payroll profile, or reject it with a reason.
- Complete any remaining Payroll-only setup before including the employee in a run.
Applying enrollment does not calculate salary, post a journal, send a payslip, or release money. Repeated application is idempotent and cannot create a second linked Payroll employee.
Bank and Statutory Changes
An employee may request protected changes from self-service. HR verifies the request first. Approved bank and statutory changes then enter Payroll review instead of changing the Payroll profile immediately.
Payroll must verify the supporting evidence, enter the structured Payroll values, and confirm the existing value has not changed since HR approval. A stale-value failure protects a newer Payroll update from being overwritten. The HR approver and Payroll applier are recorded separately. When the same verified owner completes both steps, an override reason is required and retained.
Leave Changes Before Posting
Approved or cancelled unpaid leave creates a versioned Payroll impact when the required HR and Payroll configuration exists.
| Pay-run state | SikaBooks response |
|---|---|
| Draft | The next calculation uses the current approved leave data. |
| Calculated or approval pending | The affected run is reopened and must be recalculated. |
| Approved but not posted | Approval is removed; recalculate and review again. |
| Posted | The payslip and journal remain unchanged; a reviewed future adjustment is required. |
If unpaid leave cannot be calculated, configure both the unpaid-leave pay component mapping and the daily-rate divisor. SikaBooks blocks rather than guessing.
Late Leave After Posting
Use the Late leave tab in HR and Payroll review for leave approved or cancelled after the affected Payroll period was posted.
- Review the original leave request and affected period.
- Select a future open run after that period.
- Enter the reviewed adjustment amount: positive deducts from net pay and negative refunds the employee.
- Record a clear reason.
- Schedule the adjustment for calculation and review in the chosen run.
Never edit a posted payslip or journal to accommodate late leave. Use a future-period adjustment or an explicit correction run tied to the posted run.