Use case

Union and hourly payroll, rules applied every time

Collective agreements and hourly pay practices are rules. When they live in people's heads, they are applied differently each cycle. Written down, they are applied the same way every time.

By Dan Agarwal, founder·Updated

Agreement and policy rules written down, with their source.

The same rule applied at every site it covers; local variations configured.

Conflicting rules surfaced for your team to decide.

Hourly and union workforces carry the most pay rules per employee: shift differentials, premiums, overtime thresholds, guaranteed hours, seniority rates, and dues. Payroll and time systems handle much of this, but the gaps between them are usually covered by experienced analysts who know each agreement.

PCLnXAI captures those rules during discovery and applies them in the pipeline, on every line, at every location, whatever the payroll platform. The analysts who know the agreements review exceptions instead of re-checking every line.

Rules out of people's heads, into the pipeline
  • Collective agreements
  • Pay policies
  • Long-standing practices
Written, versioned rules
Scoped by site, payroll, or agreement
  • Applied to every line
  • Exceptions to analysts
  • Which rule applied, per cycle
Rules configured in your payroll or time system stay there. The pipeline covers the rules applied between systems.

Rules that typically live outside the systems

  • Which premiums are priced in the time system and which are priced in payroll.
  • Pay codes that must carry hours, and codes that must carry amounts.
  • Agreement-specific overtime, call-in, and guarantee rules at certain sites.
  • Step and seniority rates that should advance on a date.
  • Union dues and remittance files, and how they reconcile.

Consistency across locations

When the same agreement applies at many sites, the same rule is applied at all of them. When a site has a local variation, it is configured for that site. The difference is written down, not remembered. See union payroll mechanics for background.

When rules conflict

Over time, payroll teams accumulate overlapping rules. Discovery consolidates them, and where two rules disagree, the conflict is surfaced for your team to decide instead of being resolved silently.

Public sector and prevailing wage

The same approach covers public-sector agreements and prevailing wage work, where the rules are detailed and the evidence matters. See FLSA 7(k) public safety overtime and prevailing wage and Davis-Bacon for examples.

Where this sits in the payroll cycle
Source systems
  1. 1Intake
  2. 2Validation
  3. 3Reconciliation
  4. 4Exceptions
  5. 5Approval
  6. 6Close
Your payroll platform
Source systems feed six stages in your environment. Nothing reaches Your payroll platform until a person approves the load.

How PCLnXAI handles union and hourly rules

We document each rule with its source, whether an agreement, a policy, or a long-standing practice, and the pipeline applies it. Changes to rules are versioned and approved, so you can tell which rule applied in which cycle.

Frequently asked questions

Does this replace pay rules in our payroll or time system?

No. Rules configured there stay there. The pipeline covers the rules applied between systems, which are usually manual today.

Can rules differ by site or agreement?

Yes. Rules are scoped by location, payroll, or agreement as needed.

What happens when an agreement changes?

The rule is updated with an effective date and approved, and the record shows which version applied to each cycle.

Do you handle union dues files?

Yes. They are tracked and validated like any other expected input.

Further reading

See it on your own payroll.

We map how your payroll actually runs, then prove the system on your own data across live pay cycles, with your team approving every load.