Payroll operations, checked before approval
Payroll stays quiet. Every run is checked first. Payroll oversight on the platform you already run, with a named lead and a named backup on every cycle.
No deck. No pitch.
Who this is for
Nobody notices payroll until it’s wrong.
“We find the mistakes after the money moves.”
What changes: Exceptions surface before the run, while they’re still corrections.
“I approve payroll, and I can’t tell what changed.”
What changes: Every run arrives checked, with each exception explained.
“Three entities, three sets of rules, and nobody wrote them down.”
What changes: Entity and state rules written into a runbook and checked every cycle.
How it runs
The same five stops, every cycle.
Cut-off
Changes close: new starters, leavers, timesheets and deductions.
Check
We match the run against your records and the last cycle.
Explain
Every exception comes with what happened and the fix.
Approve
You review and approve. Nothing moves without you.
Submit
Your team submits. We watch the funding and filing dates.
The check
What we check before you approve
Each cycle, the Check stop runs the same list. Nothing on it is new to a payroll team. What changes is that it happens before the money moves, every time, by someone whose job it is.
- New starters and leavers. Start dates and final pay, with the rules of the state each person works in.
- Pay changes. Every rate or salary change matched to a written approval.
- Time and overtime. Hours against schedules and overtime against policy, with missing punches chased before cut-off.
- Deductions. Benefits deductions against the carrier invoice, retirement contributions, garnishments.
- Taxes and registrations. Each state and entity the run touches, with its accounts open and its rates current.
- Retro pay and corrections. Anything that reaches into a closed period, explained before it runs.
What moved and why goes into the approval note, so the person approving can see each exception and its fix without opening the platform.
The runbook
Rules written down, checked every cycle
Entity and state rules live in a runbook we write at the start and keep current. It holds the pay groups and cycles for each entity, the cut-off calendar, who approves what, the state rules that bite on final pay and deductions, the funding and filing dates we watch, and who covers when the lead is out.
When a rule changes, the runbook changes first and the next cycle is checked against it. When someone new approves payroll, the runbook is what they read.
What you keep
Approval stays with you
You approve every run. The platform and the vendor relationship stay yours, and so does every employment decision. We do not submit payroll. Your team submits once you approve, and we watch the funding and filing dates after it goes.
What it costs
Payroll oversight,from$1.5ka month
- Exceptions
- Inside the monthly fee
- Approval
- Always yours
- Who checks it
- Your lead, with a named backup
Your entities, states and pay cycles set the final number, in writing. It runs on its own or alongside one of our monthly plans.
What the record shows
As run on ADP Workforce Now
2 systems1 record
Two payroll systems consolidated onto one system of record, with exception review moved to the start of the cycle.
What finance asks first
Is this payroll software?
No. You keep the platform you run. We check the work around it, every cycle.
Who submits payroll?
Your team does, once you approve the run. We check it before it goes and handle what it flags.
How do you charge for exceptions?
They’re inside the monthly fee. If volume turns out to be unusual, we say so and rescope in the open.
Which platforms do you work on?
Rippling and HiBob first. We take others, such as ADP Workforce Now, case by case.
Tell us how payroll runs today. We’ll show you where it can slip.
In a 20-minute call we look at your cycle, your entities and your platform. A fixed monthly number follows in writing.