Oracle PeopleSoft and Deel integration

What moves between them

The flow runs primarily from Oracle PeopleSoft into Deel for employee records and from Deel back into PeopleSoft for contractor invoices and payment records. Employee hires, terminations, and rehires move from the PeopleSoft employee directory to Deel's HRIS API, where they update or create contracts. Payroll adjustments, deductions, and bonuses defined in PeopleSoft can be pushed to Deel as payroll inputs. Contractor invoices and payment data flow from Deel into PeopleSoft as AP vouchers or journal entries for accounting reconciliation. Real-time Deel webhook events (contract.created, hris.employee.terminated) trigger immediate updates when enabled; PeopleSoft data is polled on a schedule since it has no outbound webhooks.

How ml-connector handles it

ml-connector stores both credential sets encrypted. For PeopleSoft, it accepts the customer's unique hostname, port, and node name since each installation is self-hosted with no shared base URL, authenticates with HTTP Basic Auth or OAuth2 bearer token depending on PeopleTools version, and polls REST endpoints using date-range filters to retrieve employee, vendor, and payroll records at a configurable cadence. For Deel, it uses API tokens with fine-grained resource scopes or OAuth2 with automatic refresh token rotation; verifies webhook signatures using HMAC-SHA256 before processing events; and respects the Idempotency-Key requirement on write operations (POST and PATCH) to ensure duplicate payroll adjustments do not repeat if a retry occurs. When Deel rate-limits with HTTP 429, ml-connector backs off with exponential jitter and retries. Contractor invoices from Deel must be mapped to PeopleSoft vendor and cost center dimensions to post into the correct GL accounts. Every record carries a full audit trail, allowing failed downstream operations to be replayed once the issue is resolved.

A real-world example

A mid-sized software company operates Oracle PeopleSoft on-premise for HR and finance, and uses Deel to manage a distributed workforce across five countries including contractors in jurisdictions where EOR is required. Before the integration, payroll administrators managed employee lifecycle in PeopleSoft and separately entered each hire and termination into Deel's portal, creating dual-entry delays and mismatched records. At month-end, the contractor invoices from Deel were printed and manually coded to cost centers before entering PeopleSoft as AP vouchers. With PeopleSoft and Deel connected, new employees hired in PeopleSoft sync to Deel automatically within minutes, contractor invoices appear in PeopleSoft with the correct GL dimensions pre-mapped, and the dual-entry overhead is eliminated. Payroll runs in Deel reflect the same cost allocations as PeopleSoft, and reconciliation happens at the press of a button.

What you can do

• •Sync employee hires, terminations, and rehires from Oracle PeopleSoft into Deel's HRIS so workforce records stay current across geographies.
• •Push payroll adjustments, bonuses, and deductions from PeopleSoft into Deel to keep payroll inputs in sync without manual re-entry.
• •Pull contractor invoices and payment records from Deel into PeopleSoft as AP vouchers or GL journal entries, pre-mapped to the correct cost centers.
• •Handle PeopleSoft's self-hosted authentication (HTTP Basic Auth or OAuth2) and Deel's API token scopes, webhook signature verification, and OAuth2 refresh token rotation.
• •Poll PeopleSoft on a schedule since it has no outbound webhooks, and receive real-time Deel contract and employee events to keep the sync current without delay.

Questions

How does the integration work with PeopleSoft's self-hosted architecture and different PeopleTools versions?

Each Oracle PeopleSoft installation is unique with its own hostname, port, and node name; ml-connector accepts these per customer and authenticates with HTTP Basic Auth for all PeopleTools versions or OAuth2 for PeopleTools 8.58 and later. Because PeopleSoft has no standardized outbound webhooks, the integration polls REST service operations on a configurable schedule using date-range filters to retrieve employee, vendor, and payroll data.

Does the integration handle Deel's real-time webhook events and API token scopes?

Yes. ml-connector verifies Deel webhook signatures using HMAC-SHA256 before processing contract and employee lifecycle events, so it receives real-time notifications when enabled. It respects Deel's fine-grained API token scopes set at creation time and rotates OAuth2 refresh tokens automatically when access tokens expire after 30 days.

How are contractor invoices and GL accounts handled when they move from Deel to PeopleSoft?

Contractor invoices and payment records are pulled from Deel and mapped to PeopleSoft vendor master and cost center dimensions before posting into GL journal entries or AP vouchers. Because Deel embeds GL account data in payment payloads rather than exposing standalone master data, the mapping is based on Deel's cost code and invoice metadata matched to the customer's PeopleSoft chart of accounts.