MYOB and BambooHR integration

What moves between them

Employee data flows from BambooHR into MYOB. When an employee is hired, updated, or terminated in BambooHR, ml-connector creates or updates the matching contact record in MYOB, mapped to the employee category. Employment status changes and job info updates flow into the contact as well. The sync runs on a schedule tied to your HR calendar and can also accept BambooHR webhook events where they are enabled. MYOB contact records are the destination; no data flows back to BambooHR.

How ml-connector handles it

ml-connector stores both credential sets encrypted and refreshes the MYOB company file credentials on every API call, since the OAuth token expires in 20 minutes. It polls BambooHR for employee changes on a schedule you set, or receives webhook events where enabled, and creates or updates the matching MYOB contact record in the employee category. Field mappings use explicit enumeration on the BambooHR side (required by the API) and match to MYOB contact fields using the RowVersion field on PATCH requests to prevent stale update conflicts. The MYOB API enforces a rate limit of 8 requests per second, so ml-connector batches and backs off as needed. 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, billing, and GL close, and BambooHR for HR, compensation, and org structure. Before the integration, the accounting team manually entered or copy-pasted new hires and terminations from BambooHR into MYOB each month, creating a lag between HR changes and the accounting system. With MYOB and BambooHR connected, employee changes sync within hours, the accounting team no longer has to re-key names and employment status, and the contact list always reflects actual headcount.

What you can do

• •Sync employee records from BambooHR into MYOB as contact records in the employee category.
• •Keep employment status and job title changes synchronized as contact updates in MYOB.
• •Refresh MYOB company file credentials on every call and handle 20-minute token expiry transparently.
• •Poll BambooHR on a schedule you define or receive webhook events for real-time sync of employee changes.
• •Track full audit trail and replay failed syncs without data loss.

Questions

What employee data moves from BambooHR to MYOB?

Employee name, email, employment status, and job info flow from BambooHR into MYOB contact records. When an employee is hired or terminated in BambooHR, the matching record is created or updated in MYOB so your accounting contact list always reflects current headcount. MYOB does not sync compensation or benefits data; the sync is roster and employment status only.

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

MYOB access tokens expire in 20 minutes. ml-connector refreshes the company file credentials on every API call using the OAuth token and the company file username and password stored encrypted, so token expiry is transparent. The refresh token lasts one week; when it expires, you update the credential set without re-authenticating.

Does the integration support BambooHR webhooks or polling?

Both. ml-connector can poll BambooHR on a schedule you define, or receive webhook events where enabled. Webhook payloads are lightweight and trigger a follow-up GET request to fetch full employee data. Polling via OData filters on LastModified timestamps detects changes since the last sync. Choose the cadence that fits your HR calendar.