Oracle Fusion Cloud ERP and ADP integration

What moves between them

The main flow is ADP into Oracle Fusion. After each payroll run, ml-connector reads ADP's general ledger documents and posts them into Oracle Fusion's journal batch API, mapped to the matching GL accounts and cost centers. Worker records flow from ADP into Oracle Fusion so workforce data stays aligned across both systems. Reference data such as cost centers, departments, and validation tables is aligned in both directions so payroll allocations land on valid GL account combinations. Because ADP GL documents are read-only output from payroll, ml-connector never writes financial entries back into ADP.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the ADP client certificate and private key are stored securely and presented at the TLS layer on every ADP request to satisfy the mutual TLS requirement, while Oracle OAuth2 tokens are cached in memory and refreshed automatically when a call returns 401. Since Oracle Fusion exposes no shared hostname, ml-connector accepts the full customer pod URL per instance and validates API paths against that URL. Because both systems are pull-only, ml-connector polls both on a schedule tied to your payroll calendar, filtering Oracle Fusion by LastUpdateDate to retrieve only new records. ADP returns HTTP 429 when rate limits are exceeded, so ml-connector backs off with exponential retry logic. Client certificate expiry is tracked so renewal can happen before outages occur. Cost centers are mapped first, so every payroll journal line references a GL account combination that already exists in Oracle Fusion. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company runs Oracle Fusion Cloud ERP for order-to-cash, procure-to-pay, and general ledger operations, and uses ADP for payroll across multiple plants and a corporate head office. Before integration, the finance team extracted payroll registers from ADP each pay period, manually created journal entries in Oracle Fusion to post labor costs to GL accounts and cost centers, and spent days at month-end reconciling payroll totals to headcount records. With Oracle Fusion and ADP connected, each ADP payroll run's GL document flows directly into Oracle Fusion's journal batches, automatically allocated to the correct plant cost centers, and worker changes are reflected in Oracle Fusion immediately. Month-end close begins with payroll accounts already reconciled and the manual journal entry step eliminated.

What you can do

• •Post ADP general ledger documents into Oracle Fusion journal batches after each payroll run, allocated to the correct cost centers.
• •Keep Oracle Fusion worker records synchronized with ADP hires, terminations, and rehires.
• •Validate and map ADP cost centers and departments to Oracle Fusion GL account combinations before posting.
• •Authenticate ADP with mutual TLS client certificates and OAuth2 credentials, and Oracle Fusion with OAuth2 tokens refreshed hourly.
• •Poll both systems on a payroll calendar schedule, with exponential retry on rate limits and a full audit trail on every record.

Questions

Does ADP's mutual TLS client certificate requirement add complexity?

Yes, but ml-connector handles it transparently. The client certificate and private key are stored encrypted, presented at the TLS layer on every request, and the certificate expiry is tracked so renewal happens before an outage. Without the certificate, the TLS handshake fails and all calls are rejected.

Which direction does data move between Oracle Fusion and ADP?

The main flow is ADP into Oracle Fusion. Payroll GL documents and worker records move from ADP into Oracle Fusion, while cost centers and departments are aligned in both directions. ADP GL documents are read-only output from payroll processing, so ml-connector does not write financial entries back to ADP.

How does the integration handle polling when both systems lack push webhooks?

ml-connector polls both systems on a schedule tied to your payroll calendar rather than waiting for a push. Oracle Fusion records are filtered by LastUpdateDate to retrieve only new changes, and cost centers are mapped first so payroll journal lines land on valid GL accounts.