Everee vs Paychex

Everee

Everee's API tokens are created in the admin portal of each company instance, and payments wait for a payroll admin's approval unless auto-approval is arranged. The API has no preview or approval endpoint, no single OpenAPI file, no SDK and no changelog, and a company instance starts with a sales call.

Paychex

A public OpenAPI 3.0.3 definition covers 110 operations, and payroll entries stay unprocessed until a person submits the payroll in Flex. Partner credentials and the sandbox follow approval by Paychex, no price is published, and no status page, SLA or SDK was found in the reviewed pages.

Everee

1. Send two headers on every call, authorization: basic <token> and x-everee-tenant-id. Base64-encode a token that starts with sk_ first.
2. Derive each payable's externalId from stable data, never a timestamp or UUID, so a retried create is rejected instead of paying twice.
3. For contractors, call POST /integration/v1/payables/payment-request after all payable items are sent and before admins approve. Without it contractors aren't paid.
4. Send hourly wages through the Timesheets API, not Payables, and assign workLocationId so tax is worked out for the right jurisdiction.
5. Don't expect the API to move money alone. Tell the user a payroll admin must approve in the portal unless auto-approval is enabled, and read Everee's terms on automated access first.

Paychex

1. POST grant_type=client_credentials with the key and secret in the form body to /auth/oauth/v2/token. Tokens last 60 minutes and there is no refresh token, so request a new one
2. Call GET /companies first. Worker and payroll paths need a companyId or workerId the app has been granted
3. Send offset and limit on GET /companies/{companyId}/workers, 50 at most, and resend the ETag between pages. The unpaged form is withdrawn on 24 February 2027
4. Creating a check doesn't pay anyone. A person must review and submit the payroll in Paychex Flex
5. Send a unique X-payx-client-correlationId per request and keep the x-payx-txid from the response. Support asks for it
6. On 423 the client is locked by another user or process. Wait and retry