Workday Financial Management and Dayforce integration

What moves between them

Payroll flows primarily from Dayforce into Workday Financial Management. After each pay run, ml-connector reads Dayforce pay summaries and GL journal data, then posts the corresponding journal entries into Workday's general ledger, allocated to the GL accounts and org units configured in Dayforce. Employee records, org units, and job codes flow the same direction so Workday's headcount and organizational structure reflect Dayforce hires, terminations, and transfers. GL account codes are configured in Dayforce and appear in payroll reports; ml-connector maps these to Workday GL accounts so every payroll journal line lands on the correct account. Workday journal entries are the primary target for write operations; employee and supplier records are updated as reference data to keep the two systems aligned.

How ml-connector handles it

ml-connector stores both credential sets encrypted and refreshes the Dayforce OAuth token before each request cycle, since tokens expire in one hour. On the Workday side, it accepts the Integration System User credentials and decides whether to use SOAP or REST depending on the operation: SOAP for complex writes such as journal submission, REST for lighter reads on GL accounts and suppliers. ml-connector also refreshes the Dayforce client-specific base URL daily to avoid redirect overhead. Because both systems are poll-only (Workday has no native webhooks, and Dayforce's Integration Studio is customer-configured), ml-connector polls on a schedule tied to your payroll calendar: immediately after each pay run to fetch Dayforce GL documents, then posts those into Workday. Employee records are polled less frequently, since they change less often than payroll. For retries and error recovery, every record carries a full audit trail and can be replayed if a downstream Workday journal submission fails. The integration tracks both Workday's ISU session state and Dayforce's token expiry, so neither auth mechanism creates an outage.

A real-world example

A multi-national professional services firm runs Workday Financial Management for global accounting and procurement, and Dayforce for HR and payroll across 12 countries and 3000 employees. Before the integration, the finance team extracted payroll GL postings from Dayforce each pay period and manually re-entered them into Workday's general ledger, a process that spanned two days and created recurring reconciliation gaps when headcount changed. Month-end close required chasing differences between Dayforce's employee count and Workday's labor cost accounts. With Workday Financial Management and Dayforce connected, each payroll run's GL documents flow into Workday automatically within an hour of calculation in Dayforce, posted to the correct GL accounts and cost centers. Employee transfers and terminations sync overnight, so Workday's organizational structure and labor accounts are accurate by the start of month-end close.

What you can do

• •Post Dayforce payroll GL journals into Workday Financial Management's general ledger after each pay run, allocated to the correct GL accounts and cost centers.
• •Keep Workday employee and org unit records synchronized with Dayforce hires, terminations, and transfers.
• •Map Dayforce GL account codes and org units to Workday general ledger dimensions so payroll entries land on valid accounts.
• •Authenticate Workday with SOAP Integration System User credentials and REST OAuth2 refresh tokens, and Dayforce with OAuth 2.0 ROPC with hourly token refresh.
• •Poll on a schedule tied to your payroll calendar, with full audit trails and error replay on every record.

Questions

Which direction does data move between Workday Financial Management and Dayforce?

The primary flow is Dayforce into Workday Financial Management. Payroll GL journals, employees, org units, and job codes move from Dayforce into Workday, while GL account codes and org unit structures are aligned so payroll entries land on valid Workday accounts. Workday is the system of record for general ledger; Dayforce payroll data is read by ml-connector and posted as journal entries, not updated back to Dayforce.

How does ml-connector handle Dayforce's hourly token expiry and Workday's dual SOAP/REST APIs?

Dayforce OAuth tokens expire in 3600 seconds, so ml-connector refreshes the token before each request cycle and never lets it expire mid-operation. On the Workday side, ml-connector uses SOAP for complex writes such as journal submission and REST for lighter reads, choosing the right API surface for each operation. It also refreshes the Dayforce client-specific base URL daily to avoid redirect latency.

What happens if a Workday journal submission fails after Dayforce GL data is read?

Every record carries a full audit trail, including the source Dayforce pay summary data, the mapped GL accounts, and the journal entry status in Workday. If a submission fails, the record is flagged and can be replayed from the audit trail without re-reading Dayforce, so no GL data is lost and the journal can be corrected and resubmitted.