Oracle E-Business Suite and Paylocity integration

What moves between them

The main flow runs from Paylocity into Oracle E-Business Suite. After each payroll run, ml-connector reads Paylocity's payroll GL data and posted earnings and deductions, then posts the labor cost journals into EBS's general ledger, mapped to matching EBS GL accounts and cost centers. Employee records flow the same direction so EBS headcount reflects Paylocity hires, terminations, and rehires. Reference data such as pay grades, work locations, and deductions are aligned in both directions so payroll allocations land on valid EBS dimensions. GL postings are read-only in Paylocity, so ml-connector never writes financial entries back to payroll.

How ml-connector handles it

ml-connector stores both credential sets encrypted and presents HTTP Basic Auth credentials on every ISG call to the customer's unique EBS hostname and port, refreshing the EBS session token when a call returns 401. On the Paylocity side it handles OAuth 2.0 client credentials flow, requesting a new Bearer token before expiry and handling token refresh on 401 responses. Because EBS has no webhooks, ml-connector polls Paylocity for new payroll GL documents and employee changes on a schedule tied to your payroll calendar rather than waiting for a push, parsing Paylocity payroll GL rows to extract earnings, deductions, and gross pay, then mapping those amounts to the EBS GL accounts and cost centers you configure. If Paylocity webhooks are enabled, ml-connector can also receive payroll processed events to trigger the GL postings immediately. Cost centers are mapped first, so every payroll journal line references an EBS GL account and cost center that already exists. Paylocity rate limits return HTTP 429, so ml-connector backs off and retries, and it tracks OAuth token expiry to prevent a gap in syncs. Every record carries a full audit trail and can be replayed if a downstream EBS concurrent program fails or takes longer than expected to complete.

A real-world example

A mid-sized professional services firm runs Oracle E-Business Suite for financials, projects, and procurement, and uses Paylocity for payroll across two offices and a remote workforce. Before the integration, the finance team exported payroll registers from Paylocity each pay period and manually re-entered labor totals into EBS by hand, then spent the first days of month-end close reconciling differences between Paylocity headcount and the labor accounts in the ledger. With EBS and Paylocity connected, each payroll run's GL document flows into EBS automatically, allocated to the cost center for each office and project, and employee changes keep the two systems aligned. Month-end close starts with the labor accounts already reconciled, and the manual data entry step is gone.

What you can do

• •Post Paylocity payroll GL documents into Oracle EBS's general ledger after every pay run, allocated to the correct cost centers and GL accounts.
• •Keep Oracle EBS headcount aligned with Paylocity hires, terminations, and rehires.
• •Map Paylocity pay grades, work locations, and deductions to Oracle EBS GL dimensions so payroll lands on valid accounts.
• •Authenticate Oracle EBS via HTTP Basic Auth to the customer's Integrated SOA Gateway, and Paylocity via OAuth 2.0 client credentials.
• •Poll on a schedule tied to your payroll calendar, with retries, token refresh, and a full audit trail on every record.

Questions

Which direction does data move between Oracle EBS and Paylocity?

The main flow is Paylocity into Oracle EBS. Payroll GL documents and employee records move from Paylocity into EBS, while pay grades, work locations, and deductions are aligned in both directions. GL postings are read-only in Paylocity, so ml-connector does not write financial entries back into payroll.

How does the integration handle Oracle EBS's unique ISG hostname and lack of webhooks?

ml-connector accepts the full ISG URL per customer, since EBS publishes no shared base address and each installation is on a unique hostname and port. Because EBS has no modern webhooks, ml-connector polls Paylocity for new payroll GL documents and employee changes on a schedule tied to your payroll calendar rather than waiting for a push.

What authentication setup is required on both systems?

Oracle EBS requires HTTP Basic Auth credentials (username and password) and application context headers such as responsibility and organization ID, obtained once per session via the ISG login endpoint. Paylocity requires OAuth 2.0 client credentials (client ID and secret) and a Bearer token obtained from the Paylocity token endpoint and refreshed every 3600 seconds.