Oracle JD Edwards and ADP integration

What moves between them

The main flow runs from ADP into Oracle JD Edwards. After each payroll run, ml-connector reads ADP general ledger documents and posts the labor cost journals into the JD Edwards Account Ledger through an orchestration, mapped to the matching JD Edwards object accounts and business units. Worker records flow the same direction so JD Edwards Address Book headcount reflects ADP hires, terminations, and rehires. Reference data such as cost centers and departments is aligned so payroll allocations land on valid JD Edwards dimensions. ADP general ledger documents are read-only, so ml-connector never writes financial entries back into payroll.

How ml-connector handles it

ml-connector stores both credential sets encrypted and presents the ADP client certificate at the TLS layer on every request, refreshing the ADP bearer token when a call returns 401. On the JD Edwards side it accepts the full AIS Server URL per customer, since JD Edwards is on-premises with no shared base address, and re-authenticates automatically on HTTP 444 when a session token is invalidated by a server restart. Because JD Edwards has no native webhooks, it polls ADP general ledger documents and worker data on a schedule tied to your payroll calendar, and can also receive ADP event notifications where they are enabled. Journal lines are written through a configured orchestration rather than a direct table post, since the JD Edwards data service is read-only, and cost centers are mapped first so every line references an object account and business unit that already exist. ADP rate limits return HTTP 429 per gateway node, so ml-connector backs off and retries, and it tracks the ADP certificate expiry and the JD Edwards integration user license so neither turns into an outage. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized industrial distributor runs Oracle JD Edwards EnterpriseOne for finance and procurement across three branch plants and uses ADP Workforce Now for payroll. Before the integration, the finance team exported payroll registers from ADP every pay period and re-entered the labor totals into JD Edwards by hand, then spent the first days of month-end close chasing differences between HR headcount and the labor accounts in the ledger. With Oracle JD Edwards and ADP connected, each payroll run's general ledger document posts into the JD Edwards Account Ledger automatically, allocated to the business unit for each plant, and worker changes keep the two systems aligned. Month-end close starts with the labor accounts already reconciled, and the manual re-keying step is gone.

What you can do

• •Post ADP payroll general ledger documents into the JD Edwards Account Ledger after every pay run, allocated to the correct business units.
• •Keep JD Edwards Address Book headcount aligned with ADP hires, terminations, and rehires.
• •Map ADP cost centers and departments to JD Edwards object accounts and business units so payroll lands on valid accounts.
• •Authenticate ADP with OAuth2 and the required mutual TLS certificate, and JD Edwards with its session token against a customer-hosted AIS Server URL.
• •Poll on a schedule tied to your payroll calendar, with retries and a full audit trail on every record.

Questions

Which direction does data move between Oracle JD Edwards and ADP?

The main flow is ADP into JD Edwards. Payroll general ledger documents and worker records move from ADP into JD Edwards, while cost centers and departments are aligned so payroll posts to valid accounts. ADP general ledger documents are read-only, so ml-connector does not write financial entries back into payroll.

Does ADP's mutual TLS certificate requirement need special setup?

Yes. ADP requires a client certificate at the TLS layer on every call in addition to OAuth2 credentials, and the connection fails without it. ml-connector stores the certificate encrypted, presents it on each request, and tracks its expiry so a renewal is handled before it can cause an outage.

How does the integration write payroll journals into JD Edwards if its tables are read-only?

The JD Edwards data service only reads tables, so financial writes cannot be posted directly to them. ml-connector posts each payroll journal through a named orchestration or the batch entry form configured in the customer's environment, and because JD Edwards has no native webhooks it polls on a schedule rather than relying on a push.