Gross-to-net, independently checked to the cent.
A parallel run shows that payroll ran. It doesn’t show that net pay is right. Two systems agreeing with each other is not the same as either being correct.
The explainer · 3 min 36
The January table load, the back-test, a platform move, and one mismatch on a stale wage base. Wage bases per SSA, every other number invented.
The result
VeriQuant computes an independent gross-to-net for every employee and pay period from your own tax tables, wage bases and plan rules, and grades the platform’s figures against it. Every case is a match, or a mismatch that names the first step where the two calculations part ways.
Here the platform is still on last year’s Social Security wage base. The net pay is off by the exact tax that should have been withheld, and the report says so.
Drive the platform’s own pay-calculation screens per employee and match the on-screen results against the rulebook.
Read pay results through an adapter or results API in a non-production tenant.
Export the cases as a sheet in your field names, run a parallel payroll your usual way, and hand back the register.
Federal withholding tables, the wage base, contribution limits, dozens of state and local tables. Each lands as an edition with an effective date. VeriQuant re-grades every case against the new edition and names the factor that moved, so a stale table is found before the first pay run of the year, not by an employee in February.
Twice-yearly Workday releases, SuccessFactors support packs, customer go-lives. Re-run the same graded employees after each and see whose net pay moved. The employee profiles your team already keeps for parallel runs load as cases without reshaping.
Honest fit
Your engine handles thousands of jurisdictions, effective dating and garnishment priority. VeriQuant is a per-pay-period check that takes year-to-date figures as input. It verifies the engine. It does not replace it.
Federal withholding permits whole-dollar rounding, some states truncate, and your legacy system has habits of its own. Each convention is declared in the rulebook. Penny-for-penny agreement is the bar.
The tables you license or maintain never leave your network. VeriQuant runs inside it as a container or a single Java file, with an offline licence, no telemetry and your own LLM for the drafting step.
Who runs it
The analyst edits a wage base or a state table as data, with an author and a diff. Nobody opens a test script. Engineering gets the same check in CI.
Payroll platform QA
Grade every release against the employees you already keep, before customers do.
Implementation partners
Replace the parallel-run spreadsheet at go-live with a graded register you can sign.
In-house payroll teams
One check that survives the vendor’s release cycle and the January table load.
A parallel run shows that two systems agree with each other. It does not show that either is right, and when they disagree the spreadsheet cannot say why. VeriQuant computes an independent gross-to-net from your own tables and plan rules and names the first step that differs.
No. Drive the screens, read results through an adapter in a non-production tenant, or exchange a sheet of cases and a register with no API access at all.
No. It is a per-pay-period check that takes year-to-date figures as input and grades what the engine produced. It verifies the engine. It does not replace it.
No. The tables you license or maintain load as data with editions by effective date, and they never leave your network.
Running a jurisdiction or a deduction type we don’t list? We build it during your evaluation.
The next step
The first run of the year. A mid-year state change. A go-live with a thousand employees and a spreadsheet. In 45 minutes, a senior member of our team walks your payroll QA lead, compliance analyst and CIO through how the check is built for that case, and how your team runs it in your own non-production tenant.