MYOB and Workday HCM integration

What moves between them

The main flow runs from Workday into MYOB. After each payroll cycle, ml-connector reads Workday's accounting journals and posts the labor cost entries into MYOB's general ledger, mapped to the matching MYOB GL accounts and cost centers. Employee records and supplier information flow the same direction so MYOB contacts stay aligned with Workday hires, terminations, and role changes. Cost centers and organizations are mapped first so journal lines reference GL accounts that already exist in MYOB.

How ml-connector handles it

ml-connector stores MYOB OAuth credentials and company file token pair encrypted, refreshing both on 20-minute boundaries before they expire, and automatically re-supplies the three required headers (Authorization, x-myobapi-key, x-myobapi-cftoken) on every MYOB call. For Workday it manages the SOAP WS-Security envelope and ISU credentials, or the SOAP version's OAuth token if REST is disabled. It polls both systems on a schedule you define, typically tied to your payroll and GL close calendars. MYOB's $filter syntax on LastModified detects changes since last poll, and Workday's SOAP API is queried for updated workers, suppliers, and post-payroll GL journals. Because both systems are pull-only, the integration listens for manual triggers and schedule-based runs, maps GL accounts and cost centers first to validate that payroll lines land on valid MYOB dimensions, backs off on rate-limit responses (MYOB 429, Workday 429 with Retry-After), and tracks every record in audit so failed posts can be replayed.

A real-world example

A mid-sized Australian professional services firm runs MYOB Business for accounting and AR/AP, and uses Workday HCM for staffing, payroll, and procurement across multiple offices. Before the integration, the finance team received a payroll GL file from Workday each pay period, matched it manually to MYOB cost centers and expense accounts, and posted the labor journals by hand. Month-end reconciliation required chasing differences between employee headcount in Workday and labor costs in MYOB's GL. With MYOB and Workday connected, each payroll cycle's GL journals flow into MYOB automatically, allocation to the office and cost code for each team, and new hires and terminations keep contact lists and headcount aligned. Month-end close now starts with labor accounts already reconciled and the manual re-keying step eliminated.

What you can do

• •Post Workday payroll GL journals into MYOB's general ledger after every pay cycle, allocated to the correct MYOB cost centers and GL accounts.
• •Keep MYOB employee and supplier contacts aligned with Workday workers and procurement data changes.
• •Map Workday organizations and cost centers to MYOB job codes, categories, and GL dimensions so payroll lands on valid accounts.
• •Authenticate MYOB with OAuth2 plus company file credentials, and Workday with SOAP WS-Security or OAuth2 depending on data tier.
• •Poll on a schedule tied to your payroll calendar with LastModified change detection, rate-limit backoff, and full transaction replay on error.

Questions

Which direction does data move between MYOB and Workday HCM?

The main flow is Workday into MYOB. Payroll GL journals and supplier records move from Workday into MYOB, while employee and cost center data are aligned in both directions to keep GL postings valid. Workday's GL journals are read-only, so ml-connector does not write financial entries back into Workday.

How does ml-connector handle MYOB's three-header authentication and token refresh?

ml-connector stores the OAuth token, API key, and company file credentials encrypted, and manages both token lifecycles: 20-minute OAuth expiry with refresh-token-driven refresh, and company file token renewal tied to the refresh cycle. It supplies all three headers automatically on every call and detects token expiry before it can cause an outage.

What happens if Workday and MYOB have different GL account structures or cost center codes?

ml-connector maps cost centers and GL dimensions first, before posting any payroll journals. If a Workday cost center or GL account has no match in MYOB, the record halts with a mapping error in the audit trail, and the integration surfaces it for manual review so no unallocated postings land in MYOB.