How configured pay rules move from scheduling to payroll.
A schedule is a plan. A time record is evidence of activity. A payroll-ready result is the outcome of validated rules applied to that evidence. Keeping those stages connected makes complex pay decisions easier to explain, test, approve, and reconcile.
By Phi HCM · Published
This guide explains a software and implementation pattern. It is not payroll, tax, employment, or legal advice. Organizations must validate configuration against their policies, contracts, jurisdictions, providers, and approved implementation design.
Five connected stages turn workforce activity into an explainable payroll handoff.
Treating these stages as one auditable flow reduces the gap between what operations planned, what employees recorded, what managers approved, what rules calculated, and what payroll received.
- 01
Capture the planned work
Start with the published schedule, worker assignment, location, role, pay group, effective-dated policy, and any approved exception. The schedule provides context; it does not prove what was worked.
- 02
Establish the worked record
Combine punches, timesheets, leave, attestation, manager corrections, and approvals. Preserve the source and effective time zone so the same event is not interpreted differently downstream.
- 03
Evaluate configured rules
Apply the organization’s validated rule hierarchy to the worked record. Thresholds, premiums, breaks, rounding, differentials, and exceptions need an explicit order and an effective date.
- 04
Produce payroll-ready results
Translate evaluated time into the earning codes, quantities, rates, cost assignments, and identifiers expected by the receiving payroll workflow. Keep the rule result traceable to its source.
- 05
Reconcile and approve
Compare counts, hours, earning codes, amounts, exceptions, and versions before release. Confirm that the receiving workflow accepted the intended records; creating an export is not the same as acceptance.
Do not reduce a pay decision to one unexplained total.
Consider a fictional eight-hour shift from 4:00 p.m. to midnight. The organization has approved an evening differential from 6:00 p.m. to 10:00 p.m. and a night differential after 10:00 p.m. The example below shows the trace a reviewer should be able to follow; it does not prescribe a pay policy.
| Source interval | Context evaluated | Configured result | Payroll-ready output | Evidence to retain |
|---|---|---|---|---|
| 4:00–6:00 p.m. | Approved worked time; assigned role | 2 base hours | BASE · 2.00 hours | Punches, assignment, approval |
| 6:00–10:00 p.m. | Worked time inside evening window | 4 base hours + evening premium | BASE · 4.00; EVE · 4.00 | Rule version and evaluated segments |
| 10:00 p.m.–midnight | Worked time inside night window | 2 base hours + night premium | BASE · 2.00; NIGHT · 2.00 | Rule version, time zone, approval |
| Reconciliation view | 8 worked hours | 8 base; 4 evening; 2 night | Three traceable earning-code rows | Source-to-output version record |
Six questions expose hidden rule assumptions.
- 1
Which effective-dated assignment and rule set should apply to the shift?
- 2
What happens when worked time crosses midnight, a location, or a policy boundary?
- 3
Which rule wins when overtime, a premium, and a scheduled differential overlap?
- 4
Can a reviewer explain each payroll-ready earning from the underlying time record?
- 5
What is re-evaluated when a punch or approval changes after an export?
- 6
How are rejected records, corrected versions, and receiver acceptance tracked?