Paychex

Connect Paychex to collect hris evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Paychex:

   1. Sign in to Paychex Flex as a user with permission to manage connected applications (for example a Super Admin or Security Admin role).
   2. If you manage several Paychex client accounts, sign in to the one you want to manage the integration from (the 'Parent' account); other 'Child' accounts can be linked to the app afterwards.
   3. In Paychex Flex, go to Company Settings › Connected Applications and choose Create App.
   4. Name the app (for example "Safeguard"), give it a brief description, and choose the access levels to the data you want to share.
   5. Save the app. Paychex Flex generates the app's API key (the Client ID) and secret automatically; copy both.

   Where to find the other values:

   • Client ID: The API key Paychex Flex generates for the app under Company Settings › Connected Applications.
   • Company ID: Not shown on a documented Paychex Flex screen, and not described on the Paychex pages checked.
   • Access token (optional): Not shown in the UI. It is the bearer token Paychex generates when the authorization call is made with the app's key and secret in the request body; it expires after 60 minutes by default and cannot be refreshed (call the authentication endpoint again).

   Paychex's public documentation does not cover every step.

   Source: developer.paychex.com, developer.paychex.com, developer.paychex.com, developer.paychex.com, checked 2026-10-07.

   The permissions Safeguard needs: workers: read, communications: read.

2. On Compliance › Connectors, open Paychex, click Connect, choose API token and fill in:

   Field	What to enter
   Company ID	Optional.
   Client ID	Optional.
   Client secret	Optional. Stored encrypted and never shown again.

   Or, instead: Access token (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Paychex and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• HRIS connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks