Oracle E-Business Suite and Dayforce integration

What moves between them

The main flow moves from Dayforce into Oracle EBS. After each payroll run, ml-connector reads Dayforce employee records and payroll GL journals, then posts the labor cost entries into EBS GL_JE_LINES with the correct GL accounts and cost centers. Employee hire, termination, and status changes in Dayforce are read to keep EBS headcount current. The GL journals originate in Dayforce and are read-only; ml-connector does not write payroll entries back into Dayforce. Syncs are scheduled to align with your payroll calendar, typically after each payroll close in Dayforce.

How ml-connector handles it

ml-connector stores EBS and Dayforce credentials encrypted and handles each system's authentication separately. For EBS, it obtains a session token via HTTP Basic Auth to the customer-hosted ISG login endpoint, caches it, and re-authenticates on 401 response. For Dayforce, it posts to the OAuth token endpoint with the ROPC grant to retrieve a Bearer JWT, then re-posts at the 55-minute mark before expiry to avoid mid-request token failure. Both systems are polled; ml-connector queries EBS open interface tables filtered by LAST_UPDATE_DATE and Dayforce employee and payroll endpoints filtered by updateDate range. Dayforce employee records are mapped to EBS HZ_PARTIES and GL cost centers before payroll journals are posted, so every labor entry lands on a valid GL account. Because EBS interface table writes are asynchronous, ml-connector tracks which records have been submitted and polls the concurrent program status to confirm import completion. Retries are handled via the interface table queue; a failed journal is resubmitted until the import completes.

A real-world example

A mid-market services company with multiple business units runs Oracle E-Business Suite for general ledger, accounts payable, and procurement, and uses Dayforce for employee payroll and benefits across three locations. Before the integration, the accounting team exported payroll registers from Dayforce each month and manually entered labor cost journals into EBS GL, allocating them by location cost center. This process was error-prone, took two days per month, and created month-end reconciliation delays. With Dayforce and EBS connected, payroll GL journals flow directly into EBS with the correct cost center and account coding after each payroll close. Employees added or terminated in Dayforce update automatically in EBS, so headcount and payroll are always aligned. The manual re-entry is eliminated and month-end close starts with labor costs already accounted for.

What you can do

• •Post Dayforce payroll GL journals into Oracle EBS GL after each payroll close, allocated to the correct GL accounts and cost centers.
• •Keep EBS employee headcount in sync with Dayforce hires, terminations, and status changes.
• •Map Dayforce organization units and cost centers to EBS GL code combinations so payroll lands on valid accounts.
• •Authenticate EBS via HTTP Basic Auth to the customer ISG and Dayforce via OAuth 2.0 ROPC, refreshing tokens before expiry.
• •Poll both systems on a payroll schedule, queue interface table submissions, and track concurrent program imports until completion.

Questions

How does the integration handle EBS and Dayforce being very different systems with separate authentication?

ml-connector maintains separate credential sets for each system and authenticates independently. It obtains a session token from EBS via Basic Auth to the customer-hosted ISG, and posts to the Dayforce OAuth token endpoint for a Bearer JWT. Both tokens are cached and refreshed on expiry or 401 response, so the integration keeps both sides authenticated throughout each sync cycle.

Why must the integration track EBS concurrent program imports if it just posts to an interface table?

EBS writes to open interface tables are asynchronous. The connector posts a labor journal to an interface table, but a concurrent program must import it into GL_JE_LINES, which takes minutes to hours. ml-connector monitors the concurrent program status to confirm the import completed successfully, and retries failed submissions via the interface table queue until the import succeeds.

What happens to GL journals if Dayforce GL account codes change or a cost center is discontinued in EBS?

ml-connector validates Dayforce cost centers and job codes against EBS GL code combinations before posting. If a code combination does not exist in EBS, the journal is queued with an error and flagged for manual review. The integration never posts an orphaned journal; instead it surfaces the mismatch so your finance team can align the accounts before the next payroll run.