SAP S/4HANA and Paychex integration

What moves between them

Worker and organizational data flow from Paychex into SAP S/4HANA. When a worker is added or updated in Paychex (via webhook notification), ml-connector fetches the full worker record via GET and creates or updates the corresponding business partner in SAP S/4HANA, assigning the matching cost center and organization. Cost centers and company hierarchies are synced from SAP S/4HANA into Paychex to ensure pay allocations land on valid dimensions. The integration polls SAP S/4HANA on a regular cadence for cost center and business partner changes, and receives real-time worker events from Paychex webhooks. No payroll GL postings or financial data flow back to SAP S/4HANA; Paychex webhooks are notification-only and do not include changed field values.

How ml-connector handles it

ml-connector caches OAuth2 access tokens for both systems and refreshes proactively before expiry. For SAP S/4HANA, it constructs the OData filter= query with LastChangeDateTime ge timestamp to poll only changed records, respects the tenant-specific API base URL, and handles both Cloud and On-Premise modes (with sap-client query parameter for On-Premise). For Paychex, it registers webhooks for WRKR_DEM, WRKR_EMPL, WRKR_ADD, and CLT_ACCESS events at a registered endpoint you control. When Paychex notifies a worker change, ml-connector calls the Paychex GET endpoint to fetch the full worker record (since webhook payloads do not include data), maps the worker to the SAP S/4HANA business partner entity with the correct cost center and company code, and posts the change via OData. Cost centers and GL accounts are fetched from SAP S/4HANA and mapped to Paychex job codes and organizations so payroll allocations reference valid dimensions. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company with multiple plants runs SAP S/4HANA for finance and procurement and Paychex Flex for payroll across a distributed workforce. Before the integration, the HR team added new hires to Paychex, but SAP S/4HANA business partner records and cost center assignments were created separately by the finance team, leading to mismatched employee records and payroll cost allocations that did not match the finance system. With SAP S/4HANA and Paychex connected, each new hire added to Paychex automatically flows into SAP S/4HANA as a business partner with the correct cost center and company code. Cost center changes in SAP S/4HANA sync to Paychex, so payroll allocations stay in sync with the finance organization structure, and reconciliation happens automatically.

What you can do

• •Sync worker records from Paychex into SAP S/4HANA as business partners with the correct cost center and company code assignments.
• •Map Paychex companies, jobs, and organizations to SAP S/4HANA cost centers and GL accounts so payroll allocations reference valid dimensions.
• •Authenticate SAP S/4HANA via OAuth2 Client Credentials with tenant-specific API URLs and Paychex via OAuth2 Client Credentials with proactive token refresh.
• •Receive real-time worker change notifications from Paychex webhooks and poll SAP S/4HANA on a schedule you control for cost center and business partner updates.
• •Track every worker and cost center sync with full audit trails and replay failed records without manual re-keying.

Questions

Which direction does data move between SAP S/4HANA and Paychex?

Worker and organizational data flows primarily from Paychex into SAP S/4HANA. When a worker is added or updated in Paychex, ml-connector fetches the full record and creates or updates the matching business partner in SAP S/4HANA with the correct cost center assignment. Cost centers and company hierarchies are synced from SAP S/4HANA into Paychex to ensure payroll allocations land on valid dimensions.

How does the integration handle Paychex webhook payloads that do not include changed data?

Paychex webhook notifications are event-only and do not carry the changed field values. When ml-connector receives a webhook event (WRKR_EMPL, WRKR_DEM, WRKR_ADD, or CLT_ACCESS), it immediately calls the Paychex GET endpoint to fetch the full current worker or company record, then posts the complete data into SAP S/4HANA. This ensures the worker record in SAP S/4HANA always matches the live state in Paychex.

How does the integration refresh OAuth2 tokens and respect SAP S/4HANA's tenant-specific API URLs?

ml-connector caches both SAP S/4HANA and Paychex OAuth2 access tokens and refreshes them proactively before expiry. For SAP S/4HANA, it uses the tenant-specific API base URL from your Communication Arrangement (never constructs it manually), and for On-Premise deployments it adds the sap-client query parameter. For Paychex, it manages the OAuth2 Client Credentials flow and proactively refreshes the token since Paychex does not issue a refresh token.