Missing pay
Hours clocked with no pay on the run, or someone on your regular staff left off it.
Pay run check
Catch payroll mistakes before the run is approved.
- Every pay run checked against written rules while it is still a draft.
- Payroll sees only what needs a look, each flag with the rule and the math behind it.
- Every run, before approval
- Employees by record ID
- Quoted once we've seen your payroll
Example
A draft pay run, checked.
Four of 212 people on this run need a look. Everyone else passed every rule.
Flags on a draft pay run
| Record | Rule | What the check found | The math |
|---|---|---|---|
| E-1042 | Missing pay | 32 hours clocked, no regular pay on the run | 32 × $19.50 = $624.00 missing |
| E-2217 | Far from history | Gross pay of $3,912.40, against a usual $1,450.00 | 2.7 times the median of the last six runs |
| E-0381 | Overtime | 46.5 hours in the week at $22.00, no day over 8, all paid at the regular rate | 6.5 × $11.00 half-time = $71.50 owed |
| E-1675 | Minimum wage | 30 hours at $15.50 an hour, below the $16.90 minimum for that location | 30 × $1.40 = $42.00 owed |
What it checks
The mistakes hardest to undo after payday.
Each rule is written down and agreed with you before the first run. They are calculations, not legal advice.
Pay far from history
Gross pay well above or below what that person usually earns, which is how a typo in a rate or in hours shows up.
Overtime owed and paid
Overtime worked out from the punches, against what the run pays, by person and week.
Minimum wage
Every hourly rate against the minimum for the place the work was done.
Approved hours
Hours on the run against the hours managers approved.
Runs that overlap
Two runs covering the same days, or the same person paid twice for them.
How it works
Set up once, then every run.
Connect
We read the draft run from your payroll system: ADP, Gusto, Paychex, Rippling or another, through its API or an export.
Agree the rules
We write the rules down with whoever runs payroll today, set the limits with you, and test them on past runs.
Check every run
Each draft is checked as soon as we have it. Flags go to payroll by email or chat: fix, check again, approve.
The same engine as our wage and hour audit and W-2 check, run every pay period.
Production case study · multi-state fitness
One payroll check found $120k a year.
At the business where we built it, a check of payroll found split-shift premiums the payroll system was miscalculating. Measured over six months and annualized, the fix came to $120k a year. See the full case study
Questions
Which payroll systems does it work with?
ADP, Gusto, Paychex and Rippling, and any other payroll system that can export a draft run. Where its API exposes the draft run, we read it directly; otherwise we work from the preview export.
Does it change anything in payroll?
No. It reads the draft and flags what needs a look. Your team makes every change and approves the run.
What happens after approval?
The approved run can go straight into your books, split by location, with payroll journals by location.
Who sees employee names?
Flags list people by record ID. Your payroll team looks the ID up in your payroll system, where names already are.
Is this legal advice?
No. The rules are calculations agreed with you, and this is not legal advice. Questions about what the law requires go to your counsel; our wage and hour exposure audit is built for that review.
What does it cost?
A setup fee, then a monthly fee based on how many people you pay and how often, quoted once we've seen your payroll.
Talk to us about checking your pay runs.
Tell us your payroll system, how many people you pay and how often. We'll reply with the rules we'd start with.