Payroll engines do perfect math. But only with perfect inputs. Are yours?
The engine isn't the problem. The setup is: stale rates, wrong overtime classes, missed deductions, outdated work locations. Payroll validation checks the inputs, so the run only pays what the rules allow.
PAY ERRORS HIT THE MARGIN FROM BOTH DIRECTIONS.
Overpayments rarely come back. Underpayments trigger costly corrections and can cost you good workers. Beyond the correction itself, the real cost is losing a good worker, leaving a billable seat unfilled, and paying to recruit a replacement. Every pay error also creates wage-and-hour exposure that sits with you, not the client.
FOUR OVERLAPPING RULE SETS CAN GOVERN A SINGLE HOUR OF OVERTIME.
Each item below is applied by each worker's location, varying by state, changing without warning. Today that hierarchy is held together by hand, every cycle.
HERCULES CHECKS THE INPUTS BEFORE ERRORS GET PAID.
Rates, overtime rules, and multipliers against the current contract and law
Deductions, garnishments, and work-location data against the approved setup
Worked and paid compared line by line
Exceptions out before the run, with the rule and the fix
Hand
SMART AND STACKED.
Overpayments stopped before they need recovering - money that rarely comes back in full
Underpayments stopped before they cost you a worker's trust or the worker
Hours back every cycle - the team handles more volume at higher quality without adding headcount
Audit-ready proof for every pay decision where the rule, the source, and the sign-off are on file before anyone asks
Hand
FOUR WORKSTREAMS, ONE CRITICAL PROCESS. START ANYWHERE.
Address any point in the process, or fix all four, to protect margin from end-to-end.
Pay rates, overtime multipliers on the pay rate (which differ from bill-rate overtime), shift differentials, deductions, garnishments, and contract- and location-specific pay terms.
Yes. Rules apply by each worker's location, including state regimes like California's daily overtime and double-time, and Hercules flags location and tax-jurisdiction mismatches before they pay out.
Hercules tracks cumulative, stateful controls, withholding and contribution caps that stop once an annual threshold is crossed, and aggregates hours across a worker's concurrent assignments to catch threshold-driven changes like ACA eligibility and tenure-based rate shifts that per-assignment checks miss.
Both, plus duplicate payments. Overpaid money rarely comes back in full; an underpaid worker may not come back at all.
Through the worked ↔ paid ↔ billed three-way match: hours paid but never billed surface as pure margin loss, and hours worked but mispaid surface before the run.
Every pay decision keeps its rule, its source, and its sign-off — audit-ready before anyone asks.
