Payroll

The artifact

A review packet, addressed to a person

The deliverable is not a correction and not a filing. It is 4 findings that all land on one employee class on the same date, with the specific artifact to go and check named in each one.

P
PayrollAPP#eng-alerts
🔴 Benefits deduction rate dropped −55.1%class=hourly-ops
Baseline
7.16%
Now
3.21%
Confidence
99.9%
Started
Aug 12
Employee class
hourly-ops
Employees in class
412
HRIS update
Aug 12
Cycles since
2 (semi-monthly)
Likely cause · Four metrics on class=hourly-ops changed together on Aug 12, the day the HRIS version update re-keyed employee classes. Benefits deduction rate fell by more than half, effective tax rate fell, overtime hours rose, and gross-to-net rose as a consequence of the first two. The other three classes on the same register are unchanged, which rules out a company-wide policy or calendar effect. This is a flag for review, not a determination: the payroll team confirms against the carrier file, the overtime rule, and the jurisdiction mapping before anything is corrected.
  1. 1.Pull the benefits carrier eligibility file for class=hourly-ops and confirm the 412 members are still matched.
  2. 2.Check the overtime rule bound to hourly-ops for a lost daily threshold after the Aug 12 update.
  3. 3.Reconcile work-location to tax-jurisdiction mapping for the class against the pre-Aug-12 export, then take the withholding question to payroll tax counsel.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
P
PayrollAPP#eng-alerts
🔴 Overtime hours per employee jumped +66.3%class=hourly-ops
Baseline
3.729
Now
6.201
Confidence
99.9%
Started
Aug 13
Employee class
hourly-ops
Employees in class
412
HRIS update
Aug 12
Cycles since
2 (semi-monthly)
Likely cause · Four metrics on class=hourly-ops changed together on Aug 12, the day the HRIS version update re-keyed employee classes. Benefits deduction rate fell by more than half, effective tax rate fell, overtime hours rose, and gross-to-net rose as a consequence of the first two. The other three classes on the same register are unchanged, which rules out a company-wide policy or calendar effect. This is a flag for review, not a determination: the payroll team confirms against the carrier file, the overtime rule, and the jurisdiction mapping before anything is corrected.
  1. 1.Pull the benefits carrier eligibility file for class=hourly-ops and confirm the 412 members are still matched.
  2. 2.Check the overtime rule bound to hourly-ops for a lost daily threshold after the Aug 12 update.
  3. 3.Reconcile work-location to tax-jurisdiction mapping for the class against the pre-Aug-12 export, then take the withholding question to payroll tax counsel.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
What this is not

Payroll flags cycles and employee classes for human payroll review. It does not make tax determinations, does not decide what any employee is owed, and does not replace a payroll provider’s or an employer’s compliance obligations. A finding means go look at the carrier file, the overtime rule, or the jurisdiction mapping. What happened and what is owed are decided by the payroll team and, where withholding is involved, by counsel.

The ordering rule

Statistics decide whether the register changed. The written cause is generated afterwards and only ever describes a confirmed changepoint. In a domain with regulatory consequences, a model that gets to decide whether something is wrong is a liability, not a feature.