Union and hourly payroll on Oracle HCM Cloud
Collective agreements turn every timesheet into a set of rules. Those rules need checking where the hours enter, not only where they are calculated.
Hourly and unionized workforces carry the most pay rules per person: overtime thresholds, shift and weekend premiums, call-in pay, step progressions, and dues. In Oracle HCM Cloud many of these are calculated in time or payroll rules and Fast Formulas. The inputs that drive them, such as hours, codes, shifts, and dates, still come from other systems and still need to be right.
PCLnXAI checks those inputs against the rules your agreements set, before they load. A premium coded to the wrong shift, overtime that does not fit the hours worked, or a step that should have advanced is caught at intake. Read union payroll mechanics for background.
What gets checked
- Hours by day and week against the overtime thresholds in each agreement.
- Shift, weekend, and holiday premiums against the hours and times they apply to.
- Rates and steps against the agreement and the employee's progression.
- Dues and agreement-specific deductions against membership.
Interpretations become rules
Agreements leave room for interpretation, and payroll teams settle those interpretations over years. The pipeline records them as written rules, so the same interpretation applies at every location and every period, and the reasoning is visible when someone asks.
How PCLnXAI handles union and hourly rules
We work through your agreements with your payroll and labor relations teams, agree how each rule is checked, and build those checks into the pipeline in front of Oracle.
Frequently asked questions
Does this change how Oracle calculates overtime?
No. Calculation stays in Oracle. The pipeline checks that the inputs feeding that calculation fit the agreement, so the calculation starts from the right data.
Can it handle several agreements at once?
Yes. Each agreement's rules are kept separately and applied to the employees it covers.