Skip to main content
30-day free trial. No payment required. Start free
SikaBooks Help Center Guides for every SikaBooks workspace
Human Resources · Guide 9

HR and Payroll Integration

HR and Payroll share the canonical workforce employee. An HR-created employee starts as Not ready. An authorized HR reviewer completes the readiness review for identity, employment...

HR administrators and managers Updated September 3, 2026

HR and Payroll share the canonical workforce employee. An HR-created employee starts as Not ready. An authorized HR reviewer completes the readiness review for identity, employment, position, hire date, compensation, payment, and statutory prerequisites. A complete review enters the Payroll handoff queue as Ready for Payroll. A Payroll reviewer then creates exactly one linked profile; SikaBooks never silently enrolls the employee. Payroll-only and HR-only businesses continue operating independently.

Before marking an employee ready, review the readiness panel on the employee workspace. Resolve every blocker and confirm the effective date. Readiness is a reviewed handoff, not a pay-run action: it creates no payslip, payment, journal, or statutory filing. If Payroll is not enabled, HR retains the employee normally and shows the integration as unavailable.

Paid leave has no automatic pay effect. Unpaid leave affects Payroll only when its leave type is mapped to an unpaid-leave component and a daily-rate divisor is configured. Missing configuration blocks calculation rather than guessing.

Approved or cancelled unpaid leave creates a versioned Payroll-impact record. Calculated and approval-pending runs are reopened for recalculation; approved but unposted runs lose approval. Posted payslips and journals remain immutable, so late changes enter a reviewed future-period adjustment or correction flow. Review affected periods before making the final HR leave decision.

Approved bank and statutory changes do not update Payroll immediately. They enter a protected Payroll handoff queue. Payroll rechecks permissions, separation of duties, and the original-value fingerprint before applying the reviewed values. When Payroll is unavailable, the HR approval remains recorded and is clearly shown as unapplied.

This protected profile handoff records the employee request, HR reviewer, Payroll applier, effective date, old-value fingerprint, and result without exposing unmasked payment or statutory data in ordinary audit messages.

The Payroll reviewer can apply or reject a handoff. A stale-value warning means the Payroll profile changed after HR approved the request; verify the current record instead of forcing the old request through. When the same owner performs both reviews, SikaBooks requires and records an override reason.

Only one leave-accrual source should control a period. Existing Payroll accrual remains selected until HR calendar accrual is enabled or an administrator explicitly switches it. Scheduled exits exclude employees from ordinary runs after the effective date while preserving a final-settlement path.