Workday Financial Management and Procurify integration

What moves between them

Supplier and invoice records flow from Workday into Procurify. New suppliers in Workday are synced to Procurify as vendors, with name and payment terms mapped to the target format. Supplier invoices from Workday are read and posted to Procurify as bills, mapped to the matching vendors and account codes. Purchase orders and payments are synchronized in the same direction so Procurify reflects the current state in Workday. The sync runs on a polling schedule aligned to your financial close calendar, and retries automatically if a read or write fails.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Integration System User credentials for Workday SOAP calls, and the OAuth2 client ID and secret for Procurify. On the Workday side it uses SOAP for full CRUD operations on suppliers and invoices, refreshing the OAuth2 bearer token when Workday returns 401. On the Procurify side it uses REST polling with date-range filters to avoid duplicate bills and to work within Procurify's undocumented but strict rate limits. Suppliers are mapped first so every invoice bill lands on a vendor that already exists. Workday's minimum safe polling interval is 5 minutes to avoid tenant-level throttling. ml-connector tracks the last successful sync timestamp for each entity type and retries with exponential backoff if a Workday or Procurify call fails.

A real-world example

A mid-market manufacturing company runs Workday Financial Management for accounts payable and procurement, and uses Procurify for vendor onboarding and expense tracking. Before the integration, the accounts payable team manually entered new suppliers from Workday into Procurify each quarter, and the invoice records in the two systems drifted because changes to vendor payment terms or address were made in only one system. With Workday and Procurify connected, new suppliers sync automatically from Workday to Procurify, and invoices posted to Workday appear in Procurify as bills tied to the correct vendor without re-keying. The AP team no longer has to chase vendor master mismatches, and month-end reconciliation between the two systems is faster.

What you can do

• •Sync Workday suppliers into Procurify as vendors so new vendors are available immediately after they are created in Workday.
• •Post Workday supplier invoices into Procurify as bills, mapped to the matching vendors and account codes.
• •Authenticate Workday with SOAP/WS-Security credentials and OAuth2 tokens, and Procurify with OAuth2 client credentials.
• •Poll both systems on a schedule tied to your financial close calendar, with automatic retry on timeout or rate limit.
• •Maintain a complete audit trail so any record can be inspected or replayed if a downstream update fails.

Questions

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

The main flow is from Workday into Procurify. Suppliers, invoices, purchase orders, and payments move from Workday Financial Management into Procurify, so the vendor master and bill records in Procurify stay aligned with Workday. Procurify is read as the source of truth for requisitions and approved order items, but does not write back to Workday.

How does ml-connector handle Workday's dual SOAP and REST authentication?

ml-connector uses SOAP with WS-Security UsernameToken credentials for full CRUD operations on suppliers and invoices, since SOAP provides broader functionality in Workday Financial Management v46.1. It stores both the Integration System User account credentials and the OAuth2 refresh token encrypted, and refreshes the OAuth2 token when Workday returns 401 to ensure uninterrupted polling.

What polling interval is safe for Workday Financial Management to avoid rate throttling?

Workday recommends 15 to 60 minute intervals for transactional entities like invoices and purchase orders, and daily for suppliers. The minimum safe interval is 5 minutes; shorter polling may trigger tenant-level rate throttling. ml-connector tracks the last successful sync timestamp per entity type and backs off exponentially if Workday returns rate-limit errors.