Workday Financial Management and ServiceNow integration

What moves between them

The primary flow runs from Workday into ServiceNow. Workday suppliers and purchase orders poll into ServiceNow procurement tables on a 1-4 hour schedule. Workday journal entries and GL postings poll into ServiceNow GL staging tables aligned to cost centers and supplier records. Supplier master data is bidirectional: ServiceNow can supply new supplier validation, which ml-connector transforms back into Workday worktags and supplier records. Workday is the system of record for financial journals; ServiceNow staging tables are write-only destinations.

How ml-connector handles it

ml-connector accepts both the Workday ISU credentials (username and WS-Security token) and ServiceNow OAuth2 client credentials, refreshing the OAuth tokens every 25 minutes to stay within the 30-minute expiry window. It polls Workday using date-range filters with 5-minute minimum intervals to avoid tenant-level throttling, transforms suppliers into ServiceNow cmn_supplier and proc_po records, and posts GL entries into sn_apo_invoice and itfm_gl_accounts staging tables. ServiceNow instance subdomains are stored per customer, since every instance is unique and multi-tenant is not supported. ml-connector maps Workday worktags to ServiceNow cost centers to ensure all GL postings land on valid accounts, retries with exponential backoff when either API returns 429 or 500, and logs every record with full audit trail for replay if a downstream call fails. Because Workday has no outbound webhooks and ServiceNow requires custom Business Rules to push events, ml-connector initiates all reads from both systems on a customer-specified schedule.

A real-world example

A large services firm runs Workday Financial Management across three global regions for accounts payable, procurement, and GL management. They also use ServiceNow Source-to-Pay to track purchase orders and invoices within their IT service operations. Before the integration, the AP team manually exported Workday supplier and invoice data to spreadsheets every morning, then imported the data into ServiceNow by hand, creating lag and re-keying errors. With Workday and ServiceNow connected, supplier records sync overnight, invoices post to both systems automatically, and the firm's procurement and finance teams see the same data in ServiceNow without any manual handoff. Month-end close is faster because supplier and invoice records are already reconciled across both platforms.

What you can do

• •Sync Workday suppliers and purchase orders into ServiceNow procurement tables on a regular schedule.
• •Post Workday GL entries and journal postings into ServiceNow GL staging tables, aligned to cost centers.
• •Handle Workday ISU credentials and WS-Security token exchange, and ServiceNow OAuth2 client credentials with automatic 25-minute refresh.
• •Map Workday worktags to ServiceNow cost centers so financial records land on valid accounts.
• •Maintain full audit trail and support replay when either system experiences downtime or connection failures.

Questions

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

The primary flow is Workday into ServiceNow. Suppliers, purchase orders, and GL journal entries poll from Workday and post into ServiceNow procurement and GL staging tables. Supplier master data can flow bidirectionally for validation. ServiceNow GL records are write-only destinations; ml-connector does not post financial entries back into Workday.

How does ml-connector handle Workday's ISU account and WS-Security authentication?

ml-connector stores the ISU username and WS-Security token encrypted and includes them in every SOAP request header as per Workday spec. ServiceNow credentials are stored separately and rotated independently. OAuth2 tokens are refreshed every 25 minutes to avoid the 30-minute expiry.

What happens when Workday has no webhooks and ServiceNow requires custom Business Rules for outbound push?

ml-connector polls both systems on a customer-specified schedule, typically every 1 to 4 hours for purchase orders and suppliers, and more frequently for GL entries if needed. Date-range filters on Workday API calls keep polling intervals safe; the minimum safe interval is 5 minutes to avoid tenant-level rate throttling.