Situations · Payroll keeps breaking
Payroll keeps breaking. The system is not the problem.
A wrong deduction, a late new hire, a state nobody registered in, a number finance cannot tie out. The fix is the setup and the cycle around it. We prepare and check every run in your HRIS, and you approve it.
Pre-run checkThis cycle
- Changes since last run
- Entered and approved
- Exceptions
- Reviewed before the deadline
- State accounts
- Current, every state
Ready for your approval.
How it shows up
Three ways a payroll problem announces itself.
Moment 01
The run is wrong again.
A deduction that should have stopped, a retro that never went in, a new hire paid from the wrong date. Each one small. Each one a conversation you did not plan to have.
Moment 02
Someone was paid late.
A state account nobody opened, a bank file that bounced, an approval that sat in an inbox over a holiday. The person waiting does not care which.
Moment 03
Nobody can explain the number.
Payroll does not tie to the ledger, and the person who could explain why has left or is on leave. Finance closes the month with a plug.
The first 30 days
Find the causes first, then rebuild the cycle around them.
The last three runs Days 1 to 5
We go through the last three cycles line by line, list every exception and its cause, and check your state accounts and tax registrations against where you have people.
The cycle, rebuilt Weeks 2 and 3
Changes entered in the system as they happen, a pre-run check with exceptions reviewed before the deadline, and the run prepared for your approval on a fixed day.
The controls Week 4
A monthly report finance can tie to the ledger, the compliance calendar for every state, and a written scope for what we keep running.
If the setup itself needs rebuilding, we say so in week one and quote it as a fixed project.
What’s included
Every cycle checked before it runs.
- 01
A named lead and a named backup who know your setup
- 02
Payroll preparation, every cycle, for your approval
- 03
A pre-run check: changes, exceptions and approvals before the deadline
- 04
New hires, changes and leavers entered in the system as they happen
- 05
State accounts and tax registrations checked against where you have people
- 06
A monthly payroll report finance can tie to the ledger
- 07
The compliance calendar: registrations, filings and notices
- You approve every run. Amended filings for earlier periods and a rebuild of the setup are quoted separately.
What it costs
Managed people ops, from $6k a month
At 45 people and under, sized to your team on a fit call.
- Starts
- In the first week, on Rippling or HiBob
- Term
- Six months, then month to month
- Who owns it
- Your lead, with a named backup
Your headcount sets the plan. Enter it on the pricing page to see the plans for yours.
Questions people ask after a bad run.
Do you take over the run itself?
No. We prepare and check every cycle inside your system; you approve it, and it goes out under your company. The checking is where the problems were, so that is where we sit.
What if the problem really is the platform?
Usually it is the setup, not the platform. If the setup needs rebuilding we say so in the first week and quote it as a fixed project, then run the cycle on the rebuilt setup.
Can you fix the runs that already went wrong?
We trace each one to its cause, set out the correction in writing, and carry it into the next cycle where the rules allow. Amended filings for earlier periods are quoted separately.
Twenty minutes. Bring the last run.
We will tell you what went wrong, what we can take this cycle, and what needs a decision from you. A written scope follows the call.
Book a 20-minute fit call