# Onboard a new employee or contractor so they can be paid

> Onboard a new employee or contractor so they can be paid: 5 companies fully do it, 4 with a limit, 18 carry the tag. Every listing in Payroll infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/payroll.onboard-worker/
- Markdown: https://www.anchorterminal.com/niches/payroll.onboard-worker/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/payroll.onboard-worker/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/payroll.onboard-worker/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 5 | 4 | 18 | 10 | 3 |

## What counts as done

The worker created with the right type and work location, the self-service onboarding (tax forms, bank details) sent through the vendor's screens, and an onboarding status the agent can read that says what is still missing.

How agents ask for it: add our new hire to payroll; onboard this contractor; set up this driver to get paid; send the new starter their payroll forms

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Check (Check Technologies, Inc.)**: Employees and contractors are created by API, Check Onboard sends the self-service tax and bank screens, and each record's onboard object returns status with blocking_steps and remaining_steps.
- **Everee (Everee, Inc.)**: Kick off onboarding for an employee or contractor with minimal data, send the embedded onboarding screens, read hiring status, and the Requirements API lists what still blocks pay. acc-26 gates drivers on that state.
- **Gusto (Gusto, Inc.)**: POST employees with self_onboarding true sends the invite, contractors have their own onboarding, and GET employees/{id}/onboarding_status returns states such as self_onboarding_invited_overdue and the remaining steps.
- **Salsa (Salsa Software Inc.)**: POST workers takes externalId, type and classification (a repeat externalId returns a uniqueness error), and HostedWorkerOnboarding returns an inviteUrl for the worker's own tax and bank setup with status and completedAt.
- **Zeal (Puzzl Group Inc.)**: Employees and contractors are created by API with a work location, Generate Employee Onboarding Link sends the self-service screens, and Get Employee Requirements plus the onboarding and requirement webhooks say what is still missing.

## Does the job, with a limit

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.

- **Employment Hero Payroll (Employment Hero Pty Ltd)**: POST employeeonboarding/initiateselfservice creates the employee if no id is given and starts self setup. No onboarding status read naming what is missing was found in the client.
- **Paychex (Paychex, Inc.)**: POST /companies/{id}/workers creates EMPLOYEE or INDEPENDENT_CONTRACTOR workers in IN_PROGRESS status, which must be fully configured in Flex, and worker statuses are readable; no self-service onboarding send or missing-items list was found.
- **PayFit (PayFit SAS)**: POST collaborators (all countries) and POST contracts (France only) create the record, which stays incomplete until an HR admin finishes it in the app; no onboarding status read was found.
- **Worklio (Worklio, Inc.)**: POST onboarding/start from a template returns its steps, the employer fills basic and employment data, then the employee completes their own steps. Templates can only be made in BackOffice, and no single missing-items status was found beyond the step list.

- not this job: Argyle (Argyle Systems Inc.): Creating an Argyle user only opens a Link session; nothing creates an employee or contractor in a payroll system.
- not this job: Finch (Profound Platform Inc. (dba Finch)): Organisation endpoints are read-only; no worker create or onboarding route is documented.

## What stops agents finishing

- record created through the API stays incomplete until an HR admin finishes it in the app
- worker type or country not covered

## Around it

Before: recruiting.offer-accepted, hr.create-employee. After: payroll.hours-to-draft.

## Where this comes from

Weight 10 of 100 in Payroll infrastructure: 3 of 27 accounts (acc-07, acc-15, acc-26); weight set by hand since onboarding is a precondition of every pay job

As data: https://www.anchorterminal.com/api/v1/use-cases/payroll.onboard-worker.json, or the MCP tool get_use_case with id payroll.onboard-worker. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
