SYSPRO and Paylocity integration

What moves between them

Employee and payroll data flows from Paylocity into SYSPRO. New hires and terminations from Paylocity employee events are synced into SYSPRO employee records via e.net Business Objects write calls. Payroll earnings and deductions are read from Paylocity after each payroll run and posted into SYSPRO GL accounts allocated to departments and cost centers. Reference data such as pay grades, work locations, and company dimensions are aligned in both directions to ensure payroll data lands on valid SYSPRO GL accounts and cost center combinations. The sync runs on a schedule tied to your payroll calendar with supplemental webhook ingestion when available.

How ml-connector handles it

ml-connector stores SYSPRO server credentials and the initial session token obtained from Utilities/Logon, refreshing the token if SYSPRO returns a session timeout. Paylocity OAuth2 bearer tokens are refreshed on every 3600-second expiry. On the Paylocity side, ml-connector registers a webhook endpoint to receive employee and payroll events, and supplements webhooks with polling to ensure no pay statement is missed. When employee events arrive from Paylocity, ml-connector fetches full employee details via API calls before writing to SYSPRO via e.net Business Objects REST. GL account and cost center mappings are validated first, so every payroll entry references accounts that exist in SYSPRO. Paylocity rate limits are respected with exponential backoff retries, and the full audit trail is maintained for each record synced. Because Paylocity does not expose GL accounts or vendors, ml-connector cannot post payroll back into Paylocity; data moves one direction only.

A real-world example

A mid-sized discrete manufacturer runs SYSPRO ERP for manufacturing, procurement, and accounting, and uses Paylocity for payroll and HR across two plants and a regional office. Before the integration, the payroll team processed monthly payroll in Paylocity, then the accounting team manually entered payroll totals and department allocations into SYSPRO GL accounts, a time-consuming process prone to data-entry errors. With SYSPRO and Paylocity connected, each payroll run is automatically posted into SYSPRO GL accounts allocated to the correct departments. Employee changes such as new hires and transfers trigger automatic updates to SYSPRO employee records. Month-end close no longer requires manual payroll posting, and headcount records in SYSPRO match Paylocity records accurately.

What you can do

• •Sync Paylocity employee records into SYSPRO when new hires are processed or employees are terminated.
• •Post Paylocity payroll earnings into SYSPRO GL accounts allocated to departments and cost centers after each pay run.
• •Align pay grades, work locations, and company reference data between Paylocity and SYSPRO so payroll entries land on valid accounts.
• •Receive Paylocity webhook events for employee changes and payroll completion, with polling backup to ensure no records are missed.
• •Manage SYSPRO session tokens and Paylocity OAuth2 authentication with automatic refresh on expiry.

Questions

Which direction does data move between SYSPRO and Paylocity?

Data flows from Paylocity into SYSPRO. Employee records, payroll earnings, and deductions from Paylocity are synced into SYSPRO GL accounts and employee records. SYSPRO GL and employee data is read-only on the SYSPRO side; ml-connector does not write payroll back into Paylocity since Paylocity does not expose GL accounts or vendor data.

How does the integration handle session token expiry in SYSPRO and OAuth2 token refresh in Paylocity?

ml-connector logs in to SYSPRO Utilities/Logon with the operator credentials provided per customer to obtain an initial session token, then refreshes the token if SYSPRO returns a session timeout error. On the Paylocity side, ml-connector tracks the 3600-second OAuth2 token lifetime and proactively refreshes the bearer token before expiry to avoid missed payroll events.

Does Paylocity webhook delivery require special configuration, or can polling alone sync the data?

Paylocity webhooks are optional but recommended for immediate notification of employee and payroll events. If webhooks are not configured, ml-connector polls Paylocity APIs on a schedule tied to your payroll calendar to fetch pay statements and employee changes. Polling ensures no payroll data is missed even if webhook delivery fails.