Niches · Payroll infrastructure
Preview a payroll and route it to a person to approve
One company's docs show a full fit.
What counts as done
A preview with gross pay, employee taxes, deductions, net pay and the employer debit per worker and in total, and a pending run that only a named person can approve or that the agent approves with a token bound to that preview, so a stale preview is refused. The agent never submits on its own credential unless the employer turned that on.
How agents ask for it: what will this payroll cost
, show me the payroll before it goes
, get payroll ready for me to approve
, run payroll
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Check B Check Technologies, Inc. | Preview calculates taxes, benefits and net per item with payroll totals (employee taxes, liability, cash requirement); approve takes preview_started_at and refuses a superseded preview with 409. The directory MCP omits approve, so an agent can stop at pending for a person. source |
Does the job, with a limit 6
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Employment Hero Payroll E Employment Hero Pty Ltd | Pay run totals per employee give gross, tax withheld, deductions, net and employer liabilities, warnings are readable, and approval/start notifies the pay schedule's approvers. The approval is not tied to a preview, and finalise on the same key can lodge and publish payslips. source |
| Everee D Everee, Inc. | Calculate, then list run payments for wages, taxes, deductions, employer costs and net; any change returns the run to OPEN so a stale calculation cannot be approved. In Payroll Infrastructure the partner's own token approves; no person-bound or preview-bound token. Hosted payroll approves in the portal. source |
| Gusto B Gusto, Inc. | Calculate, then GET with include=taxes,benefits,deductions shows the preview; submit takes the payroll version, so a changed payroll returns 409. Submit runs on the partner's token with no person-bound approval, and Gusto only recommends the partner build a review screen. acc-05 hit the late-payroll wire step. source |
| Salsa E Salsa Software Inc. | POST payroll-runs/preview returns per-worker results with totalPayrollCost and totalToBeDebited; creating the run leaves it PENDING and a separate confirm starts the employer debit. Confirm is not tied to the preview, and any partner or user token with the role can call it. source |
| Worklio E Worklio, Inc. | Payroll Overview returns properties and reports for a calculated, unfinalised run, and a payment authorisation stage asks a user to authorise the transactions before finalize. The step sequence answers 500 when ready to finalise, and no preview-bound approval token was found. source |
| Zeal E Puzzl Group Inc. | Preview by check ids or check date runs as a job returning gross, employee and employer taxes, deductions and net per check with totals; approval is PATCH employeeCheck approved true or the dashboard. The approve call is not tied to the preview, and one unscoped key can approve. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Argyle B Argyle Systems Inc. | No payroll run, preview or approval object in the API reference. Argyle does not run payroll. source |
| Finch BB Profound Platform Inc. (dba Finch) | No payroll creation, preview or approval in the products list; Finch reads pay runs after the fact. source |
| Paychex E Paychex, Inc. | Checks carry no tax or net calculation before processing, and a person reviews and submits the payroll in Paychex Flex; there is no preview or approve operation in the OpenAPI file. source |
| PayFit C PayFit SAS | Only GET payroll-status for a period; no operation runs, previews or approves a payroll. source |
What stops agents finishing
- no preview or approval endpoint; approval only in the vendor portal
- late-payroll or funding step that needs a person (acc-05)
- terms forbid access through an agent
Around it
Before: payroll.hours-to-draft. After: payroll.payment-status, messaging.send-approval.
Where this comes from
Weight 20 of 100 in Payroll infrastructure: 5 of 27 accounts (acc-03, acc-04, acc-05, acc-12, acc-27); every builder kept the final submit with a person, so the weight rests on that pattern more than on counts
The same as data: /api/v1/use-cases/payroll.preview-and-approve.json, or the MCP tool get_use_case with id payroll.preview-and-approve. Other jobs in this category: /api/v1/niches?category=payroll.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.