Oracle PeopleSoft and Dayforce integration

What moves between them

Dayforce employee and payroll records flow into Oracle PeopleSoft. On each sync cycle, ml-connector reads changed employees and payroll summaries from Dayforce using date-range filters, then posts payroll GL journal entries into PeopleSoft's general ledger via SOAP CI calls, mapped to the correct GL accounts and cost centers in PeopleSoft. Employee changes such as hires, terminations, and job code changes are also written to PeopleSoft's employee tables. The main flow is Dayforce into PeopleSoft; reference data such as org units and jobs are fetched from Dayforce to ensure payroll allocations land on valid PeopleSoft dimensions. Polling happens daily or on a schedule tied to your payroll calendar.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Dayforce OAuth2 credentials and the Dayforce client namespace are used to fetch the client-specific API base URL daily and obtain a fresh Bearer token before each request. The PeopleSoft hostname, port, node name, and HTTP Basic Auth credentials or OAuth2 token are used to authenticate REST and SOAP calls. Because PeopleSoft SOAP CI calls for journal posting require idempotency via natural object keys, ml-connector tracks processed payroll runs by date and amount to avoid duplicate postings. Dayforce tokens expire after one hour, so ml-connector refreshes them before they expire rather than handling 401 responses. PeopleSoft has no outbound webhooks, so ml-connector polls both systems on a cadence tied to your payroll close calendar, fetching only records updated since the last sync with date-range filters to minimize API load. Every employee record and journal entry carries a full audit trail and can be replayed if a downstream write fails. Error handling covers both Dayforce OAuth2 token refresh failures and PeopleSoft SOAP faults.

A real-world example

A mid-sized industrial manufacturer runs Oracle PeopleSoft on-premise for procurement, inventory, and general ledger, and uses Dayforce in the cloud for payroll and HR. Before the integration, after each payroll run the finance team exported the payroll register from Dayforce, manually mapped labor costs to PeopleSoft cost centers and job codes, and entered the GL journal in PeopleSoft by hand. Employee changes such as transfers, raises, and terminations were tracked separately in Dayforce and had to be re-keyed into PeopleSoft's HR module. With Dayforce and PeopleSoft connected, payroll GL entries post automatically after each run, employee data syncs daily, and the ledger is always aligned with the truth in payroll. Month-end close no longer requires manual reconciliation between the two systems.

What you can do

• •Sync employee records from Dayforce to Oracle PeopleSoft, including hires, terminations, job code changes, and cost center assignments.
• •Post payroll GL journal entries from Dayforce directly into PeopleSoft's general ledger, mapped to the correct GL accounts and cost centers.
• •Refresh Dayforce's OAuth2 tokens automatically before expiry and handle PeopleSoft's HTTP Basic Auth or OAuth2 credentials per customer environment.
• •Poll both systems on a daily or payroll-calendar schedule with date-range filters to minimize API load on both sides.
• •Maintain a full audit trail on every employee and journal entry record, with replay capability if a PeopleSoft SOAP CI write fails.

Questions

How does ml-connector handle PeopleSoft's self-hosted architecture and unique hostnames?

Each customer provides their own PeopleSoft hostname, port, and node name, along with HTTP Basic Auth credentials or an OAuth2 token if they are on PeopleTools 8.58 or later. ml-connector stores these encrypted and authenticates against the customer's specific instance.

Why does ml-connector poll instead of using webhooks?

Oracle PeopleSoft has no outbound webhooks for cloud integrations, so polling with date-range filters is the recommended approach. Dayforce also offers polling only, making a scheduled daily sync the most reliable pattern for this pair.

What prevents duplicate payroll journals from posting multiple times?

ml-connector tracks processed payroll runs by their date and total amount, using these as natural idempotency keys in PeopleSoft SOAP CI calls. If a journal entry is requested twice, the second attempt is recognized as a duplicate and rejected at the PeopleSoft layer.