Niches · Payroll infrastructure

Put approved hours and pay items into the next payroll

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
8companies, fit with a limit
11companies carry the tag
28share of the category's work
10first-hand accounts

What counts as done

Every worker's hours and pay items written to the open draft payroll in one batch, each confirmed by reading the draft back, with unmatched or unsupported workers (hourly, contractors) listed with a reason and nothing submitted. A retried write changes nothing.

How agents ask for it: put this week's hours into payroll, load the timesheets into Gusto, add this bonus to Friday's payroll, send the approved shifts to payroll

Does the job, with a limit 8

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.

ListingWhy
Check B
Check Technologies, Inc.
POST /payroll_items takes an array with hourly earnings and hours, GET payroll with include_items reads it back, and X-Idempotency-Key replays the first response on retry. Workers carry only free-form metadata, not an external id, and keys need a sales contact and partner agreement. source
Employment Hero Payroll E
Employment Hero Pty Ltd
Bulk timesheets take EmployeeIdType external and ReplaceExisting, earnings lines go into an unfinalised pay run with ExternalId, and acc-13 relies on the external-id duplicate guard. Read only from the .NET client: the docs host refuses robots.txt, and keys have no scopes, so the same key can finalise. source
Everee D
Everee, Inc.
POST payroll-runs/{id}/items takes 1,000 items, validates all before saving and lists every failing item; resending an externalId updates rather than duplicates, and items list back by cursor. A company instance still starts with a demo call, and the terms restrict non-Everee agents. source
Gusto B
Gusto, Inc.
Embedded: prepare, then PUT payroll with employee_compensations (up to 100) and the current version, read back by GET; no external worker id. Production needs one to two months of review (acc-02, acc-08). For existing Gusto customers the MCP writes drafts but refuses hourly payrolls (acc-03) and matches by name. source
Paychex E
Paychex, Inc.
POST /companies/{id}/checks adds checks with payHours for several workers to an unprocessed pay period, and GET worker checks reads them back; checkCorrelationId only labels errors, with no documented retry guard. Access needs Paychex partner approval, which acc-12 is still waiting on. source
Salsa E
Salsa Software Inc.
POST /paystream with PeriodReplacement replaces a period's pay, hours and rates for many workers at once, so a retry changes nothing, and pay can be read back per worker payment. Pay entries take Salsa's workerId, not the caller's externalId, and tokens come only after a sales contact. source
Worklio E
Worklio, Inc.
Earnings are written per paystub inside an open run (PATCH paystubs/{id}, add payline, add paystub) and read back with Get list of Earnings; there is no batch write, no external worker id, and several payroll starts are documented as not idempotent. source
Zeal E
Puzzl Group Inc.
POST /employeeChecks creates checks in bulk with hourly shifts, approval_required true holds them, GET reads them back, and the spec documents an x-idempotency-key header. Without the flag Zeal processes checks the day before check date; workers match by Zeal id or metadata, and keys follow a demo. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Argyle B
Argyle Systems Inc.
Argyle reads a worker's consented payroll records; the API reference has no payroll, timesheet or pay-item write. source
Finch BB
Profound Platform Inc. (dba Finch)
Finch reads payroll and writes only deductions and contributions; there is no draft payroll, hours or pay-item write. source
PayFit C
PayFit SAS
The Partner API has no pay-item or hours write into a payroll; worked time is read-only (France), and the only payroll write is a validated absence. source

What stops agents finishing

  • agent route refuses hourly workers (acc-03)
  • production scopes need a partner review of one to two months (acc-02, acc-08)
  • no API at all, so the builder drives the web app and breaks on new steps (acc-05, acc-06)

Around it

Before: scheduling.approved-shifts, hr.timesheet-approval. After: payroll.preview-and-approve.

Where this comes from

Weight 28 of 100 in Payroll infrastructure: 10 of 27 accounts (acc-03 to acc-09, acc-12, acc-13, acc-22); the commonest job builders wired, mostly scheduling and field-service apps pushing hours to Gusto

The same as data: /api/v1/use-cases/payroll.hours-to-draft.json, or the MCP tool get_use_case with id payroll.hours-to-draft. Other jobs in this category: /api/v1/niches?category=payroll.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.