Oracle PeopleSoft and Gusto integration

What moves between them

The main flow is from Oracle PeopleSoft into Gusto. ml-connector polls PeopleSoft's employee directory on a schedule (typically daily) to read new hires, job changes, and terminations, then writes or updates corresponding employee and compensation records in Gusto. Job codes are mapped from PeopleSoft to Gusto job objects. Reference data such as earning types and locations are synced in the same direction. Gusto payroll events (processed, paid) can optionally trigger a reverse read of Gusto payroll records into PeopleSoft if PeopleSoft is configured to accept Integration Broker asynchronous messages.

How ml-connector handles it

ml-connector accepts the Oracle PeopleSoft hostname, port, node name, and credentials (HTTP Basic Auth OPRID/password or OAuth2 token), and polls the employee directory, job, and compensation endpoints on a schedule tied to your hiring and payroll cycles. It reads the most recent changes via date-range filters to avoid scanning the entire dataset. On the Gusto side, ml-connector uses the OAuth2 token (refreshing before expiry at the 2-hour mark) and includes the current object version field in PUT requests to avoid 409 Conflict errors when Gusto records have been updated out-of-band. ml-connector maps PeopleSoft job codes to Gusto job UUIDs via a lookup table, and translates PeopleSoft earning types and locations to Gusto equivalents. When a write to Gusto returns 429 (rate limit), ml-connector backs off and retries, and when a Gusto record version mismatch occurs, it re-reads the current version and retries the update. All records carry audit trails linking the source PeopleSoft ID to the target Gusto UUID.

A real-world example

A mid-sized professional services firm runs Oracle PeopleSoft on-premise for HR records and job costing, and uses Gusto for cloud payroll processing across four offices. Before the integration, the HR team exported employee lists from PeopleSoft monthly, matched them to Gusto records by name and email, and manually added new hires and terminations into Gusto. Job changes in PeopleSoft were not reflected in Gusto, so payroll allocations were often incorrect. With Oracle PeopleSoft and Gusto connected, each new hire enters PeopleSoft first, is automatically synced to Gusto with the correct job and location code, and appears ready for payroll processing by the next pay cycle. Terminations flow the same way, ensuring Gusto does not process unexpected final checks.

What you can do

• •Sync Oracle PeopleSoft employees, job assignments, and compensation history into Gusto on a schedule tied to your hire and payroll calendar.
• •Map PeopleSoft job codes and cost centers to Gusto job objects and locations so compensation allocates correctly.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer tokens, and Gusto with OAuth2, refreshing credentials before expiry.
• •Handle Gusto's 2-hour access token lifecycle and object versioning model, retrying writes that encounter version conflicts or rate limits.
• •Track all record mappings in an encrypted audit log, with the ability to replay failed syncs and trace each Gusto record back to its PeopleSoft source.

Questions

Which direction does data move between Oracle PeopleSoft and Gusto?

The primary direction is Oracle PeopleSoft into Gusto. Employee records, job assignments, and compensation are read from PeopleSoft and written to Gusto. Reference data such as job codes, locations, and earning types are aligned in the same direction. Gusto payroll events (processed, paid) can optionally trigger a reverse read back into PeopleSoft via Integration Broker messages if your PeopleSoft is configured to accept them.

How does ml-connector handle Oracle PeopleSoft's self-hosted architecture and lack of webhooks?

Each Oracle PeopleSoft customer provides their own hostname, port, node name, and credentials, since there is no shared Oracle-managed base URL. ml-connector polls the employee directory and compensation endpoints on a schedule tied to your hiring cycle, using date-range filters to fetch only changed records since the last run. This avoids scanning the entire dataset and keeps the load on your PeopleSoft instance low.

What happens if Gusto's access token expires or a record version conflict occurs?

ml-connector refreshes the Gusto OAuth2 access token before the 2-hour expiry window and caches it for subsequent requests. If a PUT to Gusto returns a 409 Conflict (version mismatch), ml-connector re-reads the current record version, updates the version field, and retries the write. Rate-limit errors (429) are handled with exponential backoff and automatic retry.