Workday Financial Management and Wise integration

What moves between them

Supplier invoices and approved payments flow from Workday Financial Management into Wise as transfer orders and recipient records on a schedule tied to your payment cycle. Wise executes those transfers and pushes back state changes and payout failures through webhooks, which ml-connector records in the audit trail. Workday approval workflows and GL account mappings determine which invoices become Wise transfers, keeping your AP books in sync with your international payout operations.

How ml-connector handles it

ml-connector stores both credential sets encrypted: Workday's ISU username and either REST OAuth2 refresh token or SOAP WS-Security credentials, and Wise's OAuth2 refresh token or personal API token. On the Workday side, it polls supplier invoices and approved payment records at intervals you specify (minimum 5 minutes) using date-range filters to avoid re-reading the same data, and it maps Workday GL accounts and worktags to Wise transfer amounts and recipient profiles. On the Wise side, it registers a webhook to receive transfer state changes and payout failures, creates recipients for each supplier with valid bank details, and executes the 4-step transfer sequence: quote the transfer amount and currency, create the recipient if new, create the transfer order with Workday payment details as the customerTransactionId, and fund it from the source balance. Quotes expire and must be refreshed if funding is delayed. ml-connector tracks quote expiry and retry on a fresh quote if needed. Every record carries a full audit trail and can be replayed if a Wise call fails mid-sequence.

A real-world example

A mid-sized software company has accounts payable and engineering vendors worldwide. Finance uses Workday Financial Management to manage supplier invoices and approvals across EUR, GBP, and USD currencies. Vendors expect payment in their local currency, so the team once manually entered each approved invoice into Wise, selected the FX quote, and initiated the payout. With Workday and Wise connected, approved invoices flow to Wise automatically; ml-connector quotes the transfer at the FX rate for that day, creates the recipient if new, executes the transfer, and records the transaction in Workday's GL so the accounts are reconciled. The finance team no longer re-keys invoices, and international payouts move on the same rhythm as AP approvals.

What you can do

• •Read supplier invoices and approved payments from Workday Financial Management on a polling schedule you control.
• •Execute transfers in Wise by creating the quote, recipient, transfer order, and funding in the correct sequence.
• •Map Workday GL accounts and worktags to Wise transfer amounts and recipient profiles so payments land in the right place.
• •Authenticate Workday via OAuth2 or WS-Security, Wise via OAuth2 or personal token, and handle token refresh and expiry.
• •Receive transfer state changes and payout failures from Wise webhooks and record every record in an immutable audit trail.

Questions

How does ml-connector handle Workday's polling requirement and lack of webhooks?

ml-connector reads supplier invoices and payments from Workday at intervals you choose (minimum 5 minutes, typically 15 to 60 minutes for transactional entities) using date-range filters to avoid re-reading the same records. This lets you tie the sync to your payment cycle without waiting for a push from Workday, since Workday Financial Management has no native webhooks.

What is the 4-step transfer sequence, and why does Wise require it?

Wise requires: create a quote for the transfer amount and FX rate, create a recipient if new, create the transfer order with those details, and fund the order from a balance. Quotes expire, so ml-connector tracks expiry and refreshes with a new quote if funding is delayed. This sequence ensures the quote rate is locked and the recipient is registered before moving money.

How does ml-connector keep Workday GL in sync with Wise payouts?

ml-connector maps Workday supplier invoices to Wise transfers using the invoice ID as the customerTransactionId, so every payout is traceable in both systems. When Wise webhooks fire for transfer state changes or failures, ml-connector records the outcome in the audit trail, so your AP GL reflects the actual payment state without manual reconciliation.