MYOB and UKG integration

What moves between them

The main flow runs from UKG into MYOB. After each pay run, ml-connector reads UKG payroll GL export data and posts the journals into MYOB's general ledger, mapped to the matching MYOB GL accounts and cost centers. Employee records flow the same direction so MYOB contacts reflect UKG hires, terminations, and status changes. Cost centers, departments, and pay groups are aligned in both directions so payroll allocations map to valid MYOB dimensions. GL journals are typically read-only in UKG, so ml-connector does not write financial entries back to the payroll system.

How ml-connector handles it

ml-connector stores both credential sets encrypted. For MYOB, it refreshes the OAuth2 bearer token every 15 minutes (before the 20-minute expiry) and supplies the API key and Base64 company file credentials on every request. For UKG, it chooses between HTTP Basic Auth with custom headers or OAuth2 client_credentials based on the customer's UKG tier, and refreshes OAuth tokens after 50 minutes (before the 1-hour expiry). ml-connector polls MYOB using OData $filter on LastModified to fetch changes since the last sync, respecting the 8 request-per-second rate limit by backing off on 429 responses. For UKG, it listens to webhooks where enabled or falls back to polling the /personnel/v1/employees/changed endpoint. Before posting payroll GL to MYOB, it validates that cost centers exist in MYOB as GL dimensions, and retries failed journal posts with exponential backoff. UKG Ready customers are routed to their separate API hostname. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized professional services firm in Australia uses MYOB for accounting and GL management, and UKG for global HR and payroll across three offices. Before the integration, the finance team received a payroll register from UKG each pay cycle and manually entered labor cost allocations into MYOB by cost center, a process that took 4 hours and often introduced discrepancies. With MYOB and UKG connected, each pay run's GL journal flows into MYOB automatically, already allocated to the correct cost centers for each office. Employee changes such as hires, role changes, and terminations in UKG immediately update MYOB contacts, so the org chart stays in sync. Month-end close is faster because labor costs are already posted and cost center allocations are validated before the journals land in the GL.

What you can do

• •Sync UKG employee master records into MYOB contacts, keeping headcount and employee data aligned across systems.
• •Post UKG payroll GL journals into MYOB's general ledger after each pay run, allocated to the correct cost centers and accounts.
• •Map cost centers and departments between UKG and MYOB so payroll allocations land on valid GL dimensions.
• •Handle MYOB's OAuth2 20-minute token refresh and company file authentication, plus UKG's dual auth schemes (Basic Auth or OAuth2) with token caching.
• •Poll MYOB with OData $filter on LastModified and UKG webhooks or delta endpoints, with retries on rate limits and a full audit trail on every record.

Questions

How does ml-connector handle MYOB's company file credentials and OAuth token expiry?

ml-connector stores both the OAuth2 bearer token and the Base64-encoded company file username and password encrypted. It refreshes the OAuth2 token every 15 minutes (before its 20-minute expiry) and includes all three required headers (Authorization, x-myobapi-key, and x-myobapi-cftoken) on every API call. The company file token does not expire, so ml-connector supplies it for the lifetime of the customer integration.

Why does ml-connector poll MYOB instead of using webhooks?

MYOB has no webhook support on the MYOB Business API. ml-connector uses OData $filter on the LastModified timestamp to detect changes since the last sync, respecting MYOB's 8 request-per-second rate limit by backing off when the API returns 429 (Too Many Requests). This approach ensures no changes are missed while staying within rate limits.

How are cost centers and departments kept in sync between MYOB and UKG?

ml-connector syncs cost center reference data in both directions before posting payroll GL. It validates that every cost center in a UKG payroll journal exists as a GL account or dimension in MYOB before the journal is posted. If a cost center is missing, the job is retried until the dimension is created in MYOB, ensuring payroll allocations always land on valid accounts.