Skip to main content
Toku keeps its roster in sync with Paychex Flex so stablecoin elections always map to the right person. Paychex models both W-2 employees and 1099 contractors as workers, and Toku syncs both. Sync is read-only and runs automatically after every connection and on a rolling schedule.

Endpoint

Toku reads workers through Paychex’s company-scoped workers resource:
A trimmed, representative example response:
See Paychex’s reference for the full schema: Worker resource.

What Toku Reads

Paychex exposes worker sub-resources for compensation, communications, and direct deposit; Toku reads only what it needs to validate elections and display the roster.

Sync Behavior

  • New workers appear in Toku automatically once they exist in Paychex Flex.
  • Updates (name, status, worker type) flow through on the next sync.
  • Inactive workers are marked inactive in Toku and stop receiving stablecoin payments.
  • A manual sync can be triggered anytime from Settings → Payroll Integrations in Toku.
Worker sync never writes to Paychex. Toku does not modify worker records, compensation, communications, or direct deposit details.

Next

Payroll Sync

How Toku tracks pay periods and checks

The Toku Deduction

How the deduction is applied via pay components